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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
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
The real issue here seems to be that a solution is needed to be able to have some backups bound to a "WEEKLY" management class and other backups to be bound to a "MONTHLY" management class. This is doable today by using different backup types.
This can be done using both FULL backups and COPY backups and then binding the FULL backups to the "WEEKLY" management class and the COPY backups to the "MONTHLY" management class. The FULL and COPY backups will coexist and will each be managed by different policies.
Commands:
tdpexcc backup DB1 full
tdpexcc backup DB1 copy
VSS Policy Binding (TDPEXC.CFG):
VSSPOLICY * * FULL MCWEEKLY
VSSPOLICY * * COPY MCMONTHLY
If this doesn't solve the requirement, can we have a discussion by phone?
The requirement to do this is due to needing different retention.
Initially using TDP for exchange we had vss policy binding set for a single node name running on a set schedule.
Eg:
Friday week 1 - run full weekly bound to weekly retention
Friday week 2 - run full monthly bound to monthly retention
Friday week 3 - run full weekly bound to weekly retention
What was discovered was that the process of running a full backup using the same nodename triggered the previous data to be rebound.
Eg: When Friday week 2 was run, all full backups prior where rebound to monthly retention.
When Friday week 3 was run, all full backups prior where rebound to weekly retention.
This resulted in unexpected data loss to combat this - all full backup was set to be retained as per our monthly requirements (retain forever) we now need to manually clean the weekly or non retain forever objects.
Happy to detail further if required.
Thank you for this request. We are seeking more clarification that would help us to understand why you are needing to delete your stale backups in this manual process rather than relying on the policies handling the expiration. We understand your requirement to delete several objects but the question is why do you need to do so? Is it to meet different retention needs such as needing to retain objects weekly, monthly or yearly?