VNX

EMC VNX Series
Version 8.1
Using VDM MetroSync with VDM MetroSync

Manager for Disaster Recovery
P/N 302-002-248 REV. 02
Copyright 2015-2016 EMC Corporation. All rights reserved. Published in the USA.
Published February, 2016
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other
countries. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com
EMC VNX Series 8.1 Using VDM MetroSync with VDM MetroSync Manager for Disaster Recovery
CONTENTS
Preface
Chapter 1
Introduction
About VDM MetroSync...................................................................................10

System requirements.................................................................................... 10
Restrictions and limitations...........................................................................11
User interface choices................................................................................... 14
Related information.......................................................................................14
Chapter 2
Concepts
15
VDM synchronous replication logical entities................................................ 16

Sync-replicable NAS pool................................................................. 16
Standby pool on a destination VNX2 system.................................... 16
Sync-replicable VDM........................................................................ 16
Use cases......................................................................................................17
Chapter 3
Setting up prerequisites
19
VDM synchronous replication setup information........................................... 20

IP aliasing for VNX with two Control Stations................................................. 20
Create an IP alias............................................................................. 21
Configure CS-to-CS communication between VNX systems............................ 21
Add systems to the same Unisphere domain................................................. 23
Create RAID groups for WIL and CPL LUNs...................................................... 23
Enable the VDM synchronous replication service...........................................24
Create a block storage pool on source and destination VNX2 systems........... 26
Chapter 4
Configuring
27
Create data LUNs for NAS resources.............................................................. 28

Create NAS user-defined pools...................................................................... 28
Create a sync-replicable VDM........................................................................ 29
Create a file system on a sync-replicable NAS pool........................................ 30
Create the first file system checkpoint on a sync-replicable NAS pool............ 31
Create a network interface for a sync-replicable VDM.....................................32
Create CIFS shares and NFS exports for each file system on your VDM........... 33
Migrate Data Mover configurations and cabinet level service.........................34
Create a VDM synchronous replication session..............................................34
Configure CIFS CA support............................................................................. 36
Configure for NFS I/O transparency in VDM synchronous replication session
..................................................................................................................... 38
Chapter 5
Managing by using the VNX for File CLI
41
About using the VNX for File CLI for managing................................................42

List information for VDM synchronous replication service.............................. 42
Show information for a sync-replicable VDM..................................................42
Reverse a synchronous replication session................................................... 43
CONTENTS
Failover a synchronous replication session....................................................45

Clean synchronous replication session..........................................................47
Delete a synchronous replication session......................................................49
Start a VDM synchronous replication session................................................ 49
Show information for VDM synchronous replication service...........................50
Disable the VDM synchronous replication service..........................................50
Modify a VDM from sync-replicable to non-sync-replicable............................ 52
Modify a VDM from non-sync-replicable to sync-replicable............................ 53
Delete a sync-replicable VDM........................................................................ 54
List information for VDM synchronous replication session............................. 54
Show information for VDM synchronous replication session..........................55
Extend a sync-replicable NAS pool................................................................ 56
Extend a sync-replicable NAS pool (without synchronous replication
session) .......................................................................................... 56
Extend a sync-replicable NAS pool (with synchronous replication
session) .......................................................................................... 56
Shrink a sync-replicable NAS pool................................................................. 58
Shrink a sync-replicable NAS pool (without synchronous replication
session)........................................................................................... 58
Shrink a sync-replicable NAS pool (with synchronous replication
session)........................................................................................... 59
Configuring for added secondary Control Stations......................................... 59
Updating VNX OE software.............................................................................60
Chapter 6
Working with ReplicatorV2 sessions
61
About Replicator V2 sessions........................................................................ 62

Enable Preserve RepV2 session for VDM MetroSync...................................... 62
Create a ReplicatorV2 session on a sync-replicable VDM............................... 62
Show Preserve RepV2 session for VDM MetroSync status.............................. 63
Disable Preserve RepV2 session for VDM MetroSync..................................... 63
Restore ReplicatorV2 sessions...................................................................... 64
Chapter 7
Using VDM MetroSync Manager
65
The VDM MetroSync Manager configuration wizard....................................... 66

Configure a synchronous replication session's failover policy........................66
Configure a synchronous replication session's failover priority......................68
Select VDM IP addresses to monitor.............................................................. 68
Start the VDM MetroSync service...................................................................68
Stop the VDM MetroSync service................................................................... 69
Manually failover a synchronous replication session..................................... 69
Manually reverse a synchronous replication session..................................... 70
Manually restore a synchronous replication session......................................70
Collect logs................................................................................................... 70
Discover monitored objects...........................................................................71
Check status................................................................................................. 71
Show synchronous replication status............................................................ 71
Chapter 8
Service checklists
73
Enable VDM synchronous replication service checklist.................................. 74

VDM synchronous replication session checklist............................................ 74
Chapter 9
4
Troubleshooting
77
CONTENTS
EMC E-Lab Interoperability Navigator.............................................................78

Retrieve information from log files................................................................. 78
NAS database mirrors are out of sync............................................................ 78
How to recover when all Data Movers are panicking...................................... 79
Error messages..............................................................................................80
EMC Training and Professional Services........................................................ 80
Appendix A
Changing FSID ranges
81
Update the FSID range minimum size............................................................ 82
CONTENTS
Preface
As part of an effort to improve and enhance the performance and capabilities of its
product lines, EMC periodically releases revisions of its hardware and software.
Therefore, some functions described in this document may not be supported by all
versions of the software or hardware currently in use. For the most up-to-date information
on product features, refer to your product release notes.
If a product does not function properly or does not function as described in this
document, please contact your EMC representative.
Special notice conventions used in this document
EMC uses the following conventions for special notices:
DANGER
Indicates a hazardous situation which, if not avoided, will result in death or serious
injury.
WARNING
Indicates a hazardous situation which, if not avoided, could result in death or serious
injury.
CAUTION
Indicates a hazardous situation which, if not avoided, could result in minor or moderate
injury.
NOTICE
Addresses practices not related to personal injury.

Note
Presents information that is important, but not hazard-related.

Where to get help
EMC support, product, and licensing information can be obtained as follows:
Product informationFor documentation, release notes, software updates, or for
information about EMC products, licensing, and service, go to EMC Online Support
(registration required) at http://Support.EMC.com.
TroubleshootingGo to EMC Online Support at http://Support.EMC.com. After logging
in, locate the applicable Support by Product page.
Technical supportFor technical support and service requests, go to EMC Customer
Service on EMC Online Support at http://Support.EMC.com. After logging in, locate
the applicable Support by Product page, and choose either Live Chat or Create a
service request. To open a service request through EMC Online Support, you must
have a valid support agreement. Contact your EMC sales representative for details
about obtaining a valid support agreement or with questions about your account.
Preface
Note
Do not request a specific support representative unless one has already been assigned to
your particular system problem.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications.
Please send your opinion of this document to:
techpubcomments@EMC.com
CHAPTER 1
Introduction
Topics include:
l
l
l
l
l
About VDM MetroSync...........................................................................................10

System requirements............................................................................................ 10
Restrictions and limitations...................................................................................11
User interface choices........................................................................................... 14
Related information...............................................................................................14
Introduction
Introduction
About VDM MetroSync

The VDM MetroSync feature provides the ability to use the VNX for File CLI to failover or
move a virtual Data Mover (VDM) from a source VNX2 system to a destination VNX2
system. The failover or move leverages block-level MirrorView/Synchronous
(MirrorView/S) replication, so the failover or move involves zero data loss in the event of
the failover/move being unplanned. This feature consolidates VDMs, file systems, file
system checkpoint schedules, CIFS servers, networking, and VDM configurations into
their own separate NAS pools. This feature works for a true disaster recovery (DR) where
the source is unavailable. For DR support in the event of an unplanned failover, an option
is provided to recover and clean up the source system to make it ready as a future
destination.
This document is intended for those who are responsible for configuring VNX for File for
DR using VDM MetroSync.
This document also describes the EMC VDM MetroSync Manager software. Along with the
same manual operations that you can perform by using CLI commands, the VDM
MetroSync Manager software allows you to:
l
Automatically monitor configured sync-replicated VDMs.
Trigger automatic failover of a selected sync-replicated VDM on a source VNX2 system

to a destination VNX2 system, based on Data Mover, File System, IP network, or
Primary LUN unavailability that would cause the NAS client to lose access to data.
For best practices and performance information related to the VDM MetroSync feature,
refer to this feature's related white paper.
System requirements
The VDM MetroSync feature requires the following software, hardware, network, and
storage configurations:
For software:
l
The source and destination VNX2 systems must use the same VNX operating
environment (OE) for file version 8.1.8.130 or later.
The MirrorView/S and SnapView Clone enablers must be installed on each array.
All file systems must use Split Log (default).
Checkpoints (SavVol) must be on the same pool as the production file system (PFS).
For hardware:
l
Two VNX2 systems
For network:
10
At a minimum, an IP network with LAN or WAN links for communication between the
source VNX2 system's Control Station and the destination VNX2 system's Control
Station.
An ICMP ping request must be allowed between 2 arrays' management IPs (Control
Station, SPA, and SPB).
To create a MirrorView link between systems, use one of the following:

n
FC Direct-connect cables between SPA-to-SPA, and SPB-to-SPB
FC switch-attached, requiring FC zone source and target SPAs; and a separate

Zone between source and target SPBs
Introduction
iSCSI protocol to configure an IP connection between SPs on source and target

systems
For VDM MetroSync Manager:

l
For VMs on a VDM MetroSync Manager server, a minimum of 2 cores with 2 GB

memory each
2 GB for log files
Restrictions and limitations

The following restrictions and limitations apply for synchronous replication:
l
Only one sync-replicable VDM is allowed on one sync-replicable NAS pool (there is a
1:1 mapping between the sync-replicable VDM and its sync-replicable NAS pool).
You can create only one synchronous replication session on one sync-replicable
VDM.
To get the same expected performance, you should use the same disk types between
each of the VNX2 systems.
Do not use the VNX File Migration feature to migrate VDMs or file systems that are
configured for use with VDM synchronous replication. Otherwise, errors will occur.
Stop the VDM MetroSync Manager service:

n
If you are manually activating a standby Data Mover by using the server_standby
command.
Before upgrading SPs, including non-disruptive upgrades.
Before upgrading the VNX for File OE software, make sure that the VDM MetroSync
Manager service is stopped, and that no VDM MetroSync replication session
operations are in process. During the upgrade process, you must not execute any
VDM MetroSync replication session operations.
You should not perform operations, (such as fracture, promote, delete, and so on) on
any MirrorView Consistency Groups and mirrors that have a prefix name of
"syncrep_", or any MirrorView mirrors and Clone Groups that have a prefix name of
"nasdb_" from the Block side directly. The "syncrep_" and "nasdb_" prefix names are
used by synchronous replication sessions, and the synchronous replication service,
respectively. Otherwise, the synchronous replication session or service will not work
properly.
During failover, if a Consistency Group beneath a synchronous replication session is

not in a "synchronized" state (for example, the source site is powered down), the
following warning prompt is generated: "WARNING: The MirrorView/S consistency
group is not in a proper state for failover activation. If you continue while the
consistency group is in this state and force the failover, a full synchronization of the
source from the destination will automatically occur during the restore to reconstruct
the group and mirrors, which is time-consuming. Are you sure you want to proceed?"
If you proceed, a MirrorView-specific "force promote" operation is triggered. After
that, due to a MirrorView-specific limitation, when the original source is back online,
a full synchronization (initial copy) is needed to re-establish the protection of the
synchronous replication session on the reverse direction.
When you reverse or failover a synchronous replication session, schedules which are
in a "complete" state will not be imported on the standby system.
After failover, if the original active Data Mover for the VDM synchronous replication
session still works, it may run into a rolling panic because the underlying LUNs
become read-only. You need to clean the synchronous replication session to set it
11
Introduction
back to a healthy state. If all of the Data Movers in the system run into a rolling panic,
you need to follow the PXE reboot process on page 79 to fix the NAS service before
a synchronous replication session can be cleaned.
12
VDM MetroSync is not supported on systems where Cabinet-level File DR solutions

are in use.
If you are using the Preserve RepV2 session for VDM MetroSync feature, VDM
MetroSync supports the use of IP Replication on VDM synchronous replication VDMs
and file systems.
Each VDM synchronous replication session is built upon a single VDM and single
user-defined storage pool.
For each system, the local and remote SPs should not exceed either the maximum
number of Consistency Groups allowed (including the maximum number of members
allowed for each group in a system) or the maximum number of mirrors allowed for
each Consistency Group.
For each system, the local and remote Data Movers and pools should consist of disk
volumes that do not exceed the maximum number of mirrors allowed for each
Consistency Group.
Shrinking a sync-replicable NAS pool is not allowed if there is an active VDM

synchronous replication session. You must delete the session, shrink the pool, and
then recreate the session.
NDMP backup on file systems on a sync-replicable NAS pool is supported; however,

the backup may be stopped when reverse or failover occurs. After a reverse or
failover, the full mount paths of the file systems will be changed. To make NDMP
backup work again, the NDMP configuration on backup software needs to be changed
accordingly.
A sync-replicable VDM cannot be migrated using nas_migrate. A workaround for this

