RecoverPoint Implementation Student Guide

RecoverPoint Implementation
Student Guide
Education Services
July 2013
Welcome to RecoverPoint Implementation.

Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011,2012, 2013 EMC Corporation. All Rights
Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne,
EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica,
Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra,
Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology,
Common Information Model, Configuration Intelligence, Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz, DatabaseXtender, Direct
Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender,
Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization,
Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever,
MediaStor, MirrorView, Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap, QuickScan,
Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts,
SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix
VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual
Provisioning, VisualSAN, VisualSRM, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and where
information lives, are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
Copyright 2013 EMC Corporation. All rights reserved. Published in the USA.
Revision Date: 07/25/2013

Revision Number: MR-7CP-RPSYSDEP.7722.4.0
Copyright 2013 EMC Corporation. All rights reserved
Course Introduction: RecoverPoint System Deployment
This course covers RecoverPoint Installation and Operations.
This module focuses on the different RecoverPoint configurations and an overview of the
multiple installation and configuration procedures when deploying a RecoverPoint solution.
Module 1: RecoverPoint Overview
This lesson covers RecoverPoint solutions.
EMC RecoverPoint is an out-of-band solution which offers advanced capabilities to deliver

enterprise-level data protection, replication, and disaster recovery. This network-based
block-level solution allows customers to protect data locally for operational and application
recovery needs. It also protects the same data remotely for disaster recovery purposes.
RecoverPoint maintains write-order consistency of the replicated data across all volumes
without impacting the production data flow between an application server and its storage.
Write-order consistency guarantees that all data written to storage is delivered in the proper
sequence so that the data can be re-used by an application after it has been replicated or
copied to a different site.
Lets take a look at how EMC RecoverPoint addresses customers challenges.

RecoverPoint ensures data replication, with high availability, and without impact to the production application
server or its data. The replicated data is stored in the same format as the source data, which eliminates the
need for costly encapsulation/de-encapsulation processes that other vendors require.
RecoverPoint is designed for enterprise customers. It includes key features such as bi-directional local and/or
remote replication, WAN optimization, and a policy-driven process. In addition, RecoverPoint ensures
consistent recovery regardless of replication distances, without requiring costly secondary or tertiary copies of
the replicated data.
RecoverPoint is not a one-size-fits-all approach. Customers can specify unique RPO/RTO polices for each of
their applications. In addition, RecoverPoint lets customers leverage under-utilized resources in one data
center to protect the resources in another data center. Providing the same functionality for data protection,
regardless of the host or storage configuration, ensures that the customers RecoverPoint investment is
maximized.
Finally, RecoverPoint protects the customers existing investment in their server, SAN and storage architectures
by providing replication across heterogeneous server and storage environments. RecoverPoint is also designed
to minimize the bandwidth consumed for replication between sites. These sites may be separated by large
physical distances. Reducing the required bandwidth can decrease monthly operating expenses for
WAN connections.
RecoverPoint provides local data protection and replication for virtual machines. It uses
continuous data capture for local SAN data protection to protect the virtual machines, as well
as the VMware ESX server platform, from data corruption. It also guarantees recoverability
locally with no data loss. RecoverPoint supports virtual-to-virtual replication between
equivalent storage configurations, such as VMFS to VMFS or RDM/P to RDM/P. This support
uses the VNX series or CLARiiON array-based write splitter or an intelligent-fabric write
splitter. Similarly, RecoverPoint supports physical and physical-to-virtual replication, as well
as virtual-to-virtual replication using host-based RecoverPoint write splitters installed in each
guest operating system. Physical RDM (RDM/P) -attached volumes are replicated locally
and/or remotely.
RecoverPoints VMware support can be used to enhance existing VMware vMotion and
Storage vMotion solutions. RecoverPoint integrates with vCenter Server to allow the
RecoverPoint administrator to quickly view virtual machines fully protected by RecoverPoint,
and for those not fully protected, to see which of the virtual machines LUNs/data stores are
not protected. Additionally, RecoverPoint is integrated with VMware vCenter Site Recovery
Manager to simplify and automate disaster recovery in VMware Infrastructure. RecoverPoint
also has a vCenter Server plug-in that automates failback for SRM configurations.
The RecoverPoint management GUI can be used to monitor virtual machine protection status
as well as physical LUNs. This ability to monitor physical and virtual storage extends to
heterogeneous storage.
If you are considering Microsoft Hyper-V, RecoverPoint can fully protect any Hyper-V
virtualized application as long as its data resides on a SAN. RecoverPoint supports Microsoft
VSS and VDI, Windows Server Core, as well as Cluster Enabler version 4 under Hyper-V.
RecoverPoint 4.0 integration with SRM enables users to test or failover SRM protection
groups to any point in time. This is done using the vSphere client and the Virtual Storage
Integrator (VSI) RecoverPoint Management. VSI is free of charge and downloadable from
support.emc.com. Installation, configuration, and usage of VSI RecoverPoint Management is
quick, easy, and very similar to all other VSI products.
The process is simple. Simply apply the point in time copy to use with SRM, run the SRM test
or failover procedure, and the test or failover will occur using the point in time specified.
RecoverPoint v4.0 and beyond provides the capability to concurrently protect data to
multiple disaster recovery sites using a single management point. For example, data can be
protected locally on one RPA cluster and concurrently copied to up to four remote RPA
clusters (fan out), or replicated from up to four remote RPA clusters to one, central RPA
cluster (fan in). As shown in both examples, there can be up to five RPA clusters in a
RecoverPoint system.
The RecoverPoint/SE system supports VNX/CLARiiON storage arrays when using

VNX/CLARiiON splitters with hosts running operating systems compatible with
RecoverPoint and the VNX/CLARiiON array.
RecoverPoint/SE Continuous remote replication (CRR) enables block protection as well as a
file DR solution. This enables failover and failback of both block and file data from one VNX
to another.
RecoverPoint/EX provides all of the data protection of RecoverPoint/CL, with the following
limitations:
Only the following storage arrays are supported:
VMAX Series
VNX Series
CLARiiON CX3 and CX4 series
VPLEX Local and Metro storage virtualization platforms
The following splitters are supported:
VNX/CLARiiON
Symmetrix
VPLEX
EMC RecoverPoint/CL provides block-level replication for on-demand protection and

recovery to any point-in-time image. This enables you to implement a single, unified
solution to protect and/or replicate data across heterogeneous storage.
RecoverPoint/CL is the full-featured offering which allows a single cluster to utilize EMC
storage array-based write splitters including the VPLEX splitter.
10
The EMC RecoverPoint family provides cost-effective, local and remote replication data
protection solutions that include point-in-time data recovery.
RecoverPoint/SE is the entry offering and is ideal for homogeneous VNX/CLARiiON CX
environments. RecoverPoint/SE is limited in function compared to RecoverPoint/CL or
RecoverPoint/EX, though does allow for the use of virtual RPAs.
If you require support for arrays other than VNX/CLARiiON, then RecoverPoint/CL or
RecoverPoint/EX is a more ideal solution than RecoverPoint/SE. RecoverPoint/CL also
supports VPLEX Local and Metro.
RecoverPoint/EX provides all of the data protection of RecoverPoint/CL. However, some
limits apply on storage array types. RecoverPoint/EX supports VMAX series, VNX series,
CLARiiON CX3 and CX4 series, Celerra unified storage environments, and VPLEX Local and
Metro storage virtualization platforms. RecoverPoint/EX supports VNX/CLARiiON-based
splitters, Symmetrix-based splitters and VPLEX splitters.
Some common features for the RecoverPoint family are:
Synchronous replication
Multipath I/O support
Virtualization hypervisor support for Hyper-V and VMware platforms.
Integration with VMware vCenter, VMware SRM and VAAI
Built-in bandwidth reduction
RPAs are available as physical servers or virtual appliances
Two to eight RecoverPoint appliances per RPA cluster for failure resiliency and throughput
11
This lesson covers the RecoverPoint components, the volume allocation requirements and
the general requirements when deploying a RecoverPoint solution.
12
A group of 2-8 physical (or virtual) RPAs that work together to replicate and protect data at the same
geographical location are called an RPA cluster. There can be up to five RPA clusters in a RecoverPoint
system. To scale-up and support a higher throughput rate, you can add up to eight RPAs to your RPA
clusters.
The number of RPAs in an RPA cluster must be the same at all RPA clusters in a RecoverPoint system.
You can manage all RPAs in an RPA cluster through a floating cluster Management IP address. In
other words, once RecoverPoint is configured, you can manage the entire installation from a single IP
address.
Each Cluster has its own repository volume. The Replication volumes, a copy or production, belong to
a cluster. RecoverPoint Write-Splitters are assigned to the cluster to which they are connected.
Clusters are licensed separately; each one must have a license. RecoverPoint clusters can be
connected to each other using Fibre Channel or the WAN connection. A cluster is installed, then
connected to another during deployment.
A cluster has a high-availability architecture with no single point of failure. New nodes can be added
or removed from the cluster as needed. Consistency Groups are configured within a node.
The maximum number of consistency groups per RPA cluster is 128. The recommended maximum
number of consistency groups per RPA is 64. In case an RPA fails, consistency groups will fail over to
another RPA.
A single RPA cannot be configured to have more than 64 consistency groups. However, in the event
of RPA failure, groups on one RPA will move to other RPAs in the cluster. In such a case, an RPA can
temporarily hold up to 128 groups, and the data of all the groups will continue to be transferred
between sites. This state is temporary, however, as an RPA with more than 64 groups may run into
high loads, and you may not be able to meet your group policies.
13
The Repository volumes contain consistency group metadata, and they are created on
existing storage arrays in the SAN environment. The Repository volumes serve all RPAs and
associated splitters for each cluster at a particular site, and they are created as part of the
installation process.
In a CRR configuration, there must be one Repository volume for the RPA cluster on the local
and remote site.
The Repository volume must be presented only to the RPAs.
The minimum size for a repository volume is 3 GB. However, for RecoverPoint/SE, the
following rules apply:
In RecoverPoint/SE 3.4 and later AND selecting the repository volume manually, the
size should be 2.86 GB on existing RAID groups (not RAID 0 groups); any capacity
beyond 3 GB is not used.
In RecoverPoint/SE 3.4 and later AND selecting the repository volume automatically,
the size should be 5.72 GB on existing RAID groups (not RAID 0 groups); capacity
beyond 5.72 GB is not used.
14
Each copy of a consistency group must contain one or more volumes that are dedicated to
holding system information or point in time history. The type of information contained in the
journal differs according to the journal type.
There are two types of journals:
Copy journals
Production journals
Copy journals are dedicated to holding point-in-time information for each image on the
production storage, as well as bookmarks that mark significant points in time. The copy
journals hold all changes to data, so that the copy storage can be rolled back to a previous
point in time (PIT). There are as many copy journals as there are local and remote copies in a
consistency group.
Production journals are dedicated to store information about the replication process (called
marking information) that is used to make synchronization between the production and copy
volumes, when required, much more efficient.
15
The size of a Journal volume is based on the length of time the user wishes to recover to for a specific
consistency group. For instance, if snapshots for a consistency group must be stored for 24 hours, the
journal volume must be at least as large as the amount of expected snapshot writes for a day.
The Journal Volume has two components
Snapshot portion (80%) contains all snapshots replicated plus undo information to rollback
to a specific snapshot
Target Side Processing portion (20%) contains all of the undo information while the
volumes are in TSP mode
Best characteristics for Journal volumes
Mirrored for protection
Striped and Mirrored on target side for reliability and speed
5 I/Os for each replicated write (Journal volume is not full)
Flexible Journal volume pool and application tolerance for sizing
Recall that Journal volume is sized by determining the following:
Data set to be replicated
RTO/RPO to be achieved history is required
Rate of data change
Average I/O write rate must be determined over a long period of time.
Journal volumes should be able to:
Sustain 2X sequential writes and X sequential reads
Use striping across a volume set to increase performance
To prevent the possible loss of all journal snapshots during a group resynchronization, the
recommended minimum journal size is 10 GB for a non-distributed consistency group, or 40 GB for a
distributed consistency group.
16
Snapshots include only that data that has changed from the previous snapshot. Upon being
distributed, a snapshot creates a new current image on the remote storage. A snapshot is the
difference between one consistent image of stored data and the next.
Snapshots are taken seconds apart. The application writes to storage; at the same time, the
splitter provides a second copy of the writes to the RPA. In asynchronous replication, the RPA
gathers several writes into a single snapshot. The exact time for closing the snapshot is
determined dynamically depending on replication policies and the journal of the consistency
group. All snapshots are crash-consistent by default.
When replicating synchronously, each write is a snapshot. When the snapshot is distributed
to a copy, it is stored in the journal, making it possible to revert to previous images at any
point in time.
17
RecoverPoint Copies are all of the volumes of a consistency group that are either a source or
a target of replication at a given RPA cluster.
The following types of copies exist in a consistency group:
The production copyThe production copy consists of all of the volumes that are the
sources of replication of a consistency group, as well as the production journal volumes
Local copiesA local copy consists of all of the volumes that are the targets of replication,
for a specific consistency group
The following limitations apply to copies:

A maximum of one production copy and up to four non-production copies can be
configured per consistency group.
In local replication, there can be only one production copy and one local copy.
In remote replication, if a local copy exists there can be up to three remote copies. If a
local copy does not exist, there can be up to four remote copies.
A single cluster can have 2 remote copies maximum
18
The consistency group ensures that updates to the replicas are always consistent and in
correct write order; that is, the replicas can always be used to continue working or to restore
the production source, in case it is damaged. The consistency group monitors all the volumes
added to it to ensure consistency and write-order fidelity. If two data sets are dependent on
one another (for instance, a database and a database log), they must be in the same
consistency group.
A consistency group includes these elements:
Settings and policies: Settings, such as consistency group name, primary RPA,
reservation support; policies, such as compression, bandwidth limits, and maximum
lag, that govern the replication process.
Replication sets: A consistency group consists of one or more replication sets. Each
replication set consists of a production volume and the replica volumes to which it is
replicating.
Journals: Receive changes to data. Each copy has a single journal. Changes are
distributed from the replica journal to storage. The replica journals also retain
rollback data for their replica. The production journal does not contain rollback
information. The system marking information is contained in the production journal.
19
The RecoverPoint Appliance (RPA) is the data-protection controller for RecoverPoint. RPA
nodes utilize private LAN and shared RPA volumes for communications using the standard
TCP protocol. No FC/IP converters are needed to replicate across the WAN. The set of RPAs
at each site constitutes an RPA cluster, where each cluster can include from two to eight RPA
nodes, as configured during RecoverPoint system installation. The cluster size must be the
same at all sites in an installation. In normal operation, all RPAs in a cluster are active all of
the time. Consequently, if one of the RPAs in a cluster goes down, the RecoverPoint system
supports immediate switchover of the functions of that node to another RPA in the cluster.
With RecoverPoint version 4.0, the RPA is supported on hardware platforms (Gen4 or Gen5)
that each include a single quad port QLE2564 8 Gb HBA which supports native 8 Gb/s Fibre
Channel connectivity.
Previous hardware platforms, Gen 3 and below, are not supported with RecoverPoint version
4.0 and beyond.
20
Although deployed and used in fundamentally the same way as physical RPAs, the
RecoverPoint vRPA is the virtual appliance implementation of the RecoverPoint Appliance. As
with any other virtual machine, the vRPA operates with dynamic virtual resources allocated
to it from the hosting hypervisor.
21
Please note the following special information and best practices when using vRPA. vRPA
cluster nodes should not share the same hypervisor server. This allows for redundancy in
case the host hypervisor server fails. It also allows virtual machine load sharing across the
physical resources of multiple hosts. Where multiple vRPAs must run on the same host,
sufficient resources must be made available, especially to allow proper operation during
peak RPA load times.
RPAs and vRPAs cannot be mixed in one cluster. The cluster must be either all physical RPAs
or all vRPAs.
However, replication is supported between any of the following cluster types:
RPA and RPA
RPA and vRPA (in either direction)
vRPA and vRPA
In RecoverPoint/SE installations, the number of RPAs in each of the two clusters must be the
same, regardless of whether they are physical or virtual.
vRPA is currently certified to be deployed only on the VMware vSphere environment.
Although similar in operation and use, distinct differences in installation and deployment
exist between physical and vRPAs. Because of this, the vRPA is not covered in detail in this
course. Please refer to the EMC RecoverPoint vRPA Technical Notes for more information
about vRPA installation, deployment and management within the VMware vSphere and
vCenter environments.
22
There are three types of RecoverPoint licenses: RP/SE, RP/EX, and RP/CL. As with previous
RecoverPoint versions, RP/SE only supports a single VNX and CLARiiON-based splitter for
each cluster. It allows a maximum of two clusters, and each cluster needs its own license.
The license is based on the array and is tied to the array serial number. There are no
capacity-based RP/SE licenses. The license covers the entire array capacity. If a VNX at a
single cluster is being used for both local and remote replication, it will need both a local
replication and a remote replication license.
RP/EX supports all VMAX-based, VNX-based, and VPLEX splitters. Similar to RP/SE licenses,
RP/EX licenses are tied to the array serial number. Each array used in a cluster needs a EX
license for both local and/or remote replication. RP/EX licenses for the VNX-based splitters
are for the entire array. RP/EX licenses for VNX-based splitters are not based on capacity.
RP/EX licenses for VMAX-based and VPLEX splitters are per registered capacity. Registered
capacity means the amount of data on the array that is being protected. Locally registered
capacity is licensed separately from remotely registered capacity. RecoverPoint/EX licenses
for the VMAX can be purchased either by registered capacity or by raw capacity.
RecoverPoint/CL licenses are based on the replicated capacity. Replicated capacity simply
means the amount of data that is being replicated. RP/CL licenses are not tied to any arrays.
This makes the replication environment very flexible, since adding, changing, and refreshing
arrays does not require any change to the RecoverPoint license. RecoverPoint/Cluster
Enabler (RP/CE) is included with all RP 4.0 offerings.
23
RecoverPoint 4.0 introduces the Unisphere for RecoverPoint user interface, a web based
client that replaces the RecoverPoint Management Application available with previous
versions of RecoverPoint. Users familiar with any one of the EMC Common User Interface
Toolkit-based interfaces will find it easy and intuitive to navigate through the Unisphere for
RecoverPoint GUI. This significantly reduces the learning curve for users. When logged in,
users are immediately presented with a topology of their RecoverPoint system, as well as
health and traffic information. All protection and recovery operations are wizard-based with
clearly defined, intuitive steps.
24
The RecoverPoint CLI can be used to configure and manage an individual RPA or the entire
RecoverPoint Cluster. The 2 user accounts are the Admin account and the boxmgmt account.
The admin account is used to perform replication tasks, such as consistency group creation,
testing an image, and failover. The cluster or site management address can be used via an
ssh connection. If an RPAs management address is used, the RPA must be attached to the
cluster for a connection to be made.
The boxmgmt account launches the Installation Manager menu upon successful login.
This is normally used for each individual RPA. This menu-driven program allows for the
installation, configuration, and diagnostics of an RPA.
25
This lesson covers the RecoverPoint write-splitting options available.
26
This slide shows the types of array-based write splitting used with RecoverPoint. They are:
CLARiiON CX3/CX4, VNX Block, VMAX arrays and VPLEX.

Note: Only VNX/CLARiiON splitter and VMAX splitter will be covered in details during this
course. If you want to learn more about host-based splitters, fabric-based splitters and VPLEX
splitter refer to EMC Education Services site and search for:
RecoverPoint VPLEX Splitter Deployment and Management elearning

