rmvolume

Use the rmvolume command to remove a volume.

Syntax

Read syntax diagramSkip visual syntax diagram  rmvolume   -removehostmappings  -removefcmaps  -discardimage  -cancelbackup   volume_id  volume_name  volume_uid

Parameters

-removehostmappings
(Optional) Allows a volume to be deleted even if host mappings are removed and this volume is deleted.
-removefcmaps
(Optional) Allows a volume to be deleted even if it is a part of a FlashCopy® mapping and regardless of the state of the mappings.
-discardimage
(Optional) Allows a volume to be deleted even if data on an image mode copy cannot be made consistent.
Important: Using this parameter might result in data loss. Use it only under the direction of your product support information, or if you are willing to accept the risk of data loss on the volume.
-cancelbackup
(Optional) Allows a volume to be deleted even if a backup operation is in progress.
Important: Using this parameter might result in data loss. Use it only under the direction of your product support information, or if you are willing to accept the risk of data loss on the volume.
volume_id | volume_name | volume_uid
(Required) Specifies the volume by ID, name, or UID to be removed.

Description

Use the rmvolume command to remove a volume.

Important: Using this command deletes all copies of a volume and it cannot be undone. If the volume is replicated, the recovery copy of the volume will also be removed unless the recovery volume group has independent access enabled.

Safeguarded copy considerations

If a source volume that is being removed is a part of a FlashCopy mapping and has Safeguarded backup copies that depend on it, the following conditions apply:
  • The rmvolume parameter will succeed immediately and the actual deletion is done asynchronously.
  • The volume will go into the deleting state until all FlashCopy mappings dependent on the volume being removed have been cleaned.
  • If the cleaning rate was initially set to 0, it is changed to 50 (2 MiB per sec).
  • The user can change the cleaning rate to quickly delete the volume or to reduce the performance impact of the cleaning operation.
  • To run the rmvolume -removefcmaps command user must have the Security Admin or superuser role.
If the removed volume is a Safeguarded backup and a part of a Safeguarded FlashCopy mapping that is started and valid, then in this case preceding requirements is applicable with the following conditions:
  • To run the rmvolume command user must have the Security Admin or superuser role.
If the removed volume is a Safeguarded source with Safeguarded backups, the following conditions apply:
  • The rmvolume parameter finish immediately and the actual deletion is done asynchronously.
  • The volume will go into delete state until all the FlashCopy mappings dependent on the Safeguarded source become independent of the Safeguarded source or are deleted.
  • Safeguarded backups of this Safeguarded source will be deleted automatically as per their safeguarded_expiration_time. Associated Safeguarded FlashCopy mappings can also be deleted manually by the Security Admin or superuser role.
  • User defined FlashCopy mappings of the Safeguarded source should be deleted manually by the user.
  • If the FlashCopy mapping becomes independent of the Safeguarded source due to the completion of a background copy or cleaning, the FlashCopy mapping will be deleted by the system.
  • To run the rmvolume -removefcmaps command user must have the Security Admin or superuser role.
Note: This includes a Safeguarded source with no Safeguarded backups. A volume in a Safeguarded backup location that does not have a Safeguarded FlashCopy mapping started with it as a target or the mapping is no longer valid. This can be determined by the value of safeguarded_expiration_time of the volume not being a valid value that is either blank or 000000000000 UTC.
Note: This command is available during the upgrade process.

An invocation example to remove a volume

rmvolume 0

The detailed resulting output:

No feedback