Module+7+Data+Protection+with+Replication+and+Course+Completion+-+Participant+Guide+
Module+7+Data+Protection+with+Replication+and+Course+Completion+-+Participant+Guide+
PROTECTION WITH
REPLICATION AND
COURSE COMPLETION
PARTICIPANT GUIDE
PARTICIPANT GUIDE
Module 7 Data Protection with Replication and Course Completion
Replication Overview
Replication Overview
This topic provides an overview of the Dell Unity XT Replication feature. The
architectures of Asynchronous and Synchronous Replications are discussed and
the benefits and capabilities are listed.
Replication
Replica
Storage Resource
− Long-distance replication
o Does not impact latency
− DR solution using Recovery Point Objective
o Data amount measured in units of time
− Available on physical and virtual systems
Dell Unity XT Replication is a data protection feature that replicates storage
resources to create synchronized redundant data. With replication, it is possible to
replicate storage resources within the same system or to a remote system. The
replication feature is included in the Unity XT licensing at no additional cost.
Asynchronous
Pool A Pool B
− LUNs
− Consistency Groups
− Thin Clones
− VMware vStorage VMFS datastores
− VMware NFS datastores
− File systems
− NAS servers
Asynchronous
Synchronous
Site A Site B
− LUNs
− Consistency Groups
− Thin Clones
Because file system access depends on a NAS server, to remotely replicate a file
system, the associated NAS server must be replicated first.
Site A Site B
When a NAS server is replicated, any file systems that are associated with the NAS
server are also replicated.
The system creates separate replication sessions; a session for the NAS server
and a session for each associated file system.
Synchronous session
Resource Resource
Management
Source Destination
Site A Site B
Synchronous replication architecture uses Write Intent Logs (WIL) on each of the
systems that are involved in the replication. These logs are internal structures and
are created automatically on each system. There is a WIL for SPA and one for SPB
on each system. During normal operations, these logs are used to maintain
synchronization of the source and the replica. The Write Intent Logs hold fracture
logs, designed to track changes to the source storage resource should the
destination storage resource become unreachable. When the destination becomes
One-Directional
Bi-Directional
Initial State
The synchronous replication of a storage resource has an initial process, and then
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.
Primary Secondary
Resource
Data
Management
Source Destination
Site A Site B
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 system creates
the destination storage resource automatically. The new destination resource
contains no data.
Primary Secondary
Resource Resource
Data
Management
Source Destination
Site A Site B
2-Create WILs
In the next step, SPA, and SPB Write Intent Logs are automatically created on the
source and destination systems.
Primary Secondary
Resource Resource
Management
Source Destination
Site A Site B
3-Initial Copy
Initial synchronization of the source data is then performed. It copies all the existing
data from the source to the destination. The source resource is available to
production during the initial synchronization, but the destination is unusable until
the synchronization completes.
Primary Secondary
Resource Resource
Data
Management
Source Destination
Site A Site B
4-Host Writes
to Source
Primary Secondary
Resource Resource
Data
Management
Source Destination
Site A Site B
Primary Secondary
Resource Resource
Data
Management
Source Destination
Site A Site B
6-Dest. Ack.
After the destination system has verified the integrity of the data write, it sends an
acknowledgement back to the source system.
Primary Secondary
Resource Resource
Data
Management
Source Destination
Site A Site B
At that point, the source system sends the acknowledgement of the write operation
back to the host. The data state is synchronized between the source and
destination. Should recovery be needed from the destination, its RPO is zero.
Primary Secondary
Resource Resource
Movie:
Active In Sync
Syncing
Paused
Out of Sync
Failed Over
Consistent
Synchronous replications 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 that the replication has been stopped and has
the sync state of Consistent. This state indicates that the WIL is used to perform
synchronization of the destination.
A Failed Over session has one of two sync states. It can show an Inconsistent
state meaning the sync state was not In Sync or Consistent before the Failover. If
the sync state was In Sync before the Failover, it will be Out of Sync after session
Failover.
from one of its other states. For example, if the system has been recovered from
the Lost Sync Communications state.
The table details the various maximum capabilities for synchronous replication that
are based on specific Dell Unity XT models. The maximum replication sessions
include all replication sessions on the system, which include both synchronous and
asynchronous replication sessions, local or remote. The replication destination
storage resources count towards the system maximums, even though they are not
host accessible as a destination image. In Dell Unity XT, only one replication
connection that is used for synchronous replication, or synchronous and
asynchronous replication, can be created. Only one pair of systems can replicate
synchronously with each other.
Synchronous session
Resource Resource
Management
Source Destination
Site A Site B
The steps for creating remote replication sessions are different depending upon the
replication mode; either asynchronous or synchronous. Synchronous remote
replication steps are covered here. Before a synchronous replication session is
created, communications must be established between the replicating systems.
The first step is to identify the Synchronous FC Ports on the source and destination
systems for use to establish FC connectivity. This connectivity forms the
connections that carry the data between the two replicating systems.
Next, create Replication Interfaces on both the source and destination systems.
The interfaces must be created on the Sync Replication Management Ports and
form a portion of the management channel for replication.
After the connection is created, verify it can be seen on the peer system.
selected during the resource creation wizard. Or if the storage resource already
exists, it can be selected from the storage resource Properties page.
Next, configure the replication settings which define the replication mode and
destination system. The system automatically creates a destination resource and
the Write Intent Logs on both systems.
Before you create a synchronous remote replication session, you must configure
active communications channels between the two systems. The active
communications channels are different for the two replication modes, synchronous
is shown here.
1. Synchronous FC connections
FC-based connectivity
between source and
destination SPs
Carries replicated
data
Data
Management
2: Replication
Source Interfaces [sync] Destination
3: Replication
Connection
Mode of replication
Channel for management
One of several Fibre Channel ports on each SP of the Dell Unity XT system is
configured and used for synchronous replication. If available, the system uses
Fibre Channel Port 4 of SPA and SPB. If not available, and then the system uses
Fibre Channel Port 0 of I/O module 0. If that is not available, and then Port 0 of I/O
module 1 is used.
After the Synchronous FC Ports on the replicating systems are verified, the Fibre
Channel connectivity is established between the corresponding SP ports on each
system. Direct connect or zoned fabric connectivity is supported.
Although the Synchronous FC ports can also support host connectivity, Dell
recommends that they be dedicated to synchronous replication.
Unisphere
In Unisphere, navigate to the System View page for the rear view of the DPE to
identify the Synchronous FC Ports. In the example, the SPA FC Port 4 is selected
and its Replication Capability lists Sync replication.
UEMCLI
Ordering of SPA/SPB
Synchronous FC Ports:
1. FC Port 4
2. Module 0 FC Port 0
3. Module 1 FC Port 0
After the Replication Connection between systems has been created, the
connection is verified from the peer system using the Verify and Update option.
This option is also used to update Replication Connections if anything has been
modified with the connection or the interfaces. The updated connection status is
displayed.
A synchronous replication session is created as part of the wizard that creates the
storage resource.
From the LUN creation wizard example, the Replication step within the wizard is
shown.
1. Checking the Enable Replication option exposes the Replication Mode and
Replicate To fields required to configure the session.
2. The mode must be set to Synchronous to create a synchronous replication
session.
3. A Destination Configuration link is also exposed to provide information
concerning the destination resources used for the session.
The next step defines what resources on the destination system the replicated item
will use. The Name and Pool settings are required. More options are available
based on the destination system. In this example, the destination is a Hybrid model
that supports Data Reduction.
The wizard presents a Summary screen for the configured replication. In the
example, the session settings for the replication and destination are displayed.
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 tab.
The architecture for asynchronous local replication is shown here. The difference
between the local and remote architecture that was 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.
Rep
Rep
Snap 2
Snap 2
Delta
Rep Rep
Snap 1 Snap 1
Pool Pool
Data
Management
Delta
Rep
Rep
Snap 1
Snap 1
Asynchronous session
Resource Resource
Data
Management
Source Destination
Site A Site B
The architecture for Dell Unity XT asynchronous remote replication is shown here.
Fundamental to remote replication is connectivity and communication between the
source and destination systems. A data connection is needed for carrying the
replicated data, and it is formed from Replication Interfaces. They are IP-based
connections that are established on each system. A communication channel is also
needed for management of the replication session. The management channel is
established on Replication Connections. It defines the management interfaces and
credentials for the source and destination systems.
One-to-Many
One-Directional
Many-to-One
Bi-Directional
For the One-to-Many and Many-to-One replication topology examples, the One-
Directional replication is depicted. One-Directional replication is not a requirement
when configuring the One-to-Many and Many-to-One replication topologies. Each
individual Replication Connection can be used for the Bi-Directional replication
between systems, which enables more replication options than depicted here.
Again, a single storage resource can only be replicated to a single destination
storage resource.
Initial State
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 and 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.
Resource
Data
Management
Site A (Source) Site B (Destination)
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
system automatically creates the destination storage resource. The destination
storage resource contains no data.
Resource Resource
Data
Management
Site A (Source) Site B (Destination)
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.
Rep Rep
Snap 2 Snap 2
Rep Rep
Snap 1 Snap 1
Resource Resource
Data
Management
Site A (Source) Site B (Destination)
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.
Rep Rep
Snap 2 Snap 2
Rep Rep
Snap 1 Snap 1
Copy
Resource Resource
Data
Management
Site A (Source) Site B (Destination)
After the initial copy is complete, the first snapshot on the destination system is
updated. The data states that are captured on the first snapshots are now identical
and create a common base.
Rep Rep
Snap 2 Snap 2
Rep Rep
Snap 1 Snap 1
Copy
Resource Resource
Data
Management
Site A (Source) Site B (Destination)
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.
Initial process
Synchronization process
1. Create destination resource 5. Source Rep Snap 2 updated
2. Create rep snapshot pairs
3. Source Rep Snap 1 copied to destination
4. Destination Rep Snap 1 updates
Rep
Rep Snap 2
Snap 2
Rep Rep
Snap 1 Snap 1
Copy
Resource Resource
Data
Management
Site A (Source) Site B (Destination)
A data difference or delta is calculated from the two source system snapshots. A
delta copy is made from the second snapshot to the destination storage resource.
Rep Rep
Snap 2 Snap 2
Delta Copy
Rep Rep
Snap 1 Snap 1
Copy
Resource Resource
Data
Management
Site A (Source) Site B (Destination)
After the copy is complete, the second snapshot on the destination system is
updated to form a common base with its corresponding source system snapshot.
Rep Rep
Snap 2 Snap 2
Delta Copy
Rep Rep
Snap 1 Snap 1
Copy
Resource Resource
Data
Management
Site A (Source) Site B (Destination)
The cycles of delta copies continue for the session by alternating between the first
and second snapshot pairs that are 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 then updated forming a new common base. The cycle
repeats using the second snapshot pair upon the next RPO synchronization time.
Rep Rep
Snap 2 Snap 2
Delta Copy
Rep Rep
Snap 1 Snap 1
Copy
Resource Resource
Data
Management
Site A (Source) Site B (Destination)
Movie:
• Asynchronous replication of
snapshots
− Primary storage resource must
also be replicated Asynchronous
− Unattached block and read-
only file snapshots
− Scheduled or user created
snapshots
• Primary storage resource
snapshots can be:
− LUNs
− Consistency Groups
− Thin Clones
− VMware VMFS datastores
− VMware NFS datastores
− File systems
• Replica retention policies can be customized
− Cost savings
− Compliance
With the Dell Unity XT replication feature, it is also possible to asynchronously
replicate a snapshot of a primary storage resource. They can be replicated either
locally or remotely. Also referred to as “Snapshot Shipping,” snapshot replication
requires that the primary storage resource is replicated. Block-based unattached
snapshots and file-based read-only snapshots are supported. The snapshots can
either be user created or created by a schedule.
The snapshot replicas can have retention policies that are applied to them that are
different from the source. The feature has multiple use case scenarios, one is cost
savings. With snapshots that are replicated to a lower-end system on the
destination site, the source snapshots can be deleted off the higher-end production
source site system. Therefore, saving capacity and its associated costs on a
production system. Another use case is for compliance needs. The retention policy
on the snapshot replicas can be tailored to any compliance needs, such as for
medical or governmental storage requirements.
Rep
Rep
Snap 2
Snap 2
Asynchronous session
Delta
User User
Snap Snap Rep
Rep Snap 1
Snap 1
Asynchronous session
Resource Resource
Data
Management
Source Destination
Site A Site B
since the snapshot data does not change, it is only replicated a single time. After
that, it is not part of any RPO-based synchronization cycle that is needed for the
replicated primary storage resource.
The table details the various maximum capabilities for asynchronous replication
that are based on specific Dell Unity XT models. The maximum replication sessions
include all replication sessions on the system, which include both synchronous and
asynchronous replication sessions, local or remote. The replication destination
storage resources count towards the system maximums, even though they are not
host accessible as a destination image.
Rep Rep
Snap 2 Snap 2
Asynchronous session
Resource Resource
Data
Management
Source Destination
Site A Site B
The steps for creating remote replication sessions are different depending upon the
replication mode; either asynchronous or synchronous. Asynchronous remote
replication steps are covered here. Before an asynchronous replication session can
be created, communications must be established between the replicating systems.
1. Create Replication Interfaces on both the source and destination systems. The
interfaces form the connection for replicating the data between the systems.
2. Create a Replication Connection between the systems. This step is performed
on either the source or the destination. It establishes the management channel
for replication.
3. Verify the connection from the peer system. Communications are now in place
for the creation of a replication session for a storage resource.
4. Define a session for a storage resource during the resource creation or, select a
source for replication if the storage resource already exists.
5. Define the replication settings which include the replication mode, RPO, and the
destination. The system automatically creates the destination resource and the
Snapshot pairs on both systems.
6. Create the replication session.
Before you create an asynchronous remote replication session, you must configure
active communications channels between the two systems. The active
communication channels are different for the two replication modes,
asynchronous is shown here.
1. Replication Interface:
IP-based connectivity
between source and
destination SPs
Carries replicated
data
Data
Management
2: Replication
Source Connection Destination
Pairs Replication
Interfaces
Mode of replication
Channel for management
− The connection pairs together the Replication Interfaces between the source
and destination systems.
− 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.
Replication Interfaces must be created on both of the replicating systems. The
creation of Replication Interfaces must be repeated on the peer system.
After the Replication Connection between systems has been created, the
connection is verified from the peer system using the Verify and Update option.
This option is also used to update Replication Connections if anything has been
modified with the connection or the interfaces. The updated connection status is
displayed.
From the NAS Server creation wizard example, the Replication step within the
wizard is shown.
1. Checking the Enable Asynchronous Replication option exposes 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.
2. A Destination Configuration link is also exposed to provide information
concerning the destination resources used for the session.
− When selected, the Replicate all existing snapshots option and the
Replicate scheduled snapshots options becomes available.
5. When the Reuse destination resource option is selected, the system
automatically searches for a resource with the same name on the destination
and replicate to it if found. If one does not exist, it creates a new destination
resource.
The next step defines what resources on the destination system the replicated item
will use and how the replica is configured. For the NAS server example, the Name,
the Pool, and Storage Processor settings are required. By default, the system
configures the replica as close as possible to the source. The user can choose to
customize the replica configuration as needed.
In the NAS server example shown, the NAS server has an associated file system
and a separate replication session is created for it. The table details the destination
resources that are used for the file system. The user can select the file system and
edit its destination configuration to customize the resources that the replica uses.
The wizard presents a Summary screen for the configured replication session. In
the example, sessions for the NAS server and its associated file system are
configured for creation.
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 tab.
Replication Operations
When replication is in place on systems, resources that are being replicated are
displayed on various Unisphere pages. Unisphere resource filtering provides a
method for administrators to identify system resources as replication source or
destination resources. The Source, Destination, and All resource filter buttons are
on Unisphere pages for administrators to filter the displayed resources. Block
storage LUNS and Consistency Groups pages include resource filter buttons. File
storage File Systems, NAS Servers, NFS Shares, and SMB Shares pages
include resource filter buttons. VMware storage Datastores and Datastore Shares
pages include resource filter buttons. The Replication Sessions page includes
resource filter buttons.
For resources being replicated locally, the Sessions page displays those sessions
in all three views. Click through each tab to see the filtered views. The
FASTVP_CG resource is being locally replicated and is seen in all views.
Source
With the Source button selected, the page displays only source resources.
Destination
With the Destination button selected, the page displays only destination
resources.
All
With the default All button selected, source, destination and any resources not
replicated are displayed.
System level replication operations are available for Pause, Resume, andFailover
of replicated resources. The system level operations are run on replication
sessions for specified replication connections to remote systems. If multiple
replication sessions exist, the system level operation impacts all sessions for the
specified remote systems to reduce discrete administrative tasks.
In Unisphere, the system level operations are available from the Replication
Connections page when a replication connection is selected.
System level
operations
Replication Connection
System level Pause and Resume operations are performed from the Replication
Connections page.
• Select the remote system with replication sessions that you want to perform the
operation on.
LUN
Asynchronous
session
Synchronous
session
UnityA-300F UnityVSA-1
Replication Connections
Pause Operation
UnityB-400
LUN
Asynchronous
session
Synchronous
session
UnityA-300F UnityVSA-1
Pause operation
Pause Results
• Source and destination sessions for selected remote systems are paused.
UnityA-300F UnityVSA-1
Resume Operation
The Resume operation is performed in the same manner as the Pause operation.
Only paused session support the resume operation.
1. From More Actions, select the Resume operation.
2. If a connection supports asynchronous and synchronous replication, select the
session type to perform the operation on.
UnityB-400
UnityA-300F UnityVSA-1
Resume operation
Resume Results
• Source and destination sessions for selected remote systems are resumed.
UnityA-300F UnityVSA-1
The system level Failover operation is designed for unplanned failover. It is run
from the destination system. The single operation fails over all file replication
sessions to the destination system.
Replication Connection
Asynchronous session
Synchronous
session
UnityA-300F UnityVSA-1
Replication Connection
Failover Operation
UnityB-400
UnityA-300F UnityVSA-1
Failover operation
Failover Results
• Replication sessions for the selected remote system are failed over.
UnityB-400
Sessions
failed over
UnityA-300F UnityVSA-1
Failover results
Session Operations
Asynchronous
Unplanned
Planned
Synchronous
Source Destination
The example compares operations from healthy asynchronous and synchronous sessions on their
source and destination systems.
Planned failover operations are performed from the source system when both
systems are available.
• Planned failover would be run to test the DR solution or if the source site was
scheduled to be down for maintenance.
Unplanned failover operations are performed from the destination system when
the source system is not available.
• For example, if the source site is affected by a power outage or natural disaster.
The Failover operation would make data available from the destination site.
From the source, it is also possible to perform session Pause or Sync operations.
Because a NAS server has networking 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 NAS server
interfaces the same is fine for sites that share common networking.
For sites where the source and destination have different networking, it is important
to modify the network configuration of the destination NAS server. The modification
is needed to ensure correct NAS server operation in a failover event.
Source Destination
The modification is performed from the NAS server 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. The client is then able to connect
to the NAS server when failed over.
Because of the dependence between a NAS server and its associated file systems,
certain NAS server replication session operations are also performed on its file
systems.
Operations grouped to NAS server level Operations not grouped to NAS server level
- Failover - Create
- Failover with sync - Sync
- Failback - Delete
- Pause - Modify
- Resume
Failover
Grouped operation
Site A Site B
In the example shown, if a failover operation is performed on the NAS server, its two associated file
systems also failover.
Grouped operations are only available to sessions that are in a healthy state.
• Grouped operations are prohibited if a NAS server is in the paused or error
state.
• Grouped operations skip any file system sessions that are in paused, error, or
non-replicated states.
The operations capable of being grouped are: Failover, Failover with sync,
Failback, Pause, and Resume.
The Create, Sync, Delete, and Modify replication operations are not grouped and
are performed discretely per session. Discrete operations are also permitted on file
system replication sessions.
Site A Site B
Select Action
The process starts with issuing the Failover with sync operation from site A which
is the primary production site.
Site A Site B
Site A Site B
A synchronization from the site A object to the site B object happens next.
Sync
Site A Site B
Pause Replication
After the sync process completes, the replication session is then paused.
Sync
Site A Site B
The site B object is and then made available for access to complete the operation.
Sync
Site A Site B
Site A Site B
Select Action
The process starts with issuing the Failover operation from site A which is the
primary production site.
Site A Site B
Site A Site B
The ongoing synchronous replication session synchronizes the data state of the
site B object to the site A object.
Sync
Site A Site B
Reverse/Restart Session
Reverse
Sync
Site A Site B
The site B object is and then made available for access to complete the operation.
Reverse
Sync
Site A Site B
Site A Site B
Unplanned event: Primary production site unavailable
The primary production site becomes unavailable and all its operations cease. Data
is not available, and replication between the sites can no longer proceed.
Site A Site B
Select Action
A Failover operation is issued from site B which is the secondary production site.
Site A Site B
Pause Replication
The operation pauses the existing replication session so that the session does not
start again should site A become available.
Site A Site B
The site B object is made available for production access to complete the
operation.
Site A Site B
Site A Site B
Replication resumes in reversed direction
The Site A replicated object must be available before the replication session can be
resumed.
Resume process
1. Site A becomes available
Site A Site B
Select Action
Resume process
1. Site A becomes available
2. Resume issued from site B
Site A Site B
Reverse/Restart Session
Resume process
1. Site A becomes available
2. Resume issued from site B
3. Paused session is reversed and restarted
Site A Site B
The operation updates the site A object with any changes that may have been
made to the site B object during the failover. The replication session then resumes
in the reverse direction and returns to a normal state. For asynchronous file
replication sessions, there is an option available to perform a synchronization of the
site A data to site B. The option overwrites any changes that are made to site B
during the failover. After the overwrite synchronization, replication is then restarted
in the reverse direction; from site B to site A in this example.
The Resume operation is preferred over Failback in situations where large amounts
of production change have accumulated due to long session pauses.
Site A Site B
Replication returns to the state before Failover
The site A replicated object must be available before the Failback operation can be
initiated on a session.
Failback process
1. Site A becomes available
Site A Site B
Select Action
Failback process
1. Site A becomes available
2. Failback issued from site B
Site A Site B
The operation removes access to the site B object and synchronizes the site A
object to the data state of the site B object.
Failback process
1. Site A becomes available
2. Failback issued from site B
3. Sync from site B to site A
Sync
Site A Site B
The operation then enables access to the site A object for production.
Failback process
1. Site A becomes available
2. Failback issued from site B
3. Sync from site B to site A
4. Access to site A object allowed
Sync
Site A Site B
Replication Restarts
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
before the failover.
Failback process
1. Site A becomes available
2. Failback issued from site B
3. Sync from site B to site A
4. Access to site A object allowed
5. Replication restarts from site A to site B
Sync
Site A Site B
This demo covers the synchronous remote replication of a LUN, and the
synchronous remote replication of a NAS Server and file system.
Movie:
Replica Access
- DR testing
User snap
Block Replica
resource resource
Source Destination
When block resources are replicated remotely, there are many benefits of being
able to access the replica data. One benefit of replica data access is that there is
no impact on the source system resources that are used for production. Another
positive aspect of accessing replica data is to have no impact on the existing
remote replication session. With replica access to data, backup and recovery of
data are possible. Testing and data mining are also possible with replica data
access. Having access to the replica data is also a valid way to test and validate
the remote replication DR solution.
Access to the replica block data on the destination system is not performed directly
to the replicated block resource. The remote replica is marked as a destination
image by the system and blocks read/write access to it. Access to the data is
accomplished through a user snapshot of the resource and attaching a host to the
snapshot. The snapshot can be a replicated user snapshot from the source. Or it
can be a user created snapshot of the replica resource on the destination system.
User snap
NAS Proxy
Server NAS NAS
Server Server
File
resource Replica
resource
Source Destination
When file resources are replicated remotely, there are many benefits of being able
to access the replica data. One benefit of replica data access is that there is no
impact on the source system resources that are used for production. Another
positive aspect of accessing replica data is to have no impact on the existing
remote replication session. With replica data access, backup and recovery of data
are possible. Testing and data mining are also possible with replica data access.
Having access to the replica data is also a valid way to test and validate the remote
replication DR solution.
Access to the replica file data is not achieved as directly as access to the source
file resource. File data is accessed through the NAS server that is associated with
the file system data. But a replicated NAS server has its production interfaces
inactive. The recommended method of accessing replica file data is to have a user
snapshot of the file resource. Access of replica file data can be done several ways.
A user snapshot of the resource could be made on the source system and
replicated to the destination system for access. A Read-only or Read/Write user
snapshot can also be made from the replica resource on the destination.
Once the user snapshot is on the destination system, there are several methods for
gaining access to its data. One way is to create a Backup and Test IP interface on
the replica NAS server. If a Read/Write snap is made, an NFS client can access a
share that is configured on the snapshot through the replica NAS server Backup
and Test IP interface. Another method for replica file data access is to create a
Proxy NAS server on the destination system. The Proxy NAS server is created in
the same manner as any NAS server. It becomes a Proxy NAS server by running a
CLI command to associate it to the replica NAS server. The Proxy NAS server must
be created on the same SP as the replica NAS server. If the replica NAS server is
configured for SMB, the Proxy NAS server must also have the same SMB
configuration. Read-only administrative access to the replica data is provided
through the Proxy NAS server. SMB client Read/Write access to the replica data is
also supported with the Proxy NAS server. For Read/Write access, the user
snapshot must be Read/Write and have a share that is configured on the Proxy
NAS server with the share path that is configured to the Read/Write user snapshot.
Create a NAS Server on destination system Configure proxy settings to replicated NAS Server
command(s) succeeded Example configures a proxy NAS Server named "nas02_Proxy" for a
output is complete
replicated NAS Server named "nas02" and root access to an NFS client.
Command succeeded
To create a proxy NAS server for accessing replica file data, a new NAS server is
created on the destination system. The new NAS server that is the proxy NAS
server must be created on the same storage processor as the replicated NAS
server. It must be configured with the same access protocols that are used on the
replicated NAS server. A similar multitenancy configuration is needed for the proxy
NAS server as the replicated NAS server. A proxy NAS server can support multiple
NAS servers file data access.
The new NAS server is then configured with the proxy settings for the replicated
NAS server. This configuration is performed with the service command svc_nas
over a secure shell connection to the destination system. Use the svc_nas -proxy
-help to view the command syntax to configure a proxy NAS server. Use the
svc_nas -proxy_share -help to view the command syntax to configure an SMB
share for proxy access to a file system on another NAS server. The example
configures a proxy NAS server that is named nas02_Proxy for a NAS server that is
named nas02 and gives a specific NFS client root access.
1. Replication Overview
a. The Dell Unity XT Replication feature creates synchronized redundant data
replicas of storage resources within the same system or remote system.
b. Synchronous replication is a data protection solution for limited distances.
- The operation ensures zero data loss between local source and remote
replica.
- Each block data written is saved to the local and remote system at the
same time.
c. Asynchronous replication is primarily used to replicate data over long
distances.
- The write operations to the source are not instantly replicated to the
remote replica.
- All writes are tracked on the source and the deltas (data difference) are
replicated to the destination during the synchronization cycles.
d. The Dell Unity XT platform supports the asynchronous local replication of
supported storage resources between pools.
e. The Dell Unity XT platform supports asynchronous or synchronous remote
replications of supported storage resources between storage systems.
f. Supported synchronous remote replication topologies are One-Directional,
and Bi-Directional. The supported asynchronous remote replication
topologies are One-Directional, Bi-Directional, One-to-Many, and Many-
to-One.
g. The synchronous replication session states are: Active, Paused, Failed
Over, or Lost Sync Communications. Depending on the session state, the
sync states are In Sync, Syncing, Out of Sync, Consistent, or
Inconsistent.
2. Replication Configuration Process
a. Replication is configured when the supported storage resource is created or
manually created from the resource properties page.
Click the Save Progress and Exit button in the course menu or below
to record this content as complete.
Go to the next learning or assessment, if applicable.