Welcome to Unity Replication.

Copyright ©2016 EMC Corporation. All Rights Reserved. Published in the USA. EMC believes the information in this publication is accurate as o f 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. The trademarks, logos, and service marks (collectively "Trademarks")
appearing in this publication are the property of EMC Corporation and other parties. Nothing contained in this publication sh ould be construed as granting any license or right to use any
Trademark without the prior written permission of the party that owns the Trademark.

EMC, EMC² AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager,
AutoStart, AutoSwap, AVALONidm, Avamar, Bus-Tech, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC CertTracker. CIO Connect,
ClaimPack, ClaimsEditor, Claralert ,cLARiiON, ClientPak, CloudArray, Codebook Correlation Technology, Common Information Model, Compuset, Compute Anywhere, Configuration
Intelligence, Configuresoft, Connectrix, Constellation Computing, EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge , Data Protection Suite. Data Protection Advisor, DBClassify, DD
Boost, Dantz, DatabaseXtender, Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document Sciences, Documentum, DR Anywhere, ECS, elnput, E-Lab,
Elastic Cloud Storage, EmailXaminer, EmailXtender , EMC Centera, EMC ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint, FirstPass, FLARE,
FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, Illuminator , InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel
Express, Invista, Ionix, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Multi-Band
Deduplication,Navisphere, Netstorage, NetWorker, nLayers, EMC OnCourse, OnAlert, OpenScale, Petrocloud, PixTools, Powerlink, PowerPath, PowerSnap, ProSphere, ProtectEverywhere,
ProtectPoint, EMC Proven, EMC Proven Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN
Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, EMC Snap, SnapImage, SnapSure, SnapView, SourceOne, SRDF, EMC Storage Administrator, StorageScope, SupportMate, SymmAPI,
SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal Data Consistency, Vblock, Velocity, Viewlets, ViPR,
Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, Virtualize Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, VSAM I/O
PLUS, VSET, VSPEX, Watch4net, WebXtender, xPression, xPresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-Friction Enterprise Storage.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 1

 This course covers Unity Replication features for the EMC Unity platform. It includes
asynchronous replication for both block and file storage resources and synchronous
replication of block storage resources. The course provides an overview of the replication
feature, how replication sessions are created, managed, and used. It also includes the
feature capabilities. Demonstrations of replications are also included.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 2

 In this module, an overview of Unity Replication is provided. The architectures of
Asynchronous and Synchronous Replications are discussed and the benefits and capabilities
are listed for Unity Replication.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 3

 Unity Replication, a feature enabled with the Replication license, enables replication of Unity
storage resources; block storage LUNs, VMware Datastores, file storage file systems,
VMware NFS Datastores and NAS Servers. Remote replication, shown here, provides
storage resource replication between Unity systems for storage resources. The file-based
storage resources of VMware NFS Datastores, NAS Servers, and file systems are replicated
to a remote Unity system asynchronously. The block-based storage resources of VMware
VMFS datastores, LUNs and LUN Consistency Groups are replicated to a remote Unity
system in either an asynchronous or synchronous manner.

Remote Replication is one method that enables data centers to avoid disruptions in
operations. In a disaster recovery scenario, if the source site becomes unavailable, the
replicated data will still be available for access from the remote site. Remote Replication
uses a Recovery Point Objective (RPO) which is an amount of data, measured in units of
time to perform automatic data synchronization between the source and remote systems.
The RPO for asynchronous replication is configurable. The RPO for synchronous replication
is set to zero. The RPO value represents the acceptable amount of data that may be lost in
a disaster situation. The remote data will be consistent to the configured RPO value. The
minimum and maximum RPO values are 5 minutes and 1440 minutes (24 hours).

Remote Replication is also beneficial for keeping data available during planned downtime
scenarios. If a production site has to be brought down for maintenance or testing the
replica data can be made available for access from the remote site. In a planned downtime
situation, the remote data is synchronized to the source before being made available and
there is no data loss.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 4

 With Unity Replication, it is possible to asynchronously replicate storage resources locally
