Recoverpoint 4 - 1implementation and Management - SRG

Welcome to RecoverPoint 4.1 Implementation and Management.
Click the Notes tab to view text that corresponds to the audio recording.
Click the Supporting Materials tab to download a PDF version of this eLearning.
Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 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 2014 EMC Corporation. All rights reserved. Published in the USA.
Copyright 2014 EMC Corporation. Do not copy - All Rights Reserved.
RecoverPoint 4.1 Implementation and Management
This course covers how to implement and utilize features and enhancements in RecoverPoint
4.1 such as snap-based replication, external storage integration, enhanced group sets, policy
templates and log collection.
This course is intended for those with a RecoverPoint background who are involved in the
implementation, management, support and troubleshooting of RecoverPoint offerings.
This module focuses on applying snap-based replication on a given consistency group.
Once snap-based replication has been configured, replication will transition through two states:
Replicating Snap and Snap Idle. Replicating Snap is displayed when the production site is
replicating to the replica site. The replication status is shown in percentage. Snap Idle is
displayed when the replication is complete and there is no activity, as shown here.
Both of these states will be used in periodic mode. If On Highload is applied, only snap
replicating will be used.
In case of an error, RecoverPoint will attempt several retries. If the snap-based replication
mode is set to On Highload, events will be sent to the user and RecoverPoint will resume
regular async replication. If the mode is set to periodic, transfers will be paused and user
intervention will be required.
This module focuses on the steps necessary to integrate a VNX storage array to a RecoverPoint
Appliance (RPA) cluster for the purpose of automatically creating journal volumes.
The Storage feature of RPA opens a direct line of communication with the storage array. The
storage array must be a VNX running VNX OE for Block 32 or later. The External Storage wizard
is located within the RPA clusters tab. The Add button can be found under the Storage ->
Registered Storage tab.
Once the storage arrays have been registered, resource pools must be registered next. The RPA
cluster will automatically create a journal volume only if at least one resource pool is
registered.
Registering your storage array on the RPA cluster provides the capability of automatically
creating journal volumes from the GUI or CLI using array storage pools. The process of creating
a consistency group remains the same, and creating a journal volume can be defined in one of
two ways:
(1) Select Provisioned Journal Volume that uses already-presented volumes to create journal
volumes for replica and production copies
or
(2) Automatically Provision Journal Volume that creates the journals from a storage pool (or
RAID group) on the storage array.
The volume is created using the default settings in the storage pool.
Click Next to see a demonstration of Automatic Journal Volume Creation.
10
Through the CLI, a storage array can be registered using the register_storage command.
For VNX systems, a type, primary and secondary IPs, and authentication are required for a
successful registration. In this example, a storage named Site4VNX is being registered to
Cluster1 and the cluster returns a message to confirm that the registration was successful.
The get_registered_storage command provides information on all storage arrays
connected to specified clusters. In this example, we need to get the registered storage
information from Cluster1 and input the cluster name at the prompt. Below Registered Storage
is the listed information about the registered storage, including the connectivity status. The
registered storage can only be used with a connectivity status of OK.
11
Before using the registered storage, a resource pool must be registered by using the
register_resource_pool command. The storage name and resource pool names are
required. In this example, Pool_0 is being registered to Cluster1 and Pool_0 is on Site4VNX.
After the command has been executed, the cluster returns a message to confirm that the
registration was successful.
The get_resource_pools command provides information about all resource pools
registered on a specified cluster and specific storage array. In this example, we want to get
information on resource pools registered to Cluster1. Currently, there is only one storage array
registered to that cluster, so we choose it. There is only one resource pool registered, Pool_0.
The resource pool is listed along with total and available size and supported tiers.
12
This module focuses on the creation of policy templates and enhanced group sets.
13
To learn the process of creating a Copy template, you will be instructed to click tabs, buttons
and drop-down menu items. The instructions for the remaining steps will appear to the right of
the screen.
If you wish to skip the steps, click the Next button to advance to the Copy Policy Template: CLI
page.
Policy templates allow the administrator to set specific parameters and apply them to a
consistency group efficiently. Create new policies from the Protection tab.
Click the Protection tab.
14
Click the Policy Templates option.
15
Click Add.
16
Click the Type drop-down menu button.
17
Select the type Copy to create a copy policy template and provide a name.
18
Journal compression has three options: none, medium and high. The maximum journal size
capacity is set to unlimited or capped at a specific number.
From the Journal Compression drop-down menu, choose Medium.
19
When selected, the Required Protection window dictates the wait time between each copy.
Click the Required Protection Window checkbox.
20
When Enable RecoverPoint Snapshot Consolidation is selected, specific parameters can be set
to dictate when snapshot copies are consolidated.
Click the Enable RecoverPoint Snapshot Consideration checkbox.
21
Once all the parameters have been set, click OK to save the template.
Click OK.
22
A copy policy template can also be created via the CLI using the create_copy_policy_template
command.
In this example, we are creating a copy template named Copy1 with a protection window of
two weeks. This template has an unlimited journal size, but it can not get larger than 10 TB.
The journal size will not be compressed. Up to twenty-five percent of the available copy journal
capacity can be used by the target journal. The template allows snapshots larger than the
capacity of the journal to be distributed among the journals.
23
The template maintains the default setting to allow replication with self-mirroring, which works
in conjunction with the Symmetrix splitter. A mix of operating systems can perform writes to
the logs. Snapshots older than three days will be consolidated up to four times daily and five
times weekly for all remaining snapshots.
It is very important to get a message confirming that the copy policy template was completed
successfully.
24
To learn the process of creating a Link template, you will be instructed to click tabs, buttons
and drop-down menu items. The instructions for the remaining steps will appear to the right of
the screen.
If you wish to skip the steps, click the Next button to advance to the Link Policy Template: CLI
page.
Policy templates allow the administrator to set specific parameters and apply them to a
consistency group efficiently. Create new policies from the Protection tab.
25
Choose the Policy Templates option.
26
Click Add.
27
Select the Type drop-down menu button.
28
From the Type drop-down menu, select Link. This will display all options for a link policy
template for your specifications.
29
Protection Settings contain two replication modes: Asynchronous and Synchronous. For the
purpose of this module, we will talk about Synchronous mode settings and change settings for
Aynchronous mode.
The dynamic settings for Synchronous can be set to sync or near-sync via enabling Dynamic by
Throughput or Dynamic by Latency.
30
For Asynchronous Replication Mode, Snap Replication is the only available editable parameter.
Click the Snap Replication drop-down menu button.
31
Snap Replication can either be set to Off, On Highload or Periodic.
Select Periodic from the drop-down menu and keep the interval to five minutes, which is the
default.
32
Within the Link template, Compression can be configured to reduce bandwidth-related

