Chapter 14

Information Storage and
Management
Storing, Managing, and Protecting Digital Information
Ali Broumandnia, Broumandnia@gmail.com 1

Section III
Business Continuity
In This Section:
• Chapter 11: Introduction to Business Continuity
• Chapter 12: Backup and Recovery
• Chapter 13: Local Replication
• Chapter 14: Remote Replication

Chapter 14
Remote Replication
• 14.1 Modes of Remote Replication
• 14.2 Remote Replication Technologies
• 14.3 Network Infrastructure
• 14.4 Concepts in Practice: EMC SRDF, EMC SAN Copy, and EMC
Mirror View
• Summary

Key Concepts:
• Synchronous and Asynchronous Replication
• LVM-Based Replication
• Host-Based Log Shipping
• Disk-Buffered Replication
• Three-Site Replication
• Data Consistency

Remote replication is the process of creating replicas of information
assets at remote sites (locations). Remote replicas help organizations
mitigate the risks associated with regionally driven outages resulting
from natural or human-made disasters. Similar to local replicas, they
can also be used for other business operations.
This chapter discusses various remote replication technologies, along
with the key steps to plan and design appropriate remote replication
solutions. In addition, this chapter describes network requirements and
management considerations in the remote replication process.

14.1 Modes of Remote Replication
The two basic modes of remote replication are synchronous and
asynchronous. In synchronous remote replication, writes must be
committed to the source and the target, prior to acknowledging “write
complete” to the host (see Figure 14-1). Additional writes on the source
cannot occur until each preceding write has been completed and
acknowledged. This ensures that data is identical on the source and the
replica at all times. Further writes are transmitted to the remote site
exactly in the order in which they are received at the source. Hence, write
ordering is maintained. In the event of a failure of the source site,
synchronous remote replication provides zero or near-zero RPO, as well
as the lowest RTO.Ali Broumandnia, Broumandnia@gmail.com 6

14.2 Remote Replication Technologies
Remote replication of data can be handled by the hosts or by the
storage arrays. Other options include specialized appliances to
replicate data over the LAN or the SAN, as well as replication
between storage arrays over the SAN.

14.2.1. Host-Based Remote Replication
Host-based remote replication uses one or more components of
the host to perform and manage the replication operation. There
are two basic approaches to host-based remote replication:
LVM-based replication and database replication via log shipping.
• LVM-Based Remote Replication
• Host-Based Log Shipping

LVM-Based Remote Replication
LVM-based replication is performed and managed at the volume group level.
Writes to the source volumes are transmitted to the remote host by the LVM.
The LVM on the remote host receives the writes and commits them to the
remote volume group. Prior to the start of replication, identical volume
groups, logical volumes, and file systems are created at the source and target
sites. Initial synchronization of data between the source and the replica can be
performed in a number of ways. One method is to backup the source data to
tape and restore the data to the remote replica. Alternatively, it can be
performed by replicating over the Until completion of initial synchronization,
production work on the source volumes is typically halted. After initial
synchronization, production work can be started on the source volumes and
replication of data can be performed over an existing standard IP network (see
Figure 14-3).Ali Broumandnia, Broumandnia@gmail.com 11

In asynchronous mode, writes are queued in a log file at the source
and sent to the remote host in the order in which they were
received. The size of the log file determines the RPO at the remote
site. In the event of a network failure, writes continue to
accumulate in the log file. If the log file fills up before the failure is
resolved, then a full resynchronization is required upon network
availability. In the event of a failure at the source site, applications
can be restarted on the remote host, using the data on the remote
replicas. LVM-based remote replication eliminates the need for a
dedicated SAN infrastructure.

Host-Based Log Shipping
Database replication via log shipping is a host-based replication
technology supported by most databases. Transactions to the source
database are captured in logs, which are periodically transmitted by
the source host to the remote host (see Figure 14-4). The remote
host receives the logs and applies them to the remote database.

Because the source host does not transmit every update and
buffer them, this alleviates the burden on the source host CPU.
Similar to LVM-based remote replication, the existing
standard IP network can be used for replicating log files. Host-
based log shipping does not scale well, particularly in the case
of applications using federated databases.

14.2.2 Storage Array-Based Remote
Replication
In storage array-based remote replication, the array operating
environment and resources perform and manage data replication.
This relieves the burden on the host CPUs, which can be better
utilized for running an application. A source and its replica device
reside on different storage arrays. In other implementations, the
storage controller is used for both the host and replication
workload. Data can be transmitted from the source storage array to
the target storage array over a shared or a dedicated network.

Synchronous Replication Mode

For synchronous remote replication, network bandwidth equal to
or greater than the maximum write workload between the two sites
should be provided at all times. Figure 14-6 illustrates the write
workload (expressed in MB/s) over time. The “Max” line indicated
in Figure 14-6 represents the required bandwidth that must be
provisioned for synchronous replication. Bandwidths lower than
the maximum write workload results in an unacceptable increase
in application response time.

Asynchronous Replication Mode