within the same Unity system as shown here. The storage resources are replicated from one
storage Pool to another within the same Unity system. The feature can be helpful should a
storage resource need to be moved for Pool capacity reasons or for changing the type of
storage the resource uses. For example, a resource could be moved from a Pool having
performance disks to a Pool having capacity disks for archival reasons.

The main focus of this training is with remote replication since it has more elements to
configure, create and manage.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 5

 The architecture for Unity Asynchronous Remote Replication is shown here. The graphic
illustrates a remote asynchronous replication session for a file system. The architecture is
the same for replicating any other file or block-based storage resource asynchronously.

Fundamental to remote replication is connectivity and communication between the source

and destination systems. A data connection is required to carry the replicated data and it is
formed from Replication Interfaces. They are IP-based connections established on each
system. A communication channel is also required to manage the replication session. The
management channel is established on Replication Connections. It defines the management
interfaces and credentials for the source and destination systems.

Asynchronous Replication architecture utilizes Unified Snapshots. The system creates two
snapshots for the source storage resource and two corresponding snapshots on the
destination storage resource. These system created snapshots cannot be modified. Based
on the replication RPO value the source snapshots are updated in an alternating fashion to
capture the source data state differences, known as deltas. The data delta for the RPO
timeframe is replicated to the destination. After the data is replicated the corresponding
destination snapshot is updated. The two corresponding snapshots capture a common data
state, known as a common base. The common base can be used to restart a stopped or
interrupted replication session.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 6

 The architecture for Unity Asynchronous Local Replication is shown here. The difference
between the local and remote architecture seen previously is that the local architecture
does not require the communications to a remote peer. The management and data
replication paths are all internal within the single system. Otherwise, local replication uses
Snapshots in the same manner. Local replication uses source and destination objects on the
two different Pools similar to how remote replication uses source and destination on two
different systems.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 7

 The asynchronous replication process is the same for local and remote replication. Shown
here is remote replication. The asynchronous replication of a storage resource has an initial
process followed by an ongoing synchronization process. The starting point is a data
populated storage resource on the source system that is available to production and has a
constantly changing data state.

The first step of the initial process for asynchronous replication is to create a storage
resource of the exact same capacity on the destination system. The storage resource is
created automatically by the system and contains no data.

In the next step, corresponding snapshot pairs are created automatically on the source and
destination systems. They capture point-in-time data states of their storage resource.

The first snapshot on the source system is used to perform an initial copy of its point-in-
time data state to the destination storage resource. This initial copy can take a significant
amount of time if the source storage resource contains a large amount of existing data.

Once the initial copy is complete, the first snapshot on the destination system is updated.
The data states captured on the first snapshots are now identical and form a common base.

Because the source storage resource is constantly changing, its data state is no longer
consistent with the first snapshot point-in-time. In the synchronization process, the second
snapshot on the source system is updated, capturing the current data state of the source.

A data difference, or delta is calculated from the two source system snapshots and a
differential copy is made from the second snapshot to the destination storage resource.

After the differential copy is complete, the second snapshot on the destination system is
updated to form a common base with its corresponding source system snapshot.

The cycle of differential copies continues for the session by alternating between the first

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 8

 and second snapshot pairs based on the RPO value. The first source snapshot is
updated, the data delta is calculated and copied to the destination, the first
destination snapshot is updated forming a new common base. The cycle repeats
using the second snapshot pair.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication ‹#›
 The architecture for Unity Synchronous Replication is shown here. The graphic illustrates a
remote synchronous replication session for a LUN. The architecture is the same for
replicating any other block-based storage resource synchronously.

The same fundamental remote replication connectivity and communication between the
source and destination systems seen earlier for asynchronous remote replication are also
required for synchronous replication. A data connection to carry the replicated data is
required and is formed using fibre channel connections between the replicating systems. A
communication channel is also required to manage the replication session. For synchronous
replication, part of the management is provided using Replication Interfaces that are IP
based interfaces for SPA and SPB using specific Sync Replication Management Ports. The
management communication between the replicating systems is established on a
Replication Connection. It defines the management interfaces and credentials for the source
and destination systems.

