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.

Add a new idea Subscribe
Status Not under consideration
Workspace Storage Protect Family
Categories Spectrum Protect (Server)
Created by Guest
Created on Sep 18, 2013

RELATED IDEAS

Enhance logging of replication failures

We are using node replication between two TSM 6.3.2.0 servers, and were experiencing some replication failures, which was due to operator error. The issue was that one policy domain on the source server did not exist on the target server, so the replicate node command was failing with a FAILURE status, and no further details. The node replication was being performed with a node group, when the command failed, all that was logged by TSM was that replication and completed with a state of failure, there was no information to state which node had failed, nor why.

I would like to request for an enhancement to the error logging of failed replicate node commands. So for example, when replicating a node group, I would be useful if it would log the status of each node (at the very least which node(s) caused the replication to fail). And when a replication fails, it would be useful if there was some indication of why, e.g. "policy domain does not exist on target server", "policy set does not exist on target server", etc.

Idea priority Low
  • 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
    |     Apr 24, 2014

    Thank you for submitting this request. This is consistent with our current product direction and is being targeted for a release. 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. Thank you for your commitment to TSM and for your support in moving the product forward.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.