is to modify the VDM from sync-replicable to non-sync-replicable and then migrate
the VDM.
Common Log file systems are not supported. Only a split-log VDM or file system
contained in a synchronous replication session is supported. To transfer a commonlog file system to a split-log file system, use host-based copy.
Only uxfs and rawfs file systems that are created on a sync-replicable NAS pool are
supported.
Temporarily unmounted file systems and checkpoints will become mounted after a
reverse or failover operation.
Temporarily unloaded VDMs will become loaded after a reverse or failover operation.
For a VDM on a sync-replicable NAS pool, you cannot mount file systems or
checkpoints to another Data Mover or VDM.
When creating VDM synchronous replication sessions, you must define separate FSID
ranges for the source and target systems.
If the top of the FSID range is reached, after more VDMs/file systems/checkpoints are
created, an FSID conflict may occur during reverse or failover. To avoid an FSID
conflict, the FSID range is enforced to no less than <fsidrange> (default is 8192)
defined in nas_param. The FSID range on source and destination VNX2 systems must
not overlap. nas_checkup will identify any potential FSID conflict for all active
VDMs under synchronous replication sessions on the system.
If the synchronous replication service or session status is not in_sync when the
disaster occurs, the system cannot guarantee the success of failover on the
synchronous replication session.
Introduction
A period of data unavailability (DU) time will occur during a synchronous replication
session reverse or failover operation. The actual DU time depends on how many file
systems or checkpoints exist on the sync-replicable NAS pool.
After a disaster occurs, DU will start. When a synchronous replication session failover
is executed, the DU will continue until the failover operation succeeds.
After failover, if the original active Data Mover for the VDM synchronous replication
session still works, it may run into a rolling panic because the underlying LUNs
become read-only. You need to clean the synchronous replication session to return it
to a healthy state.
The Home Directory feature does not support Continuous Availability (CA) capability.
Keep this in mind if you configure CIFS CA support for VDM synchronous replication.
Manual migration
The replication of Data Mover configurations or Cabinet level service is not included in
VDM synchronous replication. The following Data Mover configuration and Cabinet level
service items must be manually migrated using the migrate_system_conf command
before the creation of synchronous replication, before failover or reverse operations, and
any time this data changes:
Note
The routing table, including the default route, does not get migrated with this command.
The routes must be configured manually. To add a default gateway or a route entry, a
network interface with a status of UP must exist.
l
Data Mover configurations:

n
DNS
NIS
NTP
Local password and group
Usermapper client
FTP/SFTP
LDAP
HTTP
CEPP
CAVA
Server parameters
Netgroup
Nsswitch
Hosts
ntxmap
Cabinet level service:

n
Usermapper service
13
Introduction
User interface choices

This document describes how to configure MirrorView/S and integrate it with VNX2
systems by using the VNX for File command line interface (CLI) and the VDM MetroSync
Manager software.
You can use the Unisphere software to view the storage pools and disk types used in the
MirrorView/S configuration. You also can use Unisphere to manage storage objects, such
as file systems that reside on the source MirrorView/S-protected VDM.
Related information
Specific information related to the features and functionality described in this document
are included in:
l
EMC VNX Command Line Interface Reference for File
Online VNX man pages
Using MirrorView/Synchronous with VNX for File for Disaster Recovery
Configuring and Managing CIFS on VNX
Configuring NFS on VNX
Managing Volumes and File Systems for VNX Manually
Using VNX SnapSure
Configuring Virtual Data Movers on VNX
Parameters Guide for VNX for File
Virtual Data Movers on EMC VNX (white paper)
EMC VNX Replication Technologies (white paper)
VDM MetroSync for VNX2 - A Detailed Review (white paper)
The complete set of EMC VNX2 customer publications is available on the EMC Online
Support website at http://Support.EMC.com. After logging in to the website, click the
Support by Product page, to locate information for the specific product or feature
required.
14
CHAPTER 2
Concepts
Topics include:
l
l
VDM synchronous replication logical entities........................................................ 16

Use cases..............................................................................................................17
Concepts
15
Concepts
VDM synchronous replication logical entities

In order to enforce the restrictions and limitations that apply to synchronous replication
(see Restrictions and limitations on page 11), the following entities are specific to a VDM
synchronous replication environment:
l
Sync-replicable NAS pool
Standby pool (destination site)
Sync-replicable VDM
Sync-replicable NAS pool

A sync-replicable NAS pool must meet the following criteria:
l
It is a user-defined pool.
Its members must be disk volumes.
It has one and only one sync-replicable VDM rootfs on it.
It has no MGFS on it.
All file systems and checkpoints on it are either un-mounted or mounted on its syncreplicable VDM.
All file systems on it must be split-log file systems.
Production File Systems (PFSs) and checkpoints (SavVol) on it must be on the same
storage pool. They must not use space on a different storage pool.
No ID of a file system and checkpoint on it conflicts between the source and

destination systems.
Standby pool on a destination VNX2 system

The destination of any VDM synchronous replication configuration must have a standby
pool that meets the following criteria:
l
Have user-defined File storage pools for each VDM synchronous replication session
that is to be created. Only a single user-defined pool can be allocated per VDM
All volumes within the user-defined pools must be disk volumes (dvols).
The disk volumes in the membership must match in number and size with those in
the sync-replicable NAS pool on the active system under the synchronous replication
session.
It must not be in use.
Sync-replicable VDM
A sync-replicable VDM must meet the following criteria:
16
It is the only VDM within the sync-replicable NAS pool. This feature restricts one VDM
per pool by design.
It is created with a special flag (-syncreplicable ) on one non-sync-replicable NAS

pool. After the sync-replicable VDM is created, the pool becomes a sync-replicable
NAS pool and keeps this status throughout the whole life-cycle of the VDM. This also
happens if the VDM is modified to enable the -syncreplicable flag.
Concepts
All file systems (including the VDM rootfs) mounted on it must be split-log file
systems.
All file systems (including the VDM rootfs) and checkpoints mounted on it must be
created on its sync-replicable NAS pool.
Use cases
VDM MetroSync can be used in the following use cases:
l
Disaster recovery (DR) at the VDM level:

n
Human error
Power outages
Environmental (for example, a flood or storm)
Maintenance
Load balancing
More efficient use of hardware (a VDM-level DR solution does not require standby
Data Mover hardware like a Cabinet-level DR solution does)
Use cases
17
Concepts
18
CHAPTER 3
This chapter contains information about setting up your environment for VDM
synchronous replication for disaster recovery (DR) between two VNX2 systems using
MirrorView/S.
Note
You must complete the tasks included in this chapter before you start the configuration
tasks in the next chapter.
Topics include:
l
l
l
l
l
l
l
VDM synchronous replication setup information................................................... 20

IP aliasing for VNX with two Control Stations......................................................... 20
Configure CS-to-CS communication between VNX systems.................................... 21
Add systems to the same Unisphere domain......................................................... 23
Create RAID groups for WIL and CPL LUNs.............................................................. 23
Enable the VDM synchronous replication service...................................................24
Create a block storage pool on source and destination VNX2 systems................... 26
19
VDM synchronous replication setup information

Table 1 on page 20 provides a planning sheet for your VDM Sync Replication setup
information.
Table 1 VDM synchronous replication setup planning sheet
What you specify
Source-site
information
Destination-site
information
Control Station name

Control Station IP address
Control Station IP alias (only used for VNX2
systems with dual Control Stations)
IP aliasing for VNX with two Control Stations

If your VNX is configured with two Control Stations, you must use the IP aliasing feature. If
you do not, management of your VDM replication sessions will become degraded in the
event that the primary Control Station is running in slot 1 instead of slot 0. Configuring IP
aliasing for the VNX enables communication with the primary and secondary Control
Stations using a single IP address regardless of whether the primary Control Station is
running in slot 0 or slot 1.
The following guidelines apply to this feature:
l
When using replication for the first time, or on new systems, configure IP alias first,
then use IP alias in the nas_cel -create -ip <ipaddr> command.
For existing systems with existing replication sessions, the current slot_0 primary
Control Station IP address must be used for the IP alias. You must then assign a new
IP address to slot_0. For example:
# nas_config -IPalias -create 0
Do you want slot_0 IP address <10.6.52.154>
as your alias? [yes or no]: yes
Please enter a new IP address for slot_0: 10.6.52.95
Done
#
When IP alias is deleted using the nas_config -IPalias -delete command, the IP
address of the primary or the secondary Control Station is not changed. Changes to
the IP address of the primary or the secondary Control Station must be done
separately. Replication depends on communication between the source Control
Station and the destination Control Station. When IP alias is used for replication,
deleting the IP alias breaks the communication. The IP address which was used as
the IP alias must be restored on the primary Control Station to restore the
communication.
While performing a NAS code upgrade, do not use an IP alias to log in to the Control
Station.
EMC VNX Command Line Interface Reference for File provides details on the nas_config
command.
20
Create an IP alias
Procedure
1. Login as nasadmin, and then su to root.
2. To create an IP alias for the Control Station, use one of the following scripts:
l
For an IPv4 IP alias, use:

# /nas/sbin/nas_config -IPalias -create 0

# /nas/sbin/nas_config -IPalias -create6 0
3. Depending on whether you want to use a new IP or the current IP address as the IP
alias, you will answer no or yes to the script prompt:
l
To use a new IP address as the IP alias, answer no to the question and then type
the new IP address to use as an IP alias within the same network.
To use the current IP address as the IP alias, answer yes to the question, and then
type a new IP address to replace the current IP address.
For example, to use a new IP address as the IP alias:

Do you want slot_0 IP address <1.2.3.4> as your alias [yes or no]:
no
Please enter an IP address to use as an alias: 1.2.3.6
4. To view the IP alias you created:

# /nas/sbin/nas_config -IPalias -list

# /nas/sbin/nas_config -IPalias -list6
Configure CS-to-CS communication between VNX systems

Before you begin
Before creating a replication session for remote replication, you must establish the
trusted relationship between the source and destination VNX2 systems in your
configuration.
Note
The communication between VNX Control Stations uses HTTPS.

The procedures in this section require the following:
l
The systems are up and running and IP network connectivity exists between the
Control Stations of both VNX2 systems. Verify whether a relationship already exists
by using the nas_cel -list command.
The source and destination Control Station system times must be within 10 minutes
of each other. Take into account time zones and daylight savings time, if applicable.
EMC recommends using an NTP service on the Control Stations to control this
function. You can set this up using VIA during the VNX system initialization process or
by using the nas_cs CLI command.
Create an IP alias
21
The same 6-15 characters passphrase must be used for both VNX systems.
Note
If the VNX systems have two Control Stations, an IP alias needs to be created, and the
Control Station-to-Control Station communication should be setup using the IP alias. For
more information about creating an IP alias, see IP aliasing for VNX with two Control
Stations on page 20.
To establish communication between the source and destination sites, do the following:
Procedure
1. On the source VNX system, to establish the connection to the destination VNX system
in the replication configuration, use this command syntax:
$ nas_cel -create <cel_name> -ip <ip> -passphrase
<passphrase>
where:
<cel_name> = name of the remote destination VNX system in the configuration
<ip> = IP address (or IP alias for a VNX2 system with two Control Stations) of the
remote Control Station in slot 0
<passphrase> = the secure passphrase used for the connection, which must have 6-15
characters and be the same on both sides of the connection
Example:
To add an entry for the Control Station of the destination VNX system, cs110, from the
source VNX system cs100, type:
$ nas_cel -create cs110 -ip 192.168.168.10 -passphrase nasadmin
Output:
operation in
id
=
name
=
owner
=
device
=
channel
=
net_path
=
celerra_id =
passphrase =
progress (not interruptible)...

1
cs110
0
192.168.168.10
APM000420008170000
nasadmin
2. Repeat step 1 on the destination VNX system to establish the connection to the
source VNX system in the replication configuration.
Example:
To add an entry for the Control Station of the source VNX system, cs100, from the
destination VNX system cs110, type:
$ nas_cel -create cs100 -ip 192.168.168.12 -passphrase nasadmin
Output:
operation in progress (not interruptible)...
id
= 2
name
= cs100
owner
= 0
device
=
channel
=
net_path
= 192.168.168.12
22
celerra_id = APM000340000680000
passphrase = nasadmin
Add systems to the same Unisphere domain

To add both source and destination VNX2 systems to the same Unisphere domain:
Procedure
1. In Unisphere, login to the source system.
l
Select System List.
Click Add.
Specify the IP address of the destination SP and click Connect.
Login to the destination system with the correct username and password.
Create RAID groups for WIL and CPL LUNs

Before you begin
Fibre Channel MirrorView/S ports on each system must be cabled and zoned to each
other.
For use with MirrorView/S, you need to create a RAID group that has write intent logs
(WIL) and Clone Private LUNs (CPL).
Procedure
1. In Unisphere, select a storage system.
2. Select Storage > Storage Configuration > Storage Pools
3. Select RAID Groups.
4. Create a new RAID group:
a. Click Create.
b. Specify details for the new RAID Group and click OK.
5. Right-click the new RAID group and select Create LUN.
6. Create two LUNs for write intent logs. Make sure that one WIL LUN is owned by SPA
and the other is owned by SPB:
a. Set the User Capacity to 128 MB.
b. Specify a Name of WIL_1.
c. Click Advanced.
d. Set the Default Owner to SPA.
e. Click Apply.
f. Repeat steps a to e, using a Name of WIL_2 and a Default Owner of SPB.
7. Create two clone private LUNs. Make sure that one CPL LUN is owned by SPA and the
other is owned by SPB:
a. Set the User Capacity to 2 GB.
b. Specify a Name of CPL_1.
c. Click Advanced.
Add systems to the same Unisphere domain
23
d. Set the Default Owner to SPA.

e. Click Apply.
f. Repeat steps a to e, using a Name of CPL_2 and a Default Owner of SPB.
8. Enable the MirrorView/S connection:
a. In Unisphere, select Data Protection.
b. From the task list, under Protection, select Manage Mirror Connections.
c. Select the system that appears in the Unconnected/Unknown Systems right pane
list, and click Enable to move it to the Mirror Enabled Systems left pane list.
d. Click OK.
9. Configure the WIL LUNs:
a. From the task list, under Protection, select Configure Mirror Write Intent Log.
b. Select the two WIL LUNs you created (WIL_1 and WIL_2).
c. Click Add.
d. Click OK.
10. Configure the CPLs:
a. In Unisphere, select Data Protection.
b. From the task list, under Protection, select Configure Clone Settings.
c. Select the two CPLs you created (CPL_1 and CPL_2).
d. Click Add.
e. Click OK.
11. For the destination system, repeat these steps except skip step 8. You do not need to
enable MirrorView/S on the destination system.
Enable the VDM synchronous replication service