Synchronous Replication architecture utilizes Write Intent Logs (WIL) on each of the
systems involved in the replication. These are internal LUNs created automatically by each
system. There is a WIL for SPA and one for SPB on each system. They hold fracture logs
that are designed to track changes to the source LUN should the destination LUN become
unreachable. When the destination becomes reachable again it will automatically recover
synchronization to the source using the fracture log, thus avoiding the need for a full
synchronization.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 9

 The synchronous replication of a storage resource has an initial process followed by an
ongoing synchronization process. The starting point is a data populated storage resource on
the source system that is available to production and has a constantly changing data state.

The first step of the initial process for synchronous replication is to create a storage
resource of the exact same capacity on the destination system. The storage resource is
created automatically by the system and contains no data.

In the next step, SPA and SPB Write Intent Logs are automatically created on the source
and destination systems.

An initial synchronization of the source data is then performed. It copies all of the existing
data from the source to the destination. The source resource is available to production
during the initial synchronization but the destination will be unusable until the
synchronization completes.

Once the initial synchronization is complete, the process to maintain synchronization

begins. When a primary host writes to the source the system delays the write
acknowledgement back to the host. The write is replicated to the destination system. Once
the destination system has verified the integrity of the data write it sends an
acknowledgement back to the source system. At that point, the source system sends the
acknowledgement of the write back to the host. The data state is synchronized between the
source and destination. Should recovery be needed from the destination, its RPO would be
zero.

Should the destination become unreachable, the replication session will be out of
synchronization. The source Write Intent Log for the SP owning the resource will track the
changes. When the destination becomes available the systems will automatically recover
synchronization using the WIL.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 10

 Synchronous replications will have states for describing the session and its associated
synchronization.

An Active session state indicates normal operations and the source and destination are In
Sync.

A Paused session state indicates the replication has been stopped and will have a Sync
State of Consistent indicating the WIL will be used to perform synchronization of the
destination.

A Failed Over session will have one of two Sync States. It can show Inconsistent meaning
the Sync State was not In Sync or Consistent prior to the Failover. If the Sync State was In
Sync prior to Failover, it will be Out of Sync after session Failover.

A Lost Sync Communications session state indicates the destination is unreachable. It can
have any of the following Sync States: Out of Sync, Consistent or Inconsistent.

A Sync State of Syncing indicates a transition from Out of Sync, Consistent or Inconsistent
due to the session changing to an Active state from one of its other states; for example if
the system has been recovered from the Lost Sync Communications state.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 11

 The table details the various maximum capabilities for Asynchronous Replication based on
specific Unity models.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 12

 The table details the various maximum capabilities for Synchronous Replication based on
specific Unity models.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 13

 This module covered an overview of Unity Replication. The architectures of Asynchronous
and Synchronous replication were detailed and their benefits and capabilities were listed.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 14

 This module focuses on creating the replication communications between the two
replicating systems. It also details the process steps for creating Asynchronous and
Synchronous Replication sessions.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 15

 Replication sessions are created on storage resources for Block, File and VMware. And all
are done in a similar manner.

For Block, the replication is created on a LUN or a group of LUNs in the case of a
Consistency Group. For File, the replication is configured on a NAS server and file systems.
For VMware the storage resource is either going to be a LUN-based VMFS datastore or a file
system-based NFS datastore. When creating each of these storage resources, the Unity
system provides a wizard for their creation. Each wizard provides an option to automatically
create the replication on the resource. Each resource replication creation is nearly identical
to the other resources.

For resources already created, replications can be created manually from their Properties
page. As with the wizard, the replication creation from the resource Properties page is
nearly identical to the other resources. The following few slides will show replication
creation within the Block storage LUN creation wizard and the File storage file system
creation wizard. It will also show replications created manually from the LUN and file
system Properties pages.

Video demonstrations will also be provided for the resource replication creation.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 16

 Because file system access is dependent on a NAS Server, to remotely replicate a file
