rmmdiskgrp

The rmmdiskgrp command deletes a managed disk group so that there is no possibility to recover it.

Syntax


>>- svctask -- -- rmmdiskgrp -- --+----------+-- --------------->
                                  '- -force -'      

>--+- mdisk_group_id ---+--------------------------------------><
   '- mdisk_group_name -'

Parameters

-force: (Optional) Specifies that all virtual disks and virtual disk-to-host mappings be deleted.
Attention: Use this parameter with extreme caution. When you use this parameter, all managed disks in the group are removed and the group itself is deleted.
mdisk_group_id | mdisk_group_name: (Required) Specifies the ID or name of the managed disk group that is to be deleted.

Description

The rmmdiskgrp command deletes the specified managed disk group. The -force parameter is required if there are virtual disks that have been created from this group or if there are managed disks in the group. Otherwise, the command fails.

Deleting a managed disk group is essentially the same as deleting a cluster or part of a cluster, because the managed disk group is the central point of control of virtualization. Because virtual disks are created using available extents in the group, mapping between virtual disk extents and managed disk extents is controlled based on the group.

The command deletes all VDisk copies in the specified MDisk group. If the VDisk has no remaining synchronized copies in other MDisk groups, the VDisk is also deleted.

Attention:

This command partially completes asynchronously. All virtual disks, host mappings, and Copy Services relationships are deleted before the command completes. The deletion of the managed disk group then completes asynchronously.
Before you issue the command, ensure that you want to delete all mapping information; data that is contained on virtual disks cannot be recovered after the managed disk group has been deleted.

In detail, if you specify the -force parameter and the virtual disks are still using extents in this group, the following actions are initiated or occur:

The mappings between that disk and any host objects and the associated Copy Services relationships are deleted.
If the virtual disk is a part of a FlashCopy® mapping, the mapping is deleted.
Note: If the mapping is not in the idle_or_copied or stopped states, the mapping is force-stopped and then deleted. Force-stopping the mapping might cause other FlashCopy mappings in the cluster to also be stopped. See the description for the -force parameter in the stopfcmap command for additional information.
Any virtual disk that is in the process of being migrated into or out of the managed disk group is deleted. This frees up any extents that the virtual disk was using in another managed disk group.
Virtual disks are deleted without first flushing the cache. Therefore, the storage controller LUNs that underlie any image mode MDisks might not contain the same data as the image mode VDisk prior to the deletion.
If there are managed disks in the group, all disks are deleted from the group. They are returned to the unmanaged state.
The group is deleted.

Attention: If you use the -force parameter to delete all the managed disk groups in your cluster, you are returned to the processing state where you were after you added nodes to the cluster. All data that is contained on the virtual disks is lost and cannot be recovered.

An invocation example

svctask rmmdiskgrp -force Group3

The resulting output

No feedback