RecoverPoint Symmetrix Splitter Deployment and Management elearning
Each elearning has a video demonstration plus associated hands-on labs.
Beginning with RecoverPoint version 4.0, host- and SAN-based splitting are no longer
supported.
27
This slide describes the data flow from the application host to the production volumes and
how the RecoverPoint Appliance accesses the data as part of the CDP process.
An application server issues a write to a LUN that is being protected by RecoverPoint. This
write is split, then sent to the RecoverPoint Appliance.
As shown in this slide, split is through the VNX/CLARiiON splitter which resides on each
storage processor. Host writes are split at the array and sent to the production copy through
the RPA. The original write travels though its normal path to the production LUN.
28
The Symmetrix RecoverPoint write splitter is supported on the VMAX family of arrays with
Enginuity 5876 or later.
The Symmetrix splitter is based on Open Replicator for Symmetrix (ORS). Splitting occurs at
the Symmetrix Fibre Channel Director/Interface Adapter (FA) port. Because of this,
RecoverPoint must be zoned to the same FA ports as the replicated hosts.
From RecoverPoint 4.0 and later and Symmetrix Enginuity 5876 Q2 2013 SR and later, it is
permitted to replicate the same device with both RecoverPoint and SRDF, as long as SRDF
and RecoverPoint are replicating to two different target devices, and RecoverPoint is
replicating only to a local copy.
29
RecoverPoint combined with the VPLEX write splitter provides any point-in-time business
continuity recovery to protect VPLEX platform data across a mixture of EMC and non-EMC
arrays. In addition, RecoverPoint can test replicated data on virtual volumes without impact
to production applications.
Before RecoverPoint version 4.0 there were three types of available write splitters: host,
array and intelligent fabric splitters. As of version 4.0, only array-based splitters are available
for RecoverPoint. Particular to VPLEX, the write splitter is built into the VPLEX engine,
making this more of a transparent implementation. Also, this makes RecoverPoint services
uniformly available to EMC and non-EMC arrays alike.
The VPLEX write splitter supports RecoverPoint CRR, CDP and CLR using all arrays that VPLEX
supports and with full VPLEX functionality. The RecoverPoint VPLEX splitter supports
virtualized environments and clustering environments. These environments include VMware
HA, Microsoft MSCS/Failover clustering, Oracle stretched RAC, Oracle OVM and AIX stretched
clusters.
30
All VPLEX splitter directors on a single VPLEX platform will share the same settings. Any
operation on the VPLEX splitter will affect all its directors.
New and replaced directors will be detected and added automatically.
RecoverPoint will support the procedure of replacing directors (i.e. faulty ones) nondisruptively.
31
This lesson covers the connectivity options, zoning and masking considerations, and cabling
requirements when deploying a RecoverPoint solution.
32
The network connection consists of a management network and a replication network.
The management network has a static IP address for each appliance and a floating
static IP address for each site. The management network manages the appliances as
well as accesses the replications management CLI and GUI.
The replication network consists of a static IP address for each appliance. It

communicates to the appliances on the opposite site and replicates data between the
sites. An NTP server ensures proper time synchronization with the outside world. It is
located only on the primary site, since the appliances have an internal
synchronization method to ensure all appliances are synchronized.
Note: An NTP server is recommended, but not required, and is typically connected
through the management network.
The RecoverPoint replication solution contains a SAN Discovery feature that enables the
appliances to automatically detect and display information about the LUNs that the
appliances can see on the storage. This information includes: WWN, LUN, size, and storage
type. To determine what LUNs are associated with which replication volume, the WWN, LUN
and size must be determined ahead of time. Volume replication sets are a matching of
replication volumes that replicate between each other. Once the replication volumes have
been determined based on the WWN, LUN and size, they need to be associated into these
replication pairs.
33
In order to size the pipe, you need to know:
Average incoming I/O for a representative window in MB/s (24hrs/7days/30 days)

Compression level achievable on the data (often hard to obtain rule of thumb is 2x
6x)
From these numbers, we can compute the minimal bandwidth requirements of the
environment the multiplication of the compression level by the average incoming data.
Allocating this bandwidth for replication does not give any guarantees on RPO, or the
frequency of high loads. This is due to fact that I/O rate may fluctuate throughout the
representative period. This bandwidth is minimal in the sense that anything below it will not
necessarily suffice to sustain the incoming I/O.
To determine the actual bandwidth needed to meet the end user requirements, one must
understand the user RPO requirements, and analyze the I/O fluctuations.
34
The following are caveats/notes on RecoverPoint compression:
With RecoverPoint v3.x and above , compression can now be enabled on a

consistency group basis.
If compression settings are changed, it will result in a loss of the journal volume and
requires a full sweep.
35
The slide shows a typical SAN environment with mirrored fabrics. When mirroring an
environment, start by configuring each physical device in the storage array so that it is
presented across multiple storage ports. These storage ports would then be distributed
evenly across both fabrics. Each host accessing this storage would also have multiple ports
distributed across both fabrics. Volume access and device pathing to these storage arrays
through the servers would be handled by load balancing and path fail over software, such as
PowerPath. PowerPath manages the representation of the multiple instances of the same
devices to the host, and manages the load balancing and path failover necessary to maintain
the high availability of the environment.
36
Physical RPAs connect to the hosts and storage subsystems through a Fibre Channel SAN.
Before deploying RecoverPoint, these subsystems should be in place.
In preparation for RecoverPoint deployment, ensure that there is one RPA Fibre Channel port
available per RPA per FC fabric. This ensures high availability by providing redundancy
between all components at the site.
Note: A dual fabric configuration is required at all sites for RPA, host, and storage
connectivity.
37
RecoverPoint/SE supports two network topologies; dual-fabric and direct attach.

A dual-fabric topology is recommended, and must include the following connections:
A port on each VNX/CLARiiON storage processor to each fabric.
Host and storage devices must be connected to the Fabric. In most installations, these
connections already exist.
Minimum of one RPA FC port connected to each fabric.
38
A direct attach, switchless topology is intended for iSCSI environments. In iSCSI

environments, you should ensure all RPAs are physically connected to each other through
their HBA FC ports. In iSCSI configurations, there can be a maximum of two RPAs per RPA
cluster since two of the four existing RPA HBA FC ports are already connected directly to the
storage (for high availability). If more than two RPAs are required for the cluster, connect all
of the RPAs in the cluster through FC switches and zone them together.
Summary of the connections:
Each RPA to one port on each VNX/CLARiiON storage processor.
Two Fibre Channel ports connecting the two RPAs.
39
Within the supported hypervisor, its recommended to create four virtual networks. One for
the LAN connectivity; one for the WAN; and two for the iSCSI (one per VM adapter). Also, its
recommended that the hypervisor have at least two physical network adapters to segment
the traffic between the LAN/WAN and iSCSI. For High Availability purposes, consider having
two physical adapters for the iSCSI network as shown in the picture.
The physical network will need to be segmented in three; one for the LAN/WAN
connectivity, and one for each iSCSI connection.
Please note that vRPAs do not use the VMware vmkernel iSCSI ports. vRPAs run iSCSI over
standard IP network ports.
40
Zoning instructions vary according to the type of HBA ports installed in your RPAs and the splitter type to
be implemented. Here is information regarding RecoverPoint version 4 and for historical reference,
version 3.5. To determine which HBA ports are installed in your system, use one of the following methods:
1. Check your invoice:
Item numbers RP-HW-1U-GEN4/GN4n/GEN5/GN5n correspond to QLE25xx HBA.
Item number RP-HW-1U corresponds to QLA23xx HBA.
2. Check the HBA card bracket at the back of the RPA:
QLE25xx HBA has 8 Gb stamped on the card bracket.
QLE24xx HBA has 4 Gb stamped on the card bracket.
QLA23xx HBA has nothing written on the card bracket.
Here are some general guidelines and best practices when zoning RPAs:
Do not share VNX/CLARiiON ports between MirrorView and RecoverPoint

RPA HBA ports as both initiators and targets. Best practice is to use the RPA HBA ports as both initiators
and targets. In this configuration, maximum performance and redundancy is achieved with optimal use of
resources. Initiator-target separation is not supported in the following cases:
- When mixing different splitter types in the same site
- When using remote replication over Fibre Channel
- When using distributed consistency groups
Zone members. In general, EMC recommends single-initiator zoning, that is, zones with one initiator and
one or more targets. However, RecoverPoint Gen3 and Gen4 RPA ports can act as both initiators and
targets. In some configurations, it is required to add all RPA ports in a fabric to the same zone. The best
practice is always to zone Gen3 and Gen4 RPA ports in the same zone. In some configurations, it is
required.
41
Server-to-storage zones. In most installations, these zones already exist as part of the SAN
implementation. Confirm that these zones exist. EMC requires single-initiator zoning.
RPA-to-storage zones. The zoning guidelines are different for RecoverPoint and
RecoverPoint/SE.
RecoverPoint. All RPA ports in a fabric must be zoned with all storage ports that are
available for RecoverPoint replication. The best practice is always to use only one
zone per fabric between Gen3 and Gen4 RPAs and storage. This applies to all splitters.
RecoverPoint/SE. On each fabric, there should be a zone for each RPA, which
includes:
One HBA port of that RPA
One port for each VNX/CLARiiON storage processor (SP A and SP B)
Zoning for distributed consistency groups. Distributed consistency groups require that all
RPA Fibre Channel ports in the fabric can communicate with each other. All RPA ports in a
fabric must, therefore, be in one zone.
RPA WWNs can be recognized in the SAN by their 5001248 prefix. You can use the RPA
Installation Manager option Diagnostics > Fibre Channel diagnostics > View Fibre Channel
details to list the WWNs of each RPA.
Note: Refer to splitter e-learning modules for specifics on zoning.
42
Customers can replicate data between a production site and a remote site over Fibre
Channel. Customers can leverage existing Fibre Channel infrastructure to improve application
efficiency, throughput and performance. In this configuration, the production site RPAs must
be zoned together with the remote RPAs. Listed are a few considerations when replicating to
a remote site using FC:
Uses FC network links between sites for CRR, instead of Ethernet - WAN
Either FC or IP replication (not both)
If users choose Fibre, they can then choose to allow control connections (non-data)
between sites over IP
43
Listed are supported fabric environments for implementing asynchronous replication over
Fibre channel.
RecoverPoint 3.5 and above requires 64-bit HBAs QLE25XX

Site layout must be for CRR
ISL fabrics
Extended fabrics
Support for either ISL-connected fabrics or extended fabrics are permitted. Please consult
with the EMC TechBooks for examples of stretch fabrics.
44
Listed here are some basic restrictions and constraints. Please take a moment to read them.
45
Replication over Fibre Channel is enabled during the installation process if replication over
Fibre channel is selected, WAN replication will not co-exist.
To configure, create one zone per fabric that includes all of the site1 RPA ports together with
all of the site2 RPA ports. The fabric in the environment will consist of switches which are
connected by ISL or by extended fabrics. Eth0 (WAN interface) is still used for redundancy
purposes and is called the <Private> interface. GUI/CLI will reflect a FC setup with all
relevant information including: fabric statistics, event logs, and schema.
46
Before the RPAs are installed and consistency groups are defined, sufficient volumes must be made
available on the SAN-attached storage at each RecoverPoint cluster.
Repository As part of the installation process, a repository volume must be created at each cluster.
The repository volume should reside in a storage environment that guarantees high availability, and
must be accessible to all RPAs. The repository volume holds configuration data that is created in the
installation and replication process. Repository volumes should not be visible to the source or target
hosts.
Journal Volumes that are to be used as Journals for each Consistency Group must be masked to the
RPA. Only volumes that are masked will be available as choices as Journal volumes. Journal volumes
should be made visible to the RPAs only.
Replication Volumes that are to be used in the creation of Replication Sets must be masked to the
RPAs or vRPAs. These volumes are also masked to the hosts. If a volume(s) are to be used as a copy
or production does not change the masking requirements.
47
The slide shows a typical vRPA configuration in a standard SAN environment. Here, vRPA
nodes connect into the FC fabric using iSCSI through the hypervisor host servers. The host
servers themselves are each connected to storage through Fibre Channel HBAs or thru iSCSI
connections.
Please refer to the EMC RecoverPoint vRPA Technical Notes for more information.
48
Here is a comparison of physical and virtual RPA connection and other basic features.
49
This module covered the different RecoverPoint configurations and an overview of the
multiple installation and configuration procedures when deploying a RecoverPoint solution.
50
This module focuses on implementing a RecoverPoint/SE solution.
Module 2: RecoverPoint/SE Installation
This lesson covers an overview of RecoverPoint/SE Implementation and its requirements.
A RecoverPoint/SE solution provides data protection and disaster recovery using VNX arrays.
A RecoverPoint 4.0 implementation can contain 1 or 2 clusters, with a single array (CX or VNX
models only ) for each cluster. Physical or virtual RPAs can be used. A single cluster must
contain only one or the other type. A cluster using physical RPAs can be connected to a
separate cluster containing vRPAs.
The vRPA can reduce the total solution cost for VNX customers by up-to 60%. With a
RecoverPoint/SE license, any number of vRPAs can be ordered to scale your environment for
no additional charge.
The Virtual RecoverPoint Appliance (vRPA). vRPAs are virtual machines that run the
RecoverPoint software. They access the repository, journal, production, and copy volumes
via the iSCSI protocol, and therefore do not require any FC infrastructure. vRPAs are a great
way to get many of the benefits of RecoverPoint without the need for physical appliances or
a SAN infrastructure. One important consideration is that vRPAs are only available for use in
RecoverPoint/SE (RP/SE) configurations. This means that the storage array must be a VNX.
Another important consideration is that since RP 4.0 supports synchronous replication over
IP, if the WAN is sufficiently robust, vRPAs can be used for remote synchronous replication.
vRPAs can replicate any block data, regardless of how the hosts are connected to the VNX.
Within the Data Protection window, you are able to manage the different methods available
to protect the storage. The Snapshots option allows for LUN snapshots and File System
Checkpoint management. The Mirrors and Replications icon allows you to create and
manage Mirrors and Consistency Groups for block storage and Replication for File Storage.
On the right-hand side, there are many wizards that allow for quicker access to create and
manage data protection.
Unisphere also has plug-ins that allow for direct start-up of many storage-related tasks
including RecoverPoint/SE.
This lesson covers the RPA preparation process when deploying a RecoverPoint/SE solution.
The RecoverPoint Procedure Generator (RPPG) is a stand-alone Windows application used to

generate precise, user-driven steps for high demand tasks carried out by Customer Support
and field personnel.
In the RecoverPoint Procedure Generator, each procedure is tailored and generated based on
user selectable prompts. This generated procedure gathers the most critical parts of
RecoverPoint product guides and combines sections of documentation along with expert
advice from RecoverPoint SMEs into a sequential set of steps in a single document.
One of the major differences between RPPG and other EMC Procedure Generators is that
there is no expiration of the product or a forced re-install. RPPG will check for application
and content updates each time RPPG is launched and automatically download them (if
allowed by the user).
RPPG includes the ability to submit feedback via a form to a back-end database. We
encourage everyone to submit improvements for the tool, ideas for future procedures, and
corrections/additions to the content via this mechanism.
To facilitate a successful deployment of RecoverPoint and RecoverPoint/SE, it is important to

assemble selected information about your installed networks and storage systems. It is also
necessary to ensure that the LUNs needed by RecoverPoint are available on your storage.
EMC Global Services will assist you with these pre-deployment activities:
RecoverPoint connectivity
Zoning
Unpacking the RPAs
The Wan IP port is given a Temporary Virtual IP address: 10.77.77.77 by default. This can be
used to connect via SSH and assign a management address to be used during configuration.
Using boxmgmt user, log in to all RPAs to be deployed within the same global cluster and
set a management IP address for them.
Although this solution is not commonly used, in some scenarios where there is a DHCP
server, Deployment Manager can set the IP address during the installation. In this case, you
do not have to set them manually before the installation begins. vRPAs have a temporary
address set during the installation of the VM, but this method can be used to alter the
address.
For the Fibre Channel connections, a dual-fabric topology is recommended. It must include
the following connections:
A port on each VNX/CLARiiON storage processor to each fabric.
Each RPA HBA to each fabric
A direct attach, switchless topology, intended for iSCSI host-connected environments, must
include the following connections:
Each RPA to one port on each VNX/CLARiiON storage processor
Two Fibre Channel ports connecting the two RPAs
10
vRPAs are available to be installed using VMware vSphere server. They are deployed from
OVA files which can be downloaded from support.emc.com. During installation, there are
three options for vRPAs. The minimum vCPU, disk space, and memory configurations for
each of these is shown here. The performance of each of these options will be documented
in the RecoverPoint 4.0 Release Notes. Please see the release notes to match the proper
configuration to the environments needs. Please note that the performance numbers in the
Release Notes will be given on a reference hardware, and that performance can vary
depending on the physical hardware on which the vRPAs will run. It is also possible to change
the hardware configuration post-deployment, as long as the resources are not less than
those of the minimal configuration shown in the table.
There is no special license needed for vRPAs. Since vRPAs are only supported with RP/SE, the
RP/SE license for the array is the only license needed.
11
Configuring virtual networks for vRPA:

- In low-traffic deployments, all four network cards may be placed on the same virtual
network (on a single vSwitch).
- Where high performance is desired, separate LAN and WAN traffic from iSCSI traffic. For
even better performance, place each network (LAN, WAN, iSCSI1, and iSCSI2) on a separate
virtual switch.
- For high-availability deployments, in which clients have redundant physical switches, the
best practice is to route each iSCSI card to a different physical switch. This will usually involve
specifying a different virtual network for each of the iSCSI cards.
iSCSI bandwidth:
In VNX, either of two types of iSCSI modules may be available:
- 1Gb port cards, which allow bandwidth of 1Gb ,2Gb, 4Gb
- 10Gb port cards, which allows bandwidth of 10Gb, 20Gb
Since the vRPA relies on virtual networks, the bandwidth that the user exposes to the vRPA
iSCSI vSwitches will determine the performance that the vRPA can reach. The user can
configure vSphere hosts with quad port NICs and present them to the vSwitches.
12
vRPAs can be deployed using the OVA package, which can be downloaded from
support.emc.com
From vCenter Server management console, Select the File menu, then Deploy OVF
Template. The OVF deployment wizard appears. Specify the vRPA OVF package location.
The best practice is to create each vRPA instance individually from an OVF package. This
makes temporary IP address assignment simpler. To allow for redundancy, vRPAs should not
share the same ESX server.
13
The vRPA OVF template details appear, showing the general properties of this OVF template.
To accept, click Next.
The EMC End-User License Agreement appears. If you accept the terms, click Accept and
Next.
14
Enter the name you wish to assign to this vRPA. If you enter the name of an existing vRPA,
you will not be permitted to continue deployment.
Select the desired configuration profile. The vRPA supports dynamic provisioning of these
resources, as long as they do not go below the values selected.
15
Specify the vRPA Storage (datastore) that will be used to host the vRPA virtual machine files.
The best practice is to select a high-performance datastore. Do not use a datastore that you
intend to replicate with RecoverPoint. The datastore should be 80GB minimum.
Specify the vRPA datastore virtual Disk Format. SelectThin Provision.
16
This step in the deployment wizard maps the four required vRPA Ethernet ports (Source
Networks) to the available vSphere virtual networks (Destination Networks). Do not select
the internal VMware iSCSI network (iSCSI Network option).
17
This step determines the method of assigning a temporary IP address for management of the
vRPA. This address will be used during the installation of the RecoverPoint cluster. It is only
a temporary address and will not become permanent until the cluster is installed.
18
Specify the desired IP address for the vRPA. This address will only be used during cluster
installation by Deployment Manager.
19
The Ready to Complete screen summarizes all your selections. Click Finish to initiate the
deployment of this instance of the vRPA.
The Deploying vRPA appears, showing the progress of the deployment.
20
When deployment is completed, the vRPA Summary tab shows the vRPA package contents as
specified. The new vRPA virtual machine is ready to be powered on. The selected IP policy
will be implemented.
Use RecoverPoint Deployment Manager to add this vRPA instance to a RecoverPoint cluster
automatically when the vRPA is powered up.
21
This lesson covers deploying the VNX write-splitter for a RecoverPoint/SE solution.
22
The VNX/CLARiiON splitter runs in each storage processor of a VNX, CLARiiON CX3 or CX4
array and splits (mirrors) all writes to a VNX/CLARiiON volume, sending one copy to the
original target and the other copy to the RecoverPoint appliance.
All RecoverPoint families support the VNX/CLARiiON splitter. The VNX/CLARiiON splitter is
supported on VNX, CLARiiON CX3 and CLARiiON CX4 arrays.
The VNX/CLARiiON splitter is supported on both iSCSI and FC attached volumes and supports
hosts running OSes compatible with the VNX/CLARiiON array.
23
The RecoverPoint Splitter driver is embedded in the operating system for a VNX or CLARiiON
array. Installing the enabler for RecoverPoint can be executed using the Unisphere Service
Manager tool.
To do it, first connect to the array, as shown above.
Using Unisphere Service Manager tool, select the system to upgrade or install.
In the System tab, select Software option. The Storage System Installation Software
window will appear.
24
In the installation options, select Custom Install (default) and click Next.
Implementation tasks that are taken for granted as being done here are that the array is
available via an IP address and that security has been enabled on the array.
25
Proceeding with the implementation, we see the USM tool shows the software which is
already installed on the array. Using the browse button, we can locate the splitter code and
splitter enabler which we will install on the array. Note that the splitter code and enabler will
be available for EMC employees on the GS Intranet. You have to download this code and file
to a local management host in order to perform the installation.
Click Browse and locate the copy of software installed on your management host
Installing the Splitter bundle
Installing the Splitter enabler
Proceed with file transfer Click Next to proceed
26
The USM tool performs several base tasks as part of the installation. It checks for connected
servers, collects diagnostics, and checks a variety of rules before installation is allowed. If
there are issues found, it is possible to correct or override the existing rules. Once checking is
complete, the actual install is initiated.
27
Shown is the installation beginning on each SP of the array. Once a single SP has been
updated with the enabler and splitter code, it is rebooted. After a successful reboot, the
other SP is then installed and rebooted.
28
On VNX deployments, the splitter has been added to the VNX OE code. However, it is still
required to install the splitter enabler. This can be accomplished using USM.
29
This lesson covers the installation of RecoverPoint/SE.
30
The RecoverPoint Deployment Manager is a package of graphical user interface (GUI) wizards
that help you perform a number operations from a single management point.
The Deployment Manager can be downloaded from the Downloads section of
support.emc.com.
It is available as a zip file for use from a Windows machine.
To launch the Deployment Manager, open the folder and double-click the executable file:
RecoverPoint_DM.exe. Select the correct RecoverPoint version for the task to be completed.
At the login screen, select Other operations (EMC personnel) and enter the default CLI
RecoverPoint login credentials (user admin, password admin).
31
Deployment Manager 2.0 branches off into two paths. Throughout the solution for the
implementation scenario presented, both paths will need to be accessed. The first path
provides options for installation, upgrade, and other operations for RecoverPoint 4.0. End
users who would like to install RecoverPoint 4.0 on a new hardware appliance or virtual
RecoverPoint Appliance (vRPA) should use this option. Users who would like to upgrade to
RecoverPoint 4.0 from version 3.5 or earlier should choose the second option. This option
will launch Deployment Manager 1.1 to allow maintenance of RecoverPoint 3.x clusters.
32
The RecoverPoint/SE Installer Wizard is a graphical user interface (GUI) wizard that helps you
install a new RecoverPoint/SE configuration from a single management point. The Installer is
intended for deployment of RecoverPoint/SE using only VNX series and CLARiiON CX3 and
CX4 series splitters. This wizard is used to install a single cluster of either vRPAs or Physical
RPAs.
33
The next step in the SE installation wizard outlines the required prerequisites for the
RecoverPoint environment. The conditions are defined for both Physical and Virtual RPAs.
The environment, SAN, IP, connectivity, and Array code versions are defined.
34
The RecoverPoint/SE Installer allows you to select one of two installation modes:
Create a new installation configuration file The system creates a new installation
configuration file from the beginning. Starting with a blank configuration, the user must
enter configuration settings for the installation. The system uses these settings to
complete the installation.
Create or continue an installation from a saved configuration file The system loads the
settings from a previously saved installation configuration file.
If using the file to create a new installation from a saved file, and the file was
already applied to a previous installation, the system will allow you to use the file
and modify the configuration parameters.
35
This step defines the RecoverPoint cluster environment. Entries under the General category
create the Cluster name and the Number of RPAs. The Connectivity category lists the IP
version type and MTU size. The MTU defaults at 1500 and should not be altered unless
instructed to do so. The Environment category lists options such as the DNS server, Time
zone, and NTP server.
36
The next step in the wizard defines how to set the IP addresses of uninstalled RPAs. This
address will be used for discovery until the wizard sets the final management address.
Two options are provided :
I have already set IP addresses for the RPAs
This option is recommended when one or more of the following is true:
You have already set the IP addresses.
You are installing RPAs running releases earlier than 3.5
Your environment does not include a DHCP server.
I want Deployment Manager to discover the RPA IP addresses
This option is only relevant when RPAs are running release 3.5 or later and your
environment includes a DHCP server. When you select this option, the Discover
uninstalled RecoverPoint Appliances (RPAs) section becomes active.
37
This screen allows the user to define the management and WAN networks. The cluster
management address will be used to configure replication once the cluster is created. The
WAN address must be entered for communication even if the cluster will not be connected
to another cluster. The wizard allows for additional routes to be added if the default gateway
is not sufficient.
38
Enter the default RecoverPoint login credentials. The system prompts you to enter your
RecoverPoint login information. For username boxmgmt, the default password is boxmgmt.
Review the results of the RecoverPoint connectivity test. The system communicates and
validates the statuses of the RPAs and confirms that all components are OK, or that errors
are detected. The system presents the following results: Status, RPA, Site name, RPA IP
address, Gen (RPA hardware platform), and Comment (if applicable).
If errors are detected for an RPA, a comment appears describing the problem. To proceed to
the next step in the wizard, you must resolve all errors. Once errors are resolved, click Retry
to revalidate the communication statuses.
When all statuses appear OK (green check mark), click Next to continue.
39
This screen only appears if you are installing a virtual RPA (vRPA).
Define the RPA cluster iSCSI settings.
Connectivity
For iSCSI 1
IP type IPv4 or IPv6.
MTU Default value is 1500 (do not modify unless instructed to do so).
For iSCSI 2
IP type IPv4 or IPv6.
MTU Default value is 1500 (do not modify unless instructed to do so).
If relevant, select the I want to configure CHAP credentials for the RPAs iSCSI ports
checkbox and modify the CHAP credentials (username and password).
40
Select how to update the RecoverPoint release running on the RPAs. The RecoverPoint
release running on the RPAs is displayed (the ISO image that comes pre-installed on the
RPAs). To ensure the RPAs are running the target RecoverPoint release, you should update
them now.
Update options:
Update with an ISO image available from EMC Online Support site (recommended)
Select this option to download an ISO image available from EMC Online Support site
(login credentials required). This option will be grayed out if no ISO image can be found on
EMC Online Support site.
Update with an ISO image available locally
Select this option if you have an ISO image on your local machine, a DVD, a USB device, or an
FTP server.
Do not update. Continue with current RecoverPoint release on RPAs.
41
The system attempts to log in to each of the RPAs and validate system information. The
results of applying the configuration settings to all RPAs are displayed. Once installation has
completed successfully, click Next.
42
Enter the login credentials for your VNX/CLARiiON storage system used for this cluster.
The system now has the necessary information required to validate the VNX/CLARiiON
settings. The system attempts to log in to the VNX/CLARiiON array and validate the following
information:
The RecoverPoint/SE Installer can communicate with VNX/CLARiiON SP A and SP B.
The login credentials are correct for SP A and SP B.
SP A and B are not already attached to RecoverPoint/SE cluster.
IP settings were applied successfully.
The system communicates and validates the statuses of the RPAs and confirms that all
components are OK or that errors are detected. If errors are detected, you can click the error
to display details, and instructions on how to correct the problem. The array name and serial
number of the array are also displayed. To proceed to the next step in the wizard, you must
resolve all errors. Once errors are resolved, click Refresh to revalidate the communication
statuses. Warnings are displayed, but give the user the option to continue or not.
43
This screen only appears if you are installing a virtual RPA (vRPA). The current cluster iSCSI IP
configurations and RPA iSCSI IP settings are displayed. These were configured during the
installation of the RPA VM. Enter the iSCSI settings for the new RPAs. Interface netmask is
based on the ip type for the LAN and WAN. This was chosen in the "Environment settings"
section.
IMPORTANT: It is strongly recommended to put the iSCSI interface on a different subnet
than the LAN and WAN interface, to avoid iSCSI communication errors.
Additional gateways for the iSCSI network can be added at this time.
44
The Deployment Manager wizard allows the user to select from four options for zoning the
RPAs to storage.
Automatic - The Installer zones the RPAs and the VNX/CLARiiON arrays automatically.
Semi-automatic - The Installer creates the necessary zoning scripts, but you must
apply them yourself.
Manual - The Installer indicates which ports should be zoned together, and you are
responsible for actually creating the zones.
Direct-attach Storage - The Installer verifies that, in this switchless configuration, each
RPA is directly connected to SP A and SP B of the VNX/CLARiiON array.
Automatic zoning can be performed on Cisco fabric switches with an active zoneset, and on
Brocade (Connectrix B-Series) fabric switches running FOS 6.0 and higher with an active zone
configuration. A Telnet connection to Cisco and Brocade switches is mandatory.
The Installer automatically creates an RPA-to-storage zone for each RPA at this site, where
each zone includes:
One port for each VNX/CLARiiON storage processor
45
The Installer retrieves the WWNs for the RPA ports and the SP ports on the VNX. Zone and
mask LUNs using the RPA port WWNs are displayed in the RPAs WWNs table(s), and the
VNX/CLARiiON array port WWNs are displayed in the VNX/CLARiiON Array table.
On each fabric, create a zone for each RPA, which includes:
One port for each VNX/CLARiiON storage processor
At each site, on each fabric, create an RPA-to-RPA zone containing all local RPA HBAs that are
not used in RPA-to-storage zones (best practice). This zone provides an additional
communication link between RPAs. It can also be used for synchronous replication of
distributed Consistency Groups. If replicating over Fibre Channel, merge the RPA-to-RPA
zones at each site into one.
46
The system performs SAN diagnostics for the site, attempting to validate that the current
configuration is appropriate for the RPA, and that RecoverPoint/SE can successfully operate
in the current SAN environment. The system presents the following results: Severity, RPA,
Message ID, Category, and Description. The system confirms that all components are OK and
that no errors exist. If errors are detected, you can click the error to display details and
instructions on how to correct the problem.
Once errors are resolved, click Refresh to rerun the SAN diagnostics process. It is highly
recommended to resolve all SAN discovery warnings, even though the system allows you to
ignore them and continue the installation.
47
Determine how you want the repository volume to be selected:

Automatic - The Installer automatically creates and configures a repository volume.
Manual - The Installer lists possible volumes, and you can select the one to be configured as
the repository volume. The list is volumes configured on the VNX. Care must be taken not to
choose a volume already in another storage group.
48
After the Repository volume has been configured, the next step is for Deployment Manager
to apply the configuration and create the cluster.
These are the steps Deployment Manager Performs:
Registering RPA WWNs on VNX/CLARiiON array, Creating storage groups, Configuring RPAs,
Creating repository volume and assigning it to the newly created storage group.
From there, the wizard finishes the installation by Attaching the RPAs to the cluster and
waiting for the RPAs to come up after they reboot.
Progress bars indicate that the system is applying settings and completing the installation.
Once the progress bars complete, the system confirms that all components are OK, or that
errors are detected. If errors are detected, you can click the error to display details and
instructions on how to correct the problem. To proceed to the next step in the wizard, you
must resolve all errors. Once errors are resolved, click Retry to reapply settings and
revalidate that the RPA installation is successful.
49
You have successfully completed the RecoverPoint/SE installation. The RecoverPoint/SE

storage group created will be displayed.
IMPORTANT:
The storage group contains all the VNX/CLARiiON LUNs that RecoverPoint/SE replicates. Do
not change the name of the group, or RecoverPoint/SE may fail to function properly. To start
managing the RecoverPoint system, click the Unisphere for RecoverPoint hyperlink or click
Finish and enter the system using your browser.
50
This lesson covers Connecting RecoverPoint clusters.
51
RecoverPoint clusters can be connected together in order to perform replication to or from

different geographical locations. New clusters can be connected to existing clusters. A new
cluster is a RecoverPoint cluster that has been installed, but not licensed. Connecting RP
clusters is a 2-step process and can be done with Deployment Manager or the CLI interface.
52
The RecoverPoint Connect Cluster Wizard is a graphical user interface (GUI) wizard that helps
you connect RPA clusters running RecoverPoint 4.0 or later from a single management point.
Once completing the wizard, you will be able to connect to all clusters in the system from a
single management point.
53
Connecting a new cluster to an existing RecoverPoint system is performed in two steps. They
are to Prepare new cluster for connection or Connect a new cluster to an existing system
A cluster must be prepared before it can be added to another cluster. The wizard from
deployment manger will perform this step, or you can use the CLI via the boxmgmt account.
Once the prepare option has been selected, a list of cluster prerequisites is presented.
These must be fulfilled before continuing.
54
Enter a cluster management IP address or an RPA IP address and RecoverPoint login

credentials of the new cluster.
55
After logging in to the new cluster, the new cluster is ready to be connected.
Select the desired action:
Connect the new cluster to an existing RecoverPoint system
Select this option if the work station running Deployment Manager is able to
communicate with the existing RecoverPoint system.
If selected, click Next to continue.
Connection the new cluster at a later time
Select this option if the work station running Deployment Manager is unable to
communicate with the existing RecoverPoint system, or you do not want to connect the
new cluster now. If you select this option, click Finish to exit the wizard. To connect the
new cluster at a later time, when you re-enter the wizard, select Connect new cluster
to an existing system
IMPORTANT:
If the second option is selected, you must copy the internal cluster name and RPA WAN IP
address, displayed onscreen, and enter this information to the wizard at a later time to be
able to connect the new cluster to the existing RecoverPoint system.
56
Enter a cluster management IP address or an RPA IP address and RecoverPoint login