system, the associated NAS Server will need to be replicated first. When a NAS Server is
replicated, any file systems associated with the NAS server will also be replicated as
separate replication sessions; a session for the NAS Server and a session for each
associated file system.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 17

 Before you create a remote replication session, you first need to configure active
communications channels between the two systems. This involves first creating Replication
Interfaces on the source and destination systems. Then a Replication Connection is created
between the systems.

For Asynchronous Replication, the Replication Interfaces are dedicated IP-based

connections between the systems that will carry the replicated data. The interfaces are
defined on each SP using IPv4 or IPv6 addressing and will establish the required network
connectivity between the corresponding SPs of the source and destination systems. The
Replication Connection pairs together the Replication Interfaces between the source and
destination systems. It also defines the replication mode between the systems;
Asynchronous, Synchronous or both. The connection is also configured with the
management interface and credentials for both of the replicating systems.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 18

 The active communication channels required for Synchronous Replication are significantly
different from the previously discussed communications for Asynchronous Replication. The
first communications configuration required for Synchronous Replication are the Fibre
Channel connections between the corresponding SPs of the source and destination systems.
The Fibre Channel connectivity can be zoned fabric or direct connections. This connectivity
will carry the replicated data between the systems. Next configured are the Replication
Interfaces which are IP-based connections configured on specific Sync Replication
Management Ports on the SPs of each system. These interfaces are part of the replication
management channel. The Replication Connection is configured next and is the same as
discussed for Asynchronous Replication; it defines the replication mode, the management
interface and credentials for both of the replicating systems, and completes the
configuration of the management channel.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 19

 One of several Fibre Channel ports on each SP of the Unity system is configured and used
for Synchronous Replication. If available, the system will use Fibre Channel Port 4 of SPA
and SPB. If not available, then the system uses Fibre Channel Port 0 of IO module 0. If
that is not available, then Port 0 of IO module 1 is used.

The CLI console command can be used to verify the Fibre Channel port that the system has
specified as the Synchronous FC Ports on the SPs. The slide shows an example of running
the UEMCLI command “/remote/sys show –detail” command. In the abbreviated
example output, Fibre Channel Port 4 is specified by the system as the Synchronous FC port
for SPA and SPB.

Once the Synchronous FC Ports on the source and destination systems have been verified,
Fibre Channel connectivity can be established between the corresponding ports on the SPs
of each system. Direct connect or zoned fabric connectivity is supported.

Although the Synchronous FC ports will also support host connectivity, it is recommended
that they be dedicated to Synchronous Replication.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 20

 The steps for creating remote replication sessions are somewhat different depending upon
the replication mode; either Asynchronous or Synchronous. Asynchronous remote
replication steps are covered here. The Synchronous replication steps will be covered in a
later section.

Before an Asynchronous Replication session can be created, communications need to be

established between the replicating systems. The first step for establishing communications
is to create Replication Interfaces on both the source and destination systems. The
interfaces will form the connection for replicating the data between the systems. The next
step is to create a Replication Connection between the systems. This is done on either the
source or the destination. It establishes the management channel for replication. After it is
created, the connection should be verified from the peer system. With these steps
complete, communications are now in place for a session to be created for a storage
resource. A session can be defined for a storage resource during the resource creation or if
the storage resource already exists, it can be selected as a source for replication. The
replication settings are defined which include the replication mode, RPO and the
destination. The system will automatically create the destination resource and the Unified
Snapshot pairs on both systems. Then the replication session is established.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 21

 The creation of Replication Interfaces for remote asynchronous replication is covered here.
Replication Interfaces are not required for local asynchronous replication.

The system’s user interface provides a Replications management page that includes a
section for the Interfaces. With the Interfaces section selected, the + icon is used to create
new Replication Interfaces. On the creation screen, an available Ethernet Port from the
system must be selected. An IP address and subnet mask must be provided for both SPs.
Gateway addressing is optional and a VLAN ID configuration is also provided if needed.

As noted before, Replication Interfaces need to be created on both of the replicating

systems. The creation of Replication Interfaces needs to be repeated on the peer system.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 22

 After the Replication Interfaces are created, a Replication Connection is created between
