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.
See this idea on ideas.ibm.com
It is difficult to word a requested problem fix as an RFE, but that is what I've been asked by support to do, so here is my best effort.
Use of the “Wait” parameter of the BACKUP STGPOOL command is currently the best option to ensure that disk storage pool backups complete before tape storage pool backups. It also allows multiple runs of backups of the same storage pool when, as is often the case, it is necessary to run these processes while client backups are running, to ensure that all backed up data is protected for disaster recovery purposes.
The following 2 statements are paraphrased, but are presented as they were explained to me by support while working on the referenced PMR.
Currently, TSM reserves volumes used in the BACKUP STGPOOL process and does not release them until the process completes, when the “Wait” parameter is used at invocation of BACKUP STGPOOL.
Within the MOVE DRMEDIA process, TSM actually runs a CHECKOUT LIBVOLUME and MOVE DRMEDIA (to update the DRM status of the volume) as separate tasks within the MOVE DRMEDIA processes. The MOVE DRMEDIA task cannot update the volume while a reservation exists.
The problem that can result is that, when a reservation occurs after CHECKOUT LIBVOLUME task runs and is still in place when the MOVE DRMEDIA (for update) task runs, a volume is checked out without being updated in Disaster Recovery Manager (DRM).
I propose that this problem be addressed in the best way possible, which is why I have asked that this be an APAR for problem fix, not just documentation. As such I would leave the exact resolution up to development, but here are some suggestions:
1. Create a reservation that prevents the BACKUP STGPOOL from reserving volumes that are already being processed by the MOVE DRMEDIA process, even if only by the CHECKOUT LIBVOLUME task.
2. At the very least, provide a message that indicates that a volume has been checked out as part of the MOVE DRMEDIA process, but it was not updated in DRM.
Idea priority | Medium |
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.
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
Please get this scheduled as soon as possible. We're dealing with this issue every day now, and though some workarounds are possible, they are not preferable. This is a real problem, not just a nice-to-have enhancement or new feature.
Thanks!
Thank you for submitting the request. This is valid requirement and a solution is desirable, and we plan to provide a solution in 2013.