Disaster Recovery Using RecoverPoint

OPERATIONAL & DISASTER
RECOVERY USING
RECOVERPOINT
Operational & Disaster Recovery using RecoverPoint
Table of Contents
Introduction.................................................................................................................................................. 3
Business Challenge..........................................................................................................................................4
Solution ...........................................................................................................................................................5
Key Components........................................................................................................................................... 6
Ease of Integration, Comprehensive Features ...................................................................................................7
Lab Overview ................................................................................................................................................ 8

Lab Environment ..............................................................................................................................................9
Labs...............................................................................................................................................................10
Lab 1 - Introduction to Unisphere for RecoverPoint...................................................................................... 11

Lab Prerequisite ............................................................................................................................................12
Lab Scenario ..................................................................................................................................................13
Browse Unisphere for RecoverPoint ...............................................................................................................14
Protect Volumes.............................................................................................................................................33
Lab 2 - Operational Recovery using RecoverPoint ........................................................................................ 54

Lab Scenario ..................................................................................................................................................55
RecoverPoint Protecting the Organization Against Data Loss and Site Failure..................................................56
Lab 3 - Disaster Recovery using RecoverPoint with VMware Site Recovery Manager ..................................... 97
Lab Scenario ..................................................................................................................................................98
RecoverPoint Protecting the Organization Against Data Corruption using VMWARE Site Recovery Manager
(SRM).............................................................................................................................................................99
Conclusion ............................................................................................................................................... 170

Conclusion...................................................................................................................................................171
Introduction
Page 3
Business Challenge
Todays IT challenges can be summarized into four simple categories: Any application, any array at any
location and at any time.
Any Application
Reduce backup-windows from hours to minutes and saves on storage space

Increase performance
Lowest recovery objective while testing and running DR processes
Speed applications backup with RecoverPoints bandwidth reduction, data compression, and
deduplication technologies
Any Array
Application consistency between multiple arrays and multiple applications
Not only does RecoverPoint protect data, it does it for any vendors storage
Any Location RecoverPoint Multi-Site
Support multi-site redundancy needs
Synchronous & asynchronous continuous local/remote replication
Up to 90% bandwidth reduction with data compression, deduplication technologies, and
synchronously over IP
Any Time
Few and inflexible ways to access data from a previous point
Instant data access to earlier version of your data from different points in time
Page 4
Solution
This solution provides the following:
Point-In-Time Recovery
RecoverPoint provides continuous data protection with multiple recovery points to restore
applications instantly to a specific point in time.
Continuous Replication
Protected applications with bidirectional synchronous and asynchronous replication in a physical
virtual and cloud infrastructures.
Simplified Testing
Streamline disaster recovery testing of your application environment while production replication
continues unaffected.
RecoverPoint integrates with vCenter Server to allow the RecoverPoint administrator to quickly view virtual
machines fully protected by RecoverPoint, and to see which of the virtual machines LUNs/data stores are
not protected. Additionally, RecoverPoint is integrated with VMware Site Recovery Manager (SRM) to simplify
and automate disaster recovery failover and failback in VMware Infrastructure.
VMware vCenter SRM automates the recovery process so it becomes as simple as pressing a single button.
There is no need for you to interact with the RecoverPoint console and the VMware console: instead VMware
automates the process. All you have to do is ensure that the production virtual machines are mapped to
LUNs that are replicated by RecoverPoint to the remote site.
Page 5
Key Components
Page 6
Ease of Integration, Comprehensive Features

RecoverPoint Overview
EMC RecoverPoint is a comprehensive data protection solution that provides integrated CRR and CDP, with bidirectional synchronous and asynchronous replication. RecoverPoint offers Fan-out where the same data can be
protected to up-to 4 remote locations hence enabling businesses to achieve regulatory compliance and flexibility with
various operational scenarios. RecoverPoint offers 4:1 Fan-in as well, where various data can be protected back to a
centralized Disaster Recovery site. RecoverPoint allows users to recover applications Locally or Remotely to any point
in time without impact to the production application or to ongoing replication.
RecoverPoint offers heterogeneous replication with bandwidth efficiencies in IP or Fiber Channel synchronous or
asynchronous replication environments, which lowers your multi-year total cost of ownership. RecoverPoint CDP
enables you to roll back to any point in time for effective local recovery from events such as database corruption.
RecoverPoint integrates with VMWARE Site Recovery Manager and enables point-in-time granularity for SRM
environments through the use of it Virtual Storage Integrator (VSI).
RecoverPoint is appliance-based, and it comes in a physical form or a virtual form (Virtual Machine) which enables it to
better integrate in various environments and protect information stored across heterogeneous servers and storage
environments.
RecoverPoint uses lightweight splitting technology in the Symmetrix VMAX, Clariion VNX , and VPLEX to mirror a write
to a RecoverPoint appliance that resides outside of the primary data path. Implementing this approach enables
RecoverPoint to deliver continuous replication without impacting an applications I/O operations.
Page 7
Lab Overview
Page 8
Lab Environment
The environment for this lab includes the following:
2 VNX Array
1 Domain Controller
2 Virtual Center Servers
2 Esx Hosts
4 virtual RecoverPoint Appliances
Terminology
Page 9
Labs
Lab 1 - Introduction to Unisphere for RecoverPoint
Browsing Unisphere for RecoverPoiint
Protecting Volumes
Lab 2 - Operational Recovery using Recoverpoint
RecoverPoint protecting the ogranization against data loss and site failure
Lab 3 - Disaster Recovery usign RecoverPoint with VMware Site Recovery Manager (SRM)
RecoverPoint Protecting the Organization Against Data Corruption using VMWARE Site Recovery
Manager (SRM)
Page 10
Lab 1 - Introduction to Unisphere for

RecoverPoint
Page 11
Lab Prerequisite
As this is a fully virtualized solution this offering should be provisioned at least 2 hours in advance of test/
presentation time to allow all components sufficient time to boot and initialize.
Page 12
Lab Scenario
RainPole management has decided to protect a new application and has asked you to setup Local and
Remote replication. Given the criticality of the application and since it is your first time using the
RecoverPoint system, you've decided to log-in to the Unisphere for RecoverPoint and get familiar with the
environment. You then proceed to setup protection for the required volumes. Once Replication has been
setup, you report back to management that the critical database has been protected.
In this lab you will do the following :
Browse Unisphere for RecoverPoint.
Protect Volumes - Create and work with Consistency Groups
Page 13
Browse Unisphere for RecoverPoint

Login to Unisphere for RecoverPoint
Locate Shortcut to Unisphere for RecoverPoint. If unable to locate shortcut, open a browser and type in:
https://192.168.1.100
Right Click on the shortcut and select Open
Page 14
Accept Security Certificate warning and proceed to Unisphere
Page 15
Log-in to Unisphere for RecoverPoint