credentials of the existing cluster to which you want to connect. This cluster can be
previously installed and configured.
Enter the RecoverPoint login credentials of the existing cluster. For username boxmgmt, the
default password is boxmgmt.
57
Define the connection between the new cluster and the cluster to which you want to
Connect.
Set the desired connection type - IP or Fibre Channel. If Fibre Channel is chosen, there must
be zoning from the RPAs in one cluster to the RPAs in the other.
If you select IP, you can add an additional WAN gateway (gateway IP, target netmask, and
target subnet).
The additional gateway only needs to be configured if the gateway specified during cluster
installation is not suitable for connectivity between clusters in this environment. Otherwise,
this section can be left blank.
Other steps:
Additional cluster connections
If the system you are connecting the new cluster to contains more than one RPA cluster, a
menu will appear in the wizard.
Summary
The summary screen appears once connection of RPA clusters is complete. Once you have
completed the connection of the new cluster to the RecoverPoint system, you can start using
Unisphere for RecoverPoint.
58
This lesson covers Post-installation requirements.
59
The first time Unisphere for RecoverPoint is run after a RecoverPoint installation, the Getting
Started Wizard is displayed. This wizard guides users through the steps necessary to
configure the basic RecoverPoint settings needed to ensure their RecoverPoint systems are
up and running as soon as possible.
There are three screens in the Getting Started Wizard:
1. Welcome screen - provides a brief description of the wizard and its functionality
2. Add Licenses screen - allows you to install your RecoverPoint license and display the
license information
3. Enable Support screen - allows you to configure and test the RecoverPoint system
notifications mechanism
60
The settings in the Add Licenses screen are displayed through the Getting Started Wizard the
first time you launch Unisphere for RecoverPoint, and can be accessed through the Admin >
Manage Licenses screen each subsequent time it is launched.
To add a license:
Click Add to display the Add License dialog box.
Click Browse... and select a license file.
Click OK to add the license file to the RecoverPoint system.
61
The Enable Support screen allows you to configure the RecoverPoint system reports
mechanism (SyR) and provide one-way communication between a RecoverPoint installation
and the EMC System Reports database (ESRS).
The settings in the Enable Support screen are displayed both through the Getting Started
Wizard the first time you launch Unisphere for RecoverPoint, and through the Admin
>Configure System Notifications screen, each subsequent time it is launched.
62
Within the Data Protection window, you are able to manage the different methods available
to protect the storage. The Snapshots option allows for LUN snapshots and File System
Checkpoint management. The Mirrors and Replications icon allows you to create and
manage Mirrors and Consistency Groups for block storage and Replication for file storage. On
the right-hand side, there are many wizards that allow for quicker access to create and
manage data protection.
Unisphere also has plug-ins that allow for direct start-up of many storage-related tasks
including RecoverPoint/SE.
63
After installing a RecoverPoint/SE system, you must complete the RecoverPoint PostDeployment Form. To download the form from EMC Online Support
(http://support.emc.com), click Support by Product, type RecoverPoint SE in the Find a
Product search field. On the RecoverPoint SE page, click Documentation and download
the form from the list of documents.
Connect Home Ensure the Install Base Record is complete and accurate, including the
Connection Record. Further, ensure that 2-way connectivity is established and tested before
considering the install complete. If the customer has refused one or both of the connections,
the IB Connection Record should reflect this. To test connection: Refer to Primus emc239913
for detailed instructions.
Connect In RecoverPoint 3.2 and later supports connect in through ESRS as long as the
customer system (RPA) is registered with the ESRS gateway .
Connected to Relationship The IB group will establish a connected to relationship from
each Hardware TLA to the Software TLA. This allows an additional tie for solutions-based
reporting.
Microcode All RecoverPoint versions, including service packs and patches, have microcode
values in CSI. Please provide the version install to the IB group and they will update customer
profile.
64
Party ID (formerly Site ID) Provide customer name and location information to the IB
group. The group will verify the Party ID.
RPA Hardware Serial ID For Dell PowerEdge 1950 phase 2 (Gen1) and phase 3 (Gen3) and
Dell R610 (Gen4) platforms, use the get_box_states command. Search for the
Hardware Serial ID values of all RPAs. If the values starts with the prefix WCARP or NNG##,
then record and submit them. If the values do not start with the prefix WCARP or NNG##,
then the RPA serial number - S/N - appears on a white label (sticker) found on top of the LCD
display of each RPA. A serial number is required for each RPA. Please validate which RPAs are
at your specific site (either local or remote), as this command will report on all RPAs in the
total solution.
Note: The NNG## prefix only appears when using Dell R610 (Gen4) platforms.
Software Serial ID Use the get_account_settings CLI command to find this
information. Please validate which Software Serial ID is at your specific site (either local or
remote), as this command will report both the local and remote Software Serial IDs.
Account ID Use the get_account_settings CLI command. The value will show up in
first field labeled Account ID.
65
This module covered the installation of RecoverPoint/SE.
66
67
68
This module focuses on RecoverPoint/EX and RecoverPoint/CL installation and postinstallation steps.
Module 3: RecoverPoint/EX and CL Installation
This lesson covers the preparation process when deploying a RecoverPoint solution.
Deploying RecoverPoint/CL and /EX require installing and configuring a number of

components. This includes installing RecoverPoint Appliances (RPAs), RecoverPoint software,
and RecoverPoint splitter software.
Note: Refer to splitter e-Learning modules for specifics on splitter installation steps.
Most operations involved with deploying RecoverPoint require usage of EMC RecoverPoint
Deployment Manager.
The tasks for installing the first site (and second site if applicable) are:
1. Install RPAs.
2. Create zoning and perform LUN masking.

3. Use Deployment Manager to:
1. Install software on each RPA.

2. Configure RPAs.
3. Attach the RPAs to the RPA cluster.
4. Discover splitters
5. Configure replication
6. Post-installation requirements
Before starting the installation of the appliances:

Verify that the IP/Ethernet for management and replication interfaces are connected.
Verify that the Fibre Channel connections have all been properly connected and zoned in
the fabric/SAN for each appliance.
Verify that each appliance can see the Repository volume, Journal volumes, and all
replication volumes on the same site.
Verify that you have access to an installation laptop or computer on the RecoverPoint
management network with the latest java plug-in installed.
The Site Planning Sheet provided before the installation is used to fill in all the settings for
each site that is requested during this part of the installation. Check that the site planning
sheet has been properly filled out.
Each RPA requires one U rack space, one LAN connection, one WAN connection, two-to-four
FC SAN connections, and two electrical power sources.
Using boxmgmt user, login to all RPAs to be deployed within the same global cluster and
set a management IP address for them.
Although this solution is not commonly used, in some scenarios where there is a DHCP
server, Deployment Manager can set the IP address during the installation. In this case, you
do not have to set them manually before the installation begins. vRPAs have a temporary
address set during the installation of the VM, but this method can be used to alter the
address.
One method to find the WWNs of an RPA is to connect via SSH using the boxmgmt account.
Enter option 3 <diagnostics>, option 2 <SAN diagnostics>, option 2 < view RPA ports>.
This will display the WWNs of the 4 HBA ports. It will also give you an indication if it is
connected to a switch and zoned to any other devices.
There are three types of RecoverPoint licenses: RP/SE, RP/EX, and RP/CL. As with previous
RecoverPoint versions, RP/SE only supports VNX and CLARiiON-based splitters and supports a
maximum of two clusters. The license is based on the array and is tied to the array serial
number. There are no capacity-based RP/SE licenses. As with all RP licenses, RP/SE licenses
are based on whether the replication type is local or remote. If a VNX is being used for both
local and remote replication, it will need both a local replication and a remote replication
license.
RP/EX supports all VMAX-based, VNX-based, and VPLEX splitters. Similar to RP/SE licenses,
RP/EX licenses are tied to the array serial number. RP/EX licenses are only applicable for the
array to which they are tied.
RecoverPoint/CL licenses are based on the replicated capacity. Replicated capacity simply
means the amount of data that is being replicated. RP/CL licenses are not tied to any arrays.
This makes the replication environment very flexible, since adding, changing, and refreshing
arrays does not require any change to the RecoverPoint license.
This lesson covers Symmetrix VMAX Splitter Installation.
RecoverPoint supports the RecoverPoint Symmetrix write splitter on the VMAX family of
arrays. VMAX helps customers achieve enterprise-class reliability, availability and
serviceability. Customers who need to protect their application data locally or remotely can
use VMAX with RecoverPoint.
For existing or prospective customers, the Symmetrix splitter for VMAX offers an embedded,
less costly, and more simple solution for those that wish to take advantage of their existing
VMAX arrays.
10
Open Replicator copies data in sessions across the SAN infrastructure. When RecoverPoint
with Symmetrix splitter is deployed, RecoverPoint appliances act as if they were the remote
storage array by presenting virtual target and virtual remote devices.
When a Consistency Group is enabled, an Open Replicator RecoverPoint session is created
for each production volume within that Consistency Group. Open Replicator RecoverPoint
sessions are not created for the replica volumes until image access is enabled. Even after
image access is disabled, stopped Open Replicator RecoverPoint sessions remain for each
replica volume. Both production and replica Open Replicator RecoverPoint sessions are
removed when their Consistency Group is disabled.
Configuration changes cannot be made to a device in an Open Replicator RecoverPoint

session. For example, a device cannot be mapped or unmapped until the Consistency Group
is disabled.
11
This slide describes the data flow from the application host to the production volumes, and
how the RecoverPoint Appliance accesses the data as part of the process.
An application server issues a write to a LUN that is being protected by RecoverPoint. Writes
sent to the production volume are split and sent to the production volume and to the RPA.
This write splitting occurs at the Symmetrix Fibre Channel Director/Interface Adapter (FA)
port, then continues to the RecoverPoint Appliance.
As a requirement of this architecture, RecoverPoint Appliances must be zoned to the same
FA ports as the replicated hosts.
12
The EMC Solutions Enabler kit is the software that provides a host with the Symmetrix
Command Line Interface (SYMCLI), including the SYMAPI and CLARAPI shared libraries.
SYMCLI is a comprehensive command set for managing the storage environment.
With RecoverPoint 3.4 SP1 or later, Solutions Enabler is automatically installed on the RPAs
as part of the RP ISO install process. It is only used by Site Control. Therefore, only RPAs 1
and 2 use it.
13
Device tagging informs the Symmetrix array that the device is reserved for RecoverPoint
replication. Starting with RecoverPoint 3.5 and Enginuity microcode, 5876 tagging is required
for VMAX volumes exposed to RecoverPoint. This includes production and replica volumes,
journal volumes, the repository, and gatekeepers. Untagged volumes will not be available in
RecoverPoint for replication.
If Symmetrix LUNs are accessed by RecoverPoint through VPLEX, RecoverPoint will not check
device tagging. However, the best practice is to tag those LUNs anyway, to identify them as
reserved for RecoverPoint.
Tagged device are protected by the Symmetrix array:
Tagged devices are protected from corruption by array-based replication tools.

The Symmetrix Management Console issues a warning if an attempt is made to
change the configuration of tagged devices.
Solutions Enabler CLI requires override command arguments to make configuration

changes to tagged devices
14
RecoverPoint manages the Symmetrix splitter using Solutions Enabler. Solutions Enabler
commands are sent to the Symmetrix array via gatekeepers. Gatekeepers are small, 3cylinder devices (approximately 3 MB) that are used to send control commands to the
Symmetrix.
RecoverPoint site control manages the resources of the RecoverPoint cluster, including the
Symmetrix splitter. The active instance of RecoverPoint cluster site control can run only on
either RPA1 or RPA2, even if there are more RPAs in the cluster. As a result, the gatekeepers
must be presented to RPA1 and RPA2 only. RPA1 must have access to eight gatekeepers;
RPA2 must have access to eight separate gatekeepers. A gatekeeper should not be shared
with any other RPA or host. RPAs must have access to their gatekeepers via multiple
redundant paths. If a site comprises multiple Symmetrix splitters or multiple RecoverPoint
clusters, a total of 16 gatekeepers is required for each Symmetrix-splitter/RecoverPointcluster combination.
15
Starting with RecoverPoint 3.5 when using the Symmetrix splitter, the RecoverPoint cluster
writes a signature to each LUN that it accesses, including production, replica, journal, and
repository volumes. The signature is written to the area of the Symmetrix device known as
the nice name. The signature is a hash of information unique to each RecoverPoint cluster.
No RecoverPoint cluster can access a LUN signed by a different cluster.
If a production or replica volume is detached from the splitter or the Consistency Group is
disabled, the signature is automatically cleared. If a journal volume is removed from a
Consistency Group or the Consistency Group is disabled, the signature is automatically
cleared. The signature is also removed from any device if it is untagged.
16
A RecoverPoint cluster is qualified to support up to 6 Symmetrix splitters.

The Symmetrix array can function as a splitter for up to 6 RecoverPoint clusters.
A LUN may be accessed by only one cluster.
Site names must be unique for all RecoverPoint clusters sharing one Symmetrix splitter. For
example:
Splitter sessions to all RecoverPoint clusters count toward the maximum number of sessions
supported by the Symmetrix splitter. In case of VMAX 20K, the splitter session limit is 4096. If
the Symmetrix splitter is shared between three clusters, cluster#1 is replicating 2048 LUNs,
and cluster#2 is replicating 2048 LUNs, and no LUNs can be replicated by cluster #3.
Cluster #1 is replicating between New York and London

Cluster #2 is replicating between New York and San Francisco
Both clusters use the same Symmetrix splitter in New York, but the two clusters must
refer to the New York site by different names, such as NewYork1 and NewYork2. In
addition, the same LUN cannot be replicated both to London and to San Francisco.
RecoverPoint supports mixing the Symmetrix VMAX splitter with other splitters within the same RPA
cluster, subject to the following limitations:
Each volume can be attached to only one splitter.
There are no limitations regarding using different splitters in different Consistency Group
copies.
Starting with RecoverPoint 3.5, volumes attached to Symmetrix splitters and volumes
attached to VNX/CLARiiON splitters may be in the same Consistency Group.
17
When using the Symmetrix splitter, a LUN that is tagged for RecoverPoint can be used as an
R1 SRDF device. Replicating SRDF target devices (R2) cannot be supported and may lead to
data corruption.
18
When using RecoverPoint 3.5 and above and Enginuity microcode 5876, fake size and fake
geometry are supported. If the replica volumes in a replication set are larger than production
or are not of the same geometry, RecoverPoint will automatically and transparently request
for the array to change the presentation of the size and geometry of the replica volumes to
match production.
Even after a Consistency Group is disabled (for instance, after a migration) the fake size and
geometry will persist on the array. Manual action is required to restore the original size and
geometry.
19
This slide shows the high-level implementation steps for installing, deploying and using the
Symmetrix splitter. These steps are shown in the logical order in which they would be
performed in most environments. In the next several slides, we cover these steps in detail.
20
Splitting occurs at the FA port. When a host writes to a LUN through a specific FA port, the
same FA port must forward the write to a RecoverPoint appliance. Therefore, all RPAs must
be zoned to the same FA ports as the hosts. For the same reason, the LUNs must be exposed
(by appropriate LUN masking) to the host and the RPAs through the same FA ports.
In most implementations, create a single zone per fabric containing all RPA Fibre Channel
ports and all Symmetrix FA ports.
21
The slide shows zoning implementation in an MDS mirrored-fabric environment. As a

requirement of this architecture, RecoverPoint Appliances must be zoned to the same FA
ports as the replicated hosts.
22
LUN masking is performed on the VMAX by associating an initiator group, a port group, and a
storage group with a masking view. The instructions in the following slides indicate the
initiator, port, and storage groups that need to be associated with the required masking
views.
The best practice is to expose LUNs to host initiators and to RPA Fibre Channel ports through
the same FA ports. It is required to do so in the following cases:
when using Symmetrix splitter

when using a SANTap splitter with a host that uses LUN reservation and Enginuity
microcode prior to 5772
23
RPA masking views

1.
Create the RPA initiator groups:
a) Create an initiator group for each RPA and add its Fibre Channel port WWNs.
b) Create an RPA cluster initiator group, and add all RPA initiator groups created in step a.
c) If FA port flags do not match RecoverPoint requirements, set HBA flags for RPA cluster initiator group and
individual RPA initiator groups.
d) For Symmetrix splitter running Enginuity microcode 5875 only, enable Write-Protect ByPass (WPBP) for the
RPA cluster initiator group and for each RPA initiator group. When running Enginuity microcode 5876 and
later, Write Protect Bypass is no longer used. No action is required.
2.
Expose repository and journal LUNs to the RPA cluster:
a) Create a port group with all FA ports designated for journals.

b) Create the RPA cluster storage group with the RecoverPoint repository (if on this array) and all journal
volumes.
c) Create the masking view with the FA port group created in step 2a, RPA cluster storage group created in step
2b, and the RPA cluster initiator group created in step 1b.
3.
For Symmetrix splitter only, expose gatekeepers:
a) Create a port group for RPA1 gatekeepers or use an existing port group created in 2a. For optimal
performance, use 8 FA ports.
b) Create RPA1 gatekeeper storage group with 8 gatekeepers designated for RPA1.
c) Create a masking view with the RPA1 gatekeeper port group, RPA1 gatekeeper storage group, and RPA1
initiator group.
d) Create a port group for RPA2 gatekeepers or use an existing port group created in step 2a or 3a. For optimal
performance, use 8 different FA ports from those used for the RPA1 gatekeepers.
e) Create RPA2 gatekeeper storage group and add 8 different gatekeepers from the ones exposed to RPA1.
f) Create a masking view with the RPA2 gatekeeper port group, RPA2 gatekeeper storage group, and RPA2
initiator group.
24
Add RPA access to production and replica LUNs using one of the following two methods:
For each host masking view, create a mirroring RPA masking view using the same host
storage group, host port group and RP cluster initiator group. For example, if the Prod
masking view has Prod initiator group, Prod storage group and Prod port group, then the
equivalent RPA masking view will contain RP Cluster initiator group, Prod storage group
and Prod port group. The advantages are separating host and RPA initiator group flag
settings and the ability to use the Consistent LUN feature within the host masking view.
Create a mirroring RPA masking view for all hosts involved in RecoverPoint replication.
25
The second method is to add all RPA initiator groups to the initiator group of every host
accessing LUNs protected by RecoverPoint. The advantage of this method is fewer masking
views.
Both methods guarantee RPA access to the production and replica LUNs through the same FA
ports as the hosts.
The issue with this method is that if the host storage group contains any gatekeepers,
RecoverPoint will incorrectly assume that these are the dedicated gatekeepers it can use
with the Symmetrix splitter. Therefore, host gatekeepers should be separated into a different
host storage group, not accessible by RPAs.
26
When performing LUN masking, create a Port Group containing the Symmetrix front-end
ports involved in RecoverPoint replication. Note that these Symmetrix ports must be the
same ports through which hosts access their volumes.
Masking should be done using SMC or Solutions Enabler. This slide shows an example of
creating a port group using Solutions Enabler.
Command syntax:
#symaccess sid <Symmetrix S/N> create name <name> -type port
-dirport <dir:port,dir:port,,dir:port>
27
When performing LUN masking, create separate storage groups for RPAs 1, 2, and RP cluster.
There must be three storage groups. An example of an eight-node-cluster environment might
be:
1. RPA1 storage group: A Storage Group containing eight (8) unique gatekeeper volumes.
2. RPA2 storage group: A Storage Group containing another eight (8) unique gatekeeper
volumes.
3. RP Cluster storage group: A Storage Group containing the production volumes, the
replicas (local or remote), the Journal volumes and the Repository volume.
creating storage groups using Solutions Enabler.
Command syntax:
#symaccess sid <Symmetrix S/N> create name <name> -type
storage devs <devices>
28
After creating storage groups, run symaccess show command to verify that the
proper volumes are assigned to RPAs and RP Cluster storage groups.
29
When LUN masking for site 1 is completed, make sure RPAs at site 2 are provisioned with the
required volumes.
30
Similar to storage groups, there must be separate initiator groups for the RPAs. Three
initiator groups must be created. These include:
1. RPA1 initiator group: RPA1 HBAs only.
2. RPA2 initiator group: RPA2 HBAs only.
The third, RPA Cluster initiator group is covered in a separate slide.
creating an initiator group for RPA1 using Solutions Enabler.
Command syntax:
#symaccess sid <Symmetrix S/N> create name <name> -type
initiator -wwn <RPA port 0 WWN>
#symaccess sid <Symmetrix S/N> add name <name>
initiator wwn <RPA port 1-3 WWN>
-type
31
Run symaccess show command to verify that the proper RPA HBA WWNs are included
in the initiator group.
32
Finally, a third initiator group must be created to the RecoverPoint cluster. This includes:
3. RP Cluster initiator group: RPA1 initiator group (as a child initiator group), RPA2 initiator
group (as a child initiator group) and RPAs 3 to 8 HBA WWNs (if applicable). This initiator
group requires the new write by-pass flag be enabled. This allows RPAs to write to the replica
volumes (target devices).
It is critical that only RPA ports be placed in these Initiator Groups.
33
Run symaccess show command to verify that the proper child initiator groups and RPA
HBA WWNs are included in the RecoverPoint Cluster initiator group.
34
Masking view follows the same concept of storage groups and initiator groups. There must
be one exclusive masking view for RPA1, another for RPA2, and another one for the
RecoverPoint cluster. This allows for making the distinction of which volumes each RPA can
access. Remember that RPA1 sees eight (8) unique gatekeepers, RPA2 another eight (8)
unique gatekeepers, and the RecoverPoint cluster accesses all volumes, including repository,
journal, production and replica volumes.
creating masking views using Solutions Enabler.
Command syntax:
#symaccess sid <Symmetrix S/N> create view name <name>
<port group> -sg <storage group> -ig <initiator group>
-pg
35
To finish the LUN Masking, add RPA access to production and replica LUNs, using one of the
following two options:
1. Add all RPA initiator groups to the initiator group of every host accessing LUNs protected
by RecoverPoint, or
2. For each host masking view, create a mirroring RPA masking view using the same host
storage group, host port group and RP cluster initiator group.
36
Run symaccess list view command to display detailed masking view information.
37
All volumes involved in replication must be tagged as RecoverPoint devices, including

