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 Jun 1, 2015

TSM Node replication should report warning instead of failure when associated node cannot be replicated

TSM 7.1.x reports a replication failure when a client node that has been setup for replication has an associated node which is not setup for replication or is a Receive Node. Replication succeeds, but process result is FAILURE, which is not the case. TSM should report a warning instead of a failure as on many occasions this setup is intentional.

Idea priority Medium
  • Guest
    Reply
    |
    Dec 23, 2019

    Voting this up due to a case we opened for this exact issue (TS003148130).

    This functionality should also be rolled into Spectrum Protect 8.1.x.

    Often we restore to test/development systems using proxy node configuration on nodes that are configured for replication. This causes a replication failure of proxy node is not revoked before replication happens.

  • Guest
    Reply
    |
    Oct 30, 2017

    In our case, we do daily restore tests and generate a couple of hundred restore nodes that has temporary Grant Proxy Auth and if we got nodes that of any reason get leftover we got our Replication failed or if we start the replication after our restore test window starts.

    An idea is to have a exclude option in the replication node command to exclude either "Proxy Nodes" or exclude a domain, that should fit us because all our Temporary Restore nodes is in a RestoreTest Domain.

  • 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