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
using FCM 3.2.0
We are an SAP shop which on a frequent basis refreshes PRD to QAS environments. We wanted to use FCM to perform this landscape "refresh" . One of the requirements though is to preserve the "TARGET" environment (unmount FS and rename VG) prior to restoring from PRD source (only restoring virtual disks tied to sapdata mounts) to QAS system. Seems like that process will only work (1) time before getting "FMM0129E vmdk already exist" error.
So the process is: take backup, rename vg, restore, validate, remove disks.
What we typically do on target:
Prepping server for import
1. Unmount filesystems
Umount –a or reboot (have db stopped prior to unmounts)
2. Inactivate vg
vgchange -an qa1log
vgchange -an qa1data
vgchange -an qa2data
vgchange -an qa2log
3. Export vg
vgexport qa1log
vgexport qa1data
vgexport qa2data
vgexport qa2log
4. VG rename
a. vgrename qa1log qa1log_old
b. vgrename qa1data qa1data_old
c. vgrename qa2log qa2log_old
d. vgrename qa2data qa2data_old
Once the Database has been successfully started when then remove the disks from Linux guest as well as from vCenter (delete hard disks)
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
Thank you for submitting this request. We appreciate the suggestion and will provide an updated response after further discussions with our internal product teams.