repository, journal, gatekeeper, production and replica volumes.
Tagging can be done using Solutions Enabler, SMC, or at the Symmwin level. This slide shows
how to tag devices using Solutions Enabler.
Command syntax:
#symconfigure sid <Symmetrix S/N> -cmd set dev <device list
or device range> attribute=RCVRPNT_TAG; commit
38
After device tagging is performed, one can verify the tags by running symdev commands
to list and show details.
Command syntax:
#symdev sid <Symmetrix S/N> list rcvrpnt_tag
#symdev sid <Symmetrix S/N> show <SymDev>
39
The symrcopy set ceiling command should be used to set ceiling to NONE for all
ports involved in replication.
Command syntax:
#symrcopy sid <Symmetrix S/N> set ceiling NONE dir <director
| ALL> [-port <port # | ALL>]
Command syntax:
symrcopy -sid 205 list ceiling
40
After LUN masking is completed, log in to RPA1 and RPA2 as user admin and verify that you
can access eight (8) unique gatekeepers (GKs) each.
Command syntax:
show_symmetrix_gate_keepers
41
This lesson covers VNX Splitter Installation.
42
The VNX/CLARiiON splitter runs in each storage processor of a VNX, CLARiiON CX3 or CX4
array and splits (mirrors) all writes to a VNX/CLARiiON volume, sending one copy to the
original target and the other copy to the RecoverPoint appliance.
Both RecoverPoint and RecoverPoint/SE support the VNX/CLARiiON splitter. The
VNX/CLARiiON splitter is supported on VNX arrays, CLARiiON CX3 UltraScale arrays as well
as CLARiiON CX4 UltraFlex arrays.
The VNX/CLARiiON splitter is supported on both iSCSI and FC attached volumes and supports
hosts running OSes compatible with the VNX/CLARiiON array.
Refer to the EMC Support Matrix for supportable configurations.
43
On new VNX deployments, the splitter has been added to the VNX OE code. However, it is
still required to install the splitter enabler. Check to see if the enabler is installed by viewing
Storage System Properties.
44
When deploying RecoverPoint/CL or /EX and after zoning the RPAs and the VNX/CLARiiON
ports, the RPAs are able to be manually registered with the array. If you check in
Connectivity Status on the VNX/CLARiiON, you find the RPA ports logged in. Each RPA port
should be registered with the following configuration:
Initiator type RecoverPoint Appliance

Failover mode 4
After registering, the VNX/CLARiiON splitter is configured and controlled as any other splitter
from the RPAs perspective.
Each SP is a splitter; they work in tandem, and are seen as two per-VNX/CLARiiON to the RPA
cluster.
The next steps are configuring at least one volume to be seen by the RPAs, and then adding
the RPAs to any relevant storage groups. Remember, the RPAs need to be able to see and
access any LUNs that are protected by RecoverPoint replication.
45
In order for the RPAs to see the VNX/CLARiiON as a splitter, they must have the following
connectivity requirements met:
Be added to a storage group

Be provisioned one LUN from the VNX/CLARiiON that will be a splitter
In our environment, we created a single storage group for the RPAs. To do this:
Right-click on Storage Groups.

Select Create Storage Group.
Name the group.
Create a LUN for the group.
In most cases, there are many storage groups consisting of different hosts and LUNs. For each
Host/LUN set that needs to be protected by RecoverPoint, the RPAs must be added to that
particular storage group. This is covered in the next slides.
46
After adding the RPAs to any and all required storage groups, it is a good practice to verify
that the RPAs can see the LUNs that have been masked to them. You can do this by logging in
as boxmgmt on the RPAs and detecting for FC LUNs. As shown here, the RPAs are seeing
multiple LUNs from a single VNX/CLARiiON.
As user boxmgmt, run:
[3] Diagnostics
[2] SAN Diagnostics
[3] View Target LUNs
A list of the visible LUNs for that RPA is displayed.
47
This lesson covers using the Deployment manager wizard to install RecoverPoint.
48
The RecoverPoint Installer Wizard is a graphical user interface (GUI) wizard that helps you
install a new RecoverPoint RPA cluster (site) from a single management point. The wizard
can be launched after starting Deployment Manager, as previously discussed.
As of RecoverPoint 4.0, the Installer Wizard allows you to install one RPA cluster at a time.
Therefore, if you plan to deploy multiple clusters, you must run the Installer Wizard as many
times as there are clusters. Once done installing the clusters, to enable replication and
communication between them, you must run the Connect Cluster Wizard. This enables
remote communication between clusters over IP or Fibre Channel
49
Before continuing, ensure the listed conditions are met. If any of the conditions are not
fulfilled, close the wizard, fulfill the conditions, and then run the wizard again.
50
The RecoverPoint Installer allows you to select one of two installation modes.
Create a new installation configuration file: The system creates a new installation
configuration file. Starting with a blank configuration, the user must enter configuration
settings for the installation. The system uses these settings to complete the installation.
Create or continue an installation from a saved configuration file: The system loads the
settings from a previously saved installation configuration file. Its location must be
defined. If using the file to create a new installation from a saved file, and the file was
already applied to a previous installation, the system will allow you to use the file and
modify the configuration parameters.
51
From this screen, the Environment settings for the cluster can be defined. They fall under the
following categories:
General
Cluster name - Must be unique as it can cause errors if another cluster is sharing a
splitter
Number of RPAs - A cluster can have between 2 to 8 RPAs.

Time zone - A drop down menu is provided
Connectivity
LAN (management) IPv4 and/or IPv6 Type can be defined. MTU must be 1500
unless directed
WAN (replication) IPv4 or IPv6 Type can be defined. MTU must be 1500 unless
directed
Environment
Domain name
Primary DNS server
Secondary DNS server
NTP server
Secondary NTP servers
52
The wizard allows for 2 different discovery methods.

I have already set IP addresses for the RPAs: Use this method if you have already set the
temporary address using CLI.
I want Deployment Manager to discover the RPA IP addresses: This requires a DHCP
server. When selected there will be 2 choices:
- Run discovery from work station: The installer will try to discover all unattached
RPAs. The work station must be able to communicate with all the RPAs.
- Run discovery from an RPA: The installer will try to discover all unattached RPAs
from an RPA.
53
Define the cluster IP configurations and set the RPA IP settings. These settings include the
Cluster management address, each RPA address for the LAN and WAN, and the default
gateway.
54
RecoverPoint allows you to define advanced settings for unique installations. Use the
Advanced Mode for the following use cases:
If you are replicating VMware volumes with splitters running on virtual machines. If you
respond Yes, you must specify how many exposed paths you need for the replicated
VMware volumes. Refer to the EMC RecoverPoint Replicating VMware Technical Notes for
instructions on how to count the number of paths accurately.
If you are replicating a single VNX/CLARiiON storage array with more than 256 LUNs being
presented to the RPA. If you respond Yes, you must define the number of virtual WWNs
the RPA should expose to the VNX/CLARiiON array.
If you are replicating a non-EMC storage array that does not allow sharing of WWNs
between storage groups.
If you are replicating a non-EMC storage array that is not compatible with RPA HBA ports
that operate in both initiator and target mode.
55
Enter the default RecoverPoint login credentials. The system will prompt you to enter your
RecoverPoint login information. For username boxmgmt, the default password is boxmgmt.
Click next to continue.
The system communicates and validates the statuses of the RPAs and confirms that all
components are OK, or that errors are detected. The system presents the following results:
Status, RPA, Cluster name, RPA LAN IP address, RPA hardware platform, RecoverPoint
release. When all statuses appear OK (green check mark), click Next to continue.
56
At this point the wizard allows you to upgrade the current version of RecoverPoint software.
The discovered release is displayed. If this is correct, select Do not update.
If you choose to update the version of RecoverPoint, an iso image can be downloaded from
EMC support, or provided locally.
57
The system attempts to log in to each of the RPAs and validate system information. The
results of applying the configuration settings to all RPAs are displayed. Once installation has
completed successfully, click Next. This saves the configuration information to each RPA. A
green check indicates the operation was successful for each RPA.
58
The system displays the port numbers, port WWNs, and node WWNs of each RPA HBA for
the cluster. Use this information to zone and mask LUNs for the RPAs.
All RPA ports in a fabric must be zoned with all storage ports that are available for
RecoverPoint replication. For example, if a fabric has a port from SPA and SPB from a VNX to
be used for RecoverPoint. Those 2 ports should be zoned to all RPA FC ports connected to
that Fabric.
It is necessary to create zoning for distributed Consistency Groups. Distributed Consistency
Groups require that all RPA Fibre Channel ports in the fabric can communicate with each
other. All RPA ports in a fabric must, therefore, be in one zone. Normally, the RPA-to-storage
zone satisfies this requirement.
LUN Masking should be identical for each RPA port and for each RPA. To install the cluster,
only the repository is required. Replication and Journal volumes can be added after
installation and licensing.
59
The system performs SAN diagnostics for the cluster, attempting to validate that the current
configuration is appropriate for the RPA and that RecoverPoint can successfully operate in
the current SAN environment. The system will present the following results: Severity, RPA,
Message ID, Category, and Description.
The system will confirm that all components are OK and that no errors exist. If errors are
detected, you can click the error to display details and instructions on how to correct the
problem.
Once errors are resolved, click Refresh to rerun the SAN diagnostics process. It is highly
recommended to resolve all SAN discovery warnings, even though the system allows you to
ignore them and continue the installation.
60
As part of the installation process, you must create a repository volume from one of the
storage array LUNs. The repository volume holds RecoverPoint configuration data that is
created in the replication process. Once chosen, it is disruptive to change it.
LUNs presented in the table can be chosen as a repository volume as long as they meet the
minimum size requirements. The LUNs displayed will be the ones that are masked to the
RPAs.
IMPORTANT:
Since the RPA formats (clears) the selected LUN, you should ensure that the LUN is new and
does not contain any valuable data.
61
The system communicates with each RPA and performs the following steps:
Applies settings per RPA.
Selects and formats the repository volume.
Attaches each RPA to the cluster.
Reboots each RPA.
The RPAs attach to the cluster after reboot and the installation is complete.
62
You have successfully completed the RecoverPoint installation. To start managing the
RecoverPoint system, select the Open Unisphere for RecoverPoint now for cluster checkbox
and click Finish.
Unisphere for RecoverPoint will launch, provided the default browser meets the minimum
requirements.
63
This lesson covers using Deployment Manager to connect RecoverPoint Clusters.
64
RecoverPoint clusters can be connected together in order to perform replication to or from

different geographical locations. New clusters can be connected to existing clusters. A new
cluster is a RecoverPoint cluster that has been installed, but not licensed. This is a 2-step
process and can be done with Deployment Manager or the CLI interface.
65
Use Deployment Manager or CLI to connect clusters together via the WAN or Fibre Channel.
This was previously discussed in module 2. The clusters can be connected one at a time.
Each new cluster must not be licensed until the connection is complete.
66
The first time Unisphere for RecoverPoint is run after a RecoverPoint installation, the Getting
Started Wizard is displayed to guide users through the steps necessary to configure the basic
RecoverPoint settings needed to ensure their RecoverPoint systems are up and running as
soon as possible.
There are three screens in the Getting Started Wizard:
1.Welcome screen - provides a brief description of the wizard and its functionality
2.Add Licenses screen - allows you to install your RecoverPoint license and display the license
information
3.Enable Support screen - allows you to configure and test the RecoverPoint system
notifications mechanism
67
The settings in the Add Licenses screen are displayed in several places: through the Getting
Started Wizard the first time you launch Unisphere for RecoverPoint, and in the Admin >
Manage Licenses screen each subsequent time it is launched.
To add a license:
Click Add to display the Add License dialog box.
Click Browse... and select a license file.
Click OK to add the license file to the RecoverPoint system.
68
The Enable Support screen allows you to configure the RecoverPoint system reports
mechanism (SyR) and provide one-way communication between a RecoverPoint installation
and the EMC System Reports database (ESRS).
The settings in the Enable Support screen are displayed in several places: through the Getting
Started Wizard the first time you launch Unisphere for RecoverPoint, and through the Admin
>Configure System Notifications screen each subsequent time it is launched.
69
After installing a RecoverPoint system, you must complete the RecoverPoint PostDeployment Form. To download the form from EMC Online Support
(http://support.emc.com), click Support by Product, type RecoverPoint CL in the Find a
Product search field. On the RecoverPoint SE page, click Documentation and download
the form from the list of documents
Connect Home Ensure the Install Base Record is complete and accurate, including the
Connection Record. Further, ensure that 2-way connectivity is established and tested before
considering the install complete. If the customer has refused one or both of the connections,
the IB Connection Record should reflect this. To test connection: Refer to Primus emc239913
for detailed instructions.
Connect In RecoverPoint 3.2 and above supports connect in through ESRS as long as the
customer system (RPA) is registered with the ESRS gateway.
Connected to Relationship The IB group will establish a connected to relationship from
each Hardware TLA to the Software TLA. This allows additional tie for solutions-based
reporting.
Microcode All RecoverPoint versions, including service packs and patches, have microcode
values in CSI. Please provide version install to the IB group and they will update customer
profile.
70
Party ID (formerly Site ID) Provide customer name and location information to the IB
group. The group will verify the Party ID.
RPA Hardware Serial ID For Dell R610 (Gen4) platforms use the get_rpa_states
command. Search for the Hardware Serial ID values of all RPAs. If the values starts with the
prefix WCARP or NNG##, then record and submit them. If the values do not start with the
prefix WCARP or NNG##, then the RPA serial number - S/N - appears on a white label
(sticker) found on top of the LCD display of each RPA. A serial number is required for each
RPA. Please validate which RPAs are at your specific cluster, as this command will report on
all RPAs in the total solution.
Note: The NNG## prefix only appears when using Dell R610 (Gen4) platforms.
Software Serial ID Use the get_system_settings CLI command. Please validate which
Software Serial ID is at your specific site (either local or remote), as this command will report
both the local and remote Software Serial IDs.
Account ID Use the get_account_settings CLI command. Value will show up in first
field labeled Account ID.
71
This module covered the installation RecoverPoint/EX and CL.
72
73
74
This module focuses on Consistency Groups and their configuration and operations.
Module 4: RecoverPoint Operations
This lesson covers the features of Unisphere for RecoverPoint.
The RecoverPoint 4.0 and later user interface has been developed using Adobe Flex
technology and simplified to promote ease of use and a common user experience between
RecoverPoint, VNX, VPLEX and Symmetrix products.
The RecoverPoint wizards are streamlined and optimized for a simpler and more intuitive
user experience. Targeted at the IT generalist, a dashboard has been added to provide an
overview of system health at a glance, and all of the information displayed through
Unisphere for RecoverPoint is consistently auto-refreshed.
The RecoverPoint Dashboard provides a high-level overview of the RecoverPoint system. It
presents important system information to help you analyze and monitor your RecoverPoint
environment. The Dashboard can be used to give a graphical indication of the Overall
Health, the System Limits, and display System Events.
The Overall Health tab graphically displays an overview of the current status of the
RecoverPoint system. It contains views that allow you to easily monitor and analyze the
current state of the system.
Click the Overall Health tab of the Dashboard to monitor the system through the following
views:
RPA Clusters Map
Alerts
System Traffic
Consistency Group Transfer Status
The RPA Clusters Map provides a schematic representation of all RPA clusters in the
RecoverPoint system, the connectivity between them, and any system alerts received by the
clusters.
The RPA Clusters Map displays the type of connection that exists between all RPA clusters in
the system. A dashed line represents an IP (WAN) connection and a solid line represents a
Fibre Channel (LAN) connection.
The RPA Clusters Map also displays the status of all major components in the system that are
seen by the RPA cluster, including: hosts, switches, storage devices, individual RPAs, the LAN,
and the WAN.
The System Limits tab monitors important system values to let the user know how close they
are to their limits. The limits may be determined by the system, policies, licensing, or
limitations of external technologies.
The System Events tab displays the RecoverPoint event log which contains all events logged
by the RecoverPoint system, in the order that they are logged. A total of 9000 events can be
displayed in the event log.
To display system events: select Dashboard > and click the System Events tab. The
RecoverPoint event log is displayed, containing the last 9000 events logged in the
RecoverPoint system. Each event in the event log is displayed along with its relevant event ID,
summary, level, scope, point in time, RPA cluster, and topic.
Each RecoverPoint user is defined by a user name, a password, and a set of permissions.
Additional security measures can be applied to the RPA. You cannot delete any of the default
users or change the default permissions for those users. However, you can change the
default passwords.
RecoverPoint provides two independent mechanisms for authenticating users: appliancebased authentication and authentication via the organizations LDAP (Lightweight Directory
Access Protocol) server. The two authentication mechanisms can be used simultaneously,
LDAP may be used exclusively, or appliance-based authentication can be used exclusively.
In a Linux or Unix environment, open a CLI session with a site in the RecoverPoint installation
using the following SSH login:
$ ssh user@<site management IP>
In a Windows environment, open a CLI session with a site in the RecoverPoint installation
using a PuTTY login.
In the PuTTY Configuration dialog box, fill in the following details:
Host name: Site management IP
Connection type: SSH
Port: 22
Once connected, log in as user admin with password admin. User admin is permitted to run
most of the commands. Alternately, log in as user monitor with password monitor. User
monitor is permitted to run read-only commands, such as the get commands. You can add
users and change passwords, provided you have the necessary security permission.
After opening a CLI session, you can view a listing of all CLI commands by pressing Tab at the
session prompt. To receive a listing of all commands together with a brief description of each
command, type help and then press Enter. To obtain information about the required syntax
for a particular command, type: help <command name> or <command name> ? For best
display results, you should open the CLI session in a window that is at least 115 characters
wide.
To use interactive mode within the CLI, first type the command. The system then prompts
you for mandatory and optional parameter values.
For mandatory parameters:
If you press Enter without entering a value, the system displays an error message, and
prompts you again to enter a value. If you fail to enter a value a second time, the system exits
the command.
For optional parameters:
If you press Enter without entering a value, the system accepts the default value for the
parameter.
In a non-interactive CLI session, type all of the information for the command in a single
statement following the prompt. The command must start with the command name, and can
then be followed by relevant parameters. Each parameter must have the format <parameter
name>=value or -<parameter name> value. For commands with only one parameter, it is not
necessary to include the parameter name. You can just enter the parameter value after the
command name. There is no required order in which the parameters must appear in the
command line, and it is permissible to mix mandatory parameters with optional ones. You
must, however, specify all mandatory parameters. Otherwise, an error is displayed.
10
This lesson covers creating Consistency Groups for data protection.
11
Non-distributed Consistency Groups transfer data through one primary RPA that is
designated by the user during group creation and can be modified at any time through the
group policy settings.
Distributed Consistency Groups allow users to create and use Consistency Groups that
require a total throughput and IOPS rate that exceeds the supported throughput and IOPS
rate of a single RecoverPoint appliance, and prevent users from having to split data that
requires strict write-order fidelity into multiple Consistency Groups. They do so by dividing
the Consistency Group into four segments, and running these segments on one primary RPA
and one to three additional secondary RPAs, as defined by the user.
Each RPA has a maximum throughput rate (see EMC RecoverPoint and RecoverPoint/SE
Release Notes for this limit), which together with the host write-rate and available network
resources, limits the maximum size of the Consistency Group. For a higher throughput rate,
and to balance the load of extra-large Consistency Groups, define the Consistency Group as
distributed, through the group policy settings.
A maximum of 128 Consistency Groups can be defined in RecoverPoint, and a single RPA
cannot be configured to have more than 64 Consistency Groups. In the event of RPA failure,
groups that transfer data through one RPA will move to other RPAs in the cluster. In such a
case, an RPA can temporarily hold up to 128 groups, and the data of all groups will continue
to be transferred between sites. This state is temporary, however, as an RPA with more than
64 groups may run into high loads, and if this state is prolonged, group policies could be
affected.
12
Distributed groups can handle a much higher throughput and IOPS rate (see the EMC
RecoverPoint and RecoverPoint/SE Release Notes for this limit) regardless of the amount of
data being replicated.
Up to eight distributed Consistency Groups can be defined in RecoverPoint, and the total
number of distributed and non-distributed Consistency Groups is 128.
With a fully populated distributed CG (with 4 RPAs), RecoverPoint 3.3 or later can replicate in
asynchronous mode at 240 MB/sec sustained over FC and 250 MB/sec over IP.
Distributed Consistency Groups are only supported if there is a Fibre Channel (FC) connection
between all RPAs in an RPA cluster.
In FC environments, ensure that all the RPAs are connected to the SAN through a FC switch,
and zoned together so that they see each other in the SAN.
In iSCSI environments, ensure all RPAs are physically connected to each other through their
HBA FC ports.
Note: In iSCSI configurations, without the use of FC switches, there can be a maximum of two
RPAs per RPA cluster since two of the four existing RPA HBA FC ports are already connected
directly to the storage (for high availability). If more than two RPAs are required for the
cluster, connect all of the RPAs in the cluster through FC switches and zone them together.
13
The following types of copies exist in a Consistency Group:

The production copyThe production copy consists of all of the volumes that are the
sources of replication of a Consistency Group, as well as the production journal volumes.
Local copiesA local copy consists of all of the volumes that are the targets of replication,
for a specific Consistency Group, and the copy journal volumes
Remote copiesA remote copy consists of all of the volumes that are the targets of
replication, for a specific Consistency Group, and the copy journal volumes
In RecoverPoint terminology, a copy denotes a non-production copy of a volume. Local
refers to the same cluster as the production.
14
Protection of volumes using Unisphere for RecoverPoint is guided by wizards, and performed
through the Protection menu. The tree options are Protect Volumes, Manage Protection,
and Manage Group Sets.
To create a new Consistency Group, the Protect Volumes wizard can be used. Both the
Manage Protection, and Manage Group Sets wizards allow for the management of existing
Consistency Groups.
To protect volumes Select Protection > Protect Volumes. This will launch the wizard.
15
Before beginning the Protect volumes wizard, ensure that you understand the concepts of
RecoverPoint and you have your RecoverPoint environment planning document, which
includes the following:
The number of Consistency Groups that you will need, and their names.
The LUNs to include in each group, and at each copy.
The journal LUNs at each copy.
Which Consistency Groups to set as distributed.
The required RPO and RTO settings per Consistency Group.
The RPA that will handle the replication of each group.

The priority of each Consistency Group with relation to the other groups in the system.
In the Select Production Volumes screen, define the Consistency Group name, the
production name, and the RPA cluster that will manage the production.
A list of volumes will be displayed once a cluster is selected. The list is dependent on volume
masking to the RPAs, the RecoverPoint license type installed and the splitter type used by the
selected cluster.
Once a production LUN has been selected, the Modify Policies link is only enabled. This
can be used to adjust the CG polices from the default settings.
16
In the Define Production Journal screen, select the volumes to add to the journal from the
volumes list. For best performance, select volumes that are identical in size. If identically
sized volumes are not available, select volumes that are similar in size.
The list of volumes displayed is determined by LUN masking to the RPAs and the installed
RecoverPoint license.
17
Define the copy name, the RPA cluster that will manage the copy volumes, and the
replication mode. For each production volume, click the Select volume link to add a volume
to the copy. The selected volume is the volume that the production volume is replicated to.
The volume list is displayed. The volume list only contains volumes of sizes that are equal to,
or greater than, the specified production volume.
For best performance during failover, select volumes that are the same size as the
Production volume. If volumes of the same size are not available, select volumes that are as
similar in size as possible.
You cannot proceed to the next step until the Replication sets icon under the volume list
shows a green check mark to indicate that the number of Replication sets is equal to the
number of production volumes.
18
In the Define Copy Journal screen:

Select the volumes to add to the journal from the volumes list.
To continue configuring the group, click Next Display Group Summary.
19
The Group Summary screen displays the production and the copy cluster names. At this
point, if another copy is needed, the Add a Copy wizard can be used. The steps to add a
copy are the same as previously covered.
RecoverPoint 4.0 supports up to 4 copies of the production data.
20
After a Consistency Group is created, you are redirected to the Manage Recovery screen,
where you can monitor and manage your existing Consistency Groups and their protection
plans, control transfer, and mark consistent points in time across groups and sets of groups.
Once first-time initialization is complete, each Consistency Group will be in one of the
following states of transfer:
Replicating: The Consistency Group is enabled, the splitter is splitting data to the RPAs, and
the RPAs are transferring data to the remote RPAs.
Marking: The Consistency Group is enabled, the splitter is splitting the data to the RPAs, but
the RPAs are not sending the data to the remote RPAs, but instead, they are saving the
locations of the writes on the production journal. When the connection is re-established and
the system moves to Replicating mode, the copy is synchronized with the production using
this information.
The following can cause the RPA to go to marking mode:
WAN unavailable
RPAs at a remote RPA cluster not available (for instance, loss of power)
Transfer disabled manually
High load (temporary bottleneck in replication environment)
No marking/no replication: the splitter does not split data to the RPAs. This can be caused
by a manually disabled Consistency Group or by a disaster at the production site (that would
mean no RPAs are available).
21
From the Manage Consistency Groups screen, the performance parameters for a group can
be edited. By selecting the Group Policy tab, the following policy settings can be configured.
Group Name: The name of the Consistency Group.
Primary RPA: The RPA that you prefer to replicate the Consistency Group. When the
primary RPA is not available, the Consistency Group will switch to another RPA in the RPA
cluster.
Priority: Normal is the default setting. This is only relevant for remote replication over
the WAN or Fibre Channel, when two or more Consistency Groups are using the same
Primary RPA.
External Management: Using an external management application (such as RP/CE, SRM,
or REE)
Distributed Settings: The default setting is Disabled. If enabled, this allows group writes
to be distributed across multiple RPAs, significantly heightening the maximum available
RPA throughput. Additional information is discussed in the next slide.
22
Distributed Consistency Groups (DCGs) function just like regular Consistency Groups, except
they can span up to four RPAs at once. One RPA is designated the primary RPA, which
receives all incoming data from the splitter. The primary RPA then examines the target and
block# and will either process the I/O itself or forward it to the secondary RPAs within the
group via FC. The individual RPAs then replicate that data normally.
DCGs need much larger journals than normal Consistency Groups. While 10GB was the
minimum for regular Consistency Groups, 20GB is needed for DCGs. If the journal is already
at least 20GB in size, then there is only a short pause in replication when converting to a
DCG. If the journal is less than 20GB the user must increase the size of the journal manually
before the conversion can successfully complete. Converting a Consistency Group in either
direction causes the contents of the journal to be lost. Changing the secondary RPAs will not
delete the contents of the journal.
There is a maximum of 8 distributed CGs per cluster. With a fully populated distributed CG
(with 4 RPAs), RecoverPoint can replicate at 240MB/sec sustained over FC and 250MB/sec
over IP.
23
Deduplication will only work on Physical RPAs (on both sides of the WAN) with at least 8 GB
RAM.
Each RPA will use a dedicated 1 GB of RAM in order to save the transferred data. This area of
memory becomes active when the first Consistency Group with deduplication active starting
its transfer on an RPA.
All RPAs in the cluster should be 8 GB machines.
If an RPA running on a hardware platform other than GEN4 is added to a RecoverPoint cluster
while deduplication is enabled, the deduplication process will fail.
The feature can only be used in conjunction with CRR Consistency Groups with compression
enabled.
Deduplication is only relevant for asynchronous replication.
24
The Link Policy menu allows the user to configure parameters that control the logical connection
between a Production volume and each of its copies. The Link to be configured can be selected from
the window on the left side of the menu. Each copy of the Production volume will have a selectable
link.
The Protection Settings parameters allow for the configuration of the Replication mode. The choices
include Asynchronous or Synchronous. If Synchronous is selected, additional settings are available.
These include:
Dynamic by latency: When enabled, RecoverPoint alternates between synchronous and
asynchronous replication modes, as necessary, according to latency conditions.
Dynamic by throughput: When enabled, RecoverPoint alternates between synchronous and
asynchronous replication modes, as necessary, according to throughput conditions.
Additional settings include:
RPO: By default this parameter is disabled. If enabled, this setting defines the lag of the
Consistency Group, and is set manually in MB, GB, writes, seconds, minutes, or hours.
Compression: This setting is Low by default. Used to compress data before transferring it to a
remote RPA cluster. Can reduce transfer time significantly.
Enable Deduplication: Used to eliminate repetitive data before transferring the data to a remote
RPA cluster. Can reduce transfer time significantly.
Snapshot Granularity: This setting is Fixed (per second) by default.
-Fixed (per second): To create one snapshot per second, over a
specific (local or remote) link.
-Fixed (per write): To create a snapshot for every write operation,
over a specific (local or remote) link.
-Dynamic: To have the system determine the snapshot granularity
of a specific (local or remote) link, according to available
resources.
25
RecoverPoint supports the semi-automated load balancing feature. It provides

recommendations for Consistency Group distribution between the RPAs to maximize
replication availability and performance. Typically, the Consistency Group will run on the
preferred RPA unless a problem is encountered. This functionality can cause high-loads on
the RPAs in environments where the Consistency Groups are not evenly distributed between
the RPAs.
There are three possible recommendations that may be made by the semi-automated load
balancing tool.
If the RPAs arent currently balanced, the tool will recommend applying the suggested
balancing.
If the environment is stable but RPAs are not balanced, the tool will suggest how to
divide the groups differently across the RPAs.
If the environment is stable and all groups are evenly distributed across the RPAs, no
change is recommended.
The load balance algorithm is tailored for steady state, meaning it does not take into account
an RPA that is down. It performs its calculations on the known RPAs in the environment. The
balance_load command will not run when site control is down. Up to 10 (tweaks) files in the
web download folder are maintained.
Note: The semi-automated load balancing feature runs in a suggest, dont apply mode. This
means the user can accept or reject the recommendations it makes.
26
To view real time data for a selected Consistency Group, select the Statistics tab from the
Manage Protection screen.
The following traffic statistics are displayed in the Traffic sub-tab:
Total traffic
Application traffic
Initialization traffic
Incoming writes
If the Consistency Group contains a remote copy, the following replication performance
statistics are displayed in the Replication Performance sub-tab:
Bandwidth reduction
Time lag
Write lag
Data lag
27
To monitor a copys journal:

1. Select Protection > Manage Protection.
2. In the left pane, expand a group and select a copy.
3. In the right pane, select the Journal tab.
The following describes the information displayed in the Journal tab of each copy.
Current: Snapshot currently being distributed to the journal.
Storage: Storage access status. The current condition of a volume at the copy storage can
be:
No Access, during normal replication.

Direct Access, during direct image access.
Logged Access, during logged access.
Journal Lag: Amount of data (represented by snapshots) in the copy journal that has not
yet been distributed to the copy storage. The maximum journal lag setting defines the
current recovery point objective. In the event of a disaster, this is the maximum amount of
data loss that may be incurred.
28
This lesson covers the differences between image and direct access as well as the steps to
create bookmarks using the RecoverPoint Management Application interface.
29
A snapshot is a point in time marked by the system for recovery purposes. A snapshot
includes only that data that has changed from the previous image. Upon being distributed, it
creates a new current image on the remote storage.
A snapshot is the difference between one consistent image of stored data and the next.
Snapshots are taken seconds apart. The application writes to storage; at the same time, the
splitter provides a second copy of the writes to the RecoverPoint appliance. In asynchronous
replication, the appliance gathers several writes into a single snapshot. The exact time for
closing the snapshot is determined dynamically depending on replication policies and the
journal of the Consistency Group. In synchronous replication, each write is a snapshot. When
the snapshot is distributed to a replica, it is stored in the journal volume, making it possible
to revert to previous images by selecting the stored snapshots.
The snapshots at a copy are displayed in the copy Journal Tab.
For each Consistency Group, a Snapshot Granularity policy can be configured to regulate data
transfer. Remember that the following granularities can be defined:
Fixed (per write): To create a snapshot from every write operation.
Fixed (per second): To create one snapshot per second.
Dynamic: To have the system determine the snapshot granularity according to
available resources.
A bookmark is a named snapshot. The bookmark uniquely identifies an image. Bookmarks
can be set and named manually; they can also be created automatically by the system either
at regular intervals or in response to a system event.
Bookmarked images are listed by name. The bookmarked snapshots at a copy are displayed
in the copy Journal Tab.
30
RecoverPoint captures every write, enabling you to recover data from any point in time. Keeping days to
months of every point in time, however, requires very large journals. Over time, re-writes to a single disk
location consume a large amount of journal space. Additionally, the need to recover back to an exact point in
time decreases as the data ages. The granularity of snapshots becomes less important over time. Snapshot
consolidation enables longer-term point-in-time recovery using the same storage consumption. Snapshot
consolidation discards re-writes to the same disk location to save on journal space, which allows a longer
history to be retained in the journal.
Using snapshot consolidation, you decide how long to retain every write captured, and at what point to
consolidate these writes to a daily, weekly, or monthly snapshot. Snapshot consolidation allows you to retain
the crucial per write or per second data of write transactions for a specified period of time (for example, the
last 12 hours, days, weeks or months of transactions) and only then to start gradually increasing the granularity
of older snapshots at preset intervals (for example, to create daily, then weekly, and then monthly snapshots).
With snapshot consolidation:
All writes to a single disk location are saved in their end-state at one specific point-in-time. Therefore, all
writes to the same disk location between the start-time and end-time of the consolidation are deleted.
The amount of journal space saved depends on the I/O pattern, how many blocks get re-written, and other
factors.
The time needed to consolidate snapshots depends on the number and size of the snapshots being
consolidated.
A minimum of 1 GB of changes (writes) must have occurred and been transferred to the replica journal for
the snapshot consolidation process to start.
By default, 20% of the journal's capacity is dedicated to the image access log used during Logged access,
another 5% of the journal's capacity is dedicated to the calculation of indexes that are used for Virtual
access, and an additional ~1GB is dedicated to handling bursts during distribution. This means that only
~75% of the journal is available for the storage of snapshots. When snapshot consolidation is enabled, the
consolidation process uses 25% of the remaining ~75%. Therefore, for consolidation to occur, 25% of 75%
of the journal must be free (must not contain snapshots).
31
The journal consists of snapshots (represented by small vertical lines), which are collections
of one or more writes to storage. Since the snapshots are always in strict write-order, writing
the next snapshot to storage creates a valid image of the data at the next point in time. By
the same token, rolling back to the previous snapshot (undoing the last write to storage)
creates a valid image of the storage data as it was at the previous point in time.
Image access allows you to pick the exact point in time at which you wish to see the storage
data. The selected snapshot marker marks the snapshot you wish to access.
In logged access, RecoverPoint will roll back (or forward) the snapshots, applying them to the
image in storage until the selected image (point in time of the data) is reached. Once this
image is reached, which may take time if there are many snapshots to undo or to distribute,
you can access it and even modify it. For instance, you may want to use this for testing or
data analysis. Any changes made to the image during image access will be recorded in the
image access log, so that the image can be restored to its exact state before image access.
When you disable image access, all writes made during image access will be undone
(according to the undo information in the image access log), and the image will roll forward
to distribute writes in the journal to the replica.
Virtual access works on the same principle, except that the image is not created by rolling
back snapshots and applying them to the stored image. Instead, the image is created on a
virtual disk by pulling the needed data either from the snapshots or from the storage. The
virtual disk is deleted when image access is disabled. Virtual access is quicker than logged
access, but is not suitable for extensive processing or when large areas of the image must be
accessed.
32
This lesson covers using RecoverPoint for data recovery.
33
Use Test a Copy to access and test copy images. In RecoverPoint, image access is designed to
allow for the brief verification, backup, cloning, or data analysis of a copy, before failover or
production recovery.
Before testing, or in other words enabling image access to a copy:
Decide which image access mode best suits your purposes
If you need more time to test than your image access log or journal will allow, you can add
additional journal volumes to the journal
During testing (that is, while image access is enabled), Journal lag (RPO) increases as the
production writes reach the copy journal. Unless the journal becomes full and you encounter
a high load, replication can continue as usual. Production writes are transferred to the copy
and stored in the image access log of the copy journal.
34
To start the Test a Copy wizard, select Recovery > Test a Copy. The initial screen allows the
user to choose a copy to test. This is displayed in picture 1. All copies of the Consistency
Group will be displayed. Next an Image and Image access mode are chosen (picture 2).
Image Access Modes are:
Logged Access - An image access mode that physically rolls the copy storage to the
selected image (bookmark or point in time).
Virtual Access - An image access mode that creates only the required parts of the image
you selected in a separate virtual volume, enabling image access almost instantly, as the
system does not physically roll the copy storage to the selected image.
Roll image in background - An image access setting that physically rolls the copy storage to
the selected image in the background when Virtual Access is selected as the image access
mode. Once the roll is complete, the system starts accessing the volume physically.
The wizard allows you to select an image in one of two ways. You can select The Latest
Image, which is the last snapshot that was created. The other choice is to select an image
from the image list, this opens a list of images in the copy journal, and enables you to easily
identify and select an image from the list by point in time, snapshot size (or the delta
between the selected snapshot and the snapshot before it), bookmark, consistency, and
consolidation policy. An Example is displayed in picture 3.
Once the selections are complete, select Test the Image.
35
The Test the Image screen displays RecoverPoint enabling image access to the copy
volumes. Wait for image access to be enabled and the system to roll to the selected image to
begin testing.
You know that image access is enabled (in the Activity pane) by the image access status icon
in the Completed (in RecoverPoint) task list. When image access is enabled, perform the
steps under Next (at the copy host) task list.
Prepare the copy volumes for testing: Mount the copy volumes that you want to access. If
the volumes are in a volume group managed by a logical volume manager, import the
volume group. Access the copy volumes, and test them as required.
While testing, take note of the Image access log capacity progress bar in the Activity pane. If
the image access log becomes full, all writes to the copy are blocked. You will then have to
make a decision to either Add journal space, Undo writes, or Disable image access.
36
Use Recover Production to correct file or logical corruption by rolling the production data
back to a previous point-in-time. Production recovery is only available if the copys journal is
still intact; therefore, it is not available after distributing a snapshot that is larger than the
capacity of the journal.
The Recover Production wizard guides you through the process of selecting a copy image,
testing it, and recovering the production from the selected image.
During production recovery:
Transfer from production to the copy is briefly paused. Transfer from production to other
copies does not resume until the production is restored.
Host access to storage is blocked.
Current production data is overwritten.
Distribution from the copy journal to the copy storage stops.
37
To recover the production data, select Recovery > Recover Production. The wizard will
launch.
In the Select a Copy screen:
a. Select the Consistency Group to perform Production Recovery.
b. Select a non-production copy.
c. Click Next Select an Image.
The copy chosen should be the most likely to have an image stored in its Journal that
contains the correct point in time to which recovery is desired.
38
In the Select an Image screen, select an image that you want to verify and then recover to.
To restore your production from a copy, you generally want the most recent copy image that
you know to be valid. For example, if you are using Microsoft Volume Shadow Copy Service,
you probably want to select the most recent shadow copy. The shadow copies will be
bookmarked with the name that you assigned to shadow copies in the Microsoft Volume
Shadow Copy Service configuration. Images also may be labeled using bookmarks.
Click Next Start Recovery to continue.
39
In the Start Recovery screen you can see that RecoverPoint has enabled image access using the
previously selected image (picture 1). The display on the left shows the production as still being
accessible and Logged Access is enabled at the cluster chosen.
From the Host accessing the copy, the image can be verified. While testing the copy image, undo
information for any changes made to the copy is written to the image access log in the Journal. This
will be deleted once Image Access is disabled. Once the image is verified, Click Finish. A warning
appears (picture 2) to ensure that the host accessing the copy has Un-mounted the volume. The
Production host also has to Un-mount the volume. The last part of the warning is a reminder that the
production volume(s) will be overwritten with the selected image.
When Yes is selected from the warning screen, RecoverPoint will:
Disable Image Access to the copy
Disable Host access to Production
Overwrite Production with the Image selected from the copy
The direction of replication changes, and replication proceeds from the copy image to the
production, as the copy image is being applied to the production. The marking information in the
production journal is deleted, and the copy journal is deleted. The group undergoes a full sweep to
ensure consistency between the copy volumes and the production volumes. The copy Transfer status
reverts back to Active. The production Transfer status reverts back to Direct access, and the
production Role reverts back to Production as image access at the production is enabled.
When the warning screen is acknowledged, the Manage Recovery screen opens (picture 3). This can
be used to monitor the progress of the group.
40
RecoverPoint Failover wizard can be used to migrate all production activities to a copy.
Migration should be planned well in advance, and the image selected for migration should be
part of an overall migration strategy. Failover can be temporary, such as an unplanned site
outage. For groups with more than one non-production copy, you can also temporarily fail
over to perform routine maintenance on the production system, and then fail back to the
production.
41
The first step in the Failover Wizard is the Select a Copy screen. From this menu a
Consistency Group, whose copy you will use to perform the testing, failover or production
recovery, is selected. Next, select a copy to which you want to failover. Then select Next
Select an Image to move to the next screen in the Wizard.
42
The next step in the Failover Wizard is the select an Image to which to failover. The menu
allows you to choose from:
The latest image
An image from the list: This option will bring up a menu. It will contain all the snapshots
and bookmarks stored in the Journal.
A specific point in time: This option will allow you to search for a bookmark by name, or
specify a time for the image to be selected from.
Logged access or Virtual access can be selected as a method to access the image.
Select Next Start Failover to continue. When this is selected, RecoverPoint starts enabling
image access to the copy volumes. Wait for image access to be enabled and the system to
roll to the selected image before beginning testing. You know that image access is enabled
(in the Activity pane) by the image access status icon in the Completed (in RecoverPoint) task
list. When image access is enabled, perform the steps under the Next (at the copy host) task
list.
43
From the Start Failover screen, the state of both the production and the copy are shown.
Steps are given for actions to be completed at the copy host. Notice that image access is
enabled at the copy. This allows for testing of the selected image before failover actually
occurs. During image testing, all copy host writes are written to the image access log in the
copy journal - until image access is disabled. If the image access log becomes full, replication
is paused. At this point a new Image can be selected. The Production volume is still
accessible by a host. When Finish is selected, the failover process will start.
44
When Finish is selected, the wizard brings the user to the Manage Recovery Screen. To view
the current state of the failover, select the Show Activity Diagram to the right in the
Manage Recovery Screen. Notice here the copy that was used to failover to is displayed in
the role of Remote Source. The Journal used by this copy is erased. The former production
volume is now in the role of Target at Production with no access. Notice that data transfer
is only between the copy at Austin and the former production volume at Franklin. At this
point the user can fail back to the former production volume, or set the current Remote
Source as production.
45
The Manage Recovery screen is where you can monitor and manage your existing
Consistency Groups and their protection plans, control transfer, and mark consistent points
in time across groups and sets of groups.
When the Consistency Groups node is selected in the left pane, the list of all Consistency
Groups in the system is displayed in the right pane. The list of all Consistency Groups displays
the status of every Consistency Group in the RecoverPoint system.
Use this screen for monitoring all Consistency Groups.
To monitor the status of replication for a specific group select a group and click the Status tab
in the right pane.
46
This module covered Consistency Groups and their configuration and operations.
47
48
This module focuses on VPLEX Splitter Deployment and Management.
Copyright 2013 EMC Corporation. All Rights Reserved.
Module 5: RecoverPoint VPLEX Splitter Deployment and Management
This lesson provides an overview of the features, functionality, and operational function of
the VPLEX Splitter.
The VPLEX storage virtualization platform enables distributed data federation locally or
remotely across heterogeneous storage for both EMC and non-EMC block storage arrays.
VPLEXs AccessAnywhere technology can extend data over distance within and between
data centers.
There are multiple topologies available in the VPLEX family. VPLEX Local is designed for use in
a single data center. VPLEX Metro extends these benefits to multiple sites. You can
transparently relocate data and applications over distance, protect your datacenter against
disaster, and enable efficient collaboration between sites. These use cases are enabled by
VPLEXs distributed cache architecture, which allows both clusters to present the same
distributed volumes to servers in both sites.
VPLEX Geo adds the same support for data mobility and access over extended asynchronous
distances.
VPLEX natively supports a RecoverPoint splitter with GeoSynchrony 5.1 and above. The
Splitter is available for VPLEX Local and Metro. Customers who need Any Point in Time
Recovery protection for VPLEX Local and Metro can directly use VPLEX with RecoverPoint.
For existing or prospective customers of VPLEX, the VPLEX splitter offers a more simplistic
and easier to manage alternative to fabric-based splitters. RecoverPoint protects the VPLEX
platform for mobility, availability, and collaboration with any point-in-time business
continuity. It also supports easier access for disaster recovery via an asynchronous third site
across a mixture of EMC and non-EMC arrays.
The VPLEX splitter supports RecoverPoint Multi Site Topology. In addition, the RecoverPoint
VPLEX splitter supports virtualized and clustering environments.
In the case of the VPLEX write splitter, for simplicity, the host writes data to the volume
through the VPLEX splitter. The VPLEX Splitter sends it to the RecoverPoint Appliance (RPA)
and to the array cache.
The splitter waits for acknowledgment from both the local RPA and the array prior to
acknowledging the host in a CDP or asynchronous CRR configuration. In a synchronous CRR
configuration, the splitter waits for acknowledgment from both the remote RPA and the
array prior to acknowledging the host.
Both the array and RPA acknowledge to the splitter as soon as the I/O has been recorded and
mirrored internally for fault recovery.
RecoverPoint next enters the transfer and distribution process where, in brief, the write is
logged in the journal and written to the replica copy. Depending on the type of replication
protection, the data is sequenced, check-summed, compressed, and replicated. The data is
then received, decompressed, sequenced, and written to the journal. Finally, the data is
distributed write-order-consistently to the replica volumes.
RecoverPoint can be used to replicate VPLEX Local virtual volumes. This Continuous Data
Protection (CDP) refers to protecting local VPLEX virtual volumes, the production LUN, with
another VPLEX Local virtual volume, the copy.
RecoverPoint Continuous Remote Replication (CRR) provides bidirectional block-level

replication between two sites over Fibre Channel or a WAN. RecoverPoint supports up to 4
copies of the production LUN(s). Notice that there is not a VPLEX at the DR site.
RecoverPoint EX or CL can support any Array-based splitter at the DR site. This solution
allows the replication of virtual to physical volumes. This slide displays the copy at the nonVPLEX site, but the opposite could also be true. The copy could be a virtual volume and the
production a physical volume.
With VPLEX Metro high availability Continuous Data Protection (CDP), RecoverPoint can be
used to perform replication within the same local building. Local from a RecoverPoint
perspective refers to the Production and the copy being attached to the same RecoverPoint
Cluster.
RecoverPoint can only protect distributed VPLEX devices from one site of a VPLEX Metro: the
site where RecoverPoint is attached (via Fibre Channel). Each VPLEX consistency group that is
protected by RecoverPoint must have its site preference (winning site) set to the site where
the write splitting is taking place.
RecoverPoint CRR, which involves both local and remote copies of production, works
similarly to the CDP implementation in a VPLEX Metro environment. However, the remote
replication portion replicates virtual volumes to a third site. The third sites storage may or
may not be virtualized with VPLEX.
Module 5: RecoverPoint VPLEX Splitter Deployment and Management 10
Shown here is how RecoverPoint currently supports VPLEX Local and Metro topologies.
This lesson focuses on implementing the VPLEX Splitter.
The VPLEX Splitter can only be added to a RecoverPoint installation running version 3.5 or
above. The VPLEX Splitter is only native to VPLEX GeoSynchrony 5.1 and later.
RecoverPoint cannot enforce the selection of a supported repository volume type. This is
because the repository must be selected before the RecoverPoint system is running and able
to retrieve volume information from VPLEX. The user is therefore responsible for selecting a
supported repository volume.
For RecoverPoint management information to be available at both sites of a VPLEX Metro
installation:
There must be IP connectivity between the Metro sites.
RecoverPoint must be added to the VPLEX CLI at the non-RecoverPoint site of the VPLEX
Metro
In each fabric, create one zone that includes all RecoverPoint Fibre Channel ports and all
VPLEX front-end ports involved in RecoverPoint replication. Both VPLEX and RecoverPoint
must have at least one Fibre Channel port per fabric for each VPLEX director.
Once Zoned, the RPA initiators can be registered with VPLEX.

Log in to the VPLEX GUI. Select: Provision Storage > <cluster name> > Initiators.
The Initiator Properties dialog box appears. In the Initiator Name field, select an unregistered
RecoverPoint initiator. The port WWN will be preceded by the prefix UNREGISTERED
(Example: UNREGISTERED-0x5001248061931a3b).
Click Register (at the bottom of the display). You may assign a significant name to the port.
Set Host Type = recoverpoint.
Repeat until all RecoverPoint unregistered ports are registered.
In the VPLEX GUI, create a storage view for the RecoverPoint cluster. This will allow the RPAs
to see virtual volumes, which will include the Repository.
From the drop-down menu in the VPLEX GUI, select Provision Storage > <cluster name> >
Storage Views > Create Storage View.
Use the Create Storage View wizard to create the VPLEX Storage View that will be used for
the RecoverPoint RPAs. Name it to indicate that it contains RecoverPoint volumes.
Next, add to the RecoverPoint System storage view: 1) all RecoverPoint initiators, and 2) all
VPLEX front-end ports used by the RecoverPoint VPLEX Virtual Volumes that will be used by
RecoverPoint. This includes the repository, journal, and replication volumes. Make sure that
the repository is exposed only to RecoverPoint, and not to any host server.
A best practice is to use certificates to avoid user configuration errors. To do so, the
RecoverPoint certificate is imported into VPLEX, and the VPLEX certificate is imported into
RecoverPoint. Without the certificates, VPLEX and RecoverPoint cannot obtain management,
installation, and integration information about volume types.
With the certificates, VPLEX and RecoverPoint will not display unsupported options in their
GUI, and the user therefore cannot select them inadvertently. For instance, distributed
volumes will not appear in the RecoverPoint Add Journal Volume dialog box, because
distributed volumes are not supported for journals.
Adding a RecoverPoint cluster to a VPLEX cluster is done using a VPLEX CLI command. In a
Metro configuration, perform this procedure in both clusters. Log in to the VPLEX CLI. Add
the RecoverPoint cluster or clusters.
Create a zone for each VPLEX back-end port. Add all RecoverPoint Fibre Channel ports to the
zone of each VPLEX back-end port. A VPLEX back-end port should never be in the same zone
with VPLEX front-end ports.
Create VPLEX Consistency Groups for RecoverPoint replication and journal volumes. For
replication volumes, Local virtual volumes and distributed virtual volumes should be in
separate Consistency Groups. If local copy volumes reside on the same VPLEX cluster as
production volumes, they must be in a separate VPLEX consistency group from the
production volumes.
A single VPLEX consistency group for journal volumes and the repository is allowed. Both
the Production and copy journals may be in the same VPLEX consistency group.
For each consistency group created, click the consistency group name. The Consistency
Group Properties dialog appears. Check the RecoverPoint-enabled checkbox.
Validate the VPLEX RecoverPoint configuration using the displayed VPLEX CLI command.
There may be errors if, when RPAs are zoned to VPLEX, 2 RPA ports are zoned to VPLEX frontend ports, and 2 RPA ports are zoned to VPLEX back-end ports. This command issues a
warning. The system checks that all 4 ports on the RPA are zoned to both VPLEX front-end
and back-end ports.
The best practice is to zone every RPA port to both VPLEX front-end and back-end ports.
Administrators who have purposely configured single-channel mode can safely ignore the
warning.
Splitters already configured on arrays before installing RecoverPoint will automatically be

