Help
Table Of Contents
- Dell EMC Storage Systems Online Help for the metro node appliance
- Contents
- Figures
- Welcome
- Using the GUI
- Configuring GUI default settings
- Using storage hierarchy maps
- Viewing system status
- Monitoring the system
- Performance
- The Performance Monitoring dashboard
- Viewing a chart
- Modifying a dashboard layout
- Creating a custom dashboard
- Removing a chart
- Moving a chart
- Back-end Bandwidth Chart
- Back-end Throughput chart
- Back-end Errors chart
- Back-end Latency chart
- CPU utilization chart
- Heap Usage chart
- Front-end Queue Depth chart
- Front-end Bandwidth chart
- Front-end Latency chart
- Front-end Throughput chart
- Front-end Aborts chart
- Write Latency Delta chart
- WAN Port Performance chart
- WAN Latency chart
- Rebuild Status dashboard
- Virtual Volumes dashboard
- Front End Ports dashboard
- System Health
- Performance
- Provisioning storage
- Guide
- Provisioning from storage volumes
- Provision Job properties
- Distributed storage
- Storage arrays
- Storage volumes
- Devices
- About devices
- Using the Devices view
- The Create Devices wizard
- The Add Local/Remote Mirror wizards
- Viewing the status of IO to a device
- Creating a device
- Renaming a device
- Deleting a device
- Mirroring a device
- Device status
- Device component properties
- Device properties
- Distributed device properties
- Add capacity to virtual volumes
- Extent properties
- Extents
- Distributed devices
- About distributed devices
- The Distributed Devices view
- The Create Distributed Device from Claimed Storage Volumes wizard
- Distributed device rule sets
- Changing the rule set for a distributed device
- Creating a distributed device
- Deleting a distributed device
- Renaming a distributed device
- Distributed Device status
- Virtual volumes
- About virtual volumes
- The Virtual Volumes view
- The Distributed Virtual Volumes view
- Creating a virtual volume
- About virtual volume expansion
- Expanding a virtual volume using storage volumes
- Enabling or disabling remote access for a volume
- Manually assigning LUN numbers to volumes
- Deleting a volume
- Renaming a volume
- Tearing down a volume
- Virtual Volume status
- Pool properties
- Virtual volume properties
- Show ITLs dialog box
- Logical unit properties
- ALUA Support field values
- Visibility field values
- Extent or Device mobility job properties
- Metro node port properties
- Storage array properties
- Storage view properties
- Storage volume properties
- Create Virtual Volumes dialog box
- Consistency group
- About consistency groups
- Using the Consistency Groups view
- Distributed Consistency Groups view
- Create Consistency Group wizard
- Types of consistency groups
- Creating a consistency group
- Adding a volume to a consistency group
- Removing a volume from a consistency group
- Deleting a consistency group
- Consistency Group status
- Consistency group properties
- Step 1: Select or create a consistency group for the virtual volume
- Step 1: Create a consistency group
- Step 2: Select volume options
- Step 3: Select a storage pool
- Step 3: Select a pool for each mirror on the second cluster
- Step 3: Select a pool for each mirror in the cluster
- Step3: Create thin virtual volumes
- Select a storage view for the virtual volume(s) (optional)
- Step 5: Review your selections
- Step 6: View results
- Step 2: Select volume options
- Step 2: Select volume options
- Step 3: Select a storage volume to create the virtual volume
- Step 3: Select a source and target storage volume
- Step 3: Create thin volumes
- Step 3: Select a target storage volume on the remote cluster
- Step 3: Select target storage on the remote cluster
- Step 6: View results
- Show Logical Units
- Exporting storage
- Initiators and metro node ports
- Storage views
- About storage views
- Using the Storage Views screen
- The Create Storage View wizard
- Creating a storage view
- Deleting a storage view
- Renaming a storage view
- Adding or removing initiators from a storage view
- Adding virtual volumes to a storage view
- Removing virtual volumes from a storage view
- Adding or removing metro node ports from a storage view
- Storage view status
- Storage group properties
- Director properties
- Cluster properties
- Moving data
- Mobility
- Move Data Within Cluster
- Move Data Across Clusters
- Create Mobility Job wizards
- Mobility job transfer size
- Creating a mobility job
- Viewing job details
- Committing a job
- Canceling a job
- Pausing a job
- Resuming a job
- Removing the record of a job
- Changing a job transfer size
- Searching for a job
- Mobility job status
- Notifications
Virtual volume names
If a virtual volume was created on the device, the virtual volume is given the device name, followed by _vol. For example, if the
device name is "Mydevice1", the virtual volume created on the device will be named Mydevice1_vol. You can rename the device
or virtual volume at any time in the properties dialog box.
Device names
To avoid entering a different name for each device you are creating, you can enter a base name to be used for all the devices.
Each device is given this name followed by an underscore and an incremented number. For example:
● base name_1
● base name_2
You can also change the name of individual devices if desired.
The Add Local/Remote Mirror wizards
You can mirror a device locally or remotely using the Add Local Mirror wizard or the Add Remote Mirror wizard. When you add
a local mirror, a device in the local cluster is used to create a RAID-1 device. If the local device you are mirroring is already a
RAID-1, the mirror is added as another leg.
For a remote mirror, a device in the remote cluster is used to create a distributed device. You can mirror a device with or
without a volume on top. When creating a remote mirror, the mirror must not be in a consistency group.
NOTE: For a mirror virtual volume to be thin-enabled, the supporting devices must be thin-capable.
Synchronizing data
For a remote mirror, you can indicate whether or not to perform an initial data synchronization between the devices if the
device does not have a virtual volume. Note that this is an initial synchronization. If you choose not to perform an initial
synchronization, future writes are still be mirrored. If the device has a virtual volume, the data is automatically synchronized.
If the device contains data you want to preserve, you should synchronize. Note that any data on the target device will be
overwritten.
Selecting a consistency group or detach rule for distributed devices
Because a distributed device is created when you mirror a device remotely, you must select a consistency group or a detach rule
for the distributed device. If you add the distributed device to a consistency group, the rule set used for the group will be used
for the distributed device.
You have the option of adding the volumes to a consistency group or selecting a rule set for the distributed devices. If you do
not add the distributed device to a consistency group, you must select from the predefined detach rules, or you can use the
CLI to create a detach rule which will automatically appear in the Rule Set drop-down selection box. For more information on
creating and managing detach rules, refer to the CLI Guide for metro node.
NOTE: You can only apply user-created rule sets to distributed devices that are not in a consistency group.
Selecting target devices to use as mirrors
When creating a mirror, you can select target devices automatically or manually. If you click AUTO-GENERATE MIRROR
MAPPINGS in either wizard, metro node selects a target device of the same size. If no devices are available, the appropriate
message displays. While you can manually select a target device of larger capacity, this is not recommended because you cannot
use the extra capacity. You can also save mirror mappings to a file on your system.
70
Provisioning storage