Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Apr 11, 2013

Query or report to show nodes/volumes that are not collocated

There is a need to have a query command to show which nodes and/or volumes are not abiding by the collocation settings.
eg
tsm: TEST > q collocvol
Volume collocation_type count state
P02235L5 Group 1 OK
P02222L5 Group 2 ERROR
P02257L5 SPACE 1 OK
P03244L5 NODE 2 ERROR

tsm: TEST > q collocnode
NODE collocation type state
FINANCE Group OK
FILESERVER Filespace ERROR

* Count would be the number of collocation_types on that volume.
* State would signify if the data on the volume/node conflicts with the collocation configuration

These queries could be extended to
* only show volumes/nodes in error
* filter by node name or volume name

Idea priority High
  • Guest
    Reply
    |
    Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

  • Guest
    Reply
    |
    May 29, 2014

    Thank you for submitting this request. This is being targeted for a release in the next year or two. This is not a statement of commitment as intent and plans are subject to change. We will provide an update to the request should plans change or the enhancement is delivered. We sincerely appreciate your commitment to IBM Tivoli Storage Manager and support in moving the product forward.

  • Guest
    Reply
    |
    Apr 17, 2013

    I understand that getting a good backup is the most important, but when
    you offer a feature that is "best efforts" with no way to verify, why
    have the feature?
    eg
    TSM will use "best efforts" to do a backup of a client.
    As you know there are times when for one reason or another a backup
    cannot be done.
    Imagine now, TSM does not give you a way to report if the backup
    succeeded, if it generated an error or when it started the backup?

    That is what happens when it fails to collocate, there is no report, it
    does not generate an error, warning or information message nor does post
    a message to any log that it has had to resort to non collocation.

    Does that make sense?