added to the RecoverPoint system. If a storage array is added to the RecoverPoint system
after deployment, the splitter will need to be added to the system. To do this, use the
RecoverPoint management application, Unisphere for RecoverPoint, to add the VPLEX
splitter.
At the Unisphere for RecoverPoint GUI, select the RPA Clusters tab, select Splitters, and click
the Add button. Click the Credentials button to specify credentials and to add a certificate.
Shown here is an example of a certificate.
This module presented an overview of the VPLEX Splitter for RecoverPoint. It covered
implementation of the splitter as well as use cases.
This module focuses on RecoverPoint cluster maintenance.
Module 6: RecoverPoint Cluster Maintenance
This lesson covers adding RPAs to a cluster.
Deployment Manager will allow the addition of RPAs, physical or virtual, to an existing
cluster. The RPAs can be added without the disruption of ongoing replication. Consistency
groups can then be distributed to the new RPAs to better balance the replication workload.
A list of prerequisites are displayed prior to continuing. These must be met before starting
the Wizard. A key prerequisite that is often overlooked is the storage of the new RPA.
Zoning and LUN masking should be identical to the existing RPAs in the cluster.
Create a Configuration file. This can be renamed from the default name. As with other
Wizards, the file can be used over again.
Enter the cluster information for the cluster that you are adding RPAs to. Complete the
wizard by entering the passwords for the boxmgmt and admin user accounts.
Enter the number of RPAs to add to the cluster. A cluster can have between 2 to 8 RPAs.
Displayed onscreen is the existing cluster name, the number of existing RPAs at the cluster,
and the number of RPAs that you plan to add to the cluster.
This screen allows you to review the cluster IP configurations and set the new RPA IP
settings.
Cluster management LAN, based on IP type of the cluster, is displayed. This is an IP
address that is used to configure the RPA cluster. The IP address is assigned to the RPA that is
currently running the active instance of the cluster management.
Interface netmask LAN and WAN, based on IP type of the cluster, are displayed.
IP addresses of the existing RPAs of the cluster are displayed, based on IP type of the cluster.
IP addresses of the new RPAs of the cluster must be entered, based on the IP type of the
cluster.
Default gateway Based on IP type entered when the cluster was installed.
Click Add route to add additional gateways.
This screen defines the RPA cluster iSCSI settings. Based on the previous installation, the
CHAP secret for the VNX iSCSI ports can be defined. This should match the existing
configuration.
The next screen allows the setting of an additional gateway for the new RPA(s)
The system communicates and validates the status of the new RPAs and confirms that all
components are OK, or that errors are detected.
If errors are detected for an RPA, a comment will appear describing the problem. To proceed
to the next step in the wizard, you must resolve all errors. Once errors are resolved, click
Retry to revalidate the communication statuses.
When all statuses appear OK (green check mark), click Next.
The current storage CHAP and iSCSI IP configurations are displayed. Modify the values you
want to change.
10
When adding an RPA to an existing RP/SE cluster, the login credentials for the VNX attached
must be supplied.
11
Zoning to the VNX should match the existing RPAs. For a review of the automatic and semiautomatic methods of zoning, refer to Module 2: RecoverPoint/SE Installation.
12
The system displays the port numbers, port WWNs, and node WWNs of each RPA at the
cluster. Use this information to zone and mask LUNs for the RPAs.
The Zoning and LUN masking for the new RPA should match the existing cluster. Once this is
accomplished, click next and SAN diagnostics will run.
13
The system performs SAN diagnostics for the cluster, attempting to validate that the current
the current SAN environment.
The system will present the following results: Severity, RPA, Message ID, Category, and
Description.
The system will confirm that all components are OK and that no errors exist. If errors are
detected for an RPA, a description of the error will appear.
To proceed to the next step in the wizard, you must resolve all errors. Once errors are
resolved, click Refresh to rerun the SAN diagnostics process.
14
When the configuration is applied to each RPA, a green check will be displayed. If an error
occurred to one or more RPAs, it will be displayed, and Retry can be used to apply the
settings again.
15
During this stage of the wizard, the system will:

Register RPAs initiators on the array (only relevant for a RecoverPoint/SE 3.3 SP1 and
later environment).
Prepare to add the new RPAs to the clusters.
Apply the new settings to all the RPAs in the clusters.
Finish installation of the new RPAs.
Finish adding the new RPAs.
Verify the system state is OK.
Once you have completed adding RPAs to the existing RPA clusters, you can redistribute
existing Consistency Groups to the new RPAs, or create new Consistency Groups and assign
the new RPAs as the preferred RPAs.
16
This lesson covers cluster type conversion.
17
Converting a RP/SE cluster to RP/CL or RP/EX will allow the use of additional features. Multisite connections, along with more than a single array for a cluster are some examples.
To convert a RP/SE cluster, the displayed prerequisites must be met. After completion of the
Deployment Manager Wizard, a new license(s) must be added to use the new features.
18
The Converter Wizard helps you non-disruptively convert an environment to a

RecoverPoint/SE or RecoverPoint (RecoverPoint/CL and RecoverPoint/EX) configuration from
a single management point. The conversion is done without replication downtime, full
sweep, or journal loss. Once completing the wizard, you will be able to continue using the
RecoverPoint Management Application GUI and CLI.
Select the converter you want to use. We will focus on converting to RecoverPoint/CL or EX.
19
Before continuing, ensure the displayed conditions are met on the RecoverPoint/SE
environment you are converting.
20
Enter the RecoverPoint cluster management IP address and login credentials to connect to
the cluster.
21
Review the results of the RecoverPoint connectivity test. The system communicates and
validates the statuses of the RPAs and confirms that all components are OK, or that errors
are detected.
The system presents the following results: Status, RPA, Cluster name, RPA LAN IP address,
RPA hardware platform, RecoverPoint release, and Comment (if applicable).
If errors are detected for an RPA, a comment will appear describing the problem. To proceed
to the next step in the wizard, you must resolve all errors. Once errors are resolved, click
Retry to revalidate the communication statuses. When all statuses appear OK (green check
mark), click Next to continue.
22
The system performs SAN diagnostics for the site, attempting to validate that the current
the current SAN environment.
The system will present the following results: Severity, RPA, Message ID, Category, and
Description. The system will confirm that all components are OK and that no errors exist. If
errors are detected for an RPA, a description of the error will appear. To proceed to the next
step in the wizard, you must resolve all errors. Once errors are resolved, click Refresh to
rerun the SAN diagnostics process.
It is highly recommended to resolve all SAN discovery warnings. However, the system will
allow you to ignore them and continue the installation.
23
During this stage of the wizard the system will:

Prepare the system for conversion
Convert RPAs
Finish the system conversion
Verify that the system was converted
During this stage, the system goes into maintenance mode. While in this mode, the
RecoverPoint Management Application becomes read-only. The GUI can only be used to
monitor the system, and modifications cannot be made. Once conversion is completed,
RecoverPoint exits maintenance mode and automatically performs SAN diagnostics.
Progress bars indicate that the system is applying settings and completing the installation.
Once the progress bars stop, the system will confirm that all components are OK, or that
errors are detected.
24
The wizard indicates when you have completed conversion of the environment. A warning is
given that the RecoverPoint license needs to be upgraded.
25
After connecting to Unisphere for RecoverPoint, an error is displayed. In our example a

conversion form RP/SE to RP/EX was just completed. The system at this point only has a
RP/SE license. A new RP/EX or CL license must be added. Because RecoverPoint/EX licenses
cannot be added if a RecoverPoint/SE license already exists, the SE license must be removed
first. Then the EX or CL license can be added.
For further information, refer to the Managing RecoverPoint licenses section of the EMC
RecoverPoint Administrators Guide.
26
When selected, the Convert to RecoverPoint/SE wizard will launch.
27
Before continuing, ensure the displayed conditions are met on the RecoverPoint
environment you are converting. The remaining steps are the same as the previously shown
conversion.
28
When a RecoverPoint/SE is installed using Deployment Manager (supported procedure), the

