CLI Guide

Arguments
Required arguments
[-d|--device]
context-path or
device-name
* Name or context path of the device to which to attach the mirror. Does not have to be a top-level
device. If the device name is used, verify that the name is unique throughout the metro node, including
local devices on other clusters.
Optional arguments
[-m|--mirror]
context-path or
mirror-name
* Name or context path of the mirror to detach. Does not need to be a top-level device. If the name of
a device is used, ensure the device name is not ambiguous, For example, ensure that the same device
name is not used by local devices in different clusters.
[-r|--rule-set]
rule-set
Rule-set to apply to the distributed device that is created when a mirror is added to a local device.
[-f|--force]
When --force is set, do not ask for confirmation when attaching a mirror. Allows this command to
be run using a non-interactive script. If the --force argument is not used, prompts for confirmation
in two circumstances when the mirror is remote and the parent device must be transformed into a
distributed device.
* - argument is positional.
Description
If the parent device is a RAID 0 or RAID C, it is converted to a RAID 1.
If the parent device and mirror device are from different clusters, a distributed device is created.
A storage-volume extent cannot be used as a mirror if the parent device is a distributed-device, or if the parent device is at a
different cluster than the storage-volume extent.
If you do not specify the --rule-set argument, metro node assigns a default rule-set to the distributed device as follows:
● If the parent device has a volume, the distributed device inherits the rule-set of the (exported) parent.
● If the parent device does not have a volume, the cluster that is local to the management server is assumed to be the winner.
Once determined, metro node displays a notice as to which rule-set the created distributed-device has been assigned.
When attaching a remote mirror to a local device, or when attaching a new mirror to a distributed device, both operations
consume slots. Both scenarios result in the same following error message:
VPlexcli:/clusters/cluster-2/storage-elements/extents> device attach-mirror -d
rhyan_dr_test -m rhyan_mig_src_0000
device attach-mirror: Evaluation of <<device attach-mirror -d dr_test -m mig_src_0000>>
failed.
cause: Unable to attach mirror 'mig_src_0000' to device 'dr_test'.
cause: Unable to attach mirror 'mig_src_0000' to distributed Device
'dr_test'.
cause: Firmware command error.
cause: Active metadata device does not have a free slot.
Refer to the troubleshooting section of the metro node procedures in the SolVe Desktop for instructions on increasing the
number of slots.
NOTE:
If the RAID 1 device is added to a consistency group, the consistency group’s detach rule overrides the device’s
detach rule.
Use the rebuild status command to display the rebuild’s progress.
● The rule set that will be applied to the new distributed device potentially allows conflicting detaches.
Homogeneous array requirement for thin volumes
To preserve thinness of the new RAID-1 device where the parent device is created on a thin volume and is thin-capable, the
mirror device must be created from the same storage-array-family as the parent device. If the user tries to attach a mirror leg
Commands
109