activities on the cluster.
Click the Compression drop-down menu button.
33
Compression performance can be set on low, medium or high.
Select Medium from the drop-down list.
34
Deduplication can be enabled by selecting the checkbox, as shown here.
Click OK to confirm the creation of the link policy template and continue.
35
As you can see, both the Link policy template (Link2) and copy policy template (Team1) have
been created and added to the list. They are ready to be imported into a CG during or after its
creation.
36
A link policy template is created by executing the create_link_policy_template command.
In this example, the template is named Link2. The replication mode is set to asynchronous and
the snap-based replication policy is continuous. When this link policy is applied, the first
initialization will quickly be performed. To reduce bandwidth, compression is set to low and
deduplication is also enabled. This specific template has no desired bandwidth.
It is very important to get a message confirming that the link policy template was completed
successfully.
37
To learn the process of creating Enhanced Group Sets, you will be instructed to click tabs,
buttons and drop-down menu items. The instructions for the remaining steps will appear to the
right of the screen.
If you wish to skip the steps, click the Next button to advance to the Creating Enhanced Group
Sets: CLI page.
Enhanced Group Sets can be configured via the GUI or the CLI. The Group Sets page can be
accessed by the Protection tab.
38
Select Group Sets to open the Groups Sets page.
39
The Groups Sets page displays the current list of Group Sets and allows you to create new
groups sets.
Click Add to create a group set.
40
There are four areas in the Add Group Set window that must be addressed in order to
properly create a group set.
First, the group set must have a name, which we named Team1.
Second, at least one CG must be selected and more can be added later, as long as all the CGs
are replicating from the same site.
Third, enabling parallel bookmarking means that the group set is consistent, and a frequency
needs to be selected. The default frequency is set to 20 seconds. For a non-consistent group
set, uncheck Enable Parallel Bookmarking.
Click Ok to confirm the creation of the group set.
41
In the Group Set management page, each group set is listed. In this case, the group set named
Team1 is shown. To manage that group set, select it and the available options will become
enabled at the bottom.
For the sampled group set, the available options are: Disable, Pause Transfer, Apply Bookmark,
Test Copies, Fail Over and Recover Production.
Click Next to continue.
42
Using the CLI, enhanced group sets are configured using the create_group_set command. In
this example, the group set is named Team1 that includes 001_Education and 003_Finance
consistency groups. It will be a consistent group set. Parallel bookmarking is performed every
15 minutes.
A message displays to confirm that the group set was created successfully. Otherwise, a
message provides information to help troubleshooting the reason behind the error.
The get_group_set command is able to provide information about all configured group sets on
that cluster. For this cluster, there is only one group set configured with two consistency
groups.
43
This module focuses on the method to register an RPA cluster with the Install Base (IB) group
and to collect logs from a detached RPA cluster.
44
With RecoverPoint 4.1, the appliance automatically compiles and sends the necessary product
registration information to the EMC Install Base (IB), eliminating the manual registration
process required in earlier versions. The product registration information, which includes serial
numbers, connect home method, license type, software version and party ID, can be retrieved
from the Admin section by selecting Register RecoverPoint.
At the bottom of the page, there are two options Update Form and Send Form. The Send Form
option will allow you to send this information, as is, to the IB team by choosing one of two
methods: SYR or manually (email). By choosing the manual method, the form will be exported
into a CSV file and the CSV can be sent to the IB team via email.
45
The other option is Update Form where information about the cluster is manually entered into
the form for submission. This option can be used to correct any information that the system
may have collected incorrectly or to provide additional information about the cluster. Once the
form is completed by clicking OK, the registration can then be submitted using the Send Form.
46
Prior to this version of RecoverPoint, FTP availability check was performed after the cluster
collects its log. As a result, the log collection failed if the RP cluster/system could not reach the
FTP server. With RecoverPoint 4.1, the FTP availability check performs before log collection.
As in previous versions of RecoverPoint, the log can be retrieved by entering https://<RP
Cluster Management IP>/info into a supported browser. Starting with this release,
admin/admin is used as username/password to access the info page, since webdownload has
been removed. For a production area, there will be more logs listed. Lets take a closer look at
this log.
This is the content of the tar file using 7-Zip. In this example, the processes are displayed
including Connectivity.sh and san_diag.sh. Double-clicking the Connectivity.sh file will open it.
The file shows the link status of both RPAs. This confirms that RPA2 is down and the log
collection still proceeded.
47
This course covered the method to enable snap-based replication, to register a VNX on an RPA
cluster, to create policy templates and configure enhanced group sets.
This concludes the training. Please, proceed to the course assessment.
48
49
50

Recoverpoint 4 - 1implementation and Management - SRG

Uploaded by

Document Information

Original Title

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 4 - 1implementation and Management - SRG

Uploaded by

Copyright:

Available Formats

Welcome to RecoverPoint 4.1 Implementation and Management.

Copyright 2014 EMC Corporation. Do not copy - All Rights Reserved.