General Page
PowerVS has specific requirements for adding, removing and resizing volumes. This document discusses how to perform these actions using the toolkit command WRKCLDVOL and what to be aware of.
Each volume in PowerVS is comprised of two objects: The Cloud volume which is presented to the user on the GUI, WRKCLDVOL, etc. This is the object which users directly interact with. The second object is the Storage volume. This is the volume as it exists on storage which users do not have direct access to, and is where the actual data resides. Working with replication-enabled volumes requires special care to maintain the proper relationship between Cloud and Storage volumes. If there is ever any doubt as to the operations contact PowerVS Support.
The toolkit uses the term 'Consistency Set' to refer to PowerVS 'Volume Groups'. This may be changed in the future.
Deleting a Cloud volume which is replication-enabled will also delete the associated Storage volume it is replicating to or from, even if it is attached to a VSI.
Ending replication on a Cloud volume will delete the Storage volume it is replicating to or from, even if it is attached to a VSI.
Deleting a VSI can delete Storage volumes attached to it, even if the confirmation box "Delete associated volumes" is unchecked.
The primary documentation for adding, deleting and resizing GRS-enabled volumes is listed here:
This guide augments those instructions with specific details as they relate to IBM i and where the PowerHA Toolkit for IBM i can be used.
Creating and adding GRS-Enabled Volumes to existing configurations
Creating and adding volumes to existing configurations is straight-forward. This assumes that there is also a consistency set.
- Use the PowerVS GUI to create the new volumes in the same tier and pool as volumes already in the consistency set (volume group). Use the 'set affinity to an existing volume' feature to ensure the correct tier and pool to match the consistency set is selected.
- Enable replication on the new volume using WRKCLDVOL opt 12
- Use the PowerVS GUI or Terraform etc. to attach the new primary volumes to the primary VSI.
- On the IBM i, use SST or DST to add the volume to an ASP.
- Wait for the volume replication state to reach "consistent_copying" or "consistent_copied".
Use WRKCLDVOL F11 to view the storage replication state. - Use WRKCLDVOL option 8 to 'onboard' the volume.
After onboarding, the auxiliary volume will be available at the secondary site. - At the primary site, use WRKCLDVOL option 10 'Modify Consistency Set' to add the primary volume to an existing consistency set.
- At the secondary site, use WRKCLDVOL option 10 'Modify Consistency Set' to add the auxiliary volume to an existing consistency set.
- Use the PowerVS GUI or Terraform etc. to attach the auxiliary volume to a VSI at the secondary site.
Deleting Non-replicating (GRS) Volumes:
- On the IBM i, use SST or DST to remove the volume from the configuration.
- Detach the volume from the VSI using the PowerVS GUI or Terraform.
Note: If the volume is the Boot Volume, use WRKCLDVOL option 15 to set another volume to be the Boot Volume.
A VSI must have at least one boot volume. - Use WRKCLDVOL option 4 to delete the volume.
Deleting a Replication-enabled (GRS) Primary Volume:
PowerVS guidelines are here:
- On the primary IBM i, use SST or DST to remove the volume from the configuration.
- Using the PowerVS GUI or Terraform, detach both the primary and auxiliary volumes from their respective VSIs.
Note: If the volume is the Boot Volume, use WRKCLDVOL option 15 to set another volume to be the Boot Volume.
A VSI must have at least one boot volume. - At the primary site, use WRKCLDVOL opt 10 to remove the primary volume from the consistency set.
- At the secondary site, use WRKCLDVOL opt 10 to remove the auxiliary volume from the consistency set.
- At the primary site, use WRKCLDVOL option 12 to end replication on the primary volume.
Ending volume replication will also delete the auxiliary Storage volume, even if it is attached to a VSI.
Despite being deleted from storage, the associated Cloud volume will still be visible in PowerVS. -
Use WRKCLDVOL option 4 to delete the primary volume at the primary site.
The GUI and API's will report the secondary volume as replication-enabled,
and due to that state neither the GUI nor the toolkit will allow it to be deleted.
Within 24 hours the the auxiliary Cloud volume will be marked in error,
at which point the toolkit and GUI should allow the deletion. The Cloud CLI command
can be used to delete the secondary volume prior to it being marked in error.
Deleting Replication-enabled (GRS) Auxiliary Volumes:
Deleting an auxiliary volume will also delete the associated primary volume.
PowerVS information on this topic is here:
Follow the instructions above for deleting replication-enabled primary volumes as the end result is the same.
If the primary volume has already been deleted, wait 24 hours for the auxiliary volume to be marked in error then use WRKCLDVOL opt 4 to delete it.
Resizing Replicating (GRS) Volumes:
WRKCLDVOL does not support resizing volumes, but can be used in the resizing process.
See this page for instructions on how to resize a volume:
If your location requires that the volume be removed from the consistency set / volume group use WRKCLDVOL option 10.
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z000000cxy9AAA","label":"High Availability-\u003EFull System Flash Copy"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
More support for:
IBM i
Component:
High Availability->Full System Flash Copy
Software version:
All Versions
Operating system(s):
IBM i
Document number:
7171877
Modified date:
05 February 2025
UID
ibm17171877
Manage My Notification Subscriptions