Some implementations of asynchronous remote replication maintain write
ordering. A time stamp and sequence number are attached to each write
when it is received by the source. Writes are then transmitted to the remote
array, where they are committed to the remote replica in the exact order in
which they were buffered at the source. This implicitly guarantees
consistency of data on the remote replicas. Other implementations ensure
consistency by leveraging the dependent write principle inherent to most
DBMSs. The writes are buffered for a predefined period of time. At the
end of this duration, the buffer is closed, and a new buffer is opened for
subsequent writes. All writes in the closed buffer are transmitted together
and committed to the remote replica.

Disk-Buffered Replication Mode

Three-Site Replication
• In synchronous and asynchronous replication, under normal conditions
the workload is running at the source site.
• In synchronous replication, source and target sites are usually within
200 KM (125 miles) of each other.
• A regional disaster will not affect the target site in asynchronous
replication, as the sites are typically several hundred or several
thousand kilometers apart.
• Three-site replication is used to mitigate the risks identified in two-site
replication. In a three-site replication, data from the source site is
replicated to two remote data centers.

Three-Site Replication—Cascade/Multi-hop
In the cascade/multi-hop form of replication, data flows from
the source to the intermediate storage array, known as a bunker, in
the first hop and then from a bunker to a storage array at a remote
site in the second hop. Replication between the source and the
bunker occurs synchronously, but replication between the bunker
and the remote site can be achieved in two ways: disk-buffered
mode or asynchronous mode.

Synchronous + Asynchronous
This method employs a combination of synchronous and
asynchronous remote replication technologies. Synchronous replication
occurs between the source and the bunker.
Synchronous replication occurs between the source and the bunker.
Asynchronous replication occurs between the bunker and the remote
site.
The remote replica in the bunker acts as the source for the asynchronous
replication to create a remote replica at the remote site. Figure 14-10(a)
illustrates the synchronous + Asynchronous method.

Synchronous + Disk Buffered
This method employs a combination of local and remote
replication technologies. Synchronous replication occurs between
the source and the bunker: A consistent PIT local replica is created
at the bunker. Data is transmitted from the local replica at the
bunker to the remote replica at the remote site. Optionally, a local
replica can be created at the remote site after data is received from
the bunker. Figure 14-10(b) illustrates the synchronous
+ disk buffered method.

Three-Site Replication—Triangle/Multi-target
In the three-site triangle/multi-target replication, data at the source
storage array is concurrently replicated to two different arrays. The
source-to bunker site (target 1) replication is synchronous, with a near-
zero RPO. The source-to remote site (target 2) replication is
asynchronous, with an RPO of minutes. The distance between the source
and the remote site could be thousands of miles. This configuration does
not depend on the bunker site for updating data on the remote site,
because data is asynchronously copied to the remote site directly from the
source.

14.2.3 SAN-Based Remote Replication
• SAN-based remote replication enables the replication of data between
heterogeneous storage arrays. Data is moved from one array to the
other over the SAN/ WAN.
• SAN-based remote replication is a point-in-time replication
technology. Uses of SAN-based remote replication include data
mobility, remote vaulting, and data migration.
• SAN-based replication uses two types of operations: push and pull.
These terms are defined from the perspective of the control array.
• In SAN-based replication, the control array can keep track of changes
made to the control devices after the replication session is activated.
This is allowed in the incremental push operation only.Ali Broumandnia, Broumandnia@gmail.com 31

14.3 Network Infrastructure
For remote replication over extended distances, optical network
technologies such as dense wavelength division multiplexing
(DWDM), coarse wavelength division multiplexing (CWDM), and
synchronous optical network (SONET) are deployed.

14.3.1 DWDM
DWDM is an optical technology by which data from different
channels are carried at different wavelengths over a fiber-optic
link. It is a fiber-optic transmission technique that uses light
waves to transmit data parallel by bit or serial by character. It
integrates multiple light waves with different wavelengths in a
group and directs them through a single optical fiber. Using
DWDM, different data formats at different data rates can be
transmitted together. Specifically, IP ESCON, FC, SONET and
ATM data can all travel at the same time within the optical fiber
(see Figure 14-12).

CWDM, like DWDM, uses multiplexing and demultiplexing on
different channels by assigning varied wavelengths to each channel.
Compared to DWDM, CWDM is used to consolidate environments
containing a low number of channels at a reduced cost.

14.3.2 SONET
SONET (synchronous optical network) is a network technology
that involves transferring a large payload through an optical fiber
over long distances. SONET multiplexes data streams of different
speeds into a frame and sends them across the network. The
European variation of SONET is called synchronous digital
hierarchy (SDH). Figure 14-13 shows the multiplexing of data
streams of different speeds in SONET and SDH technologies.
SONET/SDH uses generic framing procedure (GFP) and supports
the transport of both packet-oriented (Ethernet, IP) and character-
oriented (FC) data.

14.4 Concepts in Practice: EMC SRDF, EMC
SAN Copy, and EMC Mirror View
This section discusses three EMC products that use remote
replication technology. EMC Symmetric Remote Data Facility
(SRDF) and EMC Mirror View are storage array–based remote
application software's supported by EMC Symmetric and Clarion
respectively. EMC SAN Copy is SAN-based remote replication
software deployed in an EMC Clarion storage array.

