Adding a new volume to a parent volume group containing a snapshot that a thin-clone volume group was created from should automatically add the volume to the thin-clone VG when that VG is refreshed from a new snapshot taken from the parent VG.

Since the thin-clone VG is tied to the snapshot of the parent, if you add LUNs to the parent and create a new snapshot and then refresh the thin-clone from the new snapshot, it seems logical that you would want the thin-clone VG to also have the new volume. You can do this currently by creating a new thin-clone VG with a different name, selecting a subset of volumes to select the new volume, but then you have to remove that volume from the "temp" thin-clone volume group so it is unassigned, and then you can add it to the thin-clone volume group tied to the original parent volume group. It's an overly complicated process when all you want to do is add more space i.e. another LUN to a volume group and have it cascaded to thin-clone VGs.

Idea priority

Low

Post comment

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.

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use

Adding a new volume to a parent volume group containing a snapshot that a thin-clone volume group was created from should automatically add the volume to the thin-clone VG when that VG is refreshed from a new snapshot taken from the parent VG.

Please enter your email address

RELATED IDEAS

Adding a new volume to a parent volume group containing a snapshot that a thin-clone volume group was created from should automatically add the volume to the thin-clone VG when that VG is refreshed from a new snapshot taken from the parent VG.