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
In case of Flashcopy Manager for Unix/Linux and the application SAP with Oracle DB: if the database must be restored/recovered, then the BRTools must be used.
If the BRtools are being started for brrestore/brrecover, then the FlashCopy Manager does the following:
foreach filesystem {
unmount filesystem
rmfs filesystem
}
This can lead to an error during brrestore if there is a handle on a mounted filesystem. In the worst case: if several sapdata filesystems are mounted and for only one or more of all filesystems the unmount fails, then brrestore will stop and finally some sapdatas remained, some sapdatas were deleted.
Unfortunately, then the brrestore tools cannont be restarted, because they require (due to internal check) ALL sapdata filesystems mounted. This only can be fixed if the volumes which the FCM removed before are created again manually. This is a very time consuming process in order to be able to retry the brrestore.
An advice for improvement would be this:
foreach filesystem {
unmount filesystem
}
if (all filesystems unmounted)
foreach filesystem {
rmfs filesystem
}
Idea priority | High |
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 FlashCopy Manager
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - Tivoli Storage FlashCopy Manager
This enhancement has been made available in FlashCopy Manager 3.2 and higher versions. FlashCopy Manager for Unix/Linux 4.1 is the latest version available to date.
A check to see if the filesystem is in use, before attempting the restore, is absolutely necessary for my customer to adopt FCM. See PMR 41461,122,000 or Edmund Chun who told us: "According to FCM Development, the fuser check was used in previous iterations of the product, but when we moved on with the DB2 integration, DB2 strongly advised against running fuser so FCM development removed it. However, customers have been clamoring to add it back in." This RFE is supposedly the result of that clamoring, and so I add my vote here.