the two systems for remote asynchronous replication and is not required for local
replication. The Replication Connection only needs to be created on one of the replicating
systems. The requirements of the connection include the remote system management IP
address and its management credentials. The local system management password is also
required. Finally a replication mode must be selected from the drop-down. Choices are
Asynchronous, Synchronous or Both. For Asynchronous replication the Mode must be set
Asynchronous or Both. If Both is selected, Asynchronous and Synchronous sessions can be
configured between the two systems.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 23

 After the Replication Connection between systems has been created, the connection can be
verified from the peer system using the Verify and Update option. This option can also be
used to update Replication Connections if anything has been modified with the connection
or the interfaces. The updated Connection status will be displayed.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 24

 Asynchronous Replication sessions can be created as part of the wizard that creates any
Unity storage resource. From the NAS Server creation wizard example, the Replication step
within the wizard is shown. Checking the Enable Replication option will expose the
“Replication Mode”, “RPO”, and “Replicate To” fields required to configure the session. The
mode must be set to Asynchronous to create an Asynchronous replication session. To
create a remote replication session, select the remote system from the “Replicate To” drop-
down. Select Local if configuring a local replication session. A “Destination Configuration”
button is also exposed to provide information concerning the destination resources to be
used for the session.

As noted before; there is a dependency between a NAS Server and a file system. The NAS
server must be replicated prior to any associated file system.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 25

 Asynchronous Replication sessions can also be created from the storage resource Properties
page; a VMware NFS Datastore, a NAS Server or a file system. From the NAS Server
Properties page example, the “Configure Replication” button is presented to create a
replication session. It starts a wizard with a number of steps to configure the replication
session. The Replication Settings step requires the “Replication Mode”, “RPO”, and
“Replicate To” settings for the session. The mode must be set to Asynchronous to create an
Asynchronous replication session.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 26

 The next step defines what resources on the destination system the replicated item will
use. The Name, Pool and Storage Processor settings are required.

In the example NAS Server replication shown, the NAS Server has an associated file system
and a separate replication session will be created for it. The table details the destination
resources that will be used for the file system. It can be selected and edited to further
define its destination resources.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 27

 The wizard presents a Summary screen for the configured replication.

In the example, sessions for the NAS Server and its associated file system will be created.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 28

 The creation Results page displays the progress of the destination resource creation and
the session creation.

When it is complete the created sessions can be viewed from the Replications page by
selecting the Sessions section.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 29

 As mentioned previously, the steps for creating a Synchronous replication session are
different than for Asynchronous replication.

Before a Synchronous Replication session can be created, communications need to be

established between the replicating systems. The first step is to verify the Synchronous FC
Ports on the source and destination systems and establish FC connectivity to form the
connections for replicating data. The next step is to create Replication Interfaces on both
the source and destination systems. The interfaces must be created on the Sync Replication
Management Ports and will form a portion of the management channel for replication. A
Replication Connection between the systems is created next. This is done on either the
source or the destination. It establishes the management channel for replication. After it is
created, the connection should be verified from the peer system. With these steps
complete, communications are now in place for a session to be created for a storage
resource. A storage resource can now be selected for replication. It can be selected during
the resource creation wizard. Or if the storage resource already exists, it can be selected
from the storage resource Properties page. The next step is to define the replication
settings which define the replication mode and destination system. The system will
automatically create the destination resource and the Write Intent Logs on both systems.
Then the replication session is established.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 30

 The replication Interfaces for Synchronous replication are created in a similar fashion as
seen with Asynchronous replication. The requirement for Synchronous replication is that the
Interfaces are created on the Sync Replication Management Port of each SP. This is a virtual
device that uses the same physical network connection as the SP Management port. The
interfaces are configured on the same network as the SP Management but can use a
different network if VLANs are used.

The Replication Interfaces need to be configured on both the source and destination
systems.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 31

 After the Replication Interfaces are created, a Replication Connection is created between
