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
Spectrum Protect for Virtual Environments: Data Protection for Microsoft Hyper-V suite offers the option to exclude certain disks when restoring a virtual machine. See page 159 of the "IBM Spectrum Protect for Virtual Environments Version 8.1.9 - Data Protection for Microsoft Hyper-V - Installation and User's Guide"
vmname:-vhdx=disk_location
This -vhdx=disk_location option is used to specify the disk location of one or more virtual disks to
exclude from restore operations.
However, it would seem that all disks are *always* recovered no matter what options one specifies.
The difference being that in the case of a disk exclusion, an empty disk is recreated and no data is written to it.
This process can be very time consuming in the case of large disks, since the disk creation does not happen thin (space is not dynamically allocated, but completely pre-allocated during the restore process). And this will prohibit restoring VMs altogether when there are space constraints (again, likely to happen when trying to exclude large disks).
The exclude option vmname:-vhdx=disk_location should simply *not* recreate that disk at all!
Or, if that is not possible, recreate an empty disk with dynamic storage allocation (have it thin provisioned) so no time or space is wasted.
Idea priority | Urgent |
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.
This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.