To log in to Unisphere for RecoverPoint:
User: admin
Password: admin
Note: If you receive 2 login prompts, please use the same credentials to login (admin/admin)
Page 16
Dashboard
Note the Cluster map, the environment consists of 2 Clusters connected via IP. New York and Cork. Alerts are
summarized in the upper Right pane.
Overall Health - Connection Type

Hover over the link line between the two clusters to see the type of connection. RecoverPoint supports interconnecting
clusters via IP or FC
Page 17
Dashboard - System Traffic and Consistency Group Status

To quickly review each Cluster's system traffic or review the status of all Consistency Group currently configured in the
system, the lower panes offer a summarized view
Dashboard - Monitoring
A detailed monitoring view is provided under 3 tabs: System, Groups and Splitters
Page 18
Dashboard - Reviewing System Events

The third tab in the Dashboard is the System Events, it provides detailed event logs about the entire RecoverPoint
environment
Protection
Under the Protection tab, there are 3 wizards. Use this tab to configure Consistency Groups, manage Consistency
Groups or manage Groups Sets
Page 19
Review existing Consistency Groups

To review Consistency Groups that are currently protected with RecoverPoint, select Manage Protection
List Consistency Groups

A list of Consistency Groups (CGs) will be displayed, note the Status and Transfer state of each CG. For instance
Lab_2_Operational Recovery CG is shown below to be Enabled and in Active state.
Note: Active State indicates that the LUNs are protected in the Consistency Group and point-in-time images exist (and
being created) for the Source LUNs at Local and Remote Copies. Active is the desired state that each Enabled CG
should be in
Page 20
Review Protection Status

To review the status of one of the listed Consistency Groups, select a Consistency Group from the list. As an example
select Lab_2_Operational Recovery CG and view its overall status. Notice the following:
1. Production Copy in Cork
2. Local Copy in Cork
3. Remote Copy in New York
You will use this tab later on to review the replication status of the Consistency Group that you will setup
Please note that the software version we're using in this lab was developed early on and since the GUI has
significantly improved. If you notice that the Status tab is not displayed properly; please select a different tab and
return to the Status tab
Page 21
Protection Statistics
To review real-time statistics of the selected Consistency Group, select the Statistics tab and review various charts.
Page 22
Replication Sets
If you need to validate which Volumes are being protected by a Consistency Group, select the Replication Sets tab. All
protected replication sets will be listed. Note that each Copy is labeled properly according the Cluster it belongs to.
Also in the lower part of the screen, the Splitter and array information are displayed for each Copy in that Replication
Set.
Group Policy
To view or make changes to a configured Consistency Group, select the Group Policy tab.
In this tab the following can be modified:
1. Consistency Group name - The name of that particular Consistency Group
2. Assigned RPA - The primary RecoverPoint Appliance that's responsible for handling protection of the CG
3. Priority - A quality of service setting that allows you to prioritize Consistency Groups running on a particular
RecoverPoint Appliance
Page 23
4. Distributed Consistency Group - A feature that allows a CG to run on up-to 4 RecoverPoint Appliances (Note:
this feature is not available with Virtual RecoverPoint Appliances)
5. External Management - A setting that can be used to delegate the management of that particular CG to
external applications such as SRM or RPCE
Page 24
Lag Optimization
The Priority feature in RecoverPoint 4.0 offers an advanced Quality of Service setting. It allows you to set the priority of
the Consistency Group manually. Groups with a priority of 'critical' are provided ten times the priority of normal
groups. Groups with a priority of 'high' are provided three times the priority of normal groups. Groups with a priority of
'low' are provided 50% of the priority of normal groups. Groups with a priority of 'idle' are provided 1% of the priority
of normal groups.
Page 25
Link Policy
Under Link Policy tab, you can set the link type to be either Asynchronous or Synchronous for a particular copy.
To define a Recovery Point Objective for a particular Consistency Group, choose the Copy and adjust the RPO value.
The system will dynamically use its resources to achieve the defined RPO value.
Page 26
Journal Configuration
To view the Journal volume configuration of a particular Copy
1. Click on the arrow next to the Consistency Group in the left pane list
2. Select the Journal Tab
Notice that the system lists the current status of that particular Copy as well as the retention and protection details.
Point in Time and Bookmarks

On the right side of the screen, you will see a list of available point-in-time images and any available bookmarks
Page 27
Copy Policy
Under the Policy tab of a particular Copy, you can view and make changes to the name of the Copy, type of Operating
System of the protected host. This tab also allows the user to configure a Journal Consolidation policy which allows for
extending the retention period.
Page 28
Recovery Tab
Select the Recover tab to review available options. Under the Recovery tab you can:
1.
2.
3.
4.
Use the Test a Copy wizard to enable an access to an image or bookmark at one of the available copies
Use the Fail Over wizard to fail a Consistency Group to one of the available copies
Use the Recover Production wizard to restore the production Copy using one of the selected copies
Use the Manage Recovery to monitor and make changes to any of the on-going Recovery tasks
Page 29
RPA Clusters
To view the configured RecoverPoint Clusters in the System, select the RPA Clusters tab. You will see a tab for each
Cluster. RecoverPoint 4.0 allows up to 5 Clusters to be part of the same RecoverPoint System. These Clusters can be
connected via IP or FC.
In this lab, you will see the 2 Clusters New York and Cork, Click on each tab and review its configuration.
Page 30
Splitter Information
To review the Splitter configuration for a particular Cluster, to add, remove or configure credentials, select Splitters
from the list
RPA Information
To see configured RPAs part of that specific Cluster, select RPAs from the list and you view the listed RecoverPoint
Appliances in the right pane.
Page 31
Administration of RecoverPoint System

Select the Admin tab to view configuration options for various settings:
1. Manage License - View, Add and Remove license files
2. System Analysis Tools - Collect Logs, Run system reports to balance load among RecoverPoint appliances or
detect bottlenecks
3. Configure User accounts and/or Role Based Access Control
4. Configure Dial-home and System Reporting options
Summary
At this point you have browsed and learnd the new Unisphere for RecoverPoint interface and noticed the similarity in
the "feel" and "look" with other EMC products which use Unisphere such as VNX, VPLEX and VMAX. You're confident to
move on to the next step which RainPole management has tasked with to protect one of the organization's critical
applications.
Page 32
Protect Volumes
Using Unisphere for RecoverPoint to create Consistency Groups
In this part of the lab, you configure a Consistency Group to protect a critical database. RainPole management has
requested that the application be protected both Locally and Remotely. You have identified the following:
1.
2.
3.
4.
5.
6.
Source Volume at Cork - This is the Volume that contains the production data
Source Journal at Cork - This is the source journal volume required for the Production Copy
Local Copy volume at Cork - This is the Local replica volume
Local Copy Journal at Cork - This is the Local Copy journal volume required for the CDP Copy
Remote Copy volume at New York- This is the Remote replica volume
Remote Copy Journal at Journal- This is the Remote Copy journal volume required for the CRR Copy
To get started, under the Protection tab, select Protect Volumes
Page 33
Define Source Copy

