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
Enable/disable WriteSame (16) as system default
Use the set command in /clusters/cluster context to enable or disable WriteSame(16) for the entire cluster.
To enable WriteSame(16) as the cluster system default:
VPlexcli:/clusters/cluster-1> set default-write-same-16-template true
To disable WriteSame(16) as the cluster system default:
VPlexcli:/clusters/cluster-1> set default-write-same-16-template false
Offload copy overhead with XCOPY
To minimize I/O overhead and maximize performance on copy operations, data movement should occur as close to the physical
storage layer as possible, rather than at the server layer (as in host-based data copies).
Utilizing VMWare’s XCOPY feature, metro node manages data allocation and placement using virtual machines, copying data
with minimal performance impact on the host. When XCOPY is enabled, on-disk data copy and move operations occur on the
storage-array, not on the host.
Enabling and disabling XCOPY using CLI
You can enable or disable XCOPY at the cluster or storage view levels.
XCOPY can be enabled and disabled for all storage views. While it is possible to enable or disable XCOPY for individual views, it
is not recommended unless you first consult with Dell EMC Support. The best practice is to always use uniform settings in metro
node for all storage views.
1. To enable XCOPY, set the xcopy-enabled attribute to true. To disable XCOPY, set the xcopy-enabled attribute to
false.
For example, to enable XCOPY for all storage views, enter the following CLI command:
VPlexcli:/> set /clusters/**/storage-views/*::xcopy-enabled true
2. Verify the status of the xcopy-enabled attribute by listing all attributes for all storage-views as follows:
VPlexcli:/> ll /clusters/cluster-1/exports/storage-views/*
Enabling and disabling XCOPY by default
XCOPY is enabled by default in metro node because the xcopy-enabled attribute is set to true, at manufacturing time, in the
cluster context.
To change this behavior, you must alter the default template value of XCOPY.
CAUTION:
Changing the default template value of the XCOPY attribute changes the value of the XCOPY
attribute in all newly created storage views. This should be done only in rare instances, usually after
consultation from Dell EMC Support. Changing the default template value may have an adverse effect on
VMWare host I/O performance.
1. To enable XCOPY by default, set the default-xcopy-template attribute to true as follows:
VPlexcli:/> set /clusters/*::default-xcopy-template true
2. Verify the status of the default-xcopy-template attribute by listing all attributes of the cluster context
as follows:
VPlexcli:/clusters/cluster-1> ls
System Management 21