wizard connects into the CLARiiON/VNX array and changes the RPA initiator registration. This
is used by Unisphere to connect and manage the RecoverPoint cluster.
After a conversion process to RecoverPoint/SE, look for changes in the RPA registration in the
CLARiiON/VNX array. Never change the RPA registration, as doing so breaks the integration
between Unisphere and RecoverPoint/SE.
29
This lesson covers cluster modification.
30
The Modification Wizard helps you non-disruptively modify the settings of a RecoverPoint/SE
or RecoverPoint (RecoverPoint/CL and RecoverPoint/EX) system from a single management
point. The procedure is done without replication downtime, full sweep, or journal loss. While
completing the wizard, you will be able to continue using the RecoverPoint Management
Application.
31
Before continuing, ensure the displayed conditions are met in your environment. Select the I
have fulfilled the conditions for modifying the system settings checkbox, and click Next to
continue.
32
Enter the RecoverPoint cluster management IP address and login credentials to connect to
the cluster.
33
After defining a configuration file, new or existing, the Wizard displays the Environment
settings screen.
The current environment settings of the cluster are displayed. Modify the values that need to
be changed.
34
The current cluster IP configurations and RPA IP settings are displayed. Modify the values
that need to be changed.
35
The current RPA cluster iSCSI settings are displayed. Modify the values you want to change.
36
This screen will only appear if your RPA cluster is composed of virtual RPAs (vRPAs).
The current cluster iSCSI IP configurations and RPA iSCSI IP settings are displayed. Modify the
values you want to change.
Only the Default gateway and additional routes can be modified.
Click Add route to add additional gateways.
37
This screen will only appear if your RPA cluster is composed of virtual RPAs (vRPAs).
The current storage CHAP and iSCSI IP configurations are displayed. Modify the values you
want to change.
The CHAP user and password can be modified, along with additional iSCSI ports.
38
Once you have completed modifying the system settings of the cluster, you can start using
the RecoverPoint Management Application.
39
This module covered RecoverPoint cluster maintenance.
40
41
42
This module focuses on troubleshooting RecoverPoint installations.
Module 7: Troubleshooting RecoverPoint Installation
This lesson covers the tools available to troubleshoot RecoverPoint network issues and how
to use them.
The Installation Manager provides a large number of tools used to modify RPA installation
parameters and to test and diagnose RPA settings and connectivity. Login as user boxmgmt
using SSH. Select Fibre Channel diagnostics from the Diagnostics menu. The SAN diagnostics
menu then appears.
When you select Run SAN diagnostics, the system conducts a series of automatic tests that
are designed to identify a variety of the most common problems encountered in the
configuration of SAN environments. Upon completion of these tests, a message appears
confirming successful completion of the SAN diagnostics, or a report is provided detailing any
critical configuration problems.
The View RPA Ports option from the SAN diagnostics menu can be used to determine the
WWN of the RPA FC ports. Other information about the FC ports, like the FCID, are also
displayed.
If yes is answered to view remote ports, a list of all devices zoned to each RPA port is
displayed. This list can be used to verify zoning to the storage ports and to the other RPAs in
the cluster.
When you select View target LUNs, a list appears of all volumes on the SAN that are
visible to the RPA. The list identifies each LUN by vendor, product and UID. The UID is
universal and often used by other management software to ID storage. The LUNs seen from
this menu are for this individual RPA only.
Remember that all RPAs must see the same volumes. These include the repository (unique
for each local cluster), journals, and host volumes involved in replication.
Select IP diagnostics from the Diagnostics menu; the IP diagnostics menu appears. From here
several tools can be used to diagnose IP networks issues.
If you select Site connectivity tests, a menu appears that allows you to select the site youd
like to test for connectivity. The menu allows you to choose Gateway, Primary DNS server,
Secondary DNS server, and NTP server. The test returns a result of success or failure. It uses
ping to check connectivity.
When selecting the Other host option, any target IP address can be tested. The test returns
the relative success (0100%) over both the management and WAN interfaces. There is no
way to check over just one interface.
When you select View IP details, the system displays the output of running an ifconfig
process.
When you select View routing table, the system displays the routing table.
10
When you select the Test throughput, the system uses iperf to test throughput to another
RPA. For a single site, the Test throughput option does not appear.
If successful, the system responds with a standard iperf output.
11
Use the Ports diagnostics option to verify that none of the ports used by the RPAs are
blocked (for instance, by a firewall). You must test each RPA individually; that is, designate
each RPA in turn to be the server.
Please refer to EMC RecoverPoint Security Configuration Guide for the list of RPA ports that
must be open.
12
When you select System connectivity, the System Connectivity menu appears. The menu options
allow you to test and generate reports on connections between RPAs anywhere in the system. The
tests can be performed any time, either during installation or during normal operation. The following
connection tests are performed:
ping
TCP:
To ports and IP addresses
To the specific processes of the RPA
Using secure shell (SSH)
UDP (general and to RPA processes)
RecoverPoint internal protocols
The following test options are available:
-System connectivity test:
Full mesh network check Reports communication errors from any RPA to any other RPA in
the system.
Check from local RPA to all other boxes Reports errors from the local RPA to any other RPA
in the system.
-Advanced connectivity test Reports on the connection from a specific IP address that you specify
on the local RecoverPoint Appliance to an IP address and port that you specify on an RPA anywhere
in the system. Use this option to diagnose a problem specific to the local IP address or port.
-Show all results from last connectivity check Reports all results from the previous test, including
errors and tests results that were completed successfully. The port on which each error or failure
occurred is shown.
13
Available in RecoverPoint 3.4 and above, the Configure ETH auto-negotiation option is used
to adjust the Ethernet speed (in Mb) of an RPAs WAN and LAN interface. The Ethernet speed
(in Mb/s) of an RPAs WAN and LAN interface can be modified to ensure that the
management traffic does not exceed a certain transmission rate.
Log in to each RPA to enable, disable, and change the auto-negotiation values. Valid values
are 10 Mb Full Duplex or 100 Mb Full Duplex. The values must be the same on all RPAs in the
environment.
14
This lesson covers the possible performance issues when deploying a RecoverPoint solution.
15
Consistency group initialization may be slowed by several factors. If multiple groups have
been disabled for a period of time, initialization may take an extended period to complete.
As your environment grows and changes over time, initialization and replication performance
may change.
When evaluating a potential performance issue, examine the complete environment. Is the
change sudden or has it changed gradually? Consider what applications, systems, network,
and storage changes have been made since RPO calculations were first performed.
Remember that Consistency Group policies can have an impact on performance. The best
practice is to evaluate performance regularly, and each time changes are made that may
impact the RecoverPoint environment.
16
The RecoverPoint environment has three potential bottlenecks that can limit the amount of
write I/O the system can sustain: WAN pipe between sites; remote storage performance;
appliance performance. The system sustains the load dictated by the weakest link. If the
system cannot sustain the load, it goes into high load, during which it keeps tracking the I/O
with marking. Occasional high load events are not problematic. The environment should be
sized for the average I/O load, not the peaks. However, if the average has changed over time,
you may encounter more frequent high load events, or longer-duration high load events.
17
As performance issues appear, it is very possible that bottlenecks are present somewhere in
the infrastructure.
The detect_bottlenecks CLI command introduces automatic system performance
analysis and recommendations. This feature returns extensive statistics about RecoverPoint
system performance, by group, RPA ("box"), and site. The quantity and type of statistics
depend on the filters specified in the CLI detect_bottlenecks command. You must log into
the site management IP address (floating IP) as admin to run detect_bottlenecks.
The standard output includes the following set of statistics:
WAN throughput
Total incoming data rate
Initialization (synchronization) output rate
CPU utilization
Compression ratio
Percentage of time in transfer (group only)
Percentage of time in initialization (group only)
More detailed statistics are used primarily by EMC Customer Service, for analysis of system
performance and problems. For more information on the types of statistics and filters
available, refer to the RecoverPoint CLI Reference Guide.
More important for the normal user, this feature analyzes the system data in an effort to
detect the existence of any of a set of predefined problem types, called "bottlenecks".
18
The get_system_statistics command prints system performance statistics.

Information is displayed for each site in the RecoverPoint installation. For each appliance, the
following information is displayed:
SAN traffic handled by the site or RPA

WAN traffic generated by the site or RPA
Compression ratio between the input and output for the site or RPA
RPA CPU usage
WAN latency to the peer RPA
Packet loss experienced over the WAN to the peer RPA
Notes on usage:
Statistics for both sites will be displayed if no site is specified.

The 'box' parameter can take the values 'all', 'none' or a list of RPAs separated by ','.
Detailed box statistics will be displayed when the 'box' parameter takes a value other
than none.
Note that if only the box parameter is supplied a value, statistics for the selected
RPA(s) will be displayed for both sites.
19
If you select the Run internal command option from the System internal operations
menu, the list of available internal commands appears. These commands are for use by EMC
Customer Service. Do not use these options unless specifically instructed to do so by EMC
Customer Service.
The available options are:
ping standard Linux command

top standard Linux command showing processor utilization
Switch_utils For use by EMC Customer Service only
netstat standard Linux command
telnet standard Linux command

ethtool standard Linux command
ssh standard Linux command
Appliance config params For use only by EMC Customer Service. Do not use these
options.
Warning: Do not change appliance parameters unless explicitly instructed to do so by EMC

Customer Service. Changing appliance parameters without an in-depth understanding of
possible consequences is likely to cause the appliance to fail.
20
The top command shows system uptime, load average, memory utilization, running
processes at top of CPU time. This command is very useful for monitoring ahead of issues.
21
With the netstat command, you can get real-time network connections/sockets
You can review the IP configuration of the RPA and validate the settings against the network
for routing misconfigurations.
The use of the an switch allows you to verify the ports in use and check if they are active.
22
This command gathers data about configured Ethernet ports. This is helpful when you
suspect a configuration problem with the adapters or with the network settings of switches
and routers.
23
The new I/O throttling mechanism enables users to limit the storage read-rate during
initialization, allowing the production storage to handle the I/O rate. When enabled, the
read-rate of all RPAs in your RecoverPoint cluster is limited to 200 (low) / 50 (high) MBps, per
storage array. I/O throttling is disabled by default and can be enabled using the
config_io_throttling RecoverPoint CLI command.
Before 3.4 we could throttle this by stipulating a max_rate read capability on a MB/s basis,
limiting the storage read-rate of RPAs in a RecoverPoint cluster. This allows the storage to
handle the I/O rate during initialization.
The read-rate of a single RPA will be limited to 10 or 200 MB/s (depending on the throttling
level value defined by the user) divided by the number of RPAs in the cluster.
Set the throttling level to low to limit the data parallelism and I/O parallelism of all RPAs in a
RecoverPoint cluster to a maximum read-rate of 200 MB/s.
Set the throttling level to high to limit the data parallelism and I/O parallelism of all RPAs in a
RecoverPoint cluster to a maximum read-rate of 10 MB/s.
I/O throttling is configured separately for each RecoverPoint cluster.
When setting the throttling level, remember that the higher the throttling level, the longer
initializations will take. Ensure that a low throttling level is insufficient before setting the
throttling level to high.
When I/O throttling is enabled, initializations take longer to complete.
To verify whether I/O throttling is enabled, run the config_io_throttling command
through the RecoverPoint CLI with a throttling parameter and no parameter value. The
current state of the throttling mechanism is displayed.
24
The get_system_status CLI command summarizes the errors and warnings for either one site
or the entire RecoverPoint system. By default, detailed status is given, but you can also
choose summarized output.
25
Root Cause Notification
When the state of the system becomes unstable, a root cause analysis is started.
The root cause analysis continues until the system state stabilizes (in OK, ERROR, or
other state) and a full analysis of all events between the two stable points is
performed.
An Intermediate report is given in set intervals of time if the system has not
stabilized and is still waiting to finish the root cause analysis.
Some events that could cause Root Cause Analysis to kick in are:
LUN goes into error

Storage Disaster
Several High Loads
WAN Bottleneck
26
The get_box_states command also displays RPA hardware platform information.
27
By default, RecoverPoint contains the major statistics for each Cluster:
WAN throughput
Total incoming data rate
Initialization (synchronization) output rate
CPU utilization
Compression ratio
Optionally, provides more detailed statistics:
For every box

For every group, including
Percentage of time in transfer
Percentage of time in initialization
28
The feature is activated by the export_statistics command in the CLI, which offers the
filtering parameters: from, to, include_global_statistics, site, RPA, group, categories,
frequency, and file. The standard output (as listed above) is produced when the categories
parameter is set to the value, OVERVIEW. This command writes unprocessed system
statistics, according to the specified filters, to a file system that is ordered hierarchically by
site, RPA, and Consistency Group. In addition, it produces a CSV file that can be imported to
spreadsheet programs such as Excel, where it can be used to create graphs of system
behavior over the specified time period.
Your EMC Customer Service representative will instruct you in how to use these parameters
to filter the information that is returned by the command. More detailed statistics are used
primarily by EMC Customer Service, for remote analysis of system performance and
problems.
Note: This command must be run from site management.
29
This lesson covers the support options offered by EMC for RecoverPoint.
30
Using Unisphere for RecoverPoint allows links to online help and documentation. By
selecting the support icon, links to support.emc.com are displayed. Also displayed is a link to
the RecoverPoint Community on EMC One.
31
Use Configure System Notifications to set up the RecoverPoint system reports mechanism
(SyR) and provide one-way communication between a RecoverPoint installation and the EMC
System Reports database (ESRS).
System notifications consist of two types of information: system alerts and system
configuration reports. System alerts are sent in real-time (at the time that the events occur),
allowing EMC to provide pre-emptive support for RecoverPoint issues. System reports on the
configuration and state of the RecoverPoint system are sent every Sunday. Unless there are
connectivity issues between RPA clusters, or an RPA cluster in the RecoverPoint system
cannot send system reports, only one system report is sent at a time Each report contains
the information of all RPA clusters. In this case, the problematic RPA cluster will send its own
system report.
32
System notifications will only be sent provided the method of transfer (SMTP, ESRS, or FTPS)
is configured in Unisphere for RecoverPoint or the RecoverPoint CLI.
To transfer system notifications using SMTP or ESRS, ensure that port 25 is open and
available for SMTP traffic.
To transfer system notifications using FTPS, ensure that ports 990 and 989 are open and
available for FTPS traffic.
A permanent RecoverPoint license must exist in the system; system notifications will not
work with a temporary license
To ensure that system notifications can be sent using the configured transfer method, click
Test Connectivity.
In the dialog box that is displayed, enter the email address to which EMC Customer Support
can send a verification email.
33
A proactive online service capability has been built into RPAs to enable RPAs to continuously
monitor their own health and the health of the RecoverPoint system. If a serious problem
arises, the call home event mechanism automatically opens a service request with EMC
Customer Service, enabling them to proactively engage the relevant EMC personnel, start
working with the relevant customer parties, or use a configured ESRS gateway, to resolve the
issue as soon as possible.
The purpose is to generate a meaningful "call home" error event to SyR which will trigger
the opening of a new service request. These call home events are defined by rules written
and approved by support.
34
This lesson covers using System Analysis Tools to troubleshoot installations.
35
Use Admin > System Analysis Tools > Collect System Information to retrieve system log files
and environment information for support purposes. The past thirty days of system
information can be collected from RPAs and splitters to analyze and resolve support cases.
36
Before you begin, note that in order to collect system information for VNX and VPLEX
splitters, you must first define splitter credentials.
If this is your first time collecting system information, click Start. Otherwise, click Start New
Collection Process.
Configure the collection process by entering the desired values. Refer to the RecoverPoint
Administrators Guide for exact details for each value.
Select Test Connectivity to continue.
37
In the Test Connectivity screen, review the displayed information to verify that your
configuration settings are correct, and that the system can access all RPAs and splitters.
Verify that the Collection Settings are configured as intended. If required, click Back to
Define Settings to edit your settings.
Verify that a green check mark exists in the Status column of all listed splitters and RPAs, and
that the text Action succeeded exists in the Details column of all listed splitters and RPAs.
Select Finish to start the collection.
38
Upon completion of the collection process, the output file is placed in: http://[RPA IP
address]/info or https://[RPA IP address]/info.
Use the webdownload user to open and save the files.
39
After entering the password for the webdownload user, the .TAR file is available to be
downloaded and extracted.
40
To start the wizard, use Admin > System Analysis Tools > Balance Load to analyze the load on
each RPA and display a load balancing strategy.
Load balancing is the process of assigning preferred RPAs to Consistency Groups. Assigning a
preferred RPA to a Consistency Group dictates which RPA to prefer when transferring data
for a specific group. During a groups creation, a preferred RPA is assigned to each new
group. Each group will always run on its preferred RPA, unless an RPA disaster occurs. If an
RPA disaster occurs, the group will flip over to another (non-preferred) RPA, and then back as
soon as possible. Flipover (also known as switchover) can cause high loads on RPAs, and
these loads should be balanced. In other words, groups must be moved from RPA to RPA
every once in awhile to re-arrange the load.
RecoverPoints load balancing tool automates the following tasks:
Analyzing of the performance of a specified set or all Consistency Groups in the system
over a substantial period of time, and displaying a recommended load balancing strategy
based on historical performance statistics.
Saving the recommended load balancing strategy (containing the current traffic
performance statistics) of any or all of the Consistency Groups in the system, at a
particular point-in-time.
41
When the analysis is complete, click Display Results; the load balancing recommendation are
displayed.
A normal scope event is logged, indicating that the load balancing process has ended. The
event contains a copy of the load balancing recommendation output.
One or more of the following load balancing recommendations are displayed:
No action is necessary - The environment is stable, and groups are evenly distributed
across all RPAs.
Action is necessary - The environment is not stable because groups are not evenly
distributed across all RPAs. To correct this, manually modify the Preferred RPA of each
group.
Action may be necessary The environment is stable, although groups are not evenly
distributed across all RPAs, and this may affect future performance. To distribute groups
evenly across all RPAs, manually modify the Preferred RPA of each group.
42
Bottleneck detection returns statistics about RecoverPoint system performance by group, by

RPA, and by cluster.
The standard output includes the following set of statistics:
WAN (or Fibre Channel) throughput
Incoming data rate
Output data rate
Compression CPU utilization
Percentage of time in transfer
Percentage of time in initialization
Lag (RPO) during transfer
RPA utilization
Link utilization
Line latency
Packet loss
The quantity and type of statistics depends on the detection mode.
Use Admin > System Analysis Tools > Detect Bottlenecks to display statistics about system
performance by group, RPA, or RPA cluster, and use the statistics to identify and mitigate
bottlenecks in transfer. Enter the required setting values.
43
When the progress bar reaches 100%, click Display Results. The bottleneck detection results
are displayed.
Copy the results and paste them into a text file. Save the text file for later reference.
44
This lesson covers EMC Support for RecoverPoint.
45
To obtain documentation, such as release notes, admin guides and white papers, use
support.emc.com. There are several methods to search for the documents for different
products. One way is to search by product. From here, the search can be narrowed even
further to look for a certain type of documentation.
46
Support.emc.com is also the source of all product files for RecoverPoint. Downloadable files
include: device drivers, iso images, and deployment manager. Also located here is the VM
image file for vRPAs.
47
Looking for RecoverPoint hands-on experience? Go to http://education.emc.com and look for

the ESV-Lab link. There is RecoverPoint equipment available for individuals who have
completed an official training and want to get more hands-on practice.
48
This is one of the RecoverPoint virtual labs available. Field personnel can deploy RPAs from
scratch, implement any type of splitter desired, and get prepared for a customer
implementation. This all may be done through the EMC network.
49
Finally, the RecoverPoint Community on EMC ONE is a live open discussion among experts
who are involved with RecoverPoint on a daily-basis and can help others in their activities.
Various documents and other resources can be found here.
50
This module covered troubleshooting aids to be used for RecoverPoint.
51
52
This course covered RecoverPoint Installation and Operations, including the topics listed
here.
53
54

RecoverPoint Implementation Student Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RecoverPoint Implementation Student Guide

Uploaded by

Copyright:

Available Formats

RecoverPoint Implementation

Welcome to RecoverPoint Implementation.

Revision Date: 07/25/2013

Copyright 2013 EMC Corporation. All rights reserved

Course Introduction: RecoverPoint System Deployment

This course covers RecoverPoint Installation and Operations.

Copyright 2013 EMC Corporation. All rights reserved

Course Introduction: RecoverPoint System Deployment

Copyright 2013 EMC Corporation. All rights reserved

Course Introduction: RecoverPoint System Deployment

Copyright 2013 EMC Corporation. All rights reserved

Course Introduction: RecoverPoint System Deployment

Copyright 2013 EMC Corporation. All rights reserved

Course Introduction: RecoverPoint System Deployment

Copyright 2013 EMC Corporation. All rights reserved

Course Introduction: RecoverPoint System Deployment

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

This lesson covers RecoverPoint solutions.

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

EMC RecoverPoint is an out-of-band solution which offers advanced capabilities to deliver

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Lets take a look at how EMC RecoverPoint addresses customers challenges.

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

The RecoverPoint/SE system supports VNX/CLARiiON storage arrays when using

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

The following splitters are supported:

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

EMC RecoverPoint/CL provides block-level replication for on-demand protection and

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

The following limitations apply to copies:

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved

Module 1: RecoverPoint Overview

Copyright 2013 EMC Corporation. All rights reserved