the two systems. This only needs to be created on one of the replicating systems. The
requirements of the connection include the remote system management IP address and its
management credentials. The local system management password is also required. Finally
a replication mode must be selected from the drop-down. Choices are Asynchronous,
Synchronous or Both. For Synchronous replication the Mode must be set Synchronous or
Both. If Both is selected, Synchronous and Asynchronous sessions can be configured
between the two systems.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 32

 After the Replication Connection between systems has been created, the connection can be
verified from the peer system using the Verify and Update option. This option can also be
used to update Replication Connections if anything has been modified with the connection
or the interfaces. The updated Connection status will be displayed.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 33

 Synchronous Replication sessions can be created as part of the wizard that creates the
storage resource; a Block LUN or a VMware VMFS Datastore. From the LUN creation wizard
example, the Replication step within the wizard is shown. Checking the Enable Replication
option will expose the “Replication Mode” and “Replicate To” fields required to configure
the session. The Mode must be set to Synchronous to create a Synchronous replication
session. A “Destination Configuration” button is also exposed to provide information
concerning the destination resources to be used for the session.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 34

 Synchronous Replication sessions can also be created from the storage resource Properties
page; a VMware VMFS datastore or a Block LUN. From the LUN Properties page example,
the “Configure Replication” button is presented to create a replication session. It starts a
wizard with a number of steps to configure the replication session. The Replication Settings
step requires the “Replication Mode” and “Replicate To” settings for the session. The Mode
must be set to Synchronous to create a Synchronous replication session.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 35

 The next step defines what resources on the destination system the replicated item will
use. The Name and Pool settings are required. A Tiering Policy drop-down is also available.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 36

 The wizard presents a Summary screen for the configured replication.

In the example, the session settings for the replication and destination are displayed.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 37

 The creation Results page displays the progress of the destination resource creation and
the session creation.

When it is complete the created sessions can be viewed from the Replications page by
selecting the Sessions section.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 38

 This video demonstrates the creation of Remote replication communications. It details
Synchronous FC Port verification and the creation of Replication Interfaces and the
Replication Connection supporting Asynchronous and Synchronous Replication sessions.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 39

 This video demonstrates the creation of Remote Replication sessions. It details the creation
of Asynchronous and Synchronous Replication sessions.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 40

 This module covered the creation of Replication Interfaces and Connections to form the
communications for Remote Replication. It also detailed the process and creation of
Asynchronous and Synchronous Replication sessions.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 41

 This module focuses on the operations for Remote Replication. Replication operations of
Failover with Sync, Failover, Resume, and Failback are performed. Also detailed is data
access from the remote site during failover.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 42

 Replication sessions can be managed within Unisphere from two areas. The Replications
page Sessions selection provides a list of all the replication sessions. When a specific
session is selected it can be deleted, edited or by using the More Actions drop-down a
variety of replication operations can be performed.

Similar management of a session can also be done from the Properties page of the
replicated object. The Replication tab displays information about the session, provides
certain editable fields and buttons to delete or perform various replication operations.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 43

 Replication sessions can be managed from the source or destination systems. The
operations possible will differ between source or destination. The operations will also differ
based on the type of replication, Asynchronous or Synchronous, and the state of the
session.

The example is from an asynchronous file system replication that is in a normal state. From
the source it is possible to perform session Pause, Sync or Failover with Sync operations.
From the destination it is only possible to perform a session Failover operation.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 44

 The table provides a list of replication operations, a brief description of it, and which
replication mode supports the operation.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 45

 Because a NAS Server has a network interface associated with it, when the server is
replicated its network configuration is also replicated. During replication, the source NAS
Server interface is active and the destination NAS Server interface is not active. Having the
source and destination interfaces the same for the two NAS Servers is fine for an
environment where there is similar networking in place for both the source and destination
sites. For an environment where the source and destination sites have different networking,
it is important to modify the network configuration of the destination NAS Server to ensure
it will operate correctly in a failover event. This is performed from the NAS Server’s
Properties page on the destination system. Select the Override option and configure the
destination NAS Server for the networking needs of the destination site. Because the NAS
Server effectively changes its IP address when failed over, clients may need to flush their
DNS client cache to connect to the NAS Server when failed over.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 46

 Because of the file system dependence on the NAS Server, replication operations must be