Before you begin
The following prerequisites should be in effect before you enable the VDM synchronous
replication service:
l
Both source and destination systems have been added as destination systems of
each other (Control Station-to-Control Station relationship) with the same pass
phrase (use the nas_cel command command).
Cabinet DR has not been created on either the local or remote systems.
Two systems have been joined to the same Unisphere domain.
Before you can create a sync-replicable VDM, you must enable the synchronous
replication service between the source and destination systems.
Procedure
1. At either the source or destination site, type the following command syntax:
$ nas_cel -syncrep -enable {<cel_name>|id=<cel_id>}
-local_fsidrange <from>,<to>
-remote_fsidrange <from>,<to>
24
[-local_storage {raid_group=<rg_id>|block_pool=<pool_id>}]
[-remote_storage {raid_group=<rg_id>|block_pool=<pool_id>}]
where:
-enable {<cel_name>|id=<cel_id> = enables the VDM Synchronous Replication
feature on the specified VNX system (source or destination).
-local_fsidrange <from>,<to> = sets the file system identifier range on the local
VNX2 system. This range must not overlap the file system identifier range on the
remote VNX2 system. Valid values are from 1 to 32767.
-remote_fsidrange <from>,<to> = sets the file system identifier range on the
remote VNX2 system. This range must not overlap the file system identifier range on
the local VNX2 system. Valid values are from 1 to 32767.
raid_group=<rg_id> or block_pool=<pool_id> = specify either a local and remote
RAID group or a block storage pool to create synchronous replication mirror LUNs.
Example:
To enable the VDM synchronous replication service, on either the source or
destination system type:
nas_cel -syncrep -enable id=1 -local_fsidrange 4096,18000
-remote_fsidrange 18001,32000 -local_storage raid_group=0
-remote_storage raid_group=0
Output:
Now doing precondition check...
done
Now saving FSID range [18001,32000] on remote system...
done
Now saving FSID range [4096,18000] on local system...
done
Now adding remote storage info to local system...
done
Now creating sync replication mirror LUNs on local system... done
Now creating sync replication mirror LUNs on remote system...done
Now creating Mirrors and Clones (may take several minutes)...done
Now waiting for Mirrors and Clones to finish initial copy... done
Now adding NBS access to local server server_2...
done
Now adding NBS access to local server server_3...
done
Now creating mountpoint for sync replica of NAS database... done
Now mounting sync replica of NAS database...
done
Now enabling sync replication service on remote system...
done
done
Note
The initial copy operation takes longer for thick LUNs than for thin LUNs.
Results
The synchronous replication service record is saved on both sides. FSID ranges have
been set for both the source and destination systems.
If the enable service operation fails, and you want to choose different LUNs to use as
synchronous replication mirror LUNs, you must first disable the service before choosing
different LUNs.
If the MirrorView connection type is iSCSI, the enable service operation may time out
while waiting for mirrors and Clone groups to complete an initial copy. If this happens, try
to enable the service again after the mirrors and Clone groups become in-sync (this may
take hours).
Enable the VDM synchronous replication service
25
Create a block storage pool on source and destination VNX2

systems
Before you begin
l
Both source and destination VNX2 systems have been added as destination systems
of each other (Control Station-to-Control Station trusted relationship) with the same
pass phrase (use the nas_cel command command).
Procedure
1. In Unisphere, select the source VNX system.
For detailed information about creating a pool, refer to the Unisphere online help. You
can also create step-by-step instructions tailored to your VNX environment by going to
the mydocuments site at https://mydocuments.emc.com/ and click VNX Series and,
under VNX tasks, click Configure LUNs and storage pools.
2. Click Storage > Storage Configurations > Storage Pools
3. Click Create to create a block storage pool.
4. Click OK.
5. Select the destination VNX system and repeat these steps.
26
CHAPTER 4
Configuring
The topics in this chapter provide detail on the individual tasks to configure VDM
synchronous replication.
Note
The tasks included in the previous chapter must be completed before you start the tasks
in this chapter.
Topics include:
l
l
l
l
l
l
l
l
l
l
l
Create data LUNs for NAS resources...................................................................... 28

Create NAS user-defined pools.............................................................................. 28
Create a sync-replicable VDM................................................................................ 29
Create a file system on a sync-replicable NAS pool................................................ 30
Create the first file system checkpoint on a sync-replicable NAS pool.................... 31
Create a network interface for a sync-replicable VDM.............................................32
Create CIFS shares and NFS exports for each file system on your VDM................... 33
Migrate Data Mover configurations and cabinet level service.................................34
Create a VDM synchronous replication session......................................................34
Configure CIFS CA support..................................................................................... 36
Configure for NFS I/O transparency in VDM synchronous replication session......... 38
Configuring
27
Configuring
Create data LUNs for NAS resources

Create the desired number of LUNs for use as data LUNs on the source and destination
VNX2 systems. Size these LUNs appropriately, based on the amount of information to be
stored and the duration, such as 200 GB. Build these LUNs from a block storage pool and
assign them to the ~filestorage group. Keep in mind that you need to create enough LUNs
to create dedicated File storage pools (refer to Create NAS user-defined pools on page
28) for each VDM and syncrep session that is being created.
Before you begin
The VDM synchronous replication service must be enabled.
Procedure
1. In Unisphere, select the source VNX system.
2. Click Storage > LUNs.
3. Click Create on the LUNs tab.
The Create LUN window appears.
4. Fill in the fields to create the appropriate number of thick LUNs of the appropriate
size.
5. When you are finished filling in the fields, click Apply and then click OK to confirm
your settings.
The data LUNs appear on the LUNs tab.
6. Select these data LUNs and click Add to Storage Group.
Add to selected Storage Groups window appears.
7. Select the ~filestorage group from the list of Available Storage Groups and move it to
the list of Selected Storage Groups.
8. Click OK, then and click Yes and OK to confirm selection.
9. To create the NAS Disk Volumes, from the task list, under File Storage, click Rescan
Storage Systems.
10. Select the destination VNX system and repeat these steps.
Note
Create the same number of volumes using the same size as the source, which will be
presented to the target VNX and used to create the target NAS pools.
Create NAS user-defined pools

Before you begin
l
The VDM synchronous replication service must be enabled.
Data LUNs for NAS resources and NAS Disks Volumes have been created.
Create the desired number of NAS user-defined pools (one for each sync-replicable VDM)
using the NAS Disks you created in the previous section. Name these pools appropriately,
such as vdm1pool and vdm2pool.
28
Configuring
Procedure
1. On the source VNX system, run the following command to create a NAS user-defined
pool:
$ nas_pool -create -name <name> -volumes
<volume_name>[,<volume_name>,...]
where:
-create = creates a user-defined storage pool.
<name> = assigns a name to the new storage pool. If no name is specified, assigns one
by default.
-volumes <volume_name> [,<volume_name>,...] = designates the members to be

added to the storage pool. The members can be any meta, slice, stripe, or disk
volumes.
Example:
To create NAS user-defined pools and assign NAS Disks to them, type
$ nas_pool -create -name vdm1pool -volumes
d7,d8,d9,d10,d11,d12,d13,d14,d15,d16
$ nas_pool -create -name vdm2pool -volumes
d17,d18,d19,d20,d21,d22,d23,d24,d25,d26
2. Repeat Step 1 on the destination VNX system.

Note
Make sure to use the same number of volumes with the same sizes, as each source
and target pool must match in size.
Create a sync-replicable VDM

Before you begin
The following prerequisites should be in effect before you create a sync-replicable VDM:
l
The synchronous replication service has been enabled between the two VNX2
systems, source and destination.
User-defined file storage pools must be created.
To create a sync-replicable VDM, do the following:

Note
If you intend to use an existing VDM for synchronous replication, see Modify a VDM from
non-sync-replicable to sync-replicable on page 53 for instructions to modify a nonsyncreplicable VDM to be syncreplicable.
Procedure
1. At the source site, type the following command syntax:
$ nas_server [-name <name>] [-type vdm] -create <movername>
[-setstate <state>] [pool=<pool>] [-option <options>]
where:
Create a sync-replicable VDM
29
Configuring
[-name <name>] [-type vdm] -create <movername> = Creates a VDM with an

optional name for the specified VDM. The movername is case-sensitive and supports
the following characters: a through z, A through Z, 0 through 9, _ (underscore), (hyphen) though names may not start with a hyphen.
-setstate <state> = sets the state of the VDM to loaded or mounted.
pool=<pool> = assigns a rule set known as a storage pool for the VDM root file
system.
-option <options> = specifies a comma separated list of options that includes FS
type, log type, and whether the VDM is sync-replicable.
Example:
To create a sync-replicable VDM, type:
$ nas_server -name vdm1 -type vdm -create server_2 pool=vdm1pool option syncreplicable=yes
Create a file system on a sync-replicable NAS pool

To create a file system on a sync-replicable NAS pool so that it can be included in any
synchronous replication session created on the corresponding sync-replicable VDM,
follow these rules:
l
log_type=common must not be specified. Use split, which is the default.
type= Only uxfs or rawfs can be specified as type.
If you specify the mover= option, only the sync-replicable VDM on the sync-replicable
NAS pool can be specified.
Procedure
1. Specify the name of the file system, its size, the sync-replicable NAS pool, and the
VDM name by using the nas_fs command.
Use the following command syntax:
nas_fs -name <name> -create size=<integer> [T|G|M]
pool=<pool>
where:
<name> = name of the VDM file system. A file system name can be up to 240
characters, but cannot begin with a dash (-), be comprised entirely of integers or be a
single integer, contain the word root or contain a colon (:).
<integer> = size of the file system to create, in terabytes (T), gigabytes (G), or
megabytes (M).
<pool> = name of the sync-replicable NAS pool.
Example:
To create a file system on a sync-replicable NAS pool, type:
nas_fs -name VDM1_FS -create size=100G pool=VDM1_Pool
Results
The split-log file system is created on the sync-replicable NAS pool.
30
Configuring
Create the first file system checkpoint on a sync-replicable NAS

pool
To create the first checkpoint for a file system on a sync-replicable NAS pool, do the
following:
Procedure
1. Specify the name or ID of the file system, checkpoint name (optional), SavVol size
(optional), and pool of the SavVol (optional, must be the same pool as the file system
if specified) by using the fs_ckpt command.
Use the following command syntax:
fs_ckpt <fs_name> -Create
where:
<fs_name> = name of the file system. A file system name can be up to 240 characters,
but cannot begin with a dash (-), be comprised entirely of integers or be a single
integer, contain the word root or contain a colon (:).
Example:
To create a file system checkpoint on a sync-replicable NAS pool, type:
fs_ckpt VDM1_FS -Create
2. Alternatively, you can also create a checkpoint schedule by using the following
syntax.
nas_ckpt_schedule -create <name>
-filesystem { <fs_name> | id=<id> } -recurrence
{ once -runtimes <HH:MM> [ -start_on <YYYY-MM-DD> ]
[ -ckpt_name <ckpt_name> ]
daily -runtimes <HH:MM>[,...] { -keep <number_of_ckpts> |
-ckpt_names <ckpt_name>[,...] } [ -every <number_of_days> ]
[ -start_on <YYYY-MM-DD> ] [ -end_on <YYYY-MM-DD> ]
weekly -days_of_week {Mon|Tue|Wed|Thu|Fri|Sat|Sun}[,...]
-runtimes <HH:MM>[,...] { -keep <number_of_ckpts> |
-ckpt_names <ckpt_name>[,...] } [ -every <number_of_weeks> ]
[ -start_on <YYYY-MM-DD> ] [ -end_on <YYYY-MM-DD> ]
monthly -days_of_month <days>[,...] -runtimes <HH:MM>[,...]
{ -keep <number_of_ckpts> | -ckpt_names <ckpt_name>[,...] }
[ -every <number_of_months> ] [ -start_on <YYYY-MM-DD> ]
[ -end_on <YYYY-MM-DD> ] }
where:
<name> = name of checkpoint schedule; the name must be a system-wide unique
name and can contain up to 128 ASCII characters, including az, AZ, 09, and
period (.), hyphen (-), or underscore ( _ ). Names cannot start with a hyphen, include
intervening space, or contain all numbers
<fs_name> = name of the file system of which to create the checkpoint; you can also
use the file system ID; the syntax for the file system ID is filesystem id=<n>
Create the first file system checkpoint on a sync-replicable NAS pool
31
Configuring
<HH:MM> = time at which the checkpoint creation occurs; specify this value by using
the 24-hour clock format; for example, 23:59
<YYYY-MM-DD> = date on which the checkpoint creation occurs
<ckpt_name> = name of the checkpoint
<number_of_ckpts> = number of checkpoints to keep or create before the checkpoints
are refreshed
<number_of_days> = every number of days to create the checkpoints; for example, 2
generates checkpoints every 2 days; the default is 1
<number_of_weeks> = every number of weeks to create the checkpoints; for example, 2
runs the checkpoint schedule bimonthly; the default is 1
<days> = one or more days of the month to run the automated checkpoint schedule;
specify an integer between 1 and 31; use a comma to separate the days
<number_of_months> = every number of months to create the checkpoints; for
example, 3 runs the checkpoint schedule every 3 months; the default is 1
Example:
To create a daily checkpoint schedule, type:
nas_ckpt_schedule -create VDM1_Schedule -filesystem VDM1_FS
-recurrence daily -runtimes 20:00 -keep 5 -start_on 2015-08-08
Results
SavVol for the file system is created on the sync-replicable NAS pool along with the first
file system checkpoint.
Create a network interface for a sync-replicable VDM

Before you begin
The following prerequisites should be in effect before you create a network interface for a
sync-replicable VDM:
l
The synchronous replication service has been enabled between the two VNX2
systems, source and destination.
A sync-replicable VDM has been created.
Create an additional interface on each side that is not attached to any VDM. This
ensures the Data Mover will always have an interface available for dynamic DNS
updates. If you do not create these interfaces, reverse and failover operations on the
last VDM may take longer to complete.
Alternatively, you can disable dynamic DNS updates if they are not required in your
environment by running the following command:
server_param server_2 -f dns -m updateMode -v 0
This parameter change takes effect immediately.
To create and assign a network interface for each sync-replicable VDM, do the following:
Procedure
1. Type the following command syntax:
server_ifconfig <movername> -create -Device <device_name>
-name <if_name> -protocol {IP <ipv4_addr> <ipmask>
<ipbroadcast>}
32
Configuring
where:
<movername> = name of the Data Mover
<device_name> = name of the device
<if_name> = name of the interface
<ipv4_addr>, <ipmask>, and <ipbroadcast> = IP address, mask, and broadcast address.
The IP address is the address of a particular interface. The IP mask includes the
network part of the local address and the subnet, which is taken from the host field of
the address. For example, 255.255.255.0 would be a mask for a Class C network. The
IP broadcast is a special destination address that specifies a broadcast message to a
network.
Example:
To create a network interface for a sync-replicable VDM, type:
server_ifconfig server_2 -create -Device cge-1-0 -name
VDM1_Interface -protocol IP 10.10.10.50 255.255.255.0 10.10.10.255
2. Optionally, if you want the IP to carry over during a reverse or failover operation, then
on the source VNX system, type:
nas_server -vdm <vdm_name> -attach <interface>
where:
<vdm_name> = name of the VDM
<interface> = name of the interface
Example:
To attach a network interface to a sync-replicable VDM, type:
$ nas_server -vdm vdm1 -attach vdm1interface
3. If necessary, repeat Step 2 for each of the remaining sync-replicable VDMs.

Results
Allows the user to manage the network interfaces for a VDM. The interfaces are attached
to a VDM when the VDM state is loaded. When an interface is attached to a VDM, the NFS
clients connecting the Data Mover through this interface have access to the file system
exported by the VDM configuration.
Create CIFS shares and NFS exports for each file system on your
VDM
The procedures in this section require that file systems have been created on a syncreplicable NAS pool.
Create CIFS shares and NFS exports for each of the file systems on your VDM. For detailed
information about creating CIFS shares and NFS exports, refer to Configuring and Managing
CIFS on VNX and Configuring NFS on VNX. These documents are located on EMC Online
Support (registration required) at http://Support.EMC.com and in the Related documents
section of the VNX Series on the mydocuments site at https://mydocuments.emc.com/.
Create CIFS shares and NFS exports for each file system on your VDM
33
Configuring
Migrate Data Mover configurations and cabinet level service

The migration of Data Mover configurations and Cabinet level service is not included in
VDM synchronous replication. The following is the list of these configurations and
service:
l
Data Mover configurations:

n
DNS
NIS
NTP
Local passwd and group
Usermapper client
FTP/SFTP
LDAP
HTTP
CEPP
CAVA
Server Parameters
Netgroup
Nsswitch
Hosts
Cabinet level service:

n
Usermapper service
Use migrate_system_conf to migrate those configurations and service that are

needed for VDM synchronous replication after the creation of a VDM synchronous
replication session and before a reverse or failover operation. First, migrate the
usermapper, then the data mover services. For information about
migrate_system_conf, see the VNX Command Line Interface Reference Information for
File and Using VNX File Migration Technical Notes for details.
Note
The routing table, including the default route, does not get migrated with this command.
The routes need to be configured manually. To add a default gateway or a route entry, a
network interface with a status of UP must exist.
Create a VDM synchronous replication session

Before you begin
The following prerequisites should be in effect before you create a VDM synchronous
replication session:
34
Control Station-to-Control Station communication channel between the two VNX2

systems should be configured and ready for communication.
Synchronous replication service has been enabled between the two VNX2 systems,
source and destination.
Configuring
Both source and destination systems are operating with VNX OE for file version
8.1.8.130 or later version.
Specified VDM is sync-replicable, mounted, loaded or temporarily unloaded on the

Data Mover.
The destination user-defined pool is not in use and meets all sync-replicable NAS
pool criteria.
The destination user-defined pool must match the size of the source user defined
pool. If equal performance is desired at the destination site, in relation to the source
site, the destination user-defined pool should be built using the same configuration.
Local and remote Data Mover should have the same I18N mode.
Sync-replicable NAS pool of the specified VDM does not contain a File System/
Checkpoint with an FSID that is used in the remote system.
If you want the destination system to match the configuration of the source, from the
destination VNX2 system, you must manually migrate some Data Mover and Cabinet
level service items. Refer to Migrate Data Mover configurations and cabinet level
service on page 34 for details.
To create a VDM synchronous replication session, do the following:

Procedure
$ nas_syncrep -create <name> -vdm <vdm_name> -remote_system
<cel_name> -remote_pool <pool_name> -remote_mover
<mover_name> [-network_devices
<local_device_name>:<remote_device_name>[,...]]
where:
-create <name> = assigns a name to the synchronous replication session.
-vdm <vdm_name> = specifies the name of an existing source sync-replicable VDM to
replicate.
-remote_system <cel_name> = specifies the name of an existing remote VNX
system.
-remote_pool <pool_name> = specifies the name of an existing remote user-defined
pool.
-remote_mover <mover_name> = specifies the name of an existing remote Data
Mover.
[-network_devices <local_device_name>:<remote_device_name>[,...]] = specifies the
mappings of the local and remote network devices. If any network interface is
attached to the specified VDM, this parameter is mandatory; otherwise, this
parameter is optional.
Example:
To create a VDM synchronous replication session, type:
$ nas_syncrep -create 7150_syncrep_session1 -vdm 7150_vdm1
-remote_system lhmc7004 -remote_pool 7004_vdm_pool1 -remote_mover
server_2 -network_devices cge-2-0:cge-3-0
Output:
Now validating params...
Now marking remote pool as standby pool...
done
done
Create a VDM synchronous replication session
35
Configuring
Now creating CG...

Now creating remote network interface(s)...
Now updating local disk type...
Now updating remote disk type...
Now generating session entry...
done
done
done
done
done
done
Results
The initial synchronization takes time to complete. You can monitor the synchronization
status by running the nas_synrep -info command.
Note
If you create and attach a new IP interface on the source VDM after the replication session
has been created, a warning will appear stating that this new interface will not be
reversed or failed over. You must manually create the new Interface, with the same name,
in the DOWN state on the destination VNX system before you can reverse or failover the
session. If the interface is not created on the destination VNX system, a VDM
synchronous replication session reverse or failover operation will fail.
Configure CIFS CA support

In order to support CIFS CA on VDM synchronous replication reverse or failover, use the
SMB 3.0 client with CA enabled, which can be Windows Server 2012 or later. To configure
CIFS CA, you need to do the following:
Note
The Home Directory feature does not support Continuous Availability (CA) capability.
Keep this in mind when you configure CIFS Continuous Availability (CA) support for the
VDM synchronous replication feature.
Procedure
1. If not already enabled, enable the SMB 3.0 protocol.
Example:
To enable the SMB 3.0 protocol, type:
$ server_cifs server_2 -add security=NT,dialect=SMB3
2. Mount and export network Shares with the smbca flag set.
A VNX File Server configuration that uses CIFS CA requires network Shares that are
mounted and exported with a special smbca flag. CA mount and Export options are
not supported in Unisphere. For more information about CIFS, see Configuring and
Managing CIFS on VNX.
Example:
To mount and export network Shares, type:
$ server_mount server_2 -o smbca fs1 /fs1
$ server_export server_2 -P cifs -name fileshare -option
type=CA /fs1
3. If necessary, set the File server CIFS parameter smb2.maxCaTimeout.

To support VNX File Server CA, the File server uses a CIFS parameter
smb2.maxCaTimeout, with a default timeout value of 360 seconds. This value can
36
Configuring
be configured from 0-600 seconds, depending on your requirements. Parameters

Guide for VNX for File provides more information on how to modify this parameter.
4. On the destination VNX2 system, ensure the Data Mover configurations and cabinet
level service that are needed for the VDM under synchronous replication have been
migrated from the source. See Migrate Data Mover configurations and cabinet level
service on page 34 for more information.
5. The CIFS service must be started on the target Data Mover so that after a synchronous
replication session is reversed or failed over, the CIFS service will be active on the
destination VNX2 system.
Example:
Use the server_setup CLI command to start CIFS service manually. Type:
$ server_setup server_2 -Protocol cifs -option start
6. If the VNX system needs to communicate outside of its subnet, you must configure
route settings using one of the following methods (refer to Configuring and Managing
Networking on VNX for details):
Add a default gateway using the server_route CLI command, for example:
$ server_route server_2 -add default 10.11.12.1
Add a route entry using the server_route CLI command, for example:
$ server_route server_3 -add net 10.13.14.15 10.11.12.1
7. Ensure the DNS server is configured on the target Data Mover.

To achieve CIFS IO transparency, after a synchronous replication session reverse or
failover, you must make sure the destination Data Mover is configured with the same
DNS server as the source Data Mover.
Example:
Use either the server_dns CLI command to configure the DNS server manually or
the migrate_system_conf tool. Type:
$ server_dns server_2 -protocol udp dns.cifs.domain.com 10.11.12.13
or
$ /nas/bin/migrate_system_conf -mover -source_system id=1 source_user nasadmin -source_mover server_2 -destination_mover
server_2 -service dns
8. Ensure the target network interface can work on the destination VNX2 system.
The source and destination network interfaces for a synchronous replication session
are using the same name. The network interface on the destination VNX2 system is in
the down state. If the network interface on the destination VNX2 system is created
automatically during a synchronous replication session creation, then it is configured
using the same configuration as the source VNX2 system, including the IP address. If
the destination VNX2 system network interface is created manually after synchronous
replication session creation, it can be configured with any configuration which works
on the destination VNX2 system. If the network interface on the source and
destination are using different IP addresses, simply bring the destination network
interface up and see that it is working by using the server_ping CLI command.
Configure CIFS CA support
37
Configuring
Note
If the network interfaces on the source and destination are using the same IP address,
the network interface on the destination cannot be brought up; otherwise, there will
be an IP address conflict on the network. Use one of the following ways to test
whether the network interface works:
l
When the VDM is not in service to users, do a synchronous replication session

reverse and check if the CIFS server can be connected after the reverse.
Create a network interface using an IP address within the same subnet as the
destination network interface, bring it up, and test if it works using the
server_ping CLI command.
If the target network interface cannot work, check with your network administrator.
Ensure the target Data Mover has the correct routes, and, if applicable, the VLAN
functions.
Configure for NFS I/O transparency in VDM synchronous

replication session
VDM Sync Replication does not replicate Data Mover level configuration. The Data Mover
level configuration, like the default route, cannot rely on the network interface which is
attached to the VDM protected by a synchronous replication session. To add a network
interface and replicate Data Mover level configuration, you need to do the following:
Procedure
1. On the source system, add a network interface to make Data Mover level configuration
work.
The additional network interface should be up and configured with a public IP
address. It can be used by another VDM or CIFS server, but it cannot be used by any
VDM that is protected by a synchronous replication session.
2. On the destination VNX2 system, ensure the Data Mover configurations and cabinet
level service that are needed for the VDM under synchronous replication have been
migrated from the source. See Migrate Data Mover configurations and cabinet level
service on page 34 for more information.
3. If the VNX system needs to communicate outside of its subnet, you must configure
route settings using one of the following methods (refer to Configuring and Managing
Networking on VNX for details):
Add a default gateway using the server_route CLI command, for example:
$ server_route server_2 -add default 10.11.12.1
Add a route entry using the server_route CLI command, for example:
$ server_route server_3 -add net 10.13.14.15 10.11.12.1
4. Ensure the target network interface can work on the destination VNX2 system.
The source and destination network interfaces for a synchronous replication session
are using the same name. The network interface on the destination VNX2 system is in
the down state. If the network interface on the destination VNX2 system is created
automatically during a synchronous replication session creation, then it is configured
using the same configuration as the source VNX2 system, including the IP address. If
the destination VNX2 system network interface is created manually after synchronous
38
Configuring
replication session creation, it can be configured with any configuration which works
on the destination VNX2 system, as long as it uses the same name as the source
VNX2 system network interface. To ensure NFS I/O transparency, the source and
destination network interface must use the same IP address.
Note
If the network interfaces on the source and destination are using the same IP address,
the network interface on the destination cannot be brought up; otherwise, there will
be an IP address conflict on the network. Use one of the following ways to test
whether the network interface works:
l
When the VDM is not in service to users, do a synchronous replication session

reverse and check if the NFS client can connect to the NFS server and then reverse
back.
Create a network interface using an IP address within the same subnet as the
destination network interface, bring it up, and test if it works using the
server_ping CLI command.
If the target network interface cannot work, check with your network administrator.
Ensure the target Data Mover has the correct routes, and, if applicable, the VLAN
functions.
Configure for NFS I/O transparency in VDM synchronous replication session
39
Configuring
40
CHAPTER 5
Topics include:
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
l
About using the VNX for File CLI for managing........................................................42

List information for VDM synchronous replication service...................................... 42
Show information for a sync-replicable VDM..........................................................42
Reverse a synchronous replication session........................................................... 43
Failover a synchronous replication session............................................................45
Clean synchronous replication session..................................................................47
Delete a synchronous replication session..............................................................49
Start a VDM synchronous replication session........................................................ 49
Show information for VDM synchronous replication service...................................50
Disable the VDM synchronous replication service..................................................50
Modify a VDM from sync-replicable to non-sync-replicable.................................... 52
Modify a VDM from non-sync-replicable to sync-replicable.................................... 53
Delete a sync-replicable VDM................................................................................ 54
List information for VDM synchronous replication session..................................... 54
Show information for VDM synchronous replication session..................................55
Extend a sync-replicable NAS pool........................................................................ 56
Shrink a sync-replicable NAS pool......................................................................... 58
Configuring for added secondary Control Stations................................................. 59
Updating VNX OE software.....................................................................................60
41
About using the VNX for File CLI for managing

The tasks described in this section are performed by using the VNX for File CLI. The first
three topics are the primary tasks related to VDM synchronous replication for disaster
recovery (DR).
l
Reverse should be used when attempting to move a VDM from one VNX2 system to
the other while the source system is still available. For more information about when
to use reverse, see Reverse a Sync Replication session on page 43.
Failover should only be used in the event that the source VNX2 system is not
reachable.
The Clean task is related to failover.
For more information about when to use Failover and Clean, see Failover a sync
replication session on page 45.
Note
The Failover and Reverse tasks can also be performed automatically by using the VDM
MetroSync Manager software. Refer to the "Using VDM MetroSync Manager" chapter for
details.
The remaining topics are ancillary tasks related to the management of the VDM
synchronous replication environment and are also useful for troubleshooting.
List information for VDM synchronous replication service

To see which storage system has the VDM synchronous replication service enabled, do
the following:
Procedure
$ nas_cel -syncrep -list
where:
-list = displays which VNX systems have the VDM synchronous replication service
enabled.
Example:
To list VDM synchronous replication service information, on either the source or
destination VNX2 system type:
nas_cel -syncrep -list
Output:
id
0
1
name
my_system1
my_system2
syncrep
initialized
enabled
Show information for a sync-replicable VDM

Before you begin
None.
42
To display information for a specific sync-replicable VDM or all sync-replicable VDMs

between two VNX2 systems, do the following:
Procedure
$ nas_server -info -vdm {all|<vdm_name>|id=<vdm_id>}
where:
-info -vdm {all | <vdm_name> | id=<vdm_id>} = displays attributes for all VDMs,
or a specified VDM, including the network interfaces.
Example:
To display information for a sync-replicable VDM, type:
nas_server -info -vdm id=83
Output:
id
= 83
name
= my_vdm
acl
= 0
type
= vdm
server
= server_2
rootfs
= root_fs_vdm_my_vdm
I18N mode = ASCII
mountedfs =
syncreplicable = True
member_of =
status
:
defined = enabled
actual = loaded, ready
Interfaces to services mapping:
Note
The line of syncreplicable is not displayed for a non-sync-replicable VDM.
Reverse a synchronous replication session

If you need to perform maintenance or balance the load on your source VNX2 system and
maintain a sync-replicable VDM as active, reverse the direction of the corresponding VDM
synchronous replication session between the source and destination sites.
Before you begin
The following prerequisites should be in effect before you reverse a synchronous
l
Both systems of the synchronous replication session are up.
All network interfaces on the source VNX2 system have the corresponding network
interfaces with the same names on the destination VNX2 system specified for the
No FSID conflicts exist between source and destination systems.
The synchronous replication's session status and service status for remote to local is
synchronized.
Local and remote Data Mover should have the same I18N mode.
It is recommended that you leave at least one interface available on each physical
Data Mover at all times on both source and destination systems. To do this, add an
Reverse a synchronous replication session
43
interface to each primary Data Mover on both sites but leave it unattached to any
VDMs. The additional interface should be on the same subnet as the one that is on
the VDMs.
Because the interface is brought down as part of the reverse process, reversing the
last VDM on a Data Mover might remove all available interfaces from that Data Mover.
This prevents the Data Mover from communicating with the environment such as NTP
servers, DNS servers, and so on.
Also, in order to support CIFS CA (Continuous Availability) on reverse, you must use the
SMB 3.0 client with CA enabled. If the service outage time can be less than the CIFS
timeout, CIFS CA can be achieved. To configure CIFS CA support on VDM synchronous
replication reverse, see Configure CIFS CA support on page 36 for details. If you need to
configure for NFS I/O transparency, see Configure for NFS I/O transparency in VDM
synchronous replication session on page 38 for details.
This task reverses the direction of a synchronous replication session along with the
source and destination roles of the two VNX2 systems involved in the synchronous
replication session.
Procedure
1. At the destination site, type the following command syntax:
$ nas_syncrep -reverse {<name>|id=<id>}
where:
<name> = name of the synchronous replication session
<id> = identifier of the synchronous replication session
Example:
To reverse the direction of a synchronous replication session using the ID of the
synchronous replication session, type:
$ nas_syncrep -reverse id=4315
Output:
WARNING: You have just issued the nas_syncrep -reverse command.
There will be a period of Data Unavailability during the reverse
operation. After the reverse operation, the VDM/FS(s)/
checkpoint(s) protected by the sync replication session will be
reversed to the local site. Are you sure you want to proceed? [yes
or no]
2. At the warning prompt, type yes.

Output:
Now doing precondition check...
Now doing health check...
Now cleaning local...
Now
Now
Now
Now
Now
Now
Now
Now
Now
44
done: 19 s
done: 11 s
done: 1 s
Service outage start......

turning down remote network interface(s)...
done: 10 s
unloading remote VDM/FS(s)/checkpoint(s)...
done: 29 s
switching the session (may take several minutes)... done: 7 s
importing sync replica of NAS database...
done: 16 s
creating VDM...
done: 5 s
importing VDM settings...
done: 0 s
mounting exported FS(s)/checkpoint(s)...
done: 13 s
loading VDM...
done: 3 s
turning up local network interface(s)...
done: 0 s
Service outage end: 83 s
Now
Now
Now
Now
mounting unexported FS(s)/checkpoint(s)...

importing schedule(s)...
unloading remote VDM/FS(s)/checkpoint(s)...
cleaning remote...
done
done:
done:
done:
done:
Elapsed time:
0 s
0 s
16 s
17 s
116s
Results
The original destination VNX2 system becomes the source VNX2 system for the VDM in
the synchronous replication session. The NAS client can only access data from the new
source VNX2 system for the VDM. The NAS client cannot access data from the original
VNX2 system.
Until a reverse operation succeeds, do not change the VDM, file systems, and
checkpoints protected by the synchronous replication session.
Note
After the synchronous replication session is reversed, for the disk volumes in the new
standby pool, their visible servers (listed in the corresponding servers field) will
become empty.
After you finish
After you have reversed the direction of a VDM synchronous replication session so that
the destination site is the active site, and you want to make the original source site the
active site again, run the nas_syncrep -reverse command on the original source
site. This action returns the VDM, file system, file system checkpoints, file system
checkpoint schedules, and related network interfaces to the original source site, which
becomes active. The VDM at the destination site becomes standby.
Failover a synchronous replication session

During normal operation when a synchronous replication session is active, the source
sync-replicable VDM is active while the destination DM is active and designated for use
as a standby for the source sync-replicable VDM. If a failure occurs at the source site
(active VNX system in the synchronous replication session is down and not available) and
you have not set up automatic failover using the VDM MetroSync Manager product, you
need to manually failover the source sync-replicable VDM to the destination VNX by using
the VNX for File CLI.
Before you begin
The following prerequisites should be in effect before you failover a synchronous
l
Standby VNX2 system of the synchronous replication session is up.
Local and remote Data Movers should have the same I18N mode.
All network interfaces on the source VNX2 system have corresponding network
interfaces with the same names on the destination VNX2 system specified for the
No FSID conflicts exist between the source and destination systems.
The synchronous replication's session status and service status for remote to local
should not be sync_in_progress.
Failover a synchronous replication session
45
Note
If the network interface on the original source system is not in the down state (system will
only try to turn it down during the failover, but it may fail), I/O transparency cannot be
guaranteed.
Also, in order to support CIFS CA (Continuous Availability) on failover, you must use the
SMB 3.0 client with CA enabled. If the service outage time can be less than the CIFS
timeout, CIFS CA can be achieved. To configure CIFS CA support on VDM synchronous
replication failover, see Configure CIFS CA support on page 36 for details. If you need to
configure for NFS I/O transparency, see Configure for NFS I/O transparency in VDM
synchronous replication session on page 38 for details.
After a disaster occurs and the active VNX2 system is down, failover a sync-replicable
VDM to the standby VNX2 system to make it active.
NOTICE
Failover should only be used in situations where the source site is not available. In
situations where the source site is still accessible, a reverse must be used instead.
Note
When failover starts, you must not perform any operation on the VDM or synchronous
replication session on the failed site.
Procedure
1. At the destination site, type the following command syntax:
$ nas_syncrep -failover {<name>|id=<id>}
where:
<name> = name of the VDM synchronous replication session
<id> = identifier of the VDM synchronous replication session
Example:
To failover the VDM to the standby VNX2 system, type:
$ nas_syncrep -failover id=4560
Output:
WARNING: You have just issued the nas_syncrep -failover command.
Verify whether the peer system or any of its file storage
resources are accessible. If they are, you should issue the
nas_syncrep -reverse command instead. Running the nas_syncrep
-failover command while the peer system is still accessible
could result in Data Loss if the session is not in sync. Are you
sure you want to proceed? [yes or no]
2. At the warning prompt, type yes.

Output:
Now
Now
Now
Now
Now
Now
Now
Now
46
doing precondition check...

done:
doing health check...
done:
cleaning local...
done:
switching the session (may take several minutes)...
importing sync replica of NAS database...
done:
creating VDM...
done:
importing VDM settings...
done:
mounting exported FS(s)/checkpoint(s)...
done:
30 s
7 s
1 s
done: 4
15 s
5 s
0 s
3 s
Now loading VDM...

done: 4 s
Now turning up local network interface(s)...
done: 0 s
Service outage end: 69 s
Now mounting unexported FS(s)/checkpoint(s)...
done: 0 s
Now importing schedule(s)...
done: 0 s
Elapsed time: 69 s
done
Results
Until a failover operation succeeds, do not change the VDM, file systems, and
checkpoints protected by the synchronous replication session.
After the failover completes, the original standby system becomes the active system for
the VDM in the synchronous replication session. The NAS client will now access data from
the VDM on this active system. The original active system becomes the standby system
for the VDM in the synchronous replication session. After failover, the LUNs under
synchronous replication on the original active system (now the standby) become Read
Only.
After you finish
If the failed system is offline or the MirrorView link is down, the synchronous replication
session's state becomes Stopped. The data cannot be synchronized back to the original
source side.
1. Fix the issue that caused the failure at the source site.
NOTICE
If the source site Data Mover was powered off, the Data Mover network must be
disconnected before powering it on, to avoid IP address conflict.
2. Perform a Clean operation. Refer to Clean synchronous replication session on page
47 for details.
3. If the source site Data Mover network was disconnected, reconnect it.
4. At the source site, run the nas_syncrep -reverse command. This action
restores normal operation at the source site. It brings the VDM, file system, file
system checkpoints, file system checkpoint schedules, and related network
interfaces online at the source site and changes the corresponding VDM at the
destination site to standby.
Clean synchronous replication session

Before you begin
After a failover has occurred, the LUNs under synchronous replication on the original
source VNX2 system become Read Only. You need to run the nas_syncrep -Clean
command from the source site for either a specified synchronous replication session or
all synchronous replication sessions stored in the source NAS database. This action
cleans the source site of all unnecessary objects and prepares it for a nas_syncrep reverse operation. If the command is not run, you are prevented from reversing the
replication session.
Procedure
1. Fix the issue that caused the failure at the source site.
Clean synchronous replication session
47
NOTICE
If the source site Data Mover was powered off, the Data Mover network must be
disconnected before powering it on, to avoid IP address conflict.
2. Run the nas_syncrep -Clean command from the source site for either a specified
synchronous replication session or all synchronous replication sessions stored in the
source NAS database. This action cleans the source site of all unnecessary objects
and prepares it for a nas_syncrep -reverse operation.
If the nas_syncrep -Clean command is not run, you are prevented from reversing
the replication session.
3. If the source site Data Mover network was disconnected, reconnect it.
4. At the source site, run the nas_syncrep -reverse command. This action restores
normal operation at the source site. It brings the VDM, file system, file system
checkpoints, file system checkpoint schedules, and related network interfaces online
at the source site and changes the corresponding VDM at the destination site to
standby.
5. At the original source VNX2 system site, type the following command syntax:
$ nas_syncrep -Clean {-all|<name>|id=<id>}
where:
<name> = name of the synchronous replication session
<id> = identifier of the synchronous replication session
Example:
To Clean the synchronous replication session on the original source VNX2 system for a
single synchronous replication session, type:
$ nas_syncrep -Clean id=8002
Output:
Now cleaning session my_session1 (may take several minutes)...done
Now starting session my_session1...
done
Note
The Data Mover may reboot during a clean operation. If a Data Mover reboot is
needed, a warning prompt message is displayed. Otherwise, the warning prompt
message does not display.
Results
The following occur as a result of a successful Clean operation:
48
Standby VDM is deleted.
Standby file systems and checkpoints on VDM are deleted.
If necessary, the Data Mover is rebooted.
Delete a synchronous replication session

Before you begin
l
The Control Station communication channel is ready for communication between the
two sites.
To delete a VDM synchronous replication session, do the following:

Procedure
1. At the source VNX2 system site, type the following command syntax:
$ nas_syncrep -delete {<name>|id=<id>}
where:
<name> = name of the replication session
<id> = identifier of the replication session
Example:
To delete a synchronous replication session, type:
$ nas_syncrep -delete my_syncrep1
Output:
WARNING: Please do not perform any operation on my_syncrep1 on
standby system until delete is done.
Deleting...done
Results
The VNX2 system removes the synchronous replication session from the local NAS
database.
Note
After a synchronous replication session is deleted, for the disk volumes in the userdefined pool, their type will be updated (changed to the corresponding unmirrored type).
Start a VDM synchronous replication session

If the replication for a synchronous replication session has been stopped, you can restart
it.
Procedure
1. To start a specified synchronous replication session, type the following command
syntax:
$ nas_syncrep -start {-all|<name>|id=<id>}
where:
-start = starts the specified synchronous replication session. Specifying -all
starts all replication sessions.
Delete a synchronous replication session
49
Show information for VDM synchronous replication service

You can view either the VDM synchronous replication service information for a single
system or for both the source and destination systems. To view VDM synchronous
replication service information, do the following:
Procedure
$ nas_cel -syncrep -info {<cel_name>|id=<cel_id>} [-verbose]
where:
-info {<cel_name>|id=<cel_id>} [-verbose] = displays VDM synchronous replication
information about the specified VNX system.
Example:
To display VDM synchronous replication service information for a remote system with
synchronous replication enabled, type:
nas_cel -syncrep -info id=1 -verbose
Output:
id
= 1
name
= CS0_4224225
syncrep
= enabled
fsidrange
= 10001,20000
type
= MirrorView
local_storage
=
APM00144311642,MirrorView=nasdb_0784_642_mv,CloneGroup=nasdb_0784_6
42_clone
remote_storage
=
APM00143330784,MirrorView=nasdb_642_0784_mv,CloneGroup=nasdb_642_07
84_clone
service_status
=
local_to_remote = in_sync
remote_to_local = sync_in_progress (47%)
Results
Information about the VDM synchronous replication service between the source system
and the specified destination system is displayed.
Disable the VDM synchronous replication service

Before you begin
The following prerequisites should be in effect before you disable the VDM synchronous
replication service:
l
Synchronous replication service has been enabled.
Synchronous replication session does not exist.
To disable the VDM synchronous replication service, do the following:

Procedure
1. If you are using the Preserve RepV2 session for VDM MetroSync feature, you must first
remove the IP Replication sessions from sync-replicable pools, and then disable the
ReplicatorV2 Service.
50
a. Run the nas_replicate -delete <rep_session_name> -mode both

for each IP Replication session to remove from sync-replicable pools.
b. Run the nas_replicate -list command to verify that the sessions have
been deleted.
c. Run the nas_syncrep_rr -config -disable command to disable the
service.
2. View the list of synchronous replication sessions, and then remove all synchronous
replication sessions:
a. Run the nas_syncrep -list command.
b. Run the nas_syncrep -delete id=<id> command.
3. Change all source VDMs to non-sync-replicable.
a. Find all sync-replicable VDMs by typing:
nas_server -info -vdm -all
and checking whether the syncreplicable= option appears. The option does
not appear if the VDM is not set to sync-replicable.
Output:
id
= 1
name
= vdm1
acl
= 0
type
= vdm
server
= server_2
rootfs
= root_fs_vdm_vdm1
I18N mode = UNICODE
mountedfs = vdm1_fs2,vdm1_fs1,vdm1_fs3
member_of =
status
:
defined = enabled
actual = loaded, active
interface=vdm1 :cifs vdm
b. Set VDMs to non-sync-replicable.

Example:
nas_server -vdm vdm1 -option syncreplicable=no
Output:
id
= 1
name
= vdm1
acl
= 0
type
= vdm
server
= server_2
rootfs
= root_fs_vdm_vdm1
I18N mode = UNICODE
mountedfs = vdm1_fs2,vdm1_fs1,vdm1_fs3
member_of =
status
:
defined = enabled
actual = loaded, active
interface=vdm1 :cifs vdm

$ nas_cel -syncrep -disable {<cel_name>|id=<cel_id>}
where:
Disable the VDM synchronous replication service
51
-disable {<cel_name> | id=<cel_id>} = disables the VDM synchronous replication

with MirrorView feature on the specified VNX system.
Example:
To disable the VDM synchronous replication service, on the source system type:
nas_cel -syncrep -disable id=1
Output:
Now unmounting sync replica of NAS database...
done
Now deleting mountpoint for sync replica of NAS database...
done
Now deleting remote storage info...
done
Now removing NBS access to local server server_2...
done
Now removing NBS access to local server server_3...
done
Now deleting local Mirror and Clone...
done
Now disabling service (including deleting Mirror and Clone) on remote system...done
Now removing FSID range [10001,20000] on remote system...
done
Now removing FSID range [1000,10000] on local system...
done
Now removing other sync replication service settings on local system...
done
done
Modify a VDM from sync-replicable to non-sync-replicable

Before you begin
The following prerequisites should be in effect before you modify a VDM from syncreplicable to non-sync-replicable:
l
The specified VDM should be a sync-replicable VDM.
The specified VDM should not have a synchronous replication session on it.
To modify a VDM from sync-replicable to non-sync-replicable, do the following:

Procedure
$ nas_server -vdm <vdm_name> -option syncreplicable=<yes|no>
where:
-vdm <vdm_name> -option syncreplicable=<yes|no> = specifies whether the
VDM is sync-replicable.
Example:
To modify a VDM from sync-replicable to non-sync-replicable, type:
nas_server -vdm test_vdm -option syncreplicable=no
Output:
id
name
acl
type
server
rootfs
I18N mode
mountedfs
member_of
status
defined
52
=
=
=
=
=
=
=
=
=
:
=
80
test_vdm
0
vdm
server_2
root_fs_vdm_test_vdm
ASCII
enabled

Results
The sync-replicable flag on the VDM and pool are unset.
Modify a VDM from non-sync-replicable to sync-replicable

Before you begin
The following prerequisites should be in effect before you modify a VDM from non-syncreplicable to sync-replicable:
l
The rootfs of the specified VDM should be a split-log file system.
The underlying pool should meet the criteria of a sync-replicable NAS pool.
Note
If a VDM and the file systems on it are created before upgrading to VNX operating
environment (OE) for file version 8.1.8.130 or later, using the default log type (the default
before version 8.1.6 is common log), the VDM cannot be converted to sync-replicable.
To modify a VDM from non-sync-replicable to sync-replicable, do the following:
Procedure
$ nas_server -vdm <vdm_name> -option syncreplicable=<yes|no>
where:
-vdm <vdm_name> -option syncreplicable=<yes|no> = specifies whether the
VDM is sync-replicable.
Example:
To modify a VDM from non-sync-replicable to sync-replicable, type:
nas_server -vdm test_vdm -option syncreplicable=yes
Output:
id
= 80
name
= test_vdm
acl
= 0
type
= vdm
server
= server_2
rootfs
= root_fs_vdm_test_vdm
I18N mode = ASCII
mountedfs =
member_of =
status
:
defined = enabled
Results
The sync-replicable flag on the VDM and pool are set.
Modify a VDM from non-sync-replicable to sync-replicable
53
Delete a sync-replicable VDM

Before you begin
l
There is no synchronous replication session on the VDM.
The VDM that is being deleted cannot contain mounted file systems.
To delete a sync-replicable VDM, do the following:

Procedure
$ nas_server -delete <movername>
where:
-delete <movername> = deletes either the specified physical Data Mover entry from
the server table or deletes the VDM configuration.
Example:
To delete a sync-replicable VDM, type:
$ nas_server -delete my_syncrep1
Output:
id = 3
name = my_syncrep1
acl = 0
type = vdm
server =
rootfs = root_fs_my_syncrep1
I18N mode = UNICODE
mountedfs =
member_of =
status :
defined = enabled
actual = permanently unloaded
Results
The pool under the deleted VDM becomes a non-sync-replicable VDM pool as a result of a
successful Delete operation.
List information for VDM synchronous replication session

Before you begin
Either the trusted communication channel (Control Station-to-Control Station
communication) is ready between the two sites or the replicated NAS database is
synchronized.
You can list all the VDM synchronous replication sessions of which the local system is
either the active system or the standby system. To list the VDM synchronous replication
session information, do the following:
Procedure
1. At the local site, type the following command syntax:
$ nas_syncrep -list
54
where:
-list = displays all the configured synchronous replication sessions on the local
systems NAS database and those having the local system as the standby system in
the remote system's replicated NAS database.
Example:
To list the VDM synchronous replication session information, type:
nas_syncrep -list
Output:
id
5020
10030
name
my_syncrep1
my_syncrep2
vdm_name
my_vdm
my_vdm
remote_system
-->my_system1
<--my_system1
session_status
sync_in_progress
in_sync
Show information for VDM synchronous replication session

Before you begin
Either the trusted communication channel (Control Station-to-Control Station
communication) is ready between the two sites or the replicated NAS database is
synchronized.
To view VDM synchronous replication session information, do the following:
Procedure
1. At the local site, type the following command syntax:
$ nas_syncrep -info {-all|<name>|id=<id>} [-verbose]
where:
-info {all|<name>|id=<id>} [-verbose] = displays the status of a specific configured
synchronous replication session, or the status of all synchronous replication
sessions.
Example:
To display status of a specific configured synchronous replication session, type:
nas_syncrep -info my_syncrep1 -verbose
Output:
id
name
vdm_name
syncrep_role
local_system
local_pool
local_mover
remote_system
remote_pool
remote_mover
consistency_group
session_status
local_cg_state
local_cg_condition
remote_cg_state
remote_cg_conditoin
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
5020
my_syncrep1
my_vdm
active
my_system
my_pool1
server_2
my_system1
my_pool1
server_2
syncrep_72_0784_72_642
sync_in_progress (8%)
Synchronizing
Active
Synchronizing
Active
Show information for VDM synchronous replication session
55
Extend a sync-replicable NAS pool

You can add disk volumes into a sync-replicable NAS pool without a synchronous
replication session on it (see Extend a sync-replicable NAS pool (without synchronous
replication session) on page 56).
If an active VDM synchronous replication session exists, follow the instructions in Extend
a sync-replicable NAS pool (with synchronous replication session) on page 56 to
extend the pool.
Extend a sync-replicable NAS pool (without synchronous replication session)

Before you begin
A synchronous replication session has not been created on the sync-replicable VDM.
To extend a sync-replicable NAS pool, follow these rules:
l
You must specify the volume to extend the sync-replicable NAS pool.
The specified volumes must be disk volumes.
To add disk volumes into a sync-replicable NAS pool without a synchronous replication
session on it, do the following:
Procedure
1. Specify the volumes to extend the sync-replicable NAS pool by using the following
command syntax:
nas_pool -xtend <name> [-volumes
<volume_name>[,<volume_name>,...]]
where:
<name> = name of the storage pool
<volume_name> = name of one or more volumes
Example:
To extend the sync-replicable NAS pool, type:
nas_pool -xtend VDM1_Pool -volumes d17,d18,d19,d20,d21
Results
The sync-replicable NAS pool is extended with the new volumes.
Extend a sync-replicable NAS pool (with synchronous replication session)

Before you begin
A synchronous replication session has been created on the sync-replicable VDM.
To extend a sync-replicable NAS pool, follow these rules:
56
You must specify the volume to extend the sync-replicable NAS pool.
Verify that the synchronous replication session's status is in_sync before extending a
pool by running the nas_syncrep -info <session_name> command.
The automated failover service cannot be running during an extension operation.

Stop the service if it is still running.
If the synchronous replication session is failed over, before extending the pool, you
must ensure that the session is cleaned by using the nas_syncrep -Clean
<session_name> command.
To add disk volumes into a sync-replicable NAS pool with a synchronous replication
session on it, do the following:
Procedure
1. On the main VDM MetroSync Manager window, verify that the Service State is
Stopped. If not, click Stop.
2. In Unisphere, navigate to Storage > LUNs. Click Create and provision additional LUNs.
3. Add the LUNs to the ~filestorage Storage Group.
4. Click Rescan Storage Systems from the task list. This may take a few minutes to
complete.
5. To view newly added dVols, run the nas_disk -list command. Note that the new
dVols are now available for use.
6. Repeat steps 1 to 4 on the target VNX. Make sure that you create the same size LUNs
on both systems.
7. On your source VNX, run the following script to create mirrors for the new LUNs:
/nas/sbin/syncrep/syncrep_modify_mirror -create
-session <session_name> -local_disk_volumes
<volume_name>[,<volume_name>,...] -remote_disk_volumes
where:
<session_name> = name of the VDM syncrep session
<volume_name> = name of the volume or volumes to use, separated by commas
Example:
/nas/sbin/syncrep/syncrep_modify_mirror -create -session
VDM1_Session -local_disk_volumes d17,d18,d19,d20,d21
-remote_disk_volumes d17,d18,d19,d20,d21
Output:
Now creating mirror(s)...
Now waiting for mirror(s) to complete initial copy...
Done
done
done
Once the mirrors are created, the initial synchronization starts and the progress is
displayed. Allow the initial synchronization to complete and then proceed to the next
step.
Note
The initial copy operation takes longer for thick LUNs than for thin LUNs.
8. On your source VNX, run the following script to add the mirrors to the Synchronous
Replication sessions Consistency Group:
/nas/sbin/syncrep/syncrep_modify_cg -addmirror
-session <session_name> -local_disk_volumes
<volume_name>[,<volume_name>,...] -remote_disk_volumes
Extend a sync-replicable NAS pool (with synchronous replication session)
57
Example:
/nas/sbin/syncrep/syncrep_modify_cg -addmirror -session
VDM1_Session -local_disk_volumes d17,d18,d19,d20,d21
-remote_disk_volumes d17,d18,d19,d20,d21
9. On your target VNX, extend the pool by using the -skip_session_check option:
nas_pool -xtend <name> -volumes <volume_name>
[,<volume_name>,...] -skip_session_check
Example:
nas_pool -xtend VDM1_Pool -volumes d17,d18,d19,d20,d21
-skip_session_check
10. On your source VNX, extend the pool by using the -skip_session_check option.
Results
The NAS pool has been expanded on both sides without requiring a full synchronization.
The data connections between NFS and CIFS clients and servers are not impacted.
Shrink a sync-replicable NAS pool

A sync-replicable NAS pool cannot be shrunk if there is an active VDM synchronous
replication session. You can remove disk volumes from a sync-replicable NAS pool
without a synchronous replication session on it (see Shrink a sync-replicable NAS pool
(without synchronous replication session) on page 58).
If an active VDM synchronous replication session does exist, follow the instructions in
Shrink a sync-replicable NAS pool (with synchronous replication session) on page 59 to
delete the session, shrink the pool, and then recreate the session.
Shrink a sync-replicable NAS pool (without synchronous replication session)

Before you begin
A synchronous replication session has not been created on the sync-replicable VDM.
To shrink a sync-replicable NAS pool, follow these rules:
l
You must specify the volume (not the pool) to shrink the sync-replicable NAS pool.
To move some disk volumes out of a sync-replicable NAS pool without a synchronous
replication session on it, do the following:
Procedure
1. Specify the volumes to shrink the sync-replicable NAS pool by using the following
command syntax:
nas_pool -shrink <name> [-volumes
<volume_name>[,<volume_name>,...]]
where:
<name> = name of the storage pool
<volume_name> = name of one or more volumes
Example:
58
To shrink the sync-replicable NAS pool, type:

nas_pool -shrink VDM1_Pool -volumes d21
Results
The specified volumes are removed from the sync-replicable VDM's NAS pool.
Shrink a sync-replicable NAS pool (with synchronous replication session)

Before you begin
A synchronous replication session has been created on the sync-replicable VDM.
To shrink a sync-replicable NAS pool, follow these rules:
l
You must specify the volume to shrink the sync-replicable NAS pool.
The automated failover service cannot be running during a shrink operation. Stop the
service if it is still running.
To move some disk volumes out of a sync-replicable NAS pool with a synchronous
replication session on it, do the following:
Procedure
2. Delete the synchronous replication session on the VDM. See Delete a Sync Replication
session on page 49.
3. Specify the volumes to shrink the sync-replicable NAS pool using nas_pool.
For detailed information about nas_pool, refer to the nas_pool section of the EMC
VNX Command Line Interface Reference for File.
4. Shrink the standby pool of the original synchronous replication session by specifying
the volumes using nas_pool.
5. Recreate the synchronous replication session on the VDM/sync-replicable NAS pool.
See Create a VDM synchronous replication session on page 34.
Results
The specified volumes are removed from the sync-replicable VDM's NAS pool.
Configuring for added secondary Control Stations

Before you begin
If you add secondary Control Stations to your VNX2 systems after VDM synchronous
replication is enabled and running, you must add these Control Stations to the VDM
synchronous replication configuration.
l
Secondary Control Stations have been installed on the source and destination VNX2
Systems.
The NTP Service is configured on the source and destination secondary Control
Stations.
To add secondary Control Stations to your VDM synchronous replication configuration, do

the following:
Shrink a sync-replicable NAS pool (with synchronous replication session)
59
Procedure
1. Log in to the source primary Control Station as root.
2. Add the source secondary Control Station to the VDM synchronous replication
configuration.
Example:
Type:
# /nas/sbin/syncrep/syncrep_config_cs1 -cel_id 1
Output:
Copying NBS configuration file to the secondary CS ...
done
Rebooting the secondary CS to enable NBS configuration ...
done
3. Log in to the destination primary Control Station as root.

4. Add the destination secondary Control Station to the VDM synchronous replication
configuration.
Example:
Type:
# /nas/sbin/syncrep/syncrep_config_cs1 -cel_id 1
Output:
Copying NBS configuration file to the secondary CS ...
done
Rebooting the secondary CS to enable NBS configuration ...
done
5. On the source VNX2 system, configure IP aliasing.

See IP aliasing for VNX with two Control Stations on page 20 for information about IP
aliasing.
6. On the destination VNX2 system, configure IP aliasing.
7. If you will use a new IP address for IP aliasing instead of the existing CS0 IP address,
run the following command on the source VNX2 system to update the IP alias of the
destination VNX2 system, then run the command on the destination VNX2 system to
update the IP alias of the source VNX2 system:
nas_cel -modify <remote_vnx_name> -passphrase nasadmin -ip
<remote_cs_alias_ip>
Updating VNX OE software

When the VDM synchronous replication feature is operational, use the following
sequence of tasks to update the VNX OE software:
1. On the destination site, update the VNX OE for File.
2. On the destination site, update the VNX OE for Block.
3. On the source site, update the VNX OE for File.
4. On the source site, update the VNX OE for Block.
After you finish updating the VNX OE software, verify that the VDM synchronous
replication feature is operational by using nas_syncrep -list.
60
CHAPTER 6
Topics include:
l
l
l
l
l
l
About Replicator V2 sessions................................................................................ 62

Enable Preserve RepV2 session for VDM MetroSync...............................................62
Create a ReplicatorV2 session on a sync-replicable VDM....................................... 62
Show Preserve RepV2 session for VDM MetroSync status...................................... 63
Disable Preserve RepV2 session for VDM MetroSync............................................. 63
Restore ReplicatorV2 sessions.............................................................................. 64
61
About Replicator V2 sessions

You can have both ReplicatorV2 and VDM synchronous replication with MirrorView/S
sessions on the same VDM. You have the ability to replicate to a third site using
ReplicatorV2, and preserve those DR connections upon failing over or reversing a
This feature, called Preserve RepV2 sessions for VDM MetroSync, requires:
l
enabling the VDM MetroSync service before implementing.
creating ReplicatorV2 sessions from a MetroSync VDM to a non-MetroSync system.
Enable Preserve RepV2 session for VDM MetroSync

Before you begin
You can enable this feature on a VNX only if:
l
The VNX has the VDM synchronous replication service enabled.
The Data Movers have the correct operating software version.
The system has the ReplicatorV2 license enabled.
ReplicatorV2 sessions are asynchronous.

Procedure
1. To enable the Preserve RepV2 sessions for VDM MetroSync feature, type the following
command:
nas_syncrep_rr -config -enable
Output:
Enabling PreserveRepv2 on remote array
PreserveRepv2 enabled successfully
Enabling PreserveRepv2 on local array
PreserveRepv2 enabled successfully
Create a ReplicatorV2 session on a sync-replicable VDM

Before you begin
A VDM MetroSync synchronous replication session must already be created.
Procedure
1. Create the following Control Station-to-Control Station relationships by using the
nas_cel command.
l
System A to System C
System B to System C
System C to System A
System C to System B
2. Create the following interfaces by using the server_ifconfig command.
62
System A
System B
2x on System C
3. Create the following interconnects by using the nas_cel interconnect

command.
l
System A to System C
System B to System C
System C to System A
System C to System B
4. On System C:
a. Create a new pool.
b. Create LUNs.
c. Add LUNs to the ~filestorage Storage Group.
d. Run a Rescan.
e. Create a new VDM.
f. If using CIFS, make sure that the CIFS service is started.
5. On System A, create a new ReplicatorV2 session for a file system from System A to
System C. Put the destination file system on the VDM.
6. On System B:
a. Run either a reverse or failover operation on the VDM sync rep session.
b. Run the nas_syncrep_rr restore -vdm <Name> command.
c. Run the nas_syncrep_rr -free_intermediate_data command.
d. Run the nas_replicate -list command.
Results
The replication session should now appear on System B.
Show Preserve RepV2 session for VDM MetroSync status

Procedure
1. To show the Preserve RepV2 session for VDM MetroSync status, type the following
command:
nas_syncrep_rr -config -info
Output:
Configuration for PreserveRepv2 on remote array (cel_id = 1):
enabled
Configuration for PreserveRepv2 on local array: enabled
Disable Preserve RepV2 session for VDM MetroSync

Show Preserve RepV2 session for VDM MetroSync status
63
Procedure
1. To disable Preserve RepV2 session for VDM MetroSync, type the following command:
nas_syncrep_rr -config -disable
Output:
Disabling PreserveRepv2 on remote array
PreserveRepv2 disabled successfully
Disabling PreserveRepv2 on local array
PreserveRepv2 disabled successfully
Restore ReplicatorV2 sessions

Before you begin
You must have the Preserve RepV2 session for VDM MetroSync feature enabled.
You must have ReplicatorV2 sessions configured on the synchronously-replicated VDM.
Procedure
1. To restore ReplicatorV2 sessions, use the following command syntax from the VNX
system to where VDM MetroSync sessions have been failed over or reversed:
nas_syncrep_rr
| -restore {-all | -vdm {<vdm_name> | id=<vdm_id>}}
where:
-all = restores all ReplicatorV2 sessions on all VDMs.
<vdm_name> = the name of a specific VDM on which you want to restore ReplicatorV2
sessions. The VDM specified must be a sync-replicable VDM.
<vdm_id> = the ID of a specific VDM on which you want to restore ReplicatorV2
sessions. The VDM specified must be a sync-replicable VDM.
Using the -all option may take some time for the operation to complete. Check the
operation's status by running the nas_task -info <task_id> command.
For example:
$ nas_task -info 20478
Task Id
= 20478
Celerra Network Server = filesim8116cs0
Task State
= Succeeded
Movers
=
Description
= Repv2
id=237_BB0050562C7C86_0000_242_BB0050562C7C82_0000 Restored.
Error 13422034949: Internal
error.
Restore Repv2 id=247_BB0050562C7C87_0000_252_BB0050562C7C85_0000
failed.
Originator
= root@cli.localhost
Start Time
= Tue May 12 22:27:28 EDT 201
End Time
= Tue May 12 22:27:43 EDT 201
Schedule
= n/a
Response Statuses
=
64
CHAPTER 7
Topics include:
l
l
l
l
l
l
l
l
l
l
l
l
l
The VDM MetroSync Manager configuration wizard............................................... 66

Configure a synchronous replication session's failover policy................................66
Configure a synchronous replication session's failover priority.............................. 68
Select VDM IP addresses to monitor...................................................................... 68
Start the VDM MetroSync service...........................................................................68
Stop the VDM MetroSync service........................................................................... 69
Manually failover a synchronous replication session............................................. 69
Manually reverse a synchronous replication session............................................. 70
Manually restore a synchronous replication session..............................................70
Collect logs........................................................................................................... 70
Discover monitored objects...................................................................................71
Check status......................................................................................................... 71
Show synchronous replication status.................................................................... 71
65
The VDM MetroSync Manager configuration wizard

After you install the VDM MetroSync Manager, the first time it opens, the configuration
wizard starts. With this wizard you can:
l
Configure storage systems
Configure failover operations:

n
Set a VDM Network to "Failed" when either All network interfaces fail or Any VDM
network interface fails. This setting applies for each VDM; failover occurs on one
or more sessions that have failed.
If VDM MetroSync Manager cannot failover, set the VDM failover retry count.
VDM MetroSync Manager sends a Ping request to a specified remote Target IP

Address to determine if it is available, or if it has been isolated from the network.
If it does not receive an answer to the Ping request for the IP, it assumes the VDM
MetroSync Manager host has been isolated and automatic failover cannot be
performed. To ensure that a Ping request to a remote Target IP Address is
received, use a permanent, reliable IP address.
Configure SMTP (email) alerts. If you are not configuring SMTP, you must clear the
checkbox.
Optionally configure pre-failover and post-failover scripts.
View a summary page of your configuration choices.
Configure a synchronous replication session's failover policy

Before you begin
l
Systems must be imported into VDM MetroSync Manager, and synchronous

replication sessions must be configured on those systems.
The VDM MetroSync service must be stopped before you can set a failover policy for a
VDM session.
You can configure a synchronous replication session to failover automatically when the
VDM MetroSync service is started, or you can manually run failover or reverse operations.
Monitored events on page 66 identifies the events that are return warnings, and the
events that cause failovers:
Table 2 Monitored events
Event
66
Warning
Failure
Description
Remote Ping
Check the remote IP ping
Primary Site CS0
Check the /nbsnas mount on

the primary site Control
Station
Primary Site CS1

the primary site standby
Control Station
Table 2 Monitored events (continued)
Event
Warning
Failure
Description
Secondary Site CS0

the secondary site Control
Station
Secondary Site CS1

the secondary site standby
Control Station
Primary Site SPA
Check the SPA status of the

primary site
Primary Site SPB
Check the SPB status of the

primary site
Secondary Site SPA
Check the SPA status of the

secondary site
Secondary Site SPB
Check the SPB status of the

secondary site
Primary Site Data

Mover
Secondary Site Data

Mover
Check the Data Mover status

of the primary site
Check the Data Mover status
of the secondary site
VDM interface check
Send a Ping request to

interfaces on a VDM under
replication
VDM file system check
Access a file system mounted

on a VDM under replication
VDM Local LUN status

check
Check whether the status of

the local LUNs used by the
VDM are either ERROR or
DEGRADED
VDM Remote LUN

status check
Check whether the status of

the remote LUNs used by the
VDM are either ERROR or
DEGRADED
SyncRep interconnection check
Check the inter-connection

status of the synchronous
replication session
SyncRep session
check
Check the synchronous

replication session status
Procedure
1. On the main VDM MetroSync Manager window, select a VDM session for which you
want to set a policy.
2. Click the Edit (pencil) icon.
3. Set Failover Policy to either Auto or Manual.
Configure a synchronous replication session's failover policy
67
The Failover Policy is effective once the VDM MetroSync service is started. By default,
automatic failover is configured for all monitored VDM Sessions. To control certain
sessions manually, select specific VDM sessions and set each policy to Manual.
4. Click OK.
Configure a synchronous replication session's failover priority

Before you begin
l
The VDM MetroSync service must be stopped before you can set a failover priority for
a synchronous replication session.
A synchronous replication session must be configured as Auto before configuring a

failover priority.
Procedure
want to set or change a failover priority.
2. Use the Up and Down arrows to move the session up or down on the priority list.
Alternatively, you can click the Edit (pencil) icon, and then select the Failover Priority
from the drop-down list.
3. Click OK.
Select VDM IP addresses to monitor

Before you begin
The VDM MetroSync service must be stopped before you can set IP addresses to monitor.
Procedure
want to manage.
2. Click the Edit (pencil) icon.
3. In Monitor Network, select either the All IP Address checkbox to monitor all IP
addresses, or select specific IP addresses from the list box.
Note
If no IP addresses are selected, the Failover Policy changes to Manual.

4. Click OK.
Results
Any network interfaces that are not selected are not monitored by VDM MetroSync
Manager. A failure on them will not be detected, and will not initiate an automatic
failover.
Start the VDM MetroSync service

To start the VDM MetroSync service:
68
Procedure
1. Open the VDM MetroSync Manager software.
2. On the main window, click Start.
Results
The service that runs is called "EMC VDM MetroSync service" with a description of "EMC
VDM MetroSync Manager".
When the VDM MetroSync service is running, the VDM MetroSync Manager monitors all
configured VDM services on the primary site. When a VDM service failure is detected by
the VDM MetroSync Manager, the failed VDMs sessions are failed over from the primary
site to the secondary site. If multiple VDMs failed, the VDMs are failed over based on the
configured priority. If the failover of a session fails, the VDM MetroSync Manager
continues failing over lower-priority sessions before retrying.
Note
If a local standby Data Mover is configured, the service delays the failover operation for
20 seconds to allow for the local standby to be initiated. If local failover is detected, then
the service waits an additional 300 seconds before issuing the next check to allow the
local failover to complete.
If a local standby Data Mover is not configured, these delays are skipped.
Stop the VDM MetroSync service

To stop the VDM MetroSync service:
Procedure
1. On the main VDM MetroSync Manager window, click Stop.
Manually failover a synchronous replication session

Before you begin
The automated failover service cannot be running during a manual failover operation.
Note
Do not run a failover operation if the source system is accessible. If it is available, run a
reverse operation instead.
Procedure
2. Select one or more VDMs that you want to failover from your source array to the
destination array.
3. Click Failover.
After you finish
Once the failover is complete, a message window opens to show that the priority set for
each VDM has changed.
Stop the VDM MetroSync service
69
Manually reverse a synchronous replication session

Before you begin
The automated failover service cannot be running during a manual Reverse operation.
A manual reverse operation allows you to manually select all VDMs or a subset of VDMs
to move to your destination system.
Procedure
2. Select one or more VDMs that you want to move from the source VNX to the
destination VNX.
3. Click Reverse.
After you finish
Once the reverse is complete, a message window opens to show that the priority set for
each VDM has changed.
Manually restore a synchronous replication session

A manual restore operation allows you to manually restore any reversed or failed over
VDMs back to their original source VNX. If necessary as part of the restore operation, a
clean operation is also performed.
Before you begin
l
VDMs must be in the Reversed or Failed over state before you can run a Restore
operation.
If the VDM has been failed over, you must have resolved the issue with the source
system/VDM that caused the failover.
Procedure
2. Select one or more VDMs with a Reversed or Failed over state that you want to move
from the destination VNX back to the source VNX.
3. Click Restore.
Collect logs
The Main Log window, shown at the bottom of the main VDM MetroSync Manager
window, contains information about the actions performed when using the VDM
MetroSync Manager. The Main Log window information is captured in the
vmsm.main.log file, found in the C:\<Program Files>\EMC\VMSM\log folder.
Note that the <Program Files> folder name depends on the version of Windows
being used.
To create a collection log to help with troubleshooting issues:
70
Procedure
1. On the main VDM MetroSync Manager window, select Help > Log Collection.
2. By default, the Log Collection tool creates a zip file, and saves the collection's zip file
to the Desktop.
Discover monitored objects

If the monitored storage system configuration changes, such as adding sessions,
changing IP addresses, or upgrading OE software, you must discover the configuration
again.
Procedure
2. To discover monitored objects, select Management > Discover.
Results
After discovery, the VDM status of VDMs on the Primary site will be shown as "--". The
VDM status of VDMs on the Secondary site will be shown as "Reversed".
Check status
Before you begin
You must have existing VDM MetroSync sessions to check their status.
Procedure
1. On the main VDM MetroSync Manager window, select Management > Check Status.
Status information appears in the VDM MetroSync Manager Main log which displays
in the lower pane of the window. The earliest messages display at the beginning of
the log, and the latest messages display at the end of the log.
l
Fatal, Error, and Warning messages are highlighted within the VDM MetroSync
Manager Main log. If you want to change the color for a highlight, or add messages
to be highlighted, click Highlighting.
If you want to display only the status messages with highlights, select Only
Highlighted.
To always display the most current log entries first, select Follow Tail. If you do not
select Follow Tail, then the oldest entries are displayed first.
Show synchronous replication status

To view the states and events for synchronous replication sessions:
Procedure
1. On the main VDM MetroSync Manager window, select one or more synchronous
replication sessions.
2. Click the information icon.
Discover monitored objects
71
72
CHAPTER 8
Service checklists
Each topic in this chapter provides a checklist which can be used to determine if there
are any issues that need to be resolved with your VDM synchronous replication for
disaster recovery configuration.
Topics include:
l
l
Enable VDM synchronous replication service checklist.......................................... 74

VDM synchronous replication session checklist.................................................... 74
Service checklists
73
Service checklists
Enable VDM synchronous replication service checklist

After enabling the VDM synchronous replication service, answer the questions in the
following checklist to determine if there are issues with your service setup. If you answer
no to any of these questions, you should troubleshoot those issues to resolve them.
Table 3 VDM synchronous replication service setup checklist
Service setup
yes/no
For VNX Systems with dual Control Stations, an IP alias should have been
created and used to build the nas_cel connection. For VNX Systems with dual
Control Stations, is the IP alias reporting to be in the UP state? (Use the
nas_config -IPalias -list command to determine the status.)
Does the nas_cel connection from System 1 to System 2 exist? (Use the
nas_cel -list command to determine the status.)
Also verify that the nas_cel connection from System 2 to System 1 exists.
Note
For VNX Systems with dual Control Stations, the nas_cel connection should
have been configured using an IP alias. ID 0 is the self-identifier of the Control
Station and should not be mistaken for the connection between both systems.
Is the MirrorView connection enabled between both systems?
Are the Write Intent Logs configured on both systems?
Are the Clone Private LUNs configured on both systems?
Is the VDM Synchronous Replication service enabled? (Use the nas_cel syncrep -list command to determine the status.)
Note
Under the syncrep column, the service should be showing 'enabled' for the
appropriate nas_cel ID.
Run a /nas/bin/nas_checkup on both VNX Systems. Are the VNX Systems in a
healthy state?
VDM synchronous replication session checklist

After creating each VDM synchronous replication session, answer the questions in the
following checklist to determine if there are issues with the replication session creation.
If you answer no to any of these questions, you should troubleshoot those issues to
resolve them.
74
Service checklists
Table 4 VDM synchronous replication session creation checklist
VDM replication session creation
yes/no
Is the VDM replication session state either sync in progress or in sync? (Use
the nas_syncrep -list command to determine the status.)
Are all of the VDM network interfaces pingable? (Use the ping <interface
IP address> command to determine the status.)
Are all of the CIFS or NFS shares accessible? (Request that the customer
provide this information.)
Run a /nas/bin/nas_checkup on both VNX Systems. Are the VNX Systems in a
healthy state?
VDM synchronous replication session checklist
75
Service checklists
76
CHAPTER 9
Troubleshooting
As part of an effort to continuously improve and enhance the performance and

capabilities of its product lines, EMC periodically releases new versions of its hardware
and software. Therefore, some functions described in this document may not be
supported by all versions of the software or hardware currently in use. For the most up-todate information on product features, refer to your product release notes.
If a product does not function properly or does not function as described in this
document, contact your EMC Customer Support Representative.
Problem Resolution Roadmap for VNX contains additional information about using EMC
Online Support and resolving problems.
Topics included in this chapter are:

l
l
l
l
l
l
EMC E-Lab Interoperability Navigator.....................................................................78

Retrieve information from log files......................................................................... 78
NAS database mirrors are out of sync.................................................................... 78
How to recover when all Data Movers are panicking...............................................79
Error messages......................................................................................................80
EMC Training and Professional Services................................................................ 80
Troubleshooting
77
Troubleshooting
EMC E-Lab Interoperability Navigator

The EMC E-Lab Interoperability Navigator is a searchable, web-based application that
provides access to EMC interoperability support matrices. It is available on EMC Online
Support at http://Support.EMC.com. After logging in, in the right pane under Product and
Support Tools, click E-Lab Navigator.
Retrieve information from log files

System messages are reported to the system log files. To retrieve information from log
files:
l
Check the system log (sys_log) by using the nas_logviewer command.
Check the server log (nas_server.log) by using the server_log command.
Check the command error log (cmd_log.err) for message information.
Check the syncrep log (nas_syncrep.log) for message information.
Check the VDM MetroSync Manager's Main log (vmsm.main.log) for status
information.
Note
In the case of the syncrep log, during a reverse/failover operation, the level will be
changed to DEBUG and it will be changed back after the reverse/failover operation
finishes.
Checks have been added to nas_checkup for synchronous replication health. If an error
or warning is detected during a scheduled nas_checkup run, it will be included in one
single Checkup alert. The alert can be viewed through Unisphere.
NAS database mirrors are out of sync

If you receive an error that mirrors in the NAS database are not in a synchronous state,
use this procedure to resolve the synchronous replication service error.
Procedure
1. To verify the service_status of your synchronous replication session, run the following
command:
nas_cel -syncrep -info -all -verbose
id
name
syncrep
fsidrange
=
=
=
=
id
name
syncrep
fsidrange
type
local_storage
=
=
=
=
=
=
remote_storage
service_status
78
0
NAS12
initialized
1000,16000
3
NAS33
enabled
16001,32000
MirrorView
CKM00152402428,MirrorView=nasdb_428_0109_mv,
CloneGroup=nasdb_0109_428_clone
= CETV2151700109,MirrorView=nasdb_0109_428_mv,
CloneGroup=nasdb_428_0109_clone
=
Troubleshooting
local_to_remote = out_of_sync
remote_to_local = in_sync
If either the local or remote sessions are out_of_sync, note the MirrorView and
CloneGroup names.
2. Run the following command:
naviseccli -h spa mirror -sync -syncimage -name <mirror_name>
where <mirror_name> is the MirrorView name.

3. Run the following command:
naviseccli -h spa clone -syncclone -name <clone_name>
where <clone_name> is the Clone Group name.

4. Repeat step 1 to confirm the service status is now in_sync.
How to recover when all Data Movers are panicking

After a failover operation, if the original active Data Mover for the VDM synchronous
replication session still works, the Data Mover may run into a rolling panic because the
underlying LUNs become read-only. If all source Data Movers have synchronous
replication sessions, all the Data Movers can run into a rolling panic. In this case, the NAS
service is not working and the /nas folder is not accessible.
Perform a PXE reboot operation to return the Data Movers to a normal state by using the
following procedure.
Procedure
1. Stop the NAS service. Type:
$ /sbin/service nas stop
2. Start the PXE service. Type:

$ /nasmcd/sbin/t2pxe -s -R <cnt#>
where <cnt#> is the number of Data Movers in this cabinet.

3. Perform a PXE reboot of the Data Mover. Type:
$ /nasmcd/sbin/t2tty -p <slot_num>
where <slot_num> is the slot number of the Data Mover. PXE reboot only needs to be
done for one Data Mover.
4. After rebooting the Data Mover, verify that the Data Mover is accessible by typing:
$ /nasmcd/sbin/getreason
6 - slot_0 control station ready
4 - slot_2 configured
4 - slot_3 configured
After one Data Mover gets into a configured or contacted state, the /nas folder can be
accessed.
5. Stop the PXE service. Type:
$ /nasmcd/sbin/t2pxe -e
How to recover when all Data Movers are panicking
79
Troubleshooting
6. Clean all synchronous replication sessions. Type:

$ nas_syncrep -Clean -all
7. Reboot the Control Station. Type:

$ reboot -fn
Results
After the Control Station reboot, the NAS service should be working and all Data Movers
will be in the contacted state.
Error messages
All event, alert, and status messages provide detailed information and recommended
actions to help you troubleshoot the situation.
To view message details, use any of these methods:
l
Unisphere software:
n
CLI:
n
Type nas_message -info <MessageID>, where <MessageID> is the message

identification number.
Celerra Error Messages Guide:

n
Right-click an event, alert, or status message and select to view Event Details,
Alert Details, or Status Details.
Use this guide to locate information about messages that are in the earlier-release
message format.
EMC Online Support:

n
Use the text from the error message's brief description or the message's ID to
search the Knowledgebase on EMC Online Support. After logging in to EMC Online
Support, locate the applicable Support by Product page, and search for the error
message.
EMC Training and Professional Services

EMC Customer Education courses help you learn how EMC storage products work
together within your environment to maximize your entire infrastructure investment. EMC
Customer Education features online and hands-on training in state-of-the-art labs
conveniently located throughout the world. EMC customer training courses are developed
and delivered by EMC experts. Go to EMC Online Support at http://Support.EMC.com for
course and registration information.
EMC Professional Services can help you implement your system efficiently. Consultants
evaluate your business, IT processes, and technology, and recommend ways that you can
leverage your information for the most benefit. From business plan to implementation,
you get the experience and expertise that you need without straining your IT staff or hiring
and training new personnel. Contact your EMC Customer Support Representative for more
information.
80
APPENDIX A
Topics include:
l
Update the FSID range minimum size.................................................................... 82
81
Update the FSID range minimum size

Procedure
1. In order to change the FSID range minimum size (default is 8192), copy the following
entries from the /nas/sys/nas_param file to the /nas/site/nas_param file:
l
#fsidrange:<min_size>:
fsidrange:8192:
2. Using a vi editor, edit the fsidrange line of the /nas/site/nas_param to change

the <min_size> from 8192 to the value that you want.
Example:
fsidrange:2100:
82

VNX

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

VNX

Hochgeladen von

Copyright:

Verfügbare Formate

EMC VNX Series

Using VDM MetroSync with VDM MetroSync

About VDM MetroSync...................................................................................10

VDM synchronous replication logical entities................................................ 16

VDM synchronous replication setup information........................................... 20

Create data LUNs for NAS resources.............................................................. 28

Managing by using the VNX for File CLI

About using the VNX for File CLI for managing................................................42

Failover a synchronous replication session....................................................45

Working with ReplicatorV2 sessions

About Replicator V2 sessions........................................................................ 62

Using VDM MetroSync Manager

The VDM MetroSync Manager configuration wizard....................................... 66

Enable VDM synchronous replication service checklist.................................. 74

EMC E-Lab Interoperability Navigator.............................................................78

Changing FSID ranges

Update the FSID range minimum size............................................................ 82

Addresses practices not related to personal injury.

Presents information that is important, but not hazard-related.

About VDM MetroSync...........................................................................................10

About VDM MetroSync

Automatically monitor configured sync-replicated VDMs.

Trigger automatic failover of a selected sync-replicated VDM on a source VNX2 system

All file systems must use Split Log (default).

Two VNX2 systems

To create a MirrorView link between systems, use one of the following:

FC Direct-connect cables between SPA-to-SPA, and SPB-to-SPB

FC switch-attached, requiring FC zone source and target SPAs; and a separate

iSCSI protocol to configure an IP connection between SPs on source and target

For VDM MetroSync Manager:

For VMs on a VDM MetroSync Manager server, a minimum of 2 cores with 2 GB

2 GB for log files

Restrictions and limitations

Stop the VDM MetroSync Manager service:

Before upgrading SPs, including non-disruptive upgrades.

During failover, if a Consistency Group beneath a synchronous replication session is

VDM MetroSync is not supported on systems where Cabinet-level File DR solutions

Shrinking a sync-replicable NAS pool is not allowed if there is an active VDM

NDMP backup on file systems on a sync-replicable NAS pool is supported; however,

A sync-replicable VDM cannot be migrated using nas_migrate. A workaround for this

Data Mover configurations:

Local password and group

Cabinet level service:

Restrictions and limitations

User interface choices

EMC VNX Command Line Interface Reference for File

Online VNX man pages

Using MirrorView/Synchronous with VNX for File for Disaster Recovery

Configuring and Managing CIFS on VNX

Configuring NFS on VNX

Managing Volumes and File Systems for VNX Manually

Using VNX SnapSure

Configuring Virtual Data Movers on VNX

Parameters Guide for VNX for File

Virtual Data Movers on EMC VNX (white paper)

EMC VNX Replication Technologies (white paper)

VDM MetroSync for VNX2 - A Detailed Review (white paper)

VDM synchronous replication logical entities........................................................ 16

VDM synchronous replication logical entities

Sync-replicable NAS pool

Standby pool (destination site)

Sync-replicable NAS pool

Its members must be disk volumes.

It has one and only one sync-replicable VDM rootfs on it.