14.4.1 SRDF Family
SRDF offers a family of technology solutions to implement
storage array-based remote replication technologies. The three
Symmetric solutions are:
• SRDF/Synchronous (SRDF/S)
• SRDF/Asynchronous (SRDF/A)
• SRDF/Automated Replication (SRDF/AR)

14.4.2 Disaster Recovery with SRDF
The source arrays have SRDF R1 devices (source devices), and the
target arrays have SRDF R2 devices (replica devices). Data written
to R1 devices is replicated to R2 devices, either synchronously or
asynchronously. SRDF R1 and R2 devices can have any local
RAID protection, such as RAID 1 or RAID 5. SRDF R2 devices
are in a read-only (R/O) state when remote replication is in effect.
Hence, under normal operating conditions, changes cannot be
made directly to the R2 devices. The R2 devices can only receive
data from their corresponding R1 devices on the source storage
array.

Failover

Failback

14.4.3 SRDF Operations for Concurrent
Access
SRDF provides split operations to enable concurrent access to both
source and target devices. The establish and restore operations are
used to return the source-target pairs to the normal SRDF state. In
split operation, when R2 is split from R1, BC operations can be
performed on R2. The split operation enables concurrent access to
both the source and the target devices. In this operation, target
devices are made R/W, and the SRDF replication between the
source and the target is suspended, as shown in Figure 14-16.

During concurrent operations while in a SRDF split state,
changes could occur on both the source and the target devices.
Normal SRDF replication can be resumed by performing an
establish or a restore operation. With either establish or restore,
the status of the target device becomes R/O (see Figure 14-17).

14.4.4 EMC SAN Copy
SAN Copy is CLARiiON software that performs SAN-based
remote replication between CLARiiON and Symmetric or other
vendor storage arrays. It enables simultaneous creation of one or
more copies of source devices to target devices through a SAN.
Source and target devices could either be on a single array or on
multiple arrays. SAN Copy software on the CLARiiON
(designated as the control storage array) controls the entire
replication process.
• Automatic check pointing in the event of a link failure
• Transfer rate throttle

14.4.5 EMC Mirror View
• EMC MirrorView is a CLARiiON-based software that enables storage
array– based remote replication over FC SAN, IP extended SAN, and
TCP/IP networks. MirrorView family consists of Mirror
View/Synchronous (MirrorView/S), and MirrorView/Asynchronous
(MirrorView/A). MirrorView software must be installed at both source
and target CLARiiON in order to perform remote replication.
• MirrorView supports both synchronous and asynchronous replication of
data on the same CLARiiON. It also supports consistency groups for
maintaining data consistency across write-order dependent LUNs.

Mirror View Operations
• Initial Synchronization is a replication process that is used for new
mirrors (target) to create an initial copy of the primary/primary image
(LUN on source CLARiiON containing production data). During the
initial synchronization process, the primary images remain online
whereas the secondary/secondary image (LUN that contains a mirror of
the primary image) is inaccessible.
• A fracture operation stops MirrorView replication. An administrator can
initiate fracture to suspend the replication. MirrorView software can
automatically fracture when it senses a connectivity failure between the
primary and secondary LUNs.

• MirrorView/S invokes a fracture log when the secondary image is
fractured. The fracture log is a bitmap held in the memory of the
storage processor that owns the primary LUN.
• MirrorView/A does not use fracture and write intent logs, but it tracks
locations (using Snap View technology) at the primary LUNs where
updates occur. MirrorView/A utilizes the delta set mechanism to
periodically transfer data to the secondary LUNs. MirrorView uses two
bitmaps on the primary LUNs.
• A secondary image is promoted to the role of primary, when it is
necessary to run production applications at the disaster recovery site.

Summary
This chapter detailed remote replication. As a primary utility, remote
replication provides disaster recovery and disaster restart solutions. It
enables business operations to be rapidly restarted at a remote site
following an outage, with acceptable data loss. Remote replication
enables BC operations from a target site. The replica of source data at the
target can be used for backup and testing. This replica can also be used
for data repurposing, such as report generation, data warehousing, and
decision support. The segregation of business operations between the
source and target protects the source from becoming a performance
bottleneck, ensuring improved production performance at the source.

Remote replication may also be used for data center migrations, providing
the least disturbance to production operations because the applications
accessing the source data are not affected. This chapter also described
different types of remote replication solutions. The distance between the
primary site and the remote site is a prime consideration when deciding
which remote replication technology solution to deploy. Asynchronous
replication may adequately meet the RPO and RTO needs, while
permitting greater distances between the sites. Storage management
solutions provide the capability to not only automate business continuity
solutions, but also enable centralized management of the overall storage
infrastructure. Organizations must ensure security of the information
assets. The next chapter details storage security and management.Ali Broumandnia, Broumandnia@gmail.com 53

Chapter 14

More Related Content

What's hot (20)

Similar to Chapter 14 (20)

More from Ali Broumandnia (14)

Recently uploaded (20)

Chapter 14