done on the NAS Server first then to the associated file system.

The example illustrates the order of failover for a NAS Server and an associated file system.
Failover must be done first to the NAS Server, then to its associated file system. The same
is true for the Resume operation after Failover. The Resume operation is initiated first on
the NAS Server then the associated file system. Failback is done in the same order; first to
the NAS Server then to the associated file system.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 47

 Failover with Sync is an operation available to Asynchronous replication sessions. It is used
for a planned event, either scheduled maintenance or disaster recovery testing when both
the primary and secondary sites are available. It provides data availability from the
secondary site.

The example illustrates the process of the operation. It starts with issuing the Failover with
Sync operation from Site A which is the primary production site. The operation will remove
access to the replicated object on Site A. A synchronization from the Site A object to the
Site B object happens next and when it completes the replication session is paused. The
operation then makes the Site B object available for access.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 48

 Failover is an operation available to replication sessions of either mode; Asynchronous or
Synchronous. It is used for an unplanned event when the primary production site is
unavailable. It provides access to the replicated data from the secondary site.

The example illustrates the process of the operation. The primary production site becomes
unavailable and all its operations cease. Data is not available and replication between the
sites can no longer proceed. A Failover operation is issued from Site B which is the
secondary production site. The operation Pauses the existing replication session so that the
session will not start again should Site A become available. The operation then makes the
Site B object available for access and production can resume.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 49

 Resume is an operation available to replication sessions of either mode; Asynchronous or
Synchronous. It is used to restart a Paused replication session. When a failed over session
is resumed from its Paused state the direction of replication is reversed.

The example illustrates the process of a Resume operation for a session that is failed over.
The Site A replicated object must be available before the replication session can be
resumed. The Resume operation is issued from Site B. The operation will restart the
Paused session in the reverse direction. This will update the Site A object with any changes
that may have been made to the Site B object during the failover. This results in the
session resuming in the reverse direction and returned to a normal state. One may use this
method of restarting replication rather than a Failback operation if production had been
serviced from the Site B object for a significant amount of time and thus has accumulated a
significant amount of change from the Site A object. Replication in the reverse direction will
synchronize the Site A object to the data state of the Site B object. To return production to
the Site A object would require a session Failover operation followed by another Resume
operation.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 50

 Failback is an operation available to replication sessions that have failed over, either
Asynchronous or Synchronous. As its name implies it is used to return a replication session
to its state prior to the failover operation.

The example illustrates the process of a Failback operation. The Site A replicated object
must be available before the Failback operation can be initiated on a session. The Failback
operation is issued from Site B. The operation will remove access to the Site B object and
synchronize the Site A object to the data state of the Site B object. The operation then
allows access to the Site A object for production. Replication is restarted using the Site A
object as a source and the Site B object as a destination. This single operation returns the
object’s replication state as it was prior to the failover. One would use this operation to fail
back from failovers lasting for only short time periods. It is important to note that if the Site
B object had accumulated a significant amount of change due to long periods of failover,
the resync time can take a significant amount of time.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 51

 This video demonstrates Failover with Sync and Failback of Asynchronous Replication
sessions for a NAS Server and file system. It details client access to data when failed over
to the secondary production site.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 52

 This video demonstrates Failover and Failback of a Synchronous Replication session of a
LUN. It details host access to data when failed over to the secondary production site.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 53

 This module covered managing Asynchronous and Synchronous remote replication sessions.
It discussed the process of remote replication operations and how data is accessed during
planned and unplanned events.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 54

 This course covered the Unity Replication feature. It provided an overview of Asynchronous
and Synchronous replications, their architecture and capabilities. Remote replication
communications and sessions were created for both Asynchronous and Synchronous
replication modes. Session management was covered and various replication operations
were detailed. Accessing data during replication failover was also demonstrated.

This concludes the training.

Copyright 2016 EMC Corporation. All rights reserved. Unity Replication 55