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 Delivered
Workspace Storage Protect Family
Categories Spectrum Protect for Databases
Created by Guest
Created on Jul 20, 2012

RELATED IDEAS

TDP rebinding of all inactive backups to new management class

When management class changes for TDP backups TDP will rebind all previous backups to the new management class. This is opposite to TSM file level behaviour. Backups that have long retention like 7 years would all be lost by simple management class change. The next TDP backup will rebind all backups, inactive and active and then expire and delete them using normal expiration process.

It should behave the same as file level backups and rebind the active backup only, leave the years of inactive files alone. It is far too easy to wipe out all previous backups.

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
    |     Nov 30, 2012

    Thank you for submitting the request. This is a recognized requirement and a solution appears to be desirable. 
    You could however to use the current product to request for "inactive" data to be bound to a new node with a given description on installation
    so that any new management classes created don't delete older data that is no longer bound to the new retention criteria.

  • Guest
    Reply
    |     Jul 30, 2012

    An alternative suggestion could be to request for 'inactive' data to be bound to a new node with a given description as a 'just in case' option set on installation/configuration so that any new management classes created don't delete older data that is no longer bound to the new retention criteria.

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.