Administrator Guide
Table Of Contents
- Dell EMC Storage Systems Administrator Guide for PowerStore and Unity XT metro node feature
- CLI Workspace and User Accounts
- Meta Volumes
- System Management
- Thin support in metro node
- Provisioning Storage
- Volume expansion
- Data migration
- About data migrations
- Migrating thin-capable storage
- About rebuilds
- One-time data migrations
- Batch migrations
- Prerequisites
- Creating a batch migration plan
- Checking a batch migration plan
- Modifying a batch migration file
- Starting a batch migration
- Pausing/resuming a batch migration (optional)
- Canceling a batch migration (optional)
- Monitoring a batch migration’s progress
- Viewing a batch migration’s status
- Committing a batch migration
- Cleaning a batch migration
- Removing batch migration records
- Configure the WAN Network
- Consistency Groups
- Performance and Monitoring
- Metro node with active-passive storage arrays
- Index
cause: Operation was halted by the user
VPlexcli:/clusters/cluster-1/storage-elements/extents>
You can attach a mirror to a device already supporting a thin-enabled virtual-volume using the device attach-mirror
command.
To add a thick mirror leg to a thin-enabled virtual-volume, you can continue by:
● Setting the virtual-volume's thin-enabled property to false using the set command. The new virtual-volume is not thin-
enabled, nor thin-capable.
VPlexcli:/clusters/cluster-1/devices> set ../virtual-volumes/myVolume::thin-enabled
false
VPlexcli:/clusters/cluster-1/devices> device attach-mirror --device myDevice --mirror
myMirror
VPlexcli:/clusters/cluster-1/devices>
● Using the --force option with the device attach-mirror command. The new virtual-volume is not thin-enabled, nor
thin-capable.
VPlexcli:/clusters/cluster-1/devices> device attach-mirror --device myDevice --mirror
myMirror
VPlexcli:/clusters/cluster-1/devices>
In a mirrored thin setup, all the legs must come from the same storage-array family. If you try to create thin legs from the arrays
that belong to different storage-array family, the thin personality of the legs are lost and they stop supporting the thin storage
management features. The following is an example for such a scenario:
VPlexcli:/> device attach-mirror --device xio_device --mirror vnx_device
Thin-capability is only supported with homogeneous storage-array types. The top-level
device
'xio_device' is supported by XtremIO but the mirror 'vnx_device' is supported by
CLARiiON.
Since XtremIO and CLARiiON are not homogeneous, the top-level device will lose thin-
capability
after the new mirror is attached. Do you wish to proceed? (Yes/No) No
device attach-mirror: Evaluation of <<device attach-mirror --device xio_device --mirror
vnx_device>>
failed.
cause: Unable to attach mirror 'vnx_device' to device 'xio_device'.
cause: Operation was halted by the user
VPlexcli:/>
About thin migrations
Metro node supports the migration of a thin volume to another storage array.
For a thin volume to support the thin storage management features after a migration, both the source and the target volumes
must be created from the same storage-array family. If they are created from the arrays that belong to different storage-array
family, the thin-enabled attribute is retained as true, the thin-capable attribute is set to false and the UNMAP
command is rejected.
Migrating thin capable storage provides you additional information on the thin storage migrations.
28
Thin support in metro node