Under this step, configure the Consistency Group as follows:
Enter 'Lab_1_CG
Lab_1_CG' in the Consistency Group Name field
Define a name for the Production Name copy, use 'PRD
PRD'
Ensure that Production Cluster is set to Cork
Cork, where the application is currently running
Select volumes to protect. Highlight OVERVIEW_DB_PROD(20) and OVERVIEW_LOG_PROD(21)
Click on Next Define the Production Journa
Journal
Page 34
Select Production Journal

Highlight a volume to set it as a Production copy journal. In this example use OVERVIEW_JOURNAL_PROD(25) as the
Production Copy journal.
Once you have selected the journal volume, click on Next Add a Copy
Page 35
Add Replica Copy (CDP)

Let us first configure the Local (CDP) copy for our Lab_1_CG.
Define a Copy Name, enter CDP
Select a Cluster, since this is going to be the local Copy, choose Cork
Leave Protection Type set to default (Asychronous) and RPO is set to default (25 seconds).
Then click on Select Volume to add a volume to the replication set
Page 36
Select Local Copy Volume

Highlight the Local Copy (CDP) target volume OVERVIEW_LOG_CDP_(23) for the source OVERVIEW_LOG_PROD(21) and
then click OK
Page 37
Select Local Copy Volume

Highlight the Local Copy (CDP) target volume OVERVIEW_DB_CDP_(22) to pair it with the source volume
OVERVIEW_DB_PROD(20) and then click OK
Page 38
Review Replication Set

Review the pairings you chose between Production and Local copies. Click Next Select Copy Journal Settings to
proceed.
Page 39
Select Local Copy Journal

Select volume OVERVIEW_JOURNAL_CDP as the Local Copy CDP journal volume and then click Next Review the Group
Settings to proceed
Page 40
Add Remote Copy

In this step you have the option to select Finish to complete the configuration of the Consistency Group or to add
additional copies. Since the management of RainPole has requested that the application be protected Remotely to the
New York Data Center, click on Add Another Replica Copy to proceed
Page 41
Define Remote Copy

Enter a Copy Name, use CRR
Select New York as a Cluster
Then start choosing target replica volumes by clicking on Select Volume as was done with the CDP Copy.
Page 42
Select Remote Copy Volume

Choose a target volume to remotely protect OVERVIEW_LOG_PROD(21)
OVERVIEW_LOG_PROD(21). Select OVERVIEW_LOG_CRR(21) and then click
OK
Page 43
Select Remote Copy Volume

Choose a target volume to remotely protect OVERVIEW_DB_PROD(20)
OVERVIEW_DB_PROD(20). Select OVERVIEW_DB_CRR(20) and then click
OK
Page 44
Modify Copy Protection Policy

Review Replication Set volume selection.
Next click on Modify Copy Protection Policy
Page 45
Set Remote Copy Operating System Type

A new window will open, under the Copy Protection Policy tab, select Linux2_6 for the Host OS.
Page 46
Other OS Type values include
Page 47
Link Protection Policy

Review settings under the Link Protection Policy tab. Under this tab you can select to set the replication type to be
Synchronous or Asynchronous as well as defining RPO value for this copy. For this lab, you don't have to make any
changes to the default settings. Click OK once ready to proceed.
Page 48
Proceed to Select Remote Copy Journal

Click on Next Select Copy Journal Settings to proceed to configuring journal volumes for the CRR copy.
Page 49
Select Remote Copy Journal

Highlight OVERVIEW_JOURNAL_CRR volume to select as the Remote Copy journal and then click on Next Review Group
Settings to proceed
Page 50
Review Group Settings

Review settings, ensure that Production is set at Cork and that there is a Local (CDP) and Remote (CRR) Copies and
then Click on Finish to complete the configuration of your Consistency Group.
Manage Protection
After clicking on Finish, the screen will refresh and display a list of configured Consistency Groups. Locate Lab_1_CG in
the Consistency Groups list in the left pane and highlight it.
Page 51
Monitor Replication
The Consistency Group state will change from Paused by System, to Init (%) and finally to Active state. Active state
indicates that point-in-time images are available at the target copy.
Page 52
Ensure that both links are Active

Monitor replication until both links are in Active state. RecoverPoint uses efficient initialization algorithm where only
blocks which are different between source and target are transferred, hence saving on bandwidth in the case of
remote replication and ensure quick protection of applications.
Summary
At this point you have completed the configuration of a Consistency Group which offers Local and Remote continuous
protection of your organization's critical application.
Great job on protecting this critical application. RainPole's management is very confident that EMC RecoverPoint
product features will allow them to meet and even exceed their Service Level Agreements.
Page 53
Lab 2 - Operational Recovery using

RecoverPoint
Page 54
Lab Scenario
RainPole has a critical application protected with RecoverPoint and RainPole's management has set a
requirement to be able to recover this application using the Local copy or Remote copies.
In the first part of this lab you will assume that an upgrade to the system goes wrong and you're required to
restore the application using the Local copy. The second part of this lab will involve simulating a hardware
failure to the production server and you'll be required to perform a failover to the remote site where a stand
by host will continue to run the application.
Page 55
RecoverPoint Protecting the Organization Against Data Loss and Site

