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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
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
While we recognize that this is a valid requirement, it has not been a high enough priority considered along with the other work we have been doing. We do not feel that this will become a high enough priority that it will be resolved in the next two years, so we are closing this for now. Thanks for your interest.
what you are saying is that a snapdiff backup is not a valid backup? only a monthly full is?
I think it would be better/safer to:
For "Include/exclude changes", "delete backup" or "policy changes" to force a create new base eg delete the TSM created snapshot.
eg
* TSM snapshot A exists
* incremental snapdiff starts
* TSM detects one of the above conditions
* TSM removes snapshot A
* This forces TSM to create a new base
* TSM creates snapshot B
* Uses snapshot B as the new base.
For "File skipped" or "file excluded for file set" Delete the newer TSM snapshot, rather than the older one so that the problem can be corrected and the files backed up on next run. eg
* TSM snapshot A exists
* incremental snapdiff starts
* TSM snapshot B is created
* TSM attempts to backup differences between A and B
* Has to skip a file
* TSM reports the issue, but deletes the snapshot B
* operators fixes issue
* incremental snapdiff starts
* TSM snapshot C is created
* TSM attempts to backup differences between A and C
* Succeeds
* TSM deletes snapshot A
This will mean there will be no opportunity for data loss.
Thank you for submitting this enhancement request, the logic behind this behavior is explained in the following tech document: https://www-304.ibm.com/support/docview.wss?uid=swg21501576
if you feel that this RFE is still valid please provide some more information about the specific use case , what are you trying to achieve and why?
all other types of backups do this but not snapdiff.