Failure
Before we get started, let us get familiar with the environment. We will login to the Unisphere for
RecoverPoint and the Linux server.
Review Setup
In this case the Consistency Group for the application that you will be recovering has been already created (If you
would like to setup a Consistency Group refer to Lab#1).
Follow the next few steps to get familiar with the Consistency Group setup and access the replicated host.
https://192.168.1.100
Page 56
Accept Security Certificate warning and proceed to Unisphere for RecoverPoint
Page 57
Log-into Unisphere for RecoverPoint

To login to Unisphere for RecoverPoint use the following credentials:
User: admin
Password: admin
Page 58
Dashboard
Page 59
Navigate to Protection Tab

Under the Protection tab, there are 3 wizards, select the Manage Protection Wizard to view configured Consistency
Groups

Page 60

A list of Consistency Groups (CGs) will be displayed, note the Status and Transfer state of each CG. For this lab we will
be working with Lab_2_Operational Recovery CG. Notice that it's in an Enabled status and Active transfer state.
should be in
Page 61

Take a moment to review the status of the Consistency Group, select it from the list. As an example select
Lab_2_Operational Recovery CG and view its overall status. Notice the following:
2. Local Copy in Cork
Please note that the software version we're using in this lab was developed early on and since then the GUI has
Page 62
Confirm Replication Sets

protected replication sets will be listed. Note that each Copy is labeled according to the Cluster that it belongs to. Also
in the lower part of the screen, the Splitter and array information are displayed for each Copy in that Replication Set.
Page 63
Recovery Tab
Select the Recovery tab to review available options. Under the Recovery tab you can:
1.
2.
3.
4.
Use the Test a Copy wizard to enable an access to an image or bookmark at one of the available copies
Use the Fail Over wizard to fail a Consistency Group to one of the available copies
Use the Recover Production wizard to restore the production Copy using one of the selected copies
Use the Manage Recovery to monitor and make changes to any of the on-going Recovery tasks
Linux Servers
Now, you want to login to the production (Cork).
Locate PuTTY shortcut on the desktop, and double click
Page 64
Access Production Linux Server

To access the production server, select Cork Linux 01, click on Load and then Open to establish SSH to the server
Page 65
Validate File System

Login as root and for password enter Password123!
The production volume has already been mounted on the Linux server at /data
/data. This volume is protected by
RecoverPoint Lab_2_Operational_Recovery Consistency Group. Once logged, validate that /data file system is
mounted by running
df -h
Write Production Data

To simulate data being written to the protected volume, return to the Linux machine vm01
vm01. The protected volume /data
should be empty, except for the system created lost+found folder. Use the ls command to verify. We will create three
empty files and use ls to verify the files have been created.
Enter the following commands at the prompt:
cd /data
Page 66
ls
touch file1 file2 file3
ls
Page 67
Return to Unisphere for RecoverPoint

Return to the Unisphere for RecoverPoint interface and navigate to the Lab_2_Operational Recovery Consistency Group
if you're not there already. Validate that both links are in Active state.
Next we will create a Bookmark, by clicking on the Bookmark button at the bottom of the Status pane.
Create a Pre-Upgrade Bookmark

A bookmark is simply a labeled point-in-time image. Typically bookmarks are taken before upgrades, patches, data
structure changes and during quiesced state of the application. Every point-in-time image is Crash-Consistent
Crash-Consistent.
Bookmarks can be either crash-consistent if taken while the application is running or Application-Consistent if taken
while the application is quiesced.
In this scenario, you have worked with the database team who are planning a major data restructure and they have
asked you to take a bookmark before they start their data restructure process.
Enter a name for the bookmark, type Before_Upgrade
Page 68
Assuming the Bookmark was taken while the application was online, choose Crash-Consistent and click OK
Validate Bookmark
Expand the Lab_2_Operational Recovery Consistency Group and select the CDP copy. Next select the Journal tab and
validate that the bookmark which you've created in the previous step is in the CDP journal. By clicking on "Bookmark"
at the top of the bookmark column you can sort by any named bookmarks. This can help you locate your bookmark
faster.
Page 69
Data Corruption at Production

After you have taken the bookmark, the database upgrade starts but unfortunately the Database Administrator
updates the wrong table causing the application to break. RainPole management decides that they need to recover the
database to a point pre-upgrade. Fortunately, RainPole has protected this database with RecoverPoint and have the
ability to recover using many available images both locally and remotely. Once you get a request that the database
team want the database to be restored, you quickly realize that the Local Copy is the best approach. You present the
CDP copy to the Linux machine, verify the data and then restore production.
Now, to simulate the data corruption, return to the Linux server window. Let's add some text to the file named file2
using the echo command. We then use the cat command to verify the text in the file. Enter the following
command at the prompt to add text to to the file:
echo "Wrong Data" >> file2
cat file2
Verify your output matches the example above.
Oh no! We knew it! The database team didn't want that data in file2! The database need to be restored.
Unmount File System

We now have few options:
1. We can perform Test a Copy (enable image) using the bookmark we took prior to the upgrade, mount the CDP
copy on the local host and have the DBAs copy the file over from an alternate host or alternate file system to
the prod file system
Page 70
2. We can Enable Image Access, validate the data and then perform a restore or recovery from the CDP copy back
to production
3. Use the bookmark and perform Recovery.
Since you have verified the bookmark, you felt confident that it contains the data as it was prior to the upgrade, you
choose option #3.
To recover the corrupted file system, remove host's access to it.
cd /
umount /data
Let's go back to Unisphere for RecoverPoint and recover production
Page 71
Begin the Recovery Process

Select the Consistency Group
Then select the CDP copy at Cork
Click Next Select an Image
Page 72
Select Bookmark
Select - An Image from the image list
Then, select the bookmark that you created earlier Before_Upgrade
Click Next Start Recovery
Page 73
Mount CDP Copy

At this point the bookmark image that you have selected has been enabled. If you have a host which has access to the
CDP copy, you can mount the file system and validate it.
In our case the CDP copy is presented to the source Linux vm01
Validate Data
Let us switch back to the putty session we had open to Linux vm01.
Mount the replica volume and validate that file2 doesn't contain the Wrong Data string.
blockdev --rereadpt /dev/sdb
mount -t ext4 /dev/sdb1 /replica
cd /replica
cat file2
as you can see it does not contain the Wrong Data string.
Once data has been validated, you can unmount the /replica file system.
cd /
Page 74
umount /replica
Complete Recovery
Return to Unisphere for RecoverPoint and click on Finish
Page 75
Accept Warning
The Recovery process from the CDP copy to the Production Copy will start. Once complete, you will get a message
indicating that all Recovery tasks have been completed for that Copy.
At this point you're ready to go back to the Linux vm01 host and mount the file system and validate the data
Validating Data, Restarting Application

Return to the Linux vm01 host and issue
mount /data
validate the content of the file2 to ensure that it does not have the corrupted data "Wrong
Wrong Data
Data".
cd /data
cat file2
Congratulations, you have saved the application and restored it to pre-corruption state.
Page 76
Recover from Remote Copy

After successfully recovering from corruption using the Local (CDP) copy, you're now being faced with a different
scenario. In this scenario, the Linux production server in Cork encounters a hardware failure and requires repair, so
RainPole management asks you to failover the application from Cork to New York where there is a target server that
can run the application.
This time we will use the Fail Over wizard under the Recovery tab.
Connect to VC01 (Cork)

To simulate the hardware failure of the production Linux server vm01
vm01, we will log-in to VC01 and poweroff the server.
Locate the VMware vSphere Client VC01 shortcut on the desktop and double click.
Page 77
Log-in to VC01 (Cork)

Log-in information is saved but if required use Administrator and Password123!
Page 78
Power-off Lab_2_Linux_Prod
Locate the Virtual Machine named Lab_2_Linux_Prod and from the main pane select power-off
Page 79
Begin Fail Over Process

Return to Unisphere for RecoverPoint interface and in the 1st step of the Fail Over wizard,
1. Select the Consistency Group Lab_2 Operational Recovery
2. and then select which copy you want to fail over to, in this case click on the New York CRR copy
3. and select Next Select an Image to proceed
Page 80
Select an Image
In the 2nd step of the Fail Over wizard, you can choose the image you want to fail over to. You have the ability to
choose the latest image or an earlier image or bookmark. In this case we will go with the latest image.
Choose logged access. In the logged access, RecoverPoint rolls the replica to the specified point-in-time image and
then enables access to the copy. All changes made to the copy are tracked.
Click Next Start Failover to continue
Page 81
Finish Fail Over

At this point, the selected image has been enabled at the target site. You have the option of proceeding by clicking on
the Finish button, or you can validate the image first before proceeding. We will validate the image and return back to
this page when ready.
Locate VC02 Shortcut

Return to the desktop and locate the Vmware vSphere Client VC02 shortcut. Double click to login
Page 82
Login to VC02
Login to VC02 (New York), if needed use Administrator and Password123! to authenticate. We will confirm that the
remote linux host Lab_2_Linux_CRR is powered on.
Linux Servers
Now, you want to login to the remote (New York) Linux server
Page 83
Access Remote Linux Server

To access the Remote Linux server, select New York Linux 01, click on Load and then Open to establish SSH to the
server
Validate Image
Log-in as root and for password enter Password123!
The /data file system is not mounted by default at the remote Linux server at vm02
vm02.
To mount the file system, rescan and mount it as /data (if the mount point does not exist, you can create it by running
mkdir /data )
blockdev --rereadpt /dev/sdb
mount -t ext4 /dev/sdb1 /data
Page 84
df -h
cd /data
ls
As you can see all our files are there and if you view the content of file2 you will see that it does not contain the
corrupted data
cat file2
Page 85
Complete Fail Over

Since the mounted image contains the proper data, return to Unisphere for RecoverPoint and click on Finish to
complete the Fail Over wizard
Page 86
Accept Warning
You will receive a Warning window to validate that you understand the impact of performing a fail over on the current
replication. The direction of Replication will be reversed . Please note that the CDP copy will not be active in this case
since this lab is configured as RP/SE, it does not allow more than 1 Remote copy.
Read and accept the warning by selecting Yes
Page 87
Run Production at the Remote site (New York)

At this point, the application is running on the Remote (New York) side. To simulate that data is being generated, go
back to the SSH session you established earlier and create a file NewYork
touch NewYork
Page 88
Prepare for Failback

After you have successfully failed over the application to the New York site, production continued to run in New York
until the original production server vm01 in Cork has been repaired. Now RainPol's management has scheduled a time
to perform a fail-back of the application back to Cork.
To begin the fail-back process, power-off the server in New York.
Use the VMware vSphere center connection VC02
VC02, select the Lab_2_linux_CRR virtual machine and in the Getting
Started tab, select Power Off the virtual machine
Page 89
Initiate Fail-back
At this point, the application is running New York and replication has been reversed back to Cork and you need to
restore production back to Cork.
Return to Unisphere for RecoverPoint and you should be under the Manage Recovery tasks page and select Fail Back to
Production under the Lab_2 Operational Recovery Consistency Group recovery tasks
Select an Image to Fail Back to

After you've selected Select Fail Back the wizard will take you to the 2nd step which is selecting an image. Use the
latest image to fail-back to and click Next Start Failover to proceed.
Page 90
Complete Failback Process

Click Finish to complete the wizard
Accept Warning
You will receive a warning indicating that the direction of replication will be reversed and that journal history will be
erased. Since the current target journal will become the source journal, it's understandable that all remaining point-intime images will be discarded. Click Yes to proceed.
Page 91
Review Recovery Activities

Please note that after failing back, there are no outstanding Recovery Activities
Review Group Status

Return to the Protection tab and Select the Manage Protection task.
Page 92
Ensure that Replication is back to normal

Review the Group Lab_2 Operational Recovery status. Note that Cork is back set to production role and that both Local
and Remote replication have been resumed.
Power on Production server

Return to VC01 VMware vCenter and locate Lab_2_Linux_Prod server, and under the Getting Started tab, select Power
on the virtual machine to start vm01 in Cork.
Page 93
Linux Servers
Now, you want to login to the production (Cork) and verify that the application is running.
Access Production Linux Server

To access the production server, select Cork Linux 01, click on Load and then Open to establish SSH to the server
Page 94
Validate File System

Login as root and for password enter Password123!
The production volume has already been mounted on the Linux server at /data
/data.
df -h
Ensure that the data which was restored back to Cork contains all data processed while the application was running in
New York
cd /data
ls
Great job! File NewYork is there!.
Page 95
Summary
You have successfully managed to protect a critical application from 2 different disasters. In the first one, you were
able to quickly utilize RecoverPoint Local copy to restore the application to a pre-upgrade stage without losing any
data. In the second scenario a hardware failure was encountered at the primary site, and by using RecoverPoint
Remote copy you were able to select the best point-in-time image to run production at the remote site and then
failback once the production server has been repaired. RianPole management could not be happier!
Page 96
Lab 3 - Disaster Recovery using

RecoverPoint with VMware Site
Recovery Manager
Page 97
Lab Scenario
RainPole has a critical Active Directory and SQL database protected using RecoverPoint. You're using Site
Recovery Manager with SRA and the new EMC Virtual Storage Integrator (VSI) to manage the environment.
The application team has scheduled a major upgrade of the SQL database, however; they run into an issue
during the upgrade that requires them to recover back to a point prior to the start of the upgrade. Given your
expertise and the fact that you have RecoverPoint, you feel very confident that you're able to recover the
application to any point in time in.
In this exercise you will use SRM to conduct a Recovery operation using a specific point-in-time to the
Remote site and then perform a failback but first we will review the setup of the Consistency Group and the
SRM configuration.
Please Note: As this lab environment is fully virtualized there may be delays in the readiness
of Lab 3 when it is first made available. In this instance it is recomended to perform lab 1 or
2 while lab 3 is in a initializing state.
Page 98
RecoverPoint Protecting the Organization Against Data Corruption using

VMWARE Site Recovery Manager (SRM)
Before we get started, let us get familiar with the environment. We will log in to the Unisphere for
RecoverPoint and vSphere client
Review Setup
In this case, the Consistency Group for the datastore containing both the Active Directory and SQL database virtual
machines that you will be recovering has been already created (If you would like to setup a Consistency Group, please
refer to Lab#1). Follow the next few steps to get familiar with the Consistency Group setup and access the replicated
host.
https://192.168.1.100
Page 99
Accept Security Certificate warning and proceed to Unisphere for RecoverPoint
Page 100
Login to Unisphere for RecoverPoint

To log-in to Unisphere for RecoverPoint use the following credentials:
User: admin
Password: admin
Then click on Login to proceed.
Page 101
Dashboard
Page 102
Navigate to Protection Tab

Under the Protection tab, there are 3 wizards, select the Manage Protection Wizard to view configured Consistency
Groups

Page 103

A list of Consistency Groups (CGs) will be displayed, note the Status and Transfer state of each Consistency Group. For
this lab will be working with Lab_3 Disaster Recovery with SRM CG. Notice that it's in an Enabled status and Active
transfer state.
should be in
Page 104

Take a moment to review the status of the Consistency Group, select it from the list. As an example select Lab_3
Disaster Recovery with SRM CG and view its overall status. Notice the following:
Please note that the software version we're using in this lab was developed early on and since then the GUI has
Page 105
Confirm Replication Sets

protected replication sets will be listed. Note that each Copy is labeled according to the Cluster that it belongs to. Also
in the lower part of the screen, the Splitter and array information are displayed for each Copy in that Replication Set.
Page 106
Review Group Policy

Select the Group Policy tab to review the relevant settings.
Notice the following:
1. The External Application of the Consistency Group is set to SRM
2. The Managed by is set to External Application which is in this case SRM
These settings indicate the management of Lab_3 Disaster Recovery with SRM has been delegated to SRM.

Let us connect to vSphere client (VC01) and review the SRM configuration
Page 107
Login to VC01 (Cork)

Login information is saved but if required use Administrator and Password123!
Page 108
Select Hosts and Clusters to review protected virtual machines
Page 109
Protected Virtual Machines

The datastore which is being replicated in RecoverPoint Lab_3 Disaster Recovery with SRM has two virtual machines
on it, the Active Directory and SQL server.
Page 110
Site Recovery
Let us review the Site Recovery configuration for Lab_3 Disaster Recovery with SRM Consistency Group
Under Solutions and Applications, click on the Site Recovery icon
Page 111
Connect to SRM
If prompted for log in information enter Administrator for Password123!
Confirm Connection to VC01 and VC02

Once connected you will see VC01 and VC02 listed under sites. We're interested in reviewing the Protection Group,
click on the Protection Group in the lower left pane
Page 112
SRM Protection Group

Under the Protection Group, you will see an already defined Protection Group called Cork Virtual Infrastructure, if you
select it and then select the Virtual Machines tab, you can see the 2 virtual machines protected by Lab_3 Disaster
Recovery with SRM.
Page 113
SRM Recovery Plans

To review the Recovery Plans, select Recovery Plans from the lower left pane and then select the predefined Scheduled
Cork Power down plan. Under the Virtual Machines tab, confirm that both the SQL server and Active Directory are listed
and that their Recovery Status is ok.
We will return to Recovery Plans when we're ready to execute a Recovery operation.
Page 114
VSI Plugin
As part of RainPoles disaster Recovery plan they would like to able to failover to a predefined point in time. The new
EMC VSI plugin enables SRM to take advantage of RecoverPoint's point-in-time images hence allowing you to perform
Recovery operations to any point-in-time snapshot or bookmark as we will see later on in this lab. As part of this
process you will first view the plugin and the details it needs to be able to provide this capability.
To begin return to the Home screen in vSphere client and this time click on the EMC VSI plugin under the Solutions and
Applications
Page 115
View VSI Plugin details

Click on RecoverPoint Management in the left hand pane. As you can see the details required for the VSI plugin to
function correctly have already been added. These include the RecoverPoint and virtual center IP's and their
associated credentials.
Page 116
SRM Recovery using RecoverPoint and the new EMC VSI

The database team is about to begin the upgrade process and they have asked you to take a bookmark of the
environment. We first add some text to help us track the status of the database SQL server and then we take a
bookmark which can be used in the SRM Recovery. This bookmark is a cautionary step and not needed as the EMC VSI
plugin will give you access to all point-in-time images. However, taking a bookmark will help you locate the exact
point-in-time that you need to recover to in case anything goes wrong during the upgrade.
Locate a shortcut to Putty on the desktop, we will use it later on to access the command line for RecoverPoint and
create a bookmark.
Access the SQL Server in Cork

We will first RDP into the production SQL server(shown below) using mRemote and then create some data to indicate a
pre-upgrade point-in-time. We will then take a RecoverPoint bookmark which will be used later on in the EMC VSI and
SRM Recovery
Page 117
Open mRemote to establish an RDP session to SQL Server in Cork

Click on the Start button and click mRemote on the taskbar.
Page 118
Log in to the source SQL Server

Double click on SQL Server in the connections pane, this will launch an RDP session to the source SQL server.
Page 119
Locate a File on the Desktop

You should see a file called SQL status
status, double click on it to view it
Page 120
Add pre-upgrade text

A blank file will open up. To help us track the status of the data, let us append Pre-Upgrade to the file.
Page 121
Save the File

Click on File and Save to save the file.
Minimize the mremote console, we will need it later on to add corrupted data to the SQL database
Locate Putty
In order to take a bookmark of the Lab_3 Disaster Recovery with SRM Consistency Group, we will use the RecoverPoint
CLI.
Locate a shortcut to Putty on the desktop
Page 122
Select RecoverPoint Saved Session

You will find saved sessions, select the Cork RecoverPoint mgmt session and click on Open to access RecoverPoint CLI
Page 123
Log in to RecoverPoint CLI

When prompted for username and Password, enter admin
admin/admin
admin
Create a Pre-Upgrade Bookmark

A bookmark is simply a labeled point-in-time image. Typically bookmarks are taken before upgrades, patches, data
structure changes and during quiesced state of the application. Every point-in-time image is Crash-Consistent (please
note that due to the version of code used in building the lab, the Crash-Consistent is listed as Unknown). Bookmarks
can be either crash-consistent if taken while the application is running or Application-Consistent if taken while the
application is quiesced.
In this scenario, you have worked with the database team who're planning a major data restructure and they have
asked you to take a bookmark before they start their data restructure process.
To take a bookmark, execute the following command:
bookmark_image
Page 124
You will then be asked to specify a Consistency Group for the bookmark, enter Lab_3 Disaster Recovery with SRM.
Please note that you can tab and the CLI will auto-complete the name of the Consistency Group
Enter a name for the bookmark, type Before_Upgrade
Select default policy for journal consolidation which is always. Journal Consolidation policies are user defined policies
that allow for longer retention of images without requiring additional journal space.
Assuming the Bookmark was taken while the application was online, choose Crash-Consistent (Unknown) and press
Enter to continue.
Validate that the bookmark_image command was successful; the system should display Request for bookmark
registered successfully message indicating successful execution of the command.
Validate Bookmark
If you would like to validate that the bookmark has been created in the copy journal. You can execute the get_images
command
Enter Lab_3 Disaster Recovery with SRM for the group name
Then specify a copy name New York CRR
Page 125
Leave the default for the remaining 3 questions and the list of available images will be displayed. Validate that the
bookmark we just created Before_Upgrade is there.
Page 126
Data Corruption at Production

After you have taken the bookmark, the database upgrade starts but unfortunately the Database Administrator
updates the wrong table causing the application to crash. RainPole management decides that they need to failover to
the remote site and use a point in time just before the upgrade had started. Fortunately, RainPole has protected this
database with RecoverPoint and have implemented Site Recovery Manager with the new EMC VSI which enables SRM
to access any available image.
Now, to simulate the data corruption, return to the SQL server RDP session in mremote. Let's add some text to the file
named SQL Status to indicate data corruption. Let us simply add:
Wrong Data
and then make sure to save the file
You might want to close and reopen the file to make sure the Wrong Data text has been saved. Now the application is
down and we need to rollback to a pre-upgrade state.
Page 127
Page 128
Let's go back to vCenter VC01

Let's go back to vCenter VC01 and if we select the SQL Server virtual machine and then go to the EMC VSI tab, you will
see the Consistency Group Lab_3 Disaster Recovery with SRM and all available images. Search for the bookmark that
you created before the upgrade Before Upgrade
Page 129
Choose Bookmark and Apply it

Select the Before_Upgrade bookmark and click Apply
Apply. You will see a pop-up window asking you to confirm your
selection, click OK to proceed and apply the bookmark.
Validate PiT has been applied

Validate that the selected Point-in-time has been applied in the EMC VSI tab

At this point, the usual SRM Recovery can be executed, once an image has been enabled in the failover process, it will
be the bookmark you selected using the VSI plugin.
In vCenter, go to the Home screen
Page 130
Under Solutions and Applications click on Site Recovery
Connect to SRM
Page 131
SRM Recovery Plan

To execute the Recovery Plan, select Recovery Plans from the lower left pane and then select the predefined Scheduled
Cork Power down plan.
Under the Summary tab, confirm that both the Protected Site and the Recovery Site. The current Protected Site
(Production) is VC01 and the Recover Site (remote) is VC02.
When ready, click on Recovery at the top right corner.
Page 132
Begin Execution of the Recovery Plan

You will receive a notification warning ask you to confirm the consequences of the failover. Take a moment to read the
message and then tick the checkbox and click Next to proceed.
Page 133
Review Summary of Recovery Taks

A summary page of the Recovery task will be summarized. Take a moment to review it and then click on Start to initiate
the failover process
Page 134
Recovery In Progress
Review that under the Summary tab, a message stating Recover In Progress will indicate that the failover process has
been initiated successfully.
Page 135
Monitor Recovery Steps

You can also switch to the Recovery Steps tab to monitor the recovery plan execution.
You will see a list of tasks indicating the steps which are being executed by the SRM and RecoverPoint system. Virtual
machines at the current production site will be powered down, access to an image will be enabled at the remote site
and then virtual machines will be enabled at the remote site.
Page 136
Recovery Plan has been executed

You should see all Recovery Steps completed successfully.
Both Virtual Machines SQL server and Active Directory are currently running on remote site.
Page 137
History Tab
If some of the steps went by too fast and you would like to review a log of the Recovery Plan steps, click on the History
tab and then click on View as shown below
Page 138
Review Recovery Reports

A browser window will open and display a report of the Recovery Plan which you just executed. Take a moment to
review the steps.
Page 139
Connect to VC02 (New York)

We now want to validate that the bookmark (point-in-time) image we enabled in New York contains the proper data
without the corruption.
Page 140
Login to VC02 (New York)

Page 141
Open mRemote to establish and RDP session to SQL Server in New York
Open mRemote and double click SQL Server to establish and RDP session.
Page 142

Double click on the file to open it and see its content
Page 143
Validate Data
When the SQL status file opens it should the original text Pre-Upgrade without the corrupted data Wrong Data
Data.
Perfect! RecoverPoint along with the new EMC VSI allowed you roll-back the application to pre-corruption point.
Page 144
Reprotect Applications
Since the Virtual Machines are running at the Remote site we need to execute the Reprotect plan.
The Reprotect Plan will enable replication from the current active site New York (VC02) back to Cork (VC01). Please
note that while this step is essential, it's non-disruptive to the applications that are currently running at the New York
(VC02) site.
Click on Reprotect
Page 145
Reprotect Confirmation
A warning window will appear, tick the checkbox confirming that you understand the steps which will be performed
and then click Next to proceed
Page 146
Reprotect Summary
Review a summary of the Reprotect plan and click Start to enable replication from the Cork site to the New York site.
Page 147
Review Reprotect Steps

Monitor the reprotect steps until they're complete. The completion of this step indicates that replication has been
enabled from New York back to Cork.
Page 148
Review Status in Unisphere for RecoverPoint

At this point we're done with the Recovery and Reprotect tasks. Great job!
Go back to Unisphere for RecoverPoint and review the status of the Consistency Group Lab_3 Disaster Recovery with
SRM
SRM. You will notice that the production site is not set to New York and the replica copy is set to Cork and that the link
is in Active state.
Application teams as well as RainPole management are thrilled that once again RecoverPoint saved the organization
from data loss and enabled them to achieve the desirable RPO in a swift RTO!
Failback To Original Production Site (Cork)

After successfully recovering from corruption using RecoverPoint with the new EMC VSI, RainPole management has
scheduled a window to failover its critical applications that run on SQL server and Active Directory back to the Cork
site.
This time we will use the latest point-in-time image, so there is no need to apply a PiT using the EMC VSI.
But first, let us add some data to the SQL Status file at the current active site in New York.
Let us go back to the SQL server RDP session we have open and append I was running in New York! to the file.
Page 149
Make sure you save the file, it might be a good idea to close the file and reopen it to make sure the text has been
saved.
Connect to VC02 (New York)

Page 150
Login to VC02 (New York)

Page 151

Since we want to use the latest point-in-timme image, we can use Site Recovery without needing to select and apply a
bookmark using the EMC VSI.
In vCetner, go to the Home screen
Under Solutions and Applications click on Site Recovery
Page 152
Connect to SRM
Page 153
SRM Recovery Plan

To execute the Recovery Plan, select Recovery Plans from the lower left pane and then select the predefined Scheduled
Cork Power down plan.
Under the Summary tab, confirm that both the Protected Site and the Recovery Site. The current Protected Site
(Production) is VC02 and the Recover Site (remote) is VC01.
When ready, click on Recovery to begin the fail-back process
Page 154
Begin Execution of the Recovery Plan

You will receive a notification warning ask you to confirm the steps that you want to execute. Take a moment to read
the message and then check the checkbox and click Next to proceed.
Page 155
Review Summary of Recovery Tasks

A summary page of the Recovery task will be summarized. Take a moment to review it and then click on Start to initiate
the failover process
Page 156
Recovery In Progress
Review that under the Summary tab, a message stating Recover In Progress will indicate that the Recovery process has
been initiated successfully.
Page 157
Monitor Recovery Steps

You can also switch to the Recovery Steps tab to monitor the recovery plan execution.
You will see a list of tasks indicating the steps which are being executed by the SRM and RecoverPoint system. Virtual
machines at the current production site will be powered down, access to an image will be enabled at the remote site
and then virtual machines will be enabled at the remote site.
Page 158
Recovery Plan has been executed

You should see all Recovery Steps complete successfully.
Both Virtual Machines SQL server and Active Directory are currently running on Cork site.
Page 159
History Tab
If some of the steps went by too fast and you would like to review a log of the Recovery Plan steps, click on the History
tab and then click on View as shown below
Page 160
Review Recovery Reports

A browser window will open and display a report of the Recovery Plan which you just executed. Take a moment to
review the steps.
Page 161

Login to VC01 (Cork)

Page 162
Open mRemote to view status of SQL server

Once again double click on SQL server within mRemote to establish an RDP session.
Page 163

Page 164
Validate Data
When the SQL status file opens it should contain the text we've added earlier indicating that the fail-back captured the
data which processed while the application was running at the New York site. The file should contain:
Pre-Upgrade
I was running in New York!
Perfect! RecoverPoint along with the new EMC VSI allowed you roll-back the application to pre-corruption point.
Reprotect Applications
Since the Virtual Machines are running at the Cork site we still need to execute the Reprotect plan.
Page 165
The Reprotect Plan will enable replication from the current active site Cork (VC01) back to New York (VC02). Please
note that while this step is essential, it's non-disruptive to the applications that are currently running at the Cork
(VC01) site.
Return to the VC02 vSphere client where you were executing the Recovery paln and under the Summary tab, click on
Reprotect
Page 166
Reprotect Confirmation
A warning window will appear, tick the checkbox confirming that you understand the steps which will be performed
and then click Next to proceed
Page 167
Reprotect Summary
Review a summary of the Reprotect plan and click Start to enable replication from the Cork site to the New York site.
Page 168
Review Status in Unisphere for RecoverPoint

At this point we're done with the Recovery and Reprotect tasks. Great job!
Go back to Unisphere for RecoverPoint and review the status of the Consistency Group Lab_3 Disaster Recovery with
SRM
SRM. You will notice that the production site is not set to Cork and the replica copy site is set to New York and that the
link is in Active state.
Summary
You have successfully managed to protect a critical application from a major disaster. You performed a SRM Recovery
using the new EMC VSI which enabled you to access any point-in-time image. You also utilized the tight integration
between RecoverPoint and VMware to meet all of RainPole's business needs. RianPole management could not be
happier!
Page 169
Conclusion
Page 170
Conclusion
As you've seen RainPole's decision to purchase RecoverPoint has protected the organization from multiple
failure scenarios. Whether it's data corruption, hardware failures or operational recovery, RecoverPoint has
enabled the organization to achieve their desired RPO and RTO and meet their Service Level Agreements. In
addition to great integration with VMWARE SRM, RecoverPoint 4.0 enables SRM to access any point-in-time
image through its new EMC VSI. RecoverPoint 4.0 supports synchronous replication over FC or IP and
provides that ability through its Multi-Site feature to replicate applications up to 4 Remote sites.
RecoverPoint 4.0 also allows RainPole to deploy a virtual edition of the appliance, vRPA that can run on an
ESXi hypervisor. The new Unisphere for RecoerPoint simplifies management tasks through its build-in
wizards and provide the same look and feel of other EMC products.The scale, performance and features of
RecoverPoint provides an enterprise class data protection solution that's easy to integrate and manage.
Page 171

Disaster Recovery Using RecoverPoint

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Disaster Recovery Using RecoverPoint

Încărcat de

Drepturi de autor:

Formate disponibile

OPERATIONAL & DISASTER

Operational & Disaster Recovery using RecoverPoint

Lab Overview ................................................................................................................................................ 8

Lab 1 - Introduction to Unisphere for RecoverPoint...................................................................................... 11

Lab 2 - Operational Recovery using RecoverPoint ........................................................................................ 54

Conclusion ............................................................................................................................................... 170

Operational & Disaster Recovery using RecoverPoint

Reduce backup-windows from hours to minutes and saves on storage space

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Ease of Integration, Comprehensive Features

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Lab 1 - Introduction to Unisphere for

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Browse Unisphere for RecoverPoint

Right Click on the shortcut and select Open

Operational & Disaster Recovery using RecoverPoint

Accept Security Certificate warning and proceed to Unisphere

Operational & Disaster Recovery using RecoverPoint

Log-in to Unisphere for RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Overall Health - Connection Type

Operational & Disaster Recovery using RecoverPoint

Dashboard - System Traffic and Consistency Group Status

Operational & Disaster Recovery using RecoverPoint

Dashboard - Reviewing System Events

Operational & Disaster Recovery using RecoverPoint

Review existing Consistency Groups

List Consistency Groups

Operational & Disaster Recovery using RecoverPoint

Review Protection Status

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Point in Time and Bookmarks

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Operational & Disaster Recovery using RecoverPoint

Administration of RecoverPoint System

Operational & Disaster Recovery using RecoverPoint

To get started, under the Protection tab, select Protect Volumes

Operational & Disaster Recovery using RecoverPoint

Define Source Copy

Operational & Disaster Recovery using RecoverPoint

Select Production Journal

Operational & Disaster Recovery using RecoverPoint

Add Replica Copy (CDP)

Operational & Disaster Recovery using RecoverPoint

Select Local Copy Volume

Operational & Disaster Recovery using RecoverPoint

Select Local Copy Volume

Operational & Disaster Recovery using RecoverPoint

Review Replication Set