RP Admin Guide
RP Admin Guide
Version 5.1
Administrator's Guide
P/N 302-003-960
Rev 03
October 2019
Copyright © 2017-2019 Dell Inc. or its subsidiaries. All rights reserved.
Dell 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.” DELL 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 DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property
of their respective owners. Published in the USA.
Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com
Figures 9
Tables 11
Preface 13
Chapter 2 Dashboard 23
The RecoverPoint Dashboard........................................................................... 24
Overall Health................................................................................................... 25
RPA Clusters Map................................................................................25
Multipath monitoring............................................................................26
Alerts................................................................................................... 27
System Traffic..................................................................................... 28
Consistency Group Transfer Status..................................................... 28
System Limits................................................................................................... 30
System.................................................................................................30
Groups................................................................................................. 30
Storage.................................................................................................31
Splitters................................................................................................31
System Events..................................................................................................32
Display events...................................................................................... 32
Display additional event information.....................................................32
Sort events.......................................................................................... 32
Filter events......................................................................................... 33
Copy an event to the clipboard............................................................ 34
Collect system information around a specific event............................. 34
Chapter 3 Protection 37
RecoverPoint Protection.................................................................................. 38
Protect Volumes............................................................................................... 39
How to protect volumes.......................................................................39
Policy Templates.............................................................................................. 55
Display all policy templates.................................................................. 55
Create new policy templates................................................................55
Modify existing policy templates.......................................................... 56
Remove a policy template.................................................................... 57
Apply a policy template to a new consistency group............................ 57
Apply a policy template to an existing consistency group.....................57
Group Sets....................................................................................................... 59
How group sets work........................................................................... 59
Display all group sets........................................................................... 59
Create a group set............................................................................... 60
Edit a group set.................................................................................... 61
Remove a group set............................................................................. 62
Enable or disable all groups in a group set............................................ 62
Pause or start transfer for all groups in a group set............................. 62
Apply a bookmark to all of the groups in a group set............................ 63
Initiate recovery activities for a group set............................................ 63
Manage Protection........................................................................................... 63
The RecoverPoint protection policies.................................................. 64
Monitoring and managing protection....................................................73
Monitoring and managing groups......................................................... 73
Monitoring and managing copies..........................................................89
Modifying consistency groups..............................................................99
Modifying copies................................................................................. 113
Modifying links.................................................................................... 115
Modifying replication sets................................................................... 116
Modifying journals............................................................................... 119
Modifying snapshots........................................................................... 121
1 Dashboard options............................................................................................................ 24
2 Status icons...................................................................................................................... 26
3 Tooltip links.......................................................................................................................26
4 Transfer state................................................................................................................... 28
5 System LimitsSystem tab................................................................................................. 30
6 System LimitsGroup tab.................................................................................................... 31
7 System LimitsStorage tab ................................................................................................ 31
8 System LimitsSplitters tab.................................................................................................31
9 Protection options............................................................................................................ 38
10 Toolbar options................................................................................................................. 42
11 Group summary screen..................................................................................................... 53
12 Multiple consistency group actions................................................................................... 64
13 Group policies................................................................................................................... 65
14 Link policies.......................................................................................................................67
15 Copy policies.....................................................................................................................70
16 Journal policies................................................................................................................. 70
17 Status tab......................................................................................................................... 74
18 Status tab options when a group is selected..................................................................... 75
19 Priority setting default values........................................................................................... 79
20 Consolidated statistics output...........................................................................................82
21 Status tab......................................................................................................................... 89
22 Status tab options when a group is selected..................................................................... 90
23 Copy journal tab................................................................................................................94
24 Journal Tab: Snapshot Consolidation Progress information.............................................. 96
25 Journal tab image list........................................................................................................ 96
26 Options............................................................................................................................106
27 RPA cluster options......................................................................................................... 142
28 RPA cluster information...................................................................................................143
29 Storage information.........................................................................................................146
30 Resource pool storage information.................................................................................. 154
31 Volume information......................................................................................................... 159
32 RPA table information..................................................................................................... 162
33 Properties tab information...............................................................................................163
34 Status tab information.....................................................................................................164
35 Admin options.................................................................................................................. 174
36 Displayed license information...........................................................................................177
37 Pre-defined users............................................................................................................ 184
38 Pre-defined roles............................................................................................................. 188
39 Permissions..................................................................................................................... 188
40 Permission settings......................................................................................................... 189
41 LDAP settings..................................................................................................................192
42 Collect system information options.................................................................................208
43 Event Filter settings......................................................................................................... 211
44 Email settings.................................................................................................................. 213
45 Syslog settings................................................................................................................ 214
46 SNMP settings................................................................................................................ 215
47 RecoverPoint SNMP trap variables................................................................................. 216
48 System parameters sent to SyR......................................................................................220
49 Licensing support............................................................................................................243
50 Cluster information..........................................................................................................261
51 License file variables....................................................................................................... 262
52 Journal size with snapshot consolidation equation legend...............................................266
53 Normal scope events.......................................................................................................276
As part of an effort to improve our product lines, we periodically release revisions of our software
and hardware. Therefore, some functions described in this document might not be supported by all
versions of the software or hardware currently in use. The product release notes provide the most
up-to-date information on product features.
Contact your technical support professional if a product does not function properly or does not
function as described in this document.
Note: This document was accurate at publication time. Go to Online Support (https://
support.emc.com) to ensure that you are using the latest version of this document.
Purpose
This document is part of the RecoverPoint documentation set and includes conceptual information
on managing a RecoverPoint system.
Audience
This document is intended for use by storage administrators who are responsible for administering
a RecoverPoint system.
Related documentation
The following publications provide additional information:
l RecoverPoint Release Notes
l RecoverPoint Deployment Manager Release Notes
l RecoverPoint Customer Installation and Upgrade Guide
l RecoverPoint Installation and Deployment Guide
l RecoverPoint Product Guide
l RecoverPoint Administrator's Guide
l RecoverPoint CLI Reference Guide
l RecoverPoint Performance Guide
l RecoverPoint REST API Programming Guide
l RecoverPoint Security Configuration Guide
l RecoverPoint Simple Support Matrix
In addition to the core documents, we also provide White papers and Technical Notes on
applications, arrays, and splitters.
Typographical conventions
This document uses the following style conventions:
Bold Used for names of interface elements, such as names of windows,
dialog boxes, buttons, fields, tab names, key names, and menu paths
(what the user specifically selects or clicks)
Technical support
Go to Online Support and click Service Center. You will see several options for contacting
Technical Support. Note that to open a service request, you must have a valid support
agreement. Contact your sales representative for details about obtaining a valid support
agreement or with questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of
the user publications. Send your opinions of this document to techpubcomments@emc.com.
This section describes the first steps to setting up your RecoverPoint system.
of installing your RecoverPoint licenses, enabling support and registering your RecoverPoint
system. Click Next Add Licenses in the first screen of the Getting Started Wizard to get started.
Note: The settings in the Add Licenses screen are displayed both through the Getting Started
Wizard the first time you launch Unisphere for RecoverPoint, and by selecting Admin >
Manage Licenses.
Procedure
1. Install a license on page 175.
2. Click Next Enable Support to go to the Enable Support screen on page 17.
Note: The settings in the Enable Support screen are displayed both through the Getting
Started Wizard the first time you launch Unisphere for RecoverPoint, and by selecting
Admin > System Notifications > Configure System Reports and Alerts.
Procedure
1. Configure system reports and alerts on page 221.
2. Ensure that system reports are configured correctly on page 223 by clicking the Test
Connectivity button.
Note: The connectivity test, if successful, sends a call home event (number 30999) to
the Install Base and opens a Service Request with Customer Support. If you provide an
email address, Customer Support sends an email to verify that the system reports
mechanism (SyR) has been successfully configured.
Note: The settings in the Register RecoverPoint screen are displayed through both the
Getting Started Wizard the first time you launch Unisphere for RecoverPoint, and by
selecting Admin > Register RecoverPoint each subsequent time Unisphere for RecoverPoint
is launched.
Procedure
1. Register your RecoverPoint system on page 179.
2. Click the Finish button to close the Getting Started Wizard and apply your changes.
A dialog box is displayed allowing you to decide whether or not you would like to display the
Getting Started Wizard in subsequent RecoverPoint launches.
NOTICE It is not recommended to select the checkbox in the pop-up until you have
completed the tasks of adding your licenses, enabling RecoverPoint support, and
registering your RecoverPoint system.
The Status Bar that consistently appears at the bottom of the interface displays the numbers of
alerts that are currently in the system, and their severity (for example, Alerts: 1 Critical, 3 Errors,
3 Warnings. When you click the status bar from any screen in the application, you are redirected
back to The RecoverPoint Dashboard on page 24.
4. Manage Users on page 184, Manage Roles on page 187, and Manage User Authentication on
page 190.
5. Register storage on page 147 and Register resource pools on page 155.
6. (Optionally) Change Security Level on page 195.
When you're done, configure the RecoverPoint system to start protecting your data. This process
is described step-by-step in Protect Volumes on page 39.
In case of a disaster, or simply to perform routine maintenance on your production site, you can
test a copy, recover production or fail over operations to another site. Use cases and procedures
for doing so are outlined in RecoverPoint Recovery on page 128.
Once replication has been configured and started, you normally won’t need more than minimal
involvement with the system.
To troubleshoot your system, if required, refer to The RecoverPoint Dashboard on page 24,
Manage Protection on page 63 and Manage Recovery on page 138.
The types of event notification in RecoverPoint, and how to configure events is detailed in System
Notifications on page 209.
Note: RecoverPoint contains intelligent System Analysis Tools on page 196. Use these tools to
help you make your replication environment as efficient as possible.
Configuring replication
About this task
After you have completed the First steps in RecoverPoint, configure the RecoverPoint system to
start replication. The entire process is described step-by-step in Protecting Volumes.
System analysis
About this task
RecoverPoint contains intelligent System Analysis Tools on page 196 to help you make your
replication environment as efficient as possible.
RecoverPoint support
About this task
If you need support, use the Support tab to easily access all of the RecoverPoint support options
on support.emc.com.
For troubleshooting issues, be sure to collect system information before contacting Customer
Support.
This section describes the RecoverPoint dashboard and how to use it to analyze and monitor
replication in RecoverPoint.
Overall Health To graphically display an overview of the current status of the RecoverPoint
system.
System Limits To monitor how close you are to breaching your system limitations.
Overall Health
The Overall Health tab graphically displays an overview of the current status of the RecoverPoint
system. The overall health tab contains widgets that allow you to easily monitor and analyze the
current state of the system.
The Overall Health tab of the Dashboard contains the following widgets:
l RPA Clusters Map on page 25
l Alerts on page 27
l System Traffic on page 28
l Consistency Group Transfer Status on page 28
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.
When the system detects a problem with one of these major components, the RPA clusters map
displays:
Icon Description
A warning icon on each component that has warnings associated with it.
Note: The errors and warnings in the RPA clusters map widget are also displayed in the Alerts
on page 27 widget.
Hover your cursor over an RPA cluster in the map to display a tooltip with the following links:
Option Description
Display Alerts To display the Alerts dialog box containing the number of alerts registered by
the RPA cluster.
Click Details in the Alerts dialog box to display the alert texts.
Multipath monitoring
About this task
When multipathing monitoring is active, the system analyzes network errors at the level of
individual paths, and generates a warning in the RPA Clusters Map whenever there is not full
redundancy between the RPA and splitters or volumes. Full redundancy is defined as follows:
l For RPA-to-volume links, there must be at least two distinct paths between each RPA and
volume; that is, each RPA has access to at least two storage WWNs (and controllers, where
relevant) via non-overlapping paths.
l For RPA-to-splitter links, there must be at least two distinct paths between each RPA and
each splitter using different RPA ports and host (or switch) WWNs.
When RPA Multipath Monitoring is enabled, the system issues a warning upon logging in regarding
any existing links without full redundancy. In addition, warning events are written to the log.
By default, multipath monitoring is active for all copies, for links both to storage and to splitters.
Alerts
The Alerts widget provides a graphical overview of system health categorized by alert level.
Click the More details link at the bottom-right corner of the graph to display the alerts table.
The alerts table contains system errors and warnings. The errors and warnings are composed of
messages from the System Limits screen, and other general system warnings.
Hover over an error or warning in the table to display a tooltip containing the error or warning
properties.
When relevant, the dialog will show a severity, category, relevant RPA cluster, and description of
the error or warning.
Note: A system limit with a status of Critical equates to an Error in the alerts table. A system
limit with a status of Major or Minor equates to a Warning in the alerts table.
Click the Less details link at the bottom of the alerts table to close the alerts table and display the
Alerts widget.
System Traffic
The System Traffic widget provides a graphical overview of the amount of SAN and WAN traffic
passing through each RPA cluster.
Each consistency group and consistency group copy can be in any one of the following transfer
states:
Transfer Description
State
Paused Data is not being transferred to a copy, because transfer has been paused by
the user.
Paused by Data is not being transferred to a copy, because transfer has been paused by
system the system.
Transfer Description
State
Init (n%) A copy is being initialized, or undergoing a full sweep or volume sweep.
High-load The system enters a permanent high-load state while data is being transferred
to a copy.
High-load (n The system enters a temporary high-load state while data is being transferred
%) to a copy.
Snap idle The link is about to begin or has completed a snap-based replication process.
N/A Data is not being transferred to a copy, because the copy has been disabled
by the user.
The pie chart in the consistency group transfer status widget presents a breakdown of the
consistency groups in the system based on their current data transfer states, as follows:
l Active (green) - includes active, active (synchronized), Replicating snap and Snap idle
l Error (red)
l Init (orange) - includes initializing, high load, and high load (n%)
l Paused (yellow) - includes paused and paused by system
l Disabled (grey) - includes N/A
l Other (brown) - includes flushing, flushing buffer, flushing remote buffer to journal, and
unknown
Note: A consistency group’s transfer state is determined by its most severe link state. For
example, in a RecoverPoint system that is replicating to two copies, if one link is paused and
one link is active, the transfer state will be set as paused.
If there are no consistency groups in the system, the chart will be replaced by the text “No
consistency groups”.
Hover your mouse over a transfer state in the chart to see the names of the consistency groups in
that state.
System Limits
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.
System
The following information is displayed in the System tab:
Column Description
Status OK, minor, major, critical. Indicates how close a monitored setting is to its
limit.
Current Value of The current value of the setting and its limit.
Limit
Groups
The following information is displayed in the Groups tab:
Column Description
Status OK, minor, major, critical. Indicates how close a monitored setting is to its
limit.
Current Value The current value of the setting and its limit.
of Limit
Storage
The following information is displayed in the Storage tab:
Column Description
Status OK, minor, major, critical. Indicates how close a monitored setting is to its
limit.
Current Value The current value of the setting and its limit.
of Limit
Splitters
The following information is displayed in the Splitters tab (not relevant to XtremIO):
Column Description
Status OK, minor, major, critical. Indicates how close a monitored setting is to its
limit.
Current Value The current value of the setting and its limit.
of Limit
System Events
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.
Display events
About this task
To display system events; select Dashboard > 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.
Note: By default, only Normal scope events are displayed, but you can also Filter events on
page 33 to display Detailed events.
Sort events
About this task
To sort the events in the event log by ID, summary, level, scope, point in time, RPA cluster, or
topic, click the relevant column header but you can also Filter events on page 33 based on
advanced criteria.
Filter events
About this task
Filters the events in the System Events on page 32 log, and saves the event filter settings for the
current RecoverPoint user.
Procedure
1. Select Dashboard and click the System Events tab.
2. Click Filter Events. The Event Filter dialog box is displayed.
Setting Values
From The date and time (in GMT) from which events are to be displayed.
Select Unbounded to display the 9000 events preceding the date and time in
the To field.
To The date and time (in GMT) until which events are to be displayed. Select
Unbounded to display all events up until the current date and time.
Events to The IDs of the events that should not be displayed. Multiple event IDs can be
Exclude entered. Separate multiple event IDs with a comma.
Topics The topic of the events to display in the event log. Valid values are:
l RPA cluster
l Splitter
l Consistency group
l Management
l RPA
l Array
Setting Values
Containing Type the terms that must exist in the event summary in order for the event to
the text be displayed in the event log. Use commas to separate multiple terms. Select:
l Match all to display all events containing all of the specified terms in the
event summary.
l Match any to display all events containing any of the specified terms in the
event summary.
Reset to To reset all of the settings in the Event Filter dialog box to their default
Default settings.
OK To close the Event Filter dialog box, and apply the specified settings.
Cancel To close the Event Filter dialog box, without applying the specified settings.
Results
The event info that is copied to the clipboard is in the following format:
This section describes how to protect volumes, and how to monitor and manage protection and
consistency.
l RecoverPoint Protection....................................................................................................... 38
l Protect Volumes....................................................................................................................39
l Policy Templates................................................................................................................... 55
l Group Sets............................................................................................................................ 59
l Manage Protection................................................................................................................63
RecoverPoint Protection
In Unisphere for RecoverPoint, data protection is guided by wizards, and performed through the
Protection menu.
Protect To add a new consistency group and define its protection plan.
Volumes Displays the Protect Volumes wizard to guide you through the process of
defining the production and its protection plan, the copies and their protection
plans, and the production and copy journals and their protection plans.
Group Sets To create or modify sets of consistency groups, perform recovery activities or
periodically bookmark the same consistent point in time, across volumes in
multiple groups, simultaneously.
Manage To manage and monitor existing consistency groups and their protection
Protection plans, control transfer, or bookmark consistent points in time across groups
and sets of groups.
Protect Volumes
Use Protection > Protect Volumes to create consistency groups (CGs) to protect your volumes.
In RecoverPoint, CGs are used to configure protection policies, and set RPO and RTO policies
according to specific resource allocation and prioritization.
l For RecoverPoint with Unity, VNXe, or VNX with RecoverPoint/SE licenses, there is a
limitation of one array per side. If you have a local and a remote copy, make sure the local copy
is stored on the same Unity/VNXe/VNX array as the production copy.
l Ensure you have your RecoverPoint environment planning document describing the groups and
journals you will need to create, the volumes that you will need to define in each, and the RPAs
that will handle the data transfer. If you do not have this document, contact your RecoverPoint
account executive.
Your environment planning document should detail:
n The number of consistency groups that you will need, and their names.
n The LUNs to include in each group, and at each copy.
n The journal LUNs at each copy.
n Which consistency groups to set as distributed.
n The required RPO and RTO settings per consistency group.
n The RPA that will handle the replication of each group.
n The priority of each consistency group with relation to the other groups in the system.
l Decide whether you will want to Initialize from backup on page 247, and prepare accordingly.
When a consistency group is first created, or a replication set is first added to the system, the
system automatically starts a first-time initialization process at the copies (that is,
synchronizing the copy volumes with the production volumes by sending the complete image
of each production volume to each copy’s storage).
Depending on the amount of data being transferred, this process can be both time-consuming
and bandwidth-consuming. To save time and bandwidth, see First-time initialization is taking
too long on page 246.
l If one volume at a copy is on an XtremIO array, all other XtremIO volumes at that copy must be
on the same array.
l If one volume at a copy is on a VMAX3 or VMAX/AF array, all other VMAX3/AF volumes at
that copy must be on the same array.
l Ensure you have mapped all replication LUNs to RecoverPoint WWNs. Only the volumes that
are mapped and zoned to the RPA cluster are displayed in the available volumes list in
RecoverPoint.
Note: In RecoverPoint/SE only, all of the volumes of the Unity or VNX array are displayed
in the available volumes list.
l In VNX storage systems:
n There is a limit on the number of LUNs that are supported per storage group (see the
RecoverPoint Release Notes for this limit).
n If you need more LUNs than are currently available to support your replication sets and
journals, either because you have calculated your system needs or because you have
received a message that you have exceeded “the maximum number of supported LUNs”,
you may be able to create additional storage groups, according to the procedure presented
in Add more LUNs than allowed per VNX storage group on page 256.
l The Unity/VNXe storage system does not use storage groups.
l In Symmetrix VMAX2 splitter environments:
n Volumes attached to VNX splitters and volumes attached to Symmetrix splitters may be
mixed in one consistency group. See the RecoverPoint Deploying with Symmetrix VMAX2
Arrays and Splitter Technical Notes for other splitter-specific limitations.
n If any volume added is a device on a Symmetrix VMAX2 10K, 20K or 40K array, refer to
“Device Tagging” in the RecoverPoint Deploying with Symmetrix VMAX2 Arrays and Splitter
Technical Notes.
l In VNX splitter environments:
n The same consistency group can contain volumes attached to multiple splitters.
n The same consistency group can contain volumes using a VNX splitter to split writes to one
RPA cluster and volumes using a different splitter type to split writes to a different RPA
cluster.
l In Unity/VNXe splitter environments, a consistency group can contain only volumes attached
to Unity/VNXe splitters.
l In VPLEX splitter environments:
n The VPLEX consistency group name will only be displayed in the VPLEX Group column of
the volume list if you Attach volumes to the splitter on page 161 for the VPLEX splitter
(including certificate).
n After you register your VPLEX storage, you will not be able to select VPLEX volumes and
non-VPLEX volumes in the same consistency group copy. It is recommended that all
volumes in a VPLEX consistency group be configured in a single consistency group copy,
and all volumes in a non-VPLEX consistency group be configured in another consistency
group copy.
n A VPLEX MetroPoint consistency group can contain a maximum of one remote copy and
from zero to two local copies. If there is no remote copy, there must be two local copies,
one at each side of the VPLEX Metro.
n To turn a non-MetroPoint group into a MetroPoint group, when the production volume is a
VPLEX distributed volume and there exists no more than one remote copy, Add a copy to a
group on page 101.
n To turn a MetroPoint group into a non-MetroPoint group, Remove a copy from a group on
page 107.
l For replicating Oracle databases, see the instructions on how to replicate an Oracle database,
including using Oracle hot backup procedures with RecoverPoint bookmarks for point-in-time
snapshots and quick testing and disaster recovery in the RecoverPoint Replicating Oracle with
RecoverPoint Technical Notes.
Procedure
1. Select Protection > Protect Volumes.
2. In the Select Production Volumes screen:
a. Define the consistency group name, the production name, and the RPA cluster that will
manage the production.
Icon Description
To filter the volumes in the list by Size, Product, Vendor, Name, UID, LUN, or
VPLEX Group.
Note: The VPLEX Group column is only displayed after you Attach volumes to
the splitter on page 161 for your VPLEX splitter.
c. Optionally, click Modify Policies to define the group policies and copy policies now, or
skip this step and define the policies later.
The policy settings are optional. The default values provide a practical configuration. It is
recommended to accept the default settings unless there is a specific business need to
set other policies.
d. Click Next Define the Production Journal to select journal volumes that have already
been provisioned on storage.
In the Standby Production screen, enter a name for the copy in the Standby production
copy name field before you continue with this procedure.
Procedure
1. Ensure Select Provisioned Journal Volumes is selected.
3. Use the toolbar icons at the top-right corner of the screen to help you identify the required
volumes in the volume 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.
Note: In RecoverPoint/CL and RecoverPoint/EX, only the volumes that are mapped and
zoned to the RPA cluster are displayed in the available volumes list. In RecoverPoint/SE,
all of the volumes of the supported Unity Series and VNX Series arrays are displayed in
the available volumes list.
4. Optionally, click Modify Policy to define the journal policies now, or skip this step and
define the policies later using the Manage Protection screen.
Note: The Modify Policy link is only enabled after volumes are selected in the volume
list.
Procedure
1. Select Automatically Provision Journal Volumes.
Option Description
Journal size Enter a value for the journal size to define an absolute journal size at the
copy.
Predicted Select this option and enter a value for predicted incoming write-rate
incoming write- and required protection window to have RecoverPoint calculate the
rate required journal size based on your consistency group’s predicted write-
rate and a required protection window.
As you change this value, the journal size that is required to sustain the
entered values for predicted incoming write-rate and the required
protection window is dynamically updated in the Calculated journal size
field.
Tiering Policy (Optionally) Select one of the available tiering policies displayed in the
Resource pool provisioning information table below to automatically
apply the policy to the selected volumes.
Back to Select Go back to the previous screen and re-select the production volumes,
Production or (optionally) redefine the production protection policy.
Volumes
3. If there are Available Tiering Policies on storage, you can select a Tiering policy to apply
to the journal volumes from the combo-box at the bottom of the resource pool table now.
4. Select the relevant resource pool from the table.
The following information is displayed for each resource pool in the table:
Information Description
Name The name of the registered resource pool in the RecoverPoint
system.
Type The resource pool type. Valid resource pool types are:
l RAID groups
l Storage groups
l Datastores
Adding a copy
Procedure
1. In the Add a Copy screen:
a. Define the copy name and the RPA cluster that will manage the copy volumes.
Define 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.
Note: If the copy array is VMAX3/AF, click the Select storage group link to identify
each storage group whose volumes are to be added to the copy. The production and
copy storage groups must be identical. In almost all cases, use the Automatically
match volumes button to match the volumes of the currently selected production
and copy storage groups. Only if you want to manually match volumes, click the
Select volume links to add individual volumes to the copy.
Note: If one volume in a copy is on an XtremIO array, all the volumes in the
consistency group at that copy must be on an XtremIO array. Similarly, If one volume
is on a VMAX3/AF array, then all the volumes in the consistency group at that copy
must be on the same VMAX3/AF array. If the copy is on an XtremIO or VMAX3/AF
array, it must be exactly the same size as all other copies in the consistency group. It
cannot be either larger or smaller.
Note: In RecoverPoint/CL and RecoverPoint/EX, only the volumes that are mapped
and zoned to the RPA cluster are displayed in the available volumes list. In
RecoverPoint/SE, all of the volumes of the supported Unity Series or VNX Series
array are displayed in the available volumes list.
Use the toolbar icons at the top-right corner of the screen to help you identify the
required volumes in the volume list. 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.
NOTICE
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.
b. Optionally, click Modify Policies to define the copy policies and link policies now, or skip
this step and define the policies later from the Manage Protection screen.
If you want to change the protection settings using policy templates, in the Link tab, use
the Select Template drop-down to select one of your templates. Click Load to load the
settings in the template and click OK to apply the settings.
Note: The Modify Policy link is only enabled after volumes are selected in the
volume list. You can set a copy policy for the production, however, the copy policy of
the production is only relevant after failover, when the production becomes a copy.
The screen changes to allow you to Select Provisioned Copy Volumes or Automatically
Provision Copy Volumes.
l Select Select Provisioned Copy Volumes and choose a production volume. Click
Select volume, choose the copy volume to which the production volume will
replicate, and skip to step 2.b on page 49.
If there are copy volumes in the system with the same names (case sensitive) and
sizes as production volumes, the system automatically matches them and displays the
copy volumes without you having to select the volume. You can change the copy
volume by clicking the copy volume name link.
Procedure
1. Ensure Select Provisioned Journal Volumes is selected.
3. Use the toolbar icons at the top-right corner of the screen to help you identify the required
volumes in the volume 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.
Note: In RecoverPoint/CL and RecoverPoint/EX, only the volumes that are mapped and
zoned to the RPA cluster are displayed in the available volumes list. In RecoverPoint/SE,
all of the volumes of the supported Unity Series or VNX Series array are displayed in the
available volumes list.
4. Optionally, click Modify Policy to define the journal policies now, or skip this step and
define the policies later using the Manage Protection screen.
Note: The Modify Policy link is only enabled after volumes are selected in the volume
list.
l If you have an XtremIO copy, the following procedure is not relevant. Instead, ensure that the
option Automatically Provision Journal Volumes is selected, select the XtremIO array, and
click Next Display Group Summary.
Note: The journal size for automatically provisioned XtremIO journal volumes is set to 2 GB.
Procedure
1. Select Automatically Provision Journal Volumes.
Option Description
Journal size Enter a value for the journal size to define an absolute journal size at the
copy.
Predicted Select this option and enter a value for predicted incoming write-rate
incoming write- and required protection window to have RecoverPoint calculate the
rate required journal size based on your consistency group’s predicted write-
rate and a required protection window.
As you change this value, the journal size that is required to sustain the
entered values for predicted incoming write-rate and the required
protection window is dynamically updated in the Calculated journal size
field.
Tiering Policy (Optionally) Select one of the available tiering policies displayed in the
Resource pool provisioning information table below to automatically
apply the policy to the selected volumes.
Option Description
Back to Select Go back to the previous screen and re-select the production volumes,
Production or (optionally) redefine the production protection policy.
Volumes
3. If there are Available Tiering Policies on storage, you can select a Tiering policy to apply
to the journal volumes from the combo-box at the bottom of the resource pool table now.
4. Select the relevant resource pool from the table.
The following information is displayed for each resource pool in the table:
Information Description
Name The name of the registered resource pool in the RecoverPoint
system.
Type The resource pool type. Valid resource pool types are:
l RAID groups
l Storage groups
l Datastores
a. Use the following options until the consistency group diagram reflects your
requirements:
Action Description
Edit Opens the Add a Copy screen of the copy whose Edit link you clicked, allowing
you to edit the copy settings, and modify the copy volume configuration,
replication mode, or protection plan.
Delete Removes the copy whose Delete link you clicked, from the consistency group.
Note: You cannot delete the production copy.
Replication Displays detailed volume information on all replication set volumes that have been
Sets defined for the consistency group. Select a row in the replication sets table in the
top section to display the associated volume information in the bottom section.
For each volume the following information is displayed; vendor, array, serial
number, volume, UID, size and VPLEX group.
Click on the replication set name to open the Edit Replication Set dialog box,
and rename the replication set.
Action Description
Start When selected, starts transfer for the group as soon as the group is created.
replication ... NOTICE If a consistency group contains one journal created using automatic
when I click volume provisioning and one journal whose volumes were selected manually
'Finish' this setting will not work and you will have to start transfer for the group
manually.
Add a Copy Opens the Add a Copy screen, allowing you to create another copy, define the
new copy’s settings, and define the copy’s volume configuration, replication
mode, and protection plan.
Finish Note: Before you start transfer to any copy, ensure that the copy volumes
are unmounted from any hosts and any volume groups are deported from the
logical volume manager.
Creates the group, applies all of the specified settings, and starts a first-time
initialization process to synchronize the production volumes to the copy volumes.
Before you click Finish, note the following:
l If First-time initialization is taking too long on page 246, instead of allowing
RecoverPoint to send the initialization data to the copy storage, you can
initialize the copy volumes from a backup disk, saving the time it would
otherwise take to synchronize the data over a WAN or FC connection.
l By default, RecoverPoint writes the first snapshot directly to the copy
storage, bypassing the copy journal. Using the fast_first_init
parameter of the config_link_policy CLI command, you can override
the default setting and write the initialization snapshot first to the journal
(which is more time-consuming but provides greater data protection).
l To enable failover during initialization, set the value of the
allow_long_resync parameter of the config_copy_policy CLI
command to no (default is yes).
Policy Templates
Use Protection > Policy Templates to view or modify existing protection policy templates or
create new protection policy templates, for copies or links.
Policy templates are re-useable pre-defined protection settings for both copies and links.
Three default policy templates are included in RecoverPoint; default copy, default remote link and
default local link.
Policy templates work in the following way, the user:
1. Modifies an existing policy template or creates a new policy template.
2. Applies the settings in the policy template to existing links or copies using the Protect
Volumes wizard or the Manage Protection screen.
Group Sets
Use Protection > Group Sets to create or modify sets of consistency groups, perform operational
and recovery activities, and periodically bookmark the same consistent point in time across
volumes in multiple groups, simultaneously.
Note: Parallel bookmarks cannot be enabled for group sets containing consistency groups with
volumes that reside on an XtremIO array or a Data Domain.
You cannot enable parallel bookmarking for a group set if any of the groups in the group
set are part of another group set that has parallel bookmarking enabled.
c. Ensure that the Enable Parallel Bookmarking checkbox reflects your requirements. If it
is selected, ensure that the Frequency list box contains the required value.
Enabling parallel bookmarking limits the maximum number of groups in the group set to
32. You cannot add or remove groups from a group set with parallel bookmarking
enabled. The parallel bookmarking frequency should be no less than 20 seconds. Parallel
bookmarks cannot be enabled for group sets containing consistency groups with volumes
that reside on an XtremIO array.
d. Click OK.
b. Select or clear the checkboxes of groups in the list of groups to include or exclude them
from the groups set.
You will not be able to enable parallel bookmarking for the group set if any of the groups
in the group set are part of another group set that has parallel bookmarking enabled.
c. Ensure that the Enable Parallel Bookmarking checkbox reflects your requirements. If it
is selected, ensure that the Frequency list box contains the required value.
Parallel bookmarks cannot be enabled for group sets containing consistency groups with
volumes that reside on an XtremIO array. You cannot disable parallel bookmarking if it is
enabled, but you can change the Frequency. Enabling parallel bookmarking limits the
maximum number of groups in the group set to 32. You cannot add or remove groups
from a group set with parallel bookmarking enabled. The parallel bookmarking frequency
should be no less than 20 seconds.
d. Click OK.
Manage Protection
Use the Manage Protection screen to manage and monitor your existing consistency groups and
their protection plans, control transfer, and mark consistent points in time across groups and sets
of groups.
When the Manage Protection screen is first displayed, the Consistency Groups node is selected
in the left pane, and the list of all consistency groups in the system is displayed in the right pane
along with the status of every consistency group in the RecoverPoint system.
Use this screen for monitoring all consistency groups, as follows:
Column Description
Transfer The group transfer status (Paused, Active, Initializing, etc.). When a group is
configured to transfer data synchronously, the word Synchronized is
displayed next to the state of transfer. You can also see the Consistency
Group Transfer Status on page 28 through the Consistency Group Transfer
Status on page 28 widget in the Dashboard.
Alerts The number of alerts that have been logged for a group. If alerts have been
logged, click the link to display the alert texts.
Protected The size of the data that is being protected by the group.
Size
Group Set The group set name, if the group has been added to a group set.
You can also perform the following actions on multiple groups in the system simultaneously, by
clicking the relevant button at the bottom of the screen:
Button Description
Enable Group Enabling a disabled consistency group starts replication and causes a full
sweep.
Disable Only enabled if the selected consistency groups are enabled. Disables the
Group selected consistency groups. Disabling a consistency group stops all
replication, deletes journals, and causes a full sweep when the group is
enabled.
Create Create a bookmark and define snapshot policies across multiple groups on
Bookmark page 124
Group policies
Describes the policy settings for consistency groups.
To display these settings, select Protection > Manage Protection, select a consistency group in
the left pane, and click the Group Policy tab in the right pane.
Setting Description
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. Whether data will transfer when replication is switched to
another RPA depends on the value of the transfer_by_non_preffered
parameter of the config_group_policy CLI command.
Note: Best practice is to ensure that groups that replicate in synchronous
replication mode are set to use different RPAs than groups that replicate
in asynchronous replication mode . Mixing between the two may result in
low I/O rates for the synchronous groups. It is also recommended that
dynamic sync and purely synchronous consistency groups reside on
different RPAs, whenever possible.
Distribute Default=disabled
group writes Only supported if the journal is at least 40 GB.
across
Note: Both enabling and disabling this setting causes the journal of all
multiple
copies in the consistency group to be lost.
RPAs
Setting Description
External Default=none
Application Possible values are None and SRM.
l None: Using an external management application (SRM) is disabled.
l SRM: To enable support for VMware Site Recovery Manager. This option
is only valid if a RecoverPoint Storage Replication Adapter for VMware
Site Recovery Manager is installed on the vCenter Servers. For more
information, refer to the RecoverPoint Adapter for VMware Site Recovery
Manager Release Notes.
Recovery Specifies which copy the external application should fail over to.
Copy
Managed by When any value other than None is selected, Managed By is enabled and you
have the following options:
l RecoverPoint: Check this option for planned or unplanned maintenance
of the RecoverPoint system. When activated, external application support
is disabled and user-initiated RecoverPoint capabilities are enabled. When
activated, RecoverPoint user-initiated capabilities, such as image access,
image testing, changing policies and creating bookmarks are available.
l External Application: When activated, the specified external application
manages RecoverPoint. All RecoverPoint user-initiated capabilities are
disabled. The user cannot access images, change policies, or change
Setting Description
Link policies
Describes the policy settings for the links between two copies.
Setting Description
Asynchronous Default=enabled
When enabled, RecoverPoint replicates the consistency group data in
asynchronous replication mode.
Default=disabled
Setting Description
Default=disabled
Only relevant for synchronous replication mode.
When enabled, RecoverPoint uses dynamic sync mode and alternates
between synchronous and asynchronous replication modes, as
necessary, according to latency conditions (the number of
milliseconds or microseconds between the time the data is written to
the local RPA and the time that it is written to the RPA or journal at
the remote site).
l Start async replication above: When the specified limit is reached,
RecoverPoint automatically starts replicating in asynchronous
replication mode.
l Resume sync replication below: When the specified limit is
reached, RecoverPoint goes back to replicating in synchronous
replication mode.
Setting Description
Default = Low
To compress data before transferring it to a remote RPA cluster. Can
reduce transfer time significantly.
Note: Only relevant for asynchronous remote replication. Both the
enabling and disabling of compression causes a short pause in
transfer and a short initialization. Compression decreases transfer
time, but increases the source RPA’s CPU utilization.
l High: Yields the highest bandwidth reduction ratio and requires
the most RPA resources.
l Medium: Yields an average bandwidth reduction ratio and requires
an average amount of RPA resources.
l Low: Yields the lowest bandwidth reduction ratio and requires the
least RPA resources.
l None: Compression is disabled and requires no RPA resources.
See the RecoverPoint Release Notes for the supported throughput
for each compression level.
Copy policies
To display the copy policy settings, select Protection > Manage Protection, expand a consistency
group, select one of its copies, and click the Copy Policy tab.
Setting Description
Journal policies
To display the journal policies, select Protection > Manage Protection, expand a consistency
group and select one of its copies. Then, click the Copy Policy tab and note the settings in the
Journal Policy section.
Setting Description
Setting Description
Setting Description
Setting Description
Note: For the detailed consolidation policy values to be valid, the first
consolidation policy in the list must be of the shortest duration and the
last policy in the list must be of the longest duration. The first average
snapshot frequency in the list must be lower than the last.
Results
The Status tab displays a graphical representation of the consistency group and copy statuses.
The following information is displayed:
Label Displays
<Group The group name and the RPA which is handling the group data, both of which
Name> can be modified through the group policies. Group policies on page 65
Running on includes more information about group policies.
<RPA>
<Copy The relevant copy and RPA cluster names. The copy name can be modified
Name> at through the copy policies. Copy policies on page 70 includes more information
<Cluster about copy policies.
Name>
Replication A visual representation of the current replication modes and states.
modes and
l A dashed green line means that the system is replicating asynchronously.
states
l A dashed green line on top of a solid line means that the system is
replicating synchronously.
l A greyed out line means that replication has stopped.
Note: The lines move in the direction of replication.
The transfer state is displayed in the center of each link between the
production and the copy. The transfer state displayed here correlates to what
is displayed in the CG Transfer State widget of the system Dashboard.
Role The current role of the copy with regards to failover and regulation.
l Before failover: Production, Local Copy and Remote Copy
l After failover: Target at Production, Local Source and Remote Source
l During regulation: Regulated
Label Displays
Image The image currently being distributed to storage in the distribution phase.
When a group is selected in the left pane, you can click the buttons at the bottom of the Status
tab to perform the following actions:
Button Description
Create Create a bookmark and define snapshot policies for one group on page 123 by
Bookmark providing a bookmark name for the current snapshot.
Add Copy Displays the Add a copy to a group on page 101 wizard, enabling you to add a
copy to the selected consistency group.
Test Copy Displays the Test a Copy on page 128 wizard, enabling you to select and test a
copy of the selected consistency group.
Displays the Test a Copy and Fail Over on page 134 wizard, enabling you to
select and test a copy of the selected consistency group, as well as fail over to
it permanently or temporarily.
Recover Displays the Test a Copy and Recover Production on page 132 wizard,
Production enabling you to select and test a copy of the selected consistency group, and
recover production from it.
Start Only displayed if transfer is paused for the selected consistency group.
Transfer Causes the transfer of writes from the production host to all copies of the
selected consistency group to start.
Pause Only displayed if transfer is active for the selected consistency group. Causes
Transfer the transfer of writes from the production host to all copies of the selected
consistency group to pause.
Note: Best practice is not to use this command. Use Group policies on
page 65 to set policies for use of bandwidth. Pause transfer may be used
when WAN bandwidth is very limited and you wish to give the largest
bandwidth possible to another consistency group. In that case, you may
temporarily pause transfer for lower-priority consistency groups.
Disable Only displayed if the group is enabled for the selected consistency group.
Group Disables the selected consistency group.
Note: Disabling a consistency group stops all replication, deletes journals,
and causes a full sweep when the group is enabled.
Enable Group Only displayed if the group is disabled for the selected consistency group.
Enables the selected consistency group.
Note: Enabling a disabled consistency group starts replication and a full
sweep commences.
Note: When the production copy is on an XtremIO array, only Total Traffic and
Initialization Traffic statistics are available.
l The Total Traffic widget displays the total traffic that the consistency group data
generates on the RPA transferring the group data at the production and copy sites, as
well as between RPA clusters in your RecoverPoint system (in Mb/sec). The total traffic
includes the Initialization Traffic and the Application Traffic.
l The Application Traffic widget displays the traffic that the consistency group generates
on the RPA transferring the group data at the production and copy sites, as well as
between RPA clusters in your RecoverPoint system (in Mb/sec). The application traffic
includes Incoming Writes as well as RecoverPoint replication process traffic.
l The Initialization Traffic widget displays the traffic that the consistency group
generates between copies and RPA clusters in your RecoverPoint system, during
consistency group initialization (in Mb/sec). Initialization traffic can be high, as old
writes are transferred between source and target copies to synchronize between the
production volumes and the copy volumes.
l The Incoming Writes widget displays the writes to the production storage that the
consistency group generates at copies in your RecoverPoint system (in writes per
second), where each write is one I/O to the production storage.
The following statistics are displayed in the Replication Performance sub-tab:
l The Bandwidth Reduction widget displays the ratio by which RecoverPoint was able to
compress the consistency group data that is transferred between RPA clusters in your
RecoverPoint system. The bandwidth reduction ratio includes both data compression
and deduplication.
Note: Compression and deduplication are only relevant for asynchronous replication
to a remote RPA cluster.
The gains realized will vary depending on the compressibility of the replicated data.
Typically, enterprises can save 50% – 90% of their bandwidth by enabling the
compression setting.
NOTICE While enabling compression saves bandwidth, it also increases RPA CPU
utilization, which lowers RPA throughput. See the “Performance” section of the
RecoverPoint Release Notes for the impact of each compression setting on RPA
throughput. Also, both the enabling and disabling of compression causes a short
pause in transfer and a short initialization.
l The Time Lag widget displays the lag of the selected consistency group (in seconds),
when transferring data between all local and remote RPA clusters in your RecoverPoint
system.
l The Write Lag widget displays the lag of the selected consistency group (in writes),
when transferring data between all local and remote RPA clusters in your RecoverPoint
system. The write lag includes any writes generated by RecoverPoint replication
processes as well as internal RecoverPoint overhead.
l The Data Lag widget displays the lag of the selected consistency group (in MB), when
transferring data between all local and remote RPA clusters in your RecoverPoint
system.
Enabling deduplication
Before you begin
l Deduplication is only relevant for asynchronous remote replication.
l Both the enabling and disabling of deduplication causes a short pause in transfer and a short
initialization.
l Data compression must be enabled before deduplication can be enabled.
l Deduplication is only supported in RecoverPoint environments in which all (local and remote)
RPAs are:
n Physical RPAs with at least 8GB of RAM
n Virtual RPAs with at least 4GB RAM
Procedure
1. Select Protection > Manage Protection.
2. In the left pane, select a consistency group.
3. In the right pane, click the Link Policy tab.
a. In the Select link to set policy diagram, select the relevant link.
b. In the Bandwidth Reduction section, if Compression is set to None, enable
compression by changing this value to Low, Medium, or High.
c. Check the Enable Deduplication checkbox.
4. Click the Apply button.
NOTICE There is a short pause in transfer, followed by a short initialization.
6. Note the Current deduplication ratio, and Average deduplication ratio values. These
values are the current (seconds) and average (minutes) bandwidth reduction ratios, of only
the deduplication process.
Setting Value
Normal Normal
High 3 x Normal
Critical 10 x Normal
Note: Changing the default values is optional, as they provide a practical configuration.
It is recommended to accept the default settings unless there is a specific business
need to set other policies.
l Lag optimization is performed per RPA.
l The lag is optimized only if the bandwidth is the cause of the lag. It is not relevant, for example,
if the lag is caused by the distribution process at the remote site (which can happen when
replicating over Fibre Channel).
l The lag optimizer is only relevant for groups replicating asynchronously, that are not
experiencing a high load or an initialization. Groups replicating synchronously are always
prioritized over groups replicating asynchronously.
Procedure
1. Select Protection > Manage Protection
2. In the left pane, select a consistency group.
l The snapshot granularity of all links in the consistency group can be set in the link policies to
no smaller than one second.
l Journal loss will occur when modifying a group’s topology (setting a non-distributed group as
distributed, or setting a distributed group as non-distributed).
l When configuring journals for a distributed consistency group, keep the following in mind:
n All copies of distributed consistency groups must have journals that are at least 20 GB in
size.
n The recommended journal size for distributed groups with snapshot consolidation enabled is
at least 40GB.
n If the capacity of an existing copy journal is less than the minimum journal size required for
distributed consistency groups (see the RecoverPoint Release Notes for this limit) the
consistency group will need to be disabled and then enabled again after you add journal
volumes or change the size of a journal LUN on storage
Enabling a disabled group causes a full sweep.
l Distributed consistency groups are only supported if there is a Fibre Channel connection
between all RPAs in each RPA cluster in the RecoverPoint system, therefore:
n In Fibre Channel environments, make sure all of the RPAs at each RPA cluster are
connected to the SAN through a Fibre Channel switch, and zoned together so that they all
see each other in the SAN.
n Groups running on vRPAs cannot be distributed.
l If any of the primary or secondary RPAs associated with a consistency group becomes
unavailable, there will be a brief pause in transfer on all of the group’s primary and secondary
RPAs, and all of the group segments will undergo a short initialization.
l Under certain circumstances (for example, if one of the primary or secondary RPAs becomes
unavailable) two consistency group segments could be handled by the same RPA.
l In general, distributed consistency groups offer better performance than non-distributed
(regular) consistency groups, as distributed groups run on a minimum of two RPAs (one
primary RPA and one secondary RPA). There is only a small improvement in performance when
a group is run on three RPAs. However, there is a steep improvement in performance when a
group is run on four RPAs.
l The following are example journal configurations for distributed consistency groups:
n One 40 GB volume + optional smaller volumes
n Two 20 GB volumes + optional smaller volumes
n Three 16 GB volumes + optional smaller volumes
n Four 10 GB volumes + optional smaller volumes
Procedure
1. Review the relevant limitations and performance statistics of distributed groups in the
RecoverPoint Release Notes
2. Select Protection > Manage Protection.
3. In the left pane, select a consistency group.
4. In the right pane, click the Group Policy tab
5. Check or clear the Distribute group checkbox. The Secondary RPA checkboxes are
enabled or disabled accordingly.
6. If you are enabling this feature, select one to three secondary RPAs, by checking the
relevant checkboxes in the Secondary RPA section.
Results
The group writes are distributed across the selected RPAs.
After you finish
To monitor each group segment’s performance separately, and in relation to the group as a whole,
detect botttlenecks.
You can tell whether or not a group is distributed by navigating to Protection > Manage
Protection, clicking on a consistency group name in the left pane and looking at the top of the
consistency group’s Status tab. If the group is distributed, the text (primary) followed by a
comma-separated list of numbers indicating the designated secondary RPAs is displayed.
If the group is not distributed, only one RPA is specified in this area. You can also tell which of all
of your groups are distributed by navigating to Protection > Manage Protection, clicking on
Consistency Groups in the left pane and looking in the Active RPA column of the consistency
group table. Distributed consistency groups are displayed with the text (primary) followed by a
comma-separated list of numbers indicating the designated secondary RPAs.
For groups that are not distributed, only one RPA is specified in this column.
4. Open an Internet browser window and connect to an RPA with the address:
http://<RPA IP address>/info
Note: You can connect to the RPA through either an HTTP or an HTTPS connection.
7. Download and unzip the long_term_stats.tar.gz file into a folder on your local machine.
Results
The following table lists the statistics that are output by the export_consolidated_statistics
command. All statistics are valid for the sampled time interval, that is, the difference between the
“time from” and “time to” values on that row.
Table 20 Consolidated statistics output
Incoming IOs rate for link IOs/sec Number of writes that arrived
at a link on the production
side. Average IO size can be
computed as (Incoming writes
rate for link) / (Incoming IOs
rate for link).
Incoming IOs rate for box IOs/sec Number of writes that arrived
at an RPA on the production
side. For concurrent local and
remote replication, this is the
sum of incoming IOs for all
local and remote links (which
is double the actual number of
incoming writes). Average IO
size can be computed as
Incoming IOs rate for site IOs/sec Number of writes that arrived
on the production side. For
concurrent local and remote
replication, this is the sum of
incoming IOs for all local and
remote links at the site
(which is double the actual
number of incoming writes).
Average IO size can be
computed as (Total incoming
writes rate for box) /
(Incoming IOs rate for box).
The Status tab displays a graphical representation of the copy statuses. The following information
is displayed:
Label Displays
<Group The group name and the RPA which is handling the group data, both of which
Name> can be modified through the group policies. Group policies on page 65
Running on includes more information about group policies.
<RPA>
<Copy The relevant copy and RPA cluster names. The copy name can be modified
Name> at through the copy policies. Copy policies on page 70 includes more information
<Cluster about copy policies.
Name>
Replication A visual representation of the current replication modes and states.
modes and
l A dashed green line means that the system is replicating asynchronously.
states
l A dashed green line on top of a solid line means that the system is
replicating synchronously.
l A greyed out line means that replication has stopped.
Label Displays
The transfer state is displayed in the center of each link between the
production and the copy. The Transfer state displayed here correlates to
what is displayed in the Consistency Group Transfer Status on page 28 widget
of the system Dashboard.
Role The current role of the copy with regards to failover and regulation.
l Before failover: Production, Local Copy and Remote Copy
l After failover: Target at Production, Local Source and Remote Source
l During regulation: Regulated
Image The image currently being distributed to storage in the distribution phase.
When a copy is selected in the left pane, you can click the buttons at the bottom of the Status tab
to perform the following actions:
Button Description
Test Copy Displays the Test a Copy on page 128 wizard, enabling you to test the
selected copy of the selected consistency group.
Displays the Test a Copy and Fail Over on page 134 wizard, enabling you to
test and fail over to the selected copy permanently or temporarily.
Recover Displays the Test a Copy and Recover Production on page 132 wizard,
Production enabling you to test and recover production from the selected copy.
Note: Best practice is not to use this command. Use Group policies on
page 65 to set policies for use of bandwidth. Pause transfer may be used
when WAN bandwidth is very limited and you wish to give the largest
bandwidth possible to another consistency group. In that case, you may
temporarily pause transfer for lower-priority consistency groups.
Disable Copy Only displayed if the selected copy is enabled. Disables the selected copy.
Button Description
Note: Disabling a copy stops all replication, deletes journals, and causes a
volume sweep when the copy is re-enabled.
Enable Copy Only displayed if the selected copy is disabled. Enables the selected copy.
Note: Enabling a disabled copy starts replication and a volume sweep
commences.
Controlling RTO
Describes how to set and monitor the RPO at a specific copy.
Procedure
1. Select Protection > Manage Protection.
2. In the left pane, expand a consistency group, and select a copy.
3. In the right pane, click the Copy Policy tab.
4. Control the part of RTO dedicated to data access using the Maximum journal lag setting in
the Journal policies on page 70.
Results
When the system approaches the value of Maximum journal lag, it moves to three-phase
distribution mode.
After you finish
To monitor the RTO:
1. Select Protection > Manage Protection.
2. In the left pane, select a consistency group.
3. In the right pane, click the Journal tab.
The value displayed in the Journal Lag field indicates the RTO in terms of data size.
Alternatively, run the get_group_statistics CLI command to display the journal lag.
Controlling RPO
Describes how to set and monitor the RTO at a specific copy.
Before you begin
Only relevant in asynchronous replication mode
Procedure
1. Select Protection > Manage Protection.
2. In the left pane, select a consistency group.
3. In the right pane, click the Link Policy tab.
a. In the Select link to set policy diagram, select the relevant link.
b. In the Protection Settings, set the RPO policy and click the Apply button.
4. Control the RPO for each consistency group through the RPO setting in the group Link
policies on page 67.
Results
The following table describes the information displayed in the Journal tab of each copy.
Info Description
Storage Storage access status. The current condition of a volume at the copy storage
can be:
l No access, during normal replication.
l Direct Access, during direct image access.
l 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.
Compression Note: This feature is relevant for both synchronous and asynchronous
Ratio replication.
Default = none
When enabled, instructs the target RPA of the consistency group to compress
the snapshots in the journal so that more images (that is, a longer protection
window) can be saved with the same journal capacity (saving storage cost).
Enabling this option is encouraged if you have cost considerations, a low
incoming write-rate, and/or limited bandwidth.
Take note of the following:
l Compression is not available in RecoverPoint/SE.
l Compression is not relevant for the production journal (since the
production journal does not contain snapshots).
l Compression impacts the CPU resources of the target RPA of the
consistency group, and can impact that RPA’s ability to sustain its write-
load. If the target RPA of the consistency group for which you want to
Info Description
Current Indicates how far the copy journal can be rolled back. If the Required
Protection Protection Window is defined, the Current Protection Window will be in one of
Window the following statuses (indicated in parentheses after the Current Protection
Window):
l Sufficient: Image can be rolled back far enough to meet the Required
Protection Window
l Insufficient: Image cannot be rolled back far enough to meet the Required
Protection Window
l Extending: Replication has not been running long enough to be roll backed
as far as the Required Protection Window.
If the Required Protection Window is not defined, the status will be N/A.
Predicted System’s prediction of the eventual size of the protection window. Note that
Protection there is no guarantee on how long it will take to reach the predicted
Window protection window, and no guarantee that it will ever be reached (conditions
may change before it is reached).
If the Required Protection Window is defined, the Predicted Protection
Window is in one of the following statuses:
l Sufficient: Predicted Protection Window is large enough to meet the
Required Protection Window
l Insufficient: Predicted Protection Window is not large enough to meet the
Required Protection Window
If the Required Protection Window is not defined or replication has not
been running long enough to make predictions, no status will be indicated.
It can take 24 hours or longer of journal entries before the system finishes
calculating the predicted protection window.
Note: When snapshot consolidation is enabled, the Predicted
Protection Window value is displayed as N/A.
If a snapshot consolidation job is in process, the following information is also displayed (not
relevant in XtremIO):
Info Description
Stop Cancels the consolidation process. The consolidation process stops after it
completes processing the PIT it is currently working on. Stopping a
consolidation process returns the journal to the same state it was in before
the consolidation started.
The image list in the copy Journal tab displays the following information:
Info Description
Info Description
6. In five-phase distribution mode, note the process steps labeled as Distributor phase 1 and
Distributor phase 2, and note their performance statistics.
7. In three-phase distribution mode, note the process labeled Fast forward distribution
duration, and note the statistics.
The system uses the entered values as guidelines. The actual number of snapshots per
timeframe is displayed beside each policy.
Note: For the consolidation policy values to be valid, the first consolidation policy in
the list must be of the shortest duration and the last policy in the list must be of the
longest duration. The first average snapshot frequency in the list must be higher
than the last.
Results
All of the group protection policies can be modified through the Group Policy tab. Group policies
on page 65 includes more information about group protection policies.
Results
All of the Link policies on page 67 can be modified through the Link Policy tab.
If you have created Policy Templates on page 55, use the Select Template drop-down to select a
policy template. Click Load to load the template settings into the dialog box.
NOTICE After loading a policy template, modify the Link policies on page 67 as required, and
click Apply to use the settings. The settings are not applied until the Apply button is clicked.
Remove a group
About this task
NOTICE This action cannot be undone.
Procedure
1. Select Protection > Manage Protection.
2. Perform one of the following:
l Remove one group by selecting the consistency group in the left pane, clicking the
Status tab, and clicking Remove Group.
l Remove multiple groups by clicking Consistency Groups in the left pane, selecting one
or more groups in the right pane, and clicking Remove Group.
l If the there are VPLEX distributed volumes mapped to the RPA cluster at the production,
and the group contains no remote copies, or one remote copy, the Add a Copy screen
will contain two options for adding a copy.
If you are not a VPLEX Metro user or you do not want to turn a non-MetroPoint group
into a MetroPoint group, skip to the next bullet. If you are a VPLEX Metro user, and want
to turn a non-MetroPoint group into a MetroPoint group:
a. Select the Add Standby > Production Copy radio button.
b. Enter a name for the copy in the Standby production copy name field.
c. In the volume list, mark the checkboxes of each journal volume that you want to use
in your standby production journal.
Use the toolbar options at the top-right corner of the screen to help you identify the
required volumes in the volume 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.
These are the copy journal volumes for the standby copy, not the copy volumes.
d. Optionally, click Modify Policy to define the Journal policies on page 70 now, or skip
this step and define the policies later when you Modify a copy’s protection policies on
page 113.
The policy settings are optional. The default values provide a practical configuration.
It is recommended to accept the default settings unless there is a specific business
need to set other policies.
If you want to change the protection settings using Policy Templates on page 55, use
the Select Template drop-down to select one of your templates. Click Load to load
the settings in the template and click OK to apply the settings.
Note: This link is only enabled after volumes are selected in the volume list.
e. Click Next Display Copy Summary, and continue to the next step.
l Configure the copy settings:
If the group’s production volumes are not VPLEX distributed volumes or the group
contains more than one remote copy, in the Add a Copy screen:
a. Define the copy name, the RPA cluster that will manage the copy volumes, and the
replication mode.
b. 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.
Note: If one volume at a copy is on an XtremIO array, all other XtremIO volumes
at that copy must be on the same array.
The volume list is displayed. The volume list only contains volumes of sizes that are
equal to, or greater than, the specified production volume.
Note: In VPLEX splitter environments, the VPLEX consistency group name will
only be displayed in the VPLEX Group column of the volume list if you Attach
volumes to the splitter on page 161 for the VPLEX splitter (including certificate).
After you enter VPLEX credentials, you will not be able to select VPLEX volumes
and non-VPLEX volumes in the same consistency group copy. It is recommended
that all volumes in a VPLEX consistency group be configured in a single
consistency group copy, and all volumes in a non-VPLEX consistency group be
configured in another consistency group copy.
In RecoverPoint/CL and RecoverPoint/EX, only the volumes that are mapped and
zoned to the RPA cluster are displayed in the available volumes list. In
RecoverPoint/SE, all of the volumes of the supported VNX Series array are displayed
in the available volumes list. See the appropriate technical notes for your splitter for
more information.
Use the toolbar options at the top-right corner of the screen to help you identify the
required volumes in the volume list. 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.
NOTICE 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.
a. Optionally, click Modify Policy to define the Copy policies on page 70 and Link policies
on page 67 now.
The policy settings are optional. The default values provide a practical configuration. It is
recommended to accept the default settings unless there is a specific business need to
set other policies.
If you want to change the protection settings using Policy Templates on page 55, in the
Link tab, use the Select Template drop-down to select one of your templates. Click
Load to load the settings in the template and click OK to apply the settings.
l If the volume that you specified in the last step resides on a Unity/VNXe/VNX array that
has already been registered in RecoverPoint, and a resource pool was already registered
for the same Unity/VNXe/VNX array, the Journal Provisioning Method screen is
displayed.
If you want to allow RecoverPoint to automatically provision your journal volumes for
you, keep the Automatically Provision Journal Volumes radio button selected, and
select one of the following options:
Option Description
Journal size Enter a value for the journal size to define an absolute journal size at
the copy.
Predicted Select this option and enter a value for predicted incoming write-rate
incoming and required protection window to have RecoverPoint/SE calculate the
write-rate required journal size based on your consistency group’s predicted
write-rate and a required protection window.
As you change this value, the journal size that is required to sustain the
entered values for predicted incoming write-rate and the required
protection window is dynamically updated in the Calculated journal
size field.
When you are done configuring your journal settings, click Next Display Copy Summary.
l If you do not want RecoverPoint to automatically provision your journal volumes on
storage, ensure the Select Provisioned Journal Volumes radio button is selected.
For applications running on a host cluster, the journal volumes must not be resources of
the host cluster.
In the volume list:
a. Select the volumes to add to the journal.
On XtremIO arrays, the journal does not need to be larger than 2 GB for non-
distributed consistency groups, 40 GB for distributed consistency groups.
Use the toolbar options at the top-right corner of the screen to help you identify the
required volumes in the volume 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.
b. Optionally, click Modify Policy to define the Journal policies on page 70 now.
The policy settings are optional. The default values provide a practical configuration.
It is recommended to accept the default settings unless there is a specific business
need to set other policies.
If you want to change the protection settings using Policy Templates on page 55, use
the Select Template drop-down to select one of your templates. Click Load to load
the settings in the template and click OK to apply the settings.
c. Click Next Display Copy Summary.
6. In the Copy Summary screen:
a. Select a copy to display its volume details and ensure the copy summary reflects your
anticipated copy configuration:
In RecoverPoint/SE:
l If you selected to Automatically provision journal volumes based on a pre-defined
Journal Size, the Journal Size is displayed at the bottom of the Copy Summary
screen.
l If you selected to Automatically provision journal volumes based on a Predicted
incoming write-rate, and a Required protection window, the Calculated Journal Size is
displayed at the bottom of the Copy Summary screen.
b. Use the following options to create the copy, and optionally, start replication.
Table 26 Options
Action Description
Start replication When selected, starts transfer to the copy as soon as the copy is created.
to copy when I Note: Before you start transfer to any copy, ensure that the copy volumes
click 'Finish' are unmounted from any hosts and any volume groups are deported from
the logical volume manager.
Finish Creates the copy, applies all of the specified settings, and starts a first-time
initialization process to synchronize the production volumes to the copy
volumes.
Before you click Finish, note the following:
Action Description
Procedure
1. Select Protection > Manage Protection.
2. In the left pane, expand the consistency group and select the copy.
Note: If you want to turn a MetroPoint group into a non-MetroPoint group, select the
standby production copy.
3. In the right pane; select the Status tab, click Remove Copy.
The Add Replication Sets wizard opens and the Select Production Volumes screen is
displayed.
Note: For VMAX3/AF, the Select Production Storage Groups screen is displayed, and
you must choose whether the storage group you want to add at production contains
unprotected volumes only, or a mix of protected and unprotected volumes. If all volumes
are unprotected, click the Select storage group link to identify each storage group
whose volumes are to be added to the copy. The production and copy storage groups
must be identical. Use the Automatically match volumes button to match the volumes
of the production and copy storage groups. Alternatively, if the storage group at
production contains a mix of protected and unprotected volumes, click the Select
volume links to add individual volumes to the copy. Use the Volumes links in the
Volumes Details column to display details about the volumes in each storage group.
Use the toolbar options at the top-right corner of the screen to help you identify the
volumes.
The VPLEX consistency group name will only be displayed in the VPLEX Group column if
you have entered the VPLEX storage credentials (including certificate).
When you enter VPLEX credentials, you will not be able to select VPLEX volumes and
non-VPLEX volumes in the same RecoverPoint consistency group copy. It is
recommended that all volumes in a VPLEX consistency group be configured in a single
RecoverPoint consistency group copy, and vice versa.
b. To continue configuring the replication set, click Next Select Copy Volumes.
5. In the Select Copy Volumes screen:
Use the toolbar options at the top-right corner of the screen to help you identify the
required volumes in the volume list.
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 go on 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.
b. When you are done selecting the volumes at each copy, click Next Review Replication
Sets.
6. In the Review Replication Sets screen:
a. Select a row in the replication sets table in the top section of the screen to display the
associated volume information in the bottom section.
b. Click on the replication set name to open the Edit Replication Set dialog box.
7. Click Finish.
Results
All of the consistency group volumes undergo a short pause in transfer and a short initialization,
and a volume sweep occurs on the newly added volumes.
Results
All of the consistency group volumes undergo a short pause in transfer and a short initialization.
Disable groups
About this task
Note: Disabling a group stops replication, deletes all copy journals, and causes a full sweep on
all copies in the group when the group is re-enabled.
Procedure
1. Select Protection > Manage Protection.
2. Disable the group(s):
l To disable one group, select the group in the left pane, click the Status tab, and click
Disable Group.
l To disable multiple groups, click Consistency Groups in the left pane, select one or
more groups in the right pane, and click Disable Group.
Enable groups
Before you begin
l Enabling a consistency group automatically starts transfer.
l Before you start transfer to any copy, ensure that the copy volumes are unmounted from any
hosts and any volume groups are deported from the logical volume manager.
Procedure
1. Select Protection > Manage Protection.
Modifying copies
Use the Manage Protection screen to:
l Modify a copy’s protection policies on page 113
l Pause transfer to a copy on page 114
l Start transfer to a copy on page 114
l Disable a copy on page 114
l Enable a copy on page 115
4. Modify the Copy policies on page 70 and the copy Journal policies on page 70 as required.
5. If you have created Policy Templates on page 55, use the Select Template drop-down to
select one of them, and click Load to load their settings into the dialog box.
6. Click Apply to use the settings.
Note: The settings are not applied until the Apply button is clicked.
Procedure
1. Select Protection > Manage Protection.
2. In the left pane, expand the consistency group, and select the copy.
3. In the right pane; select the Status tab, click Remove Copy, and click yes in the
confirmation dialog box.
Disable a copy
Before you begin
l Disabling a copy stops replication, deletes the copy journal, and causes a volume sweep when
the copy is re-enabled.
Procedure
1. Select Protection > Manage Protection.
2. In the left pane, expand a consistency group, and select the copy.
3. In the right pane; select the Status tab, click Disable Copy, and click yes in the
confirmation dialog box.
Enable a copy
Before you begin
l Enabling a copy automatically starts transfer.
l Before you start transfer to any copy, ensure that the copy volumes are unmounted from any
hosts and any volume groups are deported from the logical volume manager.
Procedure
1. Select Protection > Manage Protection.
2. In the left pane, expand a consistency group, and select the copy.
3. In the right pane; select the Status tab, click Enable Copy, and click yes in the confirmation
dialog box.
NOTICE A volume sweep commences when transfer starts.
Modifying links
Modifies the protection policy of links between consistency group copies.
Procedure
1. Select Protection > Manage Protection.
2. Select the consistency group.
3. Click the Link Policy tab.
Results
All of the Link policies on page 67 can be modified through the Link Policy tab.
If you have created Policy Templates on page 55, select a link in the diagram and use the Select
Template drop-down to select a policy template. Click Load to load the template settings into the
Link Policy dialog box.
NOTICE After loading a policy template, modify the Link policies on page 67 as required, and
click Apply to use the settings. The settings are not applied until the Apply button is clicked.
a. Click the link next to the RPA cluster containing the volume you want to replace.
In the Select Volume dialog box, note the production volume specified in the
Production volume area at the top of the screen.
b. Select the volume to which you want to replicate the specified production volume.
c. Click OK.
Results
Data transfer is briefly paused for the group. A volume sweep occurs on any added volume(s) and
a short initialization occurs on all other volumes in the group, when data transfer re-starts.
It may take a few minutes for RecoverPoint to display the new volume sizes.
l For XtremIO arrays:
a. Select Protection > Manage Protection.
b. Select the consistency group.
c. Select the Replication Sets tab.
Resizing volumes
Before you begin
This procedure is not relevant for XtremIO.
Procedure
1. In RecoverPoint:
Modifying journals
There are two ways to change the storage capacity of an existing journal:
l Add or edit journal volumes on page 119; this process does not trigger a full sweep
synchronization, nor does it erase all history in the existing journal. After this procedure, the
copy can still be rolled back to a previous point-in-time.
l Change the size of a journal LUN on storage on page 120; this process does trigger a full sweep
synchronization, and it does erase all history in the existing journal. After this procedure, the
copy cannot be rolled back to a previous point-in-time.
c. Mark the checkboxes of the volumes that you want to add to the journal.
Clear the checkboxes of the volumes that you want to remove from the journal. Multiple
volumes can be selected.
d. Click OK.
After you finish
If you performed this procedure to enlarge the journal capacity after distributing the writes of this
consistency group across multiple RPAs, disable and then re-enable this group to trigger a full
sweep.
Procedure
1. In RecoverPoint, select Recovery > Test a Copy:
a. Enable access to the Latest Image at the copy containing the journal volume(s), in
Logged Access mode.
b. Exit the wizard without disabling image access.
Note: This ensures that all writes up until the latest image are transferred from the
copy journal to the copy storage, and only the host writes from that point forward
will need to be synchronized at the end of this procedure.
2. In RecoverPoint, disable the copy and remove the journal volume(s). Select Protection >
Manage Protection:
a. In the left pane, expand the group that the journal volume belongs to and select the
copy.
b. In the right pane; select the Journal tab, and click Edit Journal > Volumes. The Edit
Journal Volumes dialog box is displayed.
c. Clear the checkbox of the journal volume whose size you want to change and click OK.
The journal volume is removed from the RecoverPoint system.
3. At the copy’s SAN, dedicate more storage resources to the required LUN(s).
4. In RecoverPoint, click Edit Journal Volumes .
The RecoverPoint SAN discovery utility automatically detects the change in the physical
size of the volume.
Modifying snapshots
All of the points in time (snapshots) created by RecoverPoint are crash-consistent by default. You
can set or modify the Snapshot policies on page 121 of one or more snapshots by using the
following procedures:
l Modify the policies of one snapshot on page 122
l Create a bookmark and define snapshot policies for one group on page 123
Note: To automatically create parallel bookmarks at pre-defined intervals, Create a group
set on page 60.
l Create a bookmark and define snapshot policies across multiple groups on page 124
Use KVSS to Create and mark an application-consistent point in time on page 124.
Snapshot policies
Setting Description
Bookmark The name applied to a point in time snapshot. Bookmarks are used to
uniquely identify a consistent point in time across all volumes in the group.
Setting Description
Mark as The two possible values for this field are Application-Consistentand Crash-
Consistent. All snapshots are Crash-Consistent by default. Select
Application-Consistentfrom the drop down if the selected snapshot is
known to be application-consistent.
Selecting Application-Consistent does not create an application-consistent
snapshot, it only tags the snapshot as application-consistent.
Note: Snapshots are automatically marked as application-consistent by
KVSS during snapshot creation, and can be manually marked by the
user using the Snapshot Policy button. Snapshots marked as
application-consistent have a higher probability of being displayed in
the image list. If snapshot consolidation is enabled, consider selecting
Define a Consolidation Policy for this Snapshot and Never Consolidate
this Snapshot for snapshots that are marked as application-consistent.
Limit the Note: Relevant only for XtremIO and Data Domain copies. For XtremIO,
Retention Time relevant only in RecoverPoint 5.0.1 and later.
for this
Defines the period of time during which a snapshot is to be retained in the
Snapshot
copy journal. When the specified retention time is reached, the snapshot
will be prioritized for deletion with the same rules as all other snapshots.
Note: For Data Domain copies, the Retention policy can only be
changed using the set_backup_copy_retention_policy CLI
command.
4. Enter or modify any of the Snapshot policies on page 121 and click OK.
Delete a snapshot
About this task
Note: Only relevant in RecoverPoint 5.0.1 and later with XtremIO at the copy.
Procedure
1. Select Protection > Manage Protection.
2. In the left pane, expand a consistency group, and select a copy.
3. In the right pane; select the Journal tab, select a snapshot in the list, and click Delete
Snapshot.
Results
The snapshot is deleted.
The RecoverPoint Replicating Microsoft SQL Server Technical Notes and the RecoverPoint Replicating
Microsoft Windows File Systems Technical Notes contain additional detailed information on how to
download, install, and use RecoverPoint KVSS to create application-consistent bookmarks.
KVSS bookmarks are created using the kvss.exe bookmark command.
The working folder for running KVSS commands is %SystemDriver%/
EMCRecoverPointVSSProvider/.
Note: Any bookmarks created using KVSS are automatically marked as Application
Consistent- in the RecoverPoint Snapshot policies on page 121.
When using KVSS to apply bookmarks:
l Surround parameter values with quotation marks.
l You can use the vssadmin list writers command to obtain a list of registered writers on
the host.
l You can use the kvss.exe list command to display the components of each of the writers
found using the vssadmin list writers command.
l You can run the kvss.exe set_credentials command once per Windows user to define
the ip, user and password. After doing so, you will not need to type these values again.
l Multiple writers and groups can be entered simultaneously separated by a space.
To use KVSS in a Microsoft Cluster Server environment with Symmetrix DMX™ storage, the
SPC-2 flag must be enabled on the Symmetrix ports. The syntax is as follows:
kvss.exe bookmark
bookmark=<bookmark_name>
writers=<writer_name> <writer_name>
[groups=<group_name> <group_name>]
[consolidation_policy=never|survive_daily|survive_weekly|survive_monthy|
always]
[type=[FULL|COPY]][ip=<RecoverPoint_cluster_management_ip_address>]
[user=<RecoverPoint_username>]
[password=<RecoverPoint password>]
Where:
l writer = a VSS-aware host application
l group = RecoverPoint consistency group
l bookmark = name by which you can identify the applied bookmark
l consolidation_policy = consolidation policy to set for this snapshot. Valid values are:
n never Snapshot is never consolidated.
n survive_daily Snapshot remains after daily consolidations, but is consolidated in
weekly, monthly, and manual consolidations.
n survive_weekly Snapshot remains after daily and weekly consolidations, but is
consolidated in monthly and manual consolidations.
n survive_monthly Snapshot remains after daily, weekly, and monthly consolidations, but
is consolidated in manual consolidations.
n always Snapshot is consolidated in every consolidation process, whether manual or
automatic.
kvss.exe set_credentials
ip=”10.10.0.145”
user=”admin”
password=”admin”
kvss.exe bookmark
writers="Microsoft Exchange Writer"
groups="exchange\comp1" “exchange\comp2”
bookmark="exchange hourly snapshot"
consolidation_policy=”survive_daily”
To create a bookmark every subsequent time for a Microsoft Exchange application after defining
the ip, user, and password through the kvss.exe set_credentials command:
kvss.exe bookmark
writers="Microsoft Exchange Writer"
groups="exchange\comp1" “exchange\comp2”
bookmark="exchange hourly snapshot"
consolidation_policy=”survive_daily”
This section describes how to test copies, recover from disasters, and migrate to a different
storage system.
RecoverPoint Recovery
In Unisphere for RecoverPoint, data testing and recovery is guided by wizards, and performed
through the Recovery menu.
NOTICE Test a Copy and Fail Over is not relevant in ProtectPoint.
In Unity/VNXe/VNX environments you cannot enable image access in Virtual Access mode to a
snapshot created before replication volumes were resized. To access an image created before
volumes were resized, use Logged Access mode.
In XtremIO, if you enable access to a snapshot that was created before you resized LUNs,
RecoverPoint automatically adjusts the LUNs at the accessed point in time to the resized volume
size.
Test a Copy
Use the Test a Copy wizard to briefly access and test your copy images.
l If you selected a consistency group, select a non-production copy from the list of copies
or the copy diagram.
Selecting an image
Procedure
1. In the Select an Image screen, select the copy image that you want to access.
To test the image, you may want to start with the last image known to be valid. To analyze
data, you generally want the latest image.
2. Unless your copy is on an XtremIO array, you will have to select the required Image access
mode. If your copy is on an XtremIO array, skip this step.
Virtual Access without Roll image in background is preferred. However, if you need to
test images for a longer period of time or need maximum performance while testing, select
Virtual Access and check the Roll to image in background checkbox, or select Logged
Access.
3. Mount the copy volumes that you want to access and import any volume groups.
4. Click Next Test the Image to start enabling image access to the copy volumes.
If any of the groups or copies in a group set are not legal for the requested operation, they are not
displayed in the Relevant copies at target cluster table.
Procedure
1. Use the Test the Image screen to monitor your testing activity.
2. Before you begin testing, wait for image access to be enabled.
If you are accessing the image in logged access mode, wait for the system to roll to the
selected image.
Note the status of the Image access log capacity progress bar. It indicates the amount of
time that you have left to access the image before writes to the copy are blocked and you
will have to add journal volumes, undo writes, enable direct access or disable image access.
3. Test the copy image, to ensure its suitability to your purposes.
While testing the copy image, you can click Roll to Image to physically roll to the desired
image (in Virtual Access mode), Enable Direct Access to bypass the image access log and
write directly to the copy storage, Undo Writes to undo all writes to the copy volumes,
Cancel to disable image access, or Save & Close to exit the wizard without disabling image
access and display the Manage Recovery screen.
Note:
l If you Enable Direct Access you cannot roll back to an earlier image of the accessed
copy if you discover corrupted data. Moreover, in the event of a disaster at the
production during testing, you will not be able to remove any new data written to the
copy during testing unless the group contains another non-production copy.
l Before you Undo Writes, at the copy host, shut down all applications accessing the
group volumes, unmount all copy volumes, and deport any volume groups. After the
writes are undone, at the copy host, mount the copy volumes and import volume
groups to continue testing.
4. When you are done testing, click Cancel to disable image access.
5. At the copy host, stop all applications and unmount the copy volumes. Deport any copy
volume groups.
l If you selected a group set, select a target RPA cluster from the list.
Selecting an image
Procedure
1. In the Select an Image screen, select the image that you want to recover production from.
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.
Starting recovery
About this task
The Start Recovery screen differs depending upon whether you selected a consistency group or a
group set.
If any of the groups or copies in a group set are not legal for the requested operation, they are not
displayed in the Relevant copies at target cluster table.
Procedure
1. Use the Start Recovery screen to monitor your copy testing, and start recovery.
2. Wait for image access to be enabled.
Note the status of the Image access log capacity progress bar. It indicates the amount of
time that you have left to access the image before writes to the copy are blocked and you
will have to add journal volumes, undo writes, enable direct access, or disable image access.
3. Test the copy image, to ensure its suitability to your purposes.
Note the status of the Image access log capacity progress bar. It indicates the amount of
time that you have left before writes to the copy are blocked and you will have to add
journal volumes, undo writes, enable direct access or disable image access.
While testing the copy image, click Undo Writes to undo all writes to the copy volumes
without disabling image access, Cancel to disable image access, or Save & Close to exit the
wizard without disabling image access.
Note: Before you click Undo Writes, at the copy host, shut down all applications
accessing the copy volumes, unmount all copy volumes, and deport any volume groups.
After the writes are undone, mount the copy volumes and import any volume groups to
continue testing.
To recover individual XtremIO production volumes having an XtremIO or Data Domain copy,
click Volumes to Recover....
Note: Not available when recovering production for a group set.
4. Before starting recovery, if necessary, click Undo Writes to remove any writes to the copy
before production recovery. Then, at the copy host, unmount the copy volumes and deport
any volume groups.
Note: If you do not Undo Writes now, any writes made to the copy while image access
was enabled will be transferred to the production when you click Finish. Before you
click Undo Writes, at the copy host, shut down all applications accessing the copy
volumes, unmount all copy volumes, and deport any volume groups. After the writes are
undone, mount the copy volumes and import any volume groups to start production
recovery.
5. Click Finish to start production recovery and display the Manage Recovery on page 138
screen.
Note: After production recovery is complete, the group undergoes a short initialization
to synchronize the new production data at the copies.
l If you selected a group set, select a target RPA cluster from the list.
Selecting an image
Procedure
1. In the Select an Image screen, select the image to fail over to.
To permanently fail over to a copy, you generally want the most recent copy image that you
know to be valid, that was created after placing all consistency group drives into an offline
state at the production. For example, if you are using Microsoft Volume Shadow Copy
Service, you probably want to select the most recent shadow copy.
2. Select your preferred image access mode.
3. Mount the copy volumes that you want to access and import any volume groups.
Starting failover
About this task
The Start Failover screen differs depending upon whether you selected a consistency group or a
group set.
If any of the groups or copies in a group set are not legal for the requested operation, they will not
be displayed in the Relevant copies at target cluster table.
Procedure
1. Use the Start Failover screen monitor your testing activity, and start failover.
2. Wait for image access to be enabled.
Note the status of the Image access log capacity progress bar. It indicates the amount of
time that you have left to access the image before writes to the copy are blocked and you
will have to add journal volumes, undo writes, enable direct access or disable image access.
3. If you are only failing over temporarily, and planning to fail back, skip this step.
If you are failing over permanently; resume production disk activities by placing each
production drive volume used by the consistency group into an online state now.
4. At the copy host, mount the copy volumes that you want to access and import any volume
groups.
5. Test the copy image, to ensure its suitability to your purposes.
While testing the copy image, click Undo Writes to undo all writes to the copy volumes
without disabling image access, Cancel to disable image access, or Save & Close to exit the
wizard without disabling image access and display the Manage Recovery on page 138
screen.
Note: Before you click Undo Writes, at the copy host, shut down all applications
accessing the group volumes, unmount all group volumes, and deport any volume
groups. After the writes are undone, mount the copy volumes and import any volume
groups to continue testing.
6. When testing is complete and you are ready to fail over, if your group only contains one non-
production copy, the failover will be permanent.
At the copy host, unmount the copy volumes and deport any volume groups now.
7. Click Finish.
l If there is only one non-production copy in your group(s), the marking information in the
production journal is deleted, the copy journal is deleted, and the group undergoes a full
sweep before normal replication is resumed.
l If there is more than one non-production copy in your group(s), the Manage Recovery on
page 138 screen is displayed. You can repair the production while your applications and
business operations continue at the copy. When you are done, use the Manage Recovery
on page 138 screen to:
n Fail back to production
n Set your copy (or copies) as production
Manage Recovery
Use Manage Recovery to monitor and manage all of the accessed copies and recovery activities
currently occurring in the system.
The Manage Recovery screen displays an activity bar for each copy (or copies, in the case of a
group set) on which an image has been accessed by RecoverPoint. In each copy activity bar, click
the Show Activity Diagram link to monitor the activity progress and use the Select Next Action
drop-down to complete the activity.
Note: If an action that is part of a recovery activity fails for one or more of the groups in a
group set, you may want to manually perform the action for each group on which the action
failed in order to bring all of the group set's groups to the same recovery state.
Testing a copy
While Testing a copy, click Select Next Action to:
Continue Testing
Opens the Test a Copy wizard to Testing the image on page 130.
Finish Testing
Stops testing and disables image access to the relevant group or group set copies.
Failing over
While Failing Over, click Select Next Action to:
Fail Back to Production
When repairs at the production site are complete, resumes production activities at the original
production site.
Opens the Failover wizard to Starting failover on page 136. In the Start Failover screen, click
Fail Over to start failing back.
Note: The production journal is deleted.
Replication is resumed. The direction of replication is restored from the original production to
the original copies.
After failback, at the copy host(s), unmount the copy volumes and deport any volume groups.
If the group contained more than one non-production copy, the Set Production dialog box is
displayed, prompting you to decide what you want to do with any target copies of the new
production after failover. If you are failing over a group set containing groups with more than
one non-production copy, the Set Production dialog box is not displayed. In this case, before
setting a copy as the new production, you will need to manually Modify a link’s protection
policy on page 100 between the new production and all of the new target copies.
If you want to use a copy, configure a new link for it and define a link policy (not necessary for
Data Domain copies). Removing a copy deletes the copy data and settings from storage.
Disabling a copy retains the copy data and settings on storage.
Note: The journal of the new production is deleted. Replication starts from the new
production to the new copies.
Back to Wizard
Opens the Failover wizard to the Start Failover screen.
Recovering production
While recovering production only Back to Wizard is available. Click Back to Wizard to open the
Recover Production wizard to the Start Recovery screen. In the Start Recovery screen, click
Recover Production to start the recovery activity.
This section describes the RPA Clusters menu and how to use it to manage and monitor replication
in RecoverPoint.
l RecoverPoint clusters..........................................................................................................142
l General Cluster Info............................................................................................................. 142
l Storage................................................................................................................................ 145
l Splitters............................................................................................................................... 157
l RPAs....................................................................................................................................162
l vCenter Servers...................................................................................................................169
RecoverPoint clusters
Monitoring or administration of components in a RecoverPoint system that are managed by RPA
clusters is performed through the RPA Clusters interface. The information for each RPA cluster is
displayed in a separate tab of the interface.
General To display the specified RPA cluster graphically as part of a site map and view
Cluster Info general cluster information, or to display any alerts that may have been logged
for any of the physical components of your RecoverPoint system, at the
selected RPA cluster.
Storage To register arrays, vCenter Servers, and resource pools and manage their
registration in the RecoverPoint system.
RPAs To display the RPA table containing all RPAs in the selected RPA cluster, and
the status and properties of each.
The General Cluster Info section contains a Cluster Diagram and a Cluster Details section that
allow you to easily monitor and analyze the current state of the RPA cluster. The cluster diagram
contains all of the major components of the RecoverPoint system (host, storage, and RPAs) and
the connectivity between them and the RPA cluster. An icon is displayed on any system
component for which system alerts have been registered.
The following information is displayed in the details section below the cluster diagram:
Information Description
RecoverPoint The version of the RecoverPoint software that is currently installed on the
Version RPA cluster.
If the system is in maintenance mode, the RecoverPoint version will display
“N/A System is in maintenance mode”.
Internal RPA The internal system name given to RPA clusters, and used in upgrade
Cluster Name scenarios.
Information Description
Management The IP address assigned to the LAN interface of the RPA cluster in order to
IPv4 define the management interface network, in IPv4 format.
Note: Use this IP to connect to the RPA in the RPA cluster that is running
the cluster control, in IPv4 format.
Management The IP address assigned to the LAN interface of the RPA cluster in order to
IPv6 define the management interface network, in IPv6 format.
Note: Use this IP to connect to the RPA in the RPA cluster that is running
the cluster control, in IPv6 format.
RPA Type The type of the RPA cluster. Valid values are Physical or Virtual.
Information Description
Storage
Use the RPA Clusters > RPA-Cluster-Name tab > Storage link to enable RecoverPoint storage
awareness by registering new arrays, vCenter Servers and resource pools or manage existing
registered arrays, vCenter Servers, and resource pools.
Note: In RecoverPoint, Data Domain block services for ProtectPoint pools are referred to as
resource pools
Results
The Registered Storage table is displayed. The Registered Storage table contains the list of all
of the storage currently registered at the selected RPA cluster with the following storage-specific
information:
Information Description
Information Description
Connectivity Whether or not there is connectivity between the storage and the RPA
Status cluster.
Connectivity Whether the connection between the storage and the RPA cluster is via Fibre
Type Channel (FC) or IP.
Register storage
Before you begin
Note: To add Unity and VNXe storage arrays, do not use this procedure; rather, use the "Add
splitters" procedure.
Procedure
1. Select RPA Clusters, and select the tab of the relevant RPA cluster.
2. In the left pane, click Storage.
Note: You can also register vCenter Servers by selecting RPA Clusters > <RPA-
Cluster-Name> tab > vCenter Servers .
In the right pane, the Registered Storage table is displayed. The Registered Storage table
contains the list of all of the Data Domains, arrays and vCenter Servers that are currently
registered at the selected RPA cluster and their storage information.
3. In the right pane, in the Registered Storage tab, click Add. The Register Storage dialog
box is displayed.
4. In the Register Storage dialog box:
l Register an array seen by this RPA cluster
To register any Data Domain, XtremIO, VPLEX, ScaleIO, VNX, VMAX AF / VMAX3, or
vCenter Server that has already been masked to the RPA cluster:
If the XtremIO Management Server manages more than one cluster, register each cluster
separately.
3. Enter the XtremIO rp_user as the User.
4. Enter the rp_user password as the Password. This password can only be changed using the
XtremIO user interface.
2. Enter the username and password for the block services for ProtectPoint pool and DD Boost
storage-unit in the Username and Password fields.
3. Enter the DD Boost Storage Unit to use as the ProtectPoint catalog.
4. By default, the Use FC for data transfer checkbox is selected. Uncheck to use IP only for
data transfer.
Unregister storage
Unregisters storage from an RPA cluster.
About this task
Note: You can also unregister vCenter Servers by selecting RPA Clusters > RPA-Cluster-
Name > vCenters Server.
Procedure
1. Select RPA Clusters, and select the tab of the relevant RPA cluster.
2. In the left pane, click Storage.
In the right pane, the Registered Storage tab is displayed. The Registered Storage tab
contains the list of all of the storage currently registered at the selected RPA cluster, and its
storage information.
Procedure
1. Select RPA Clusters, and select the tab of the relevant RPA cluster.
2. In the left pane, click Storage.
Note: You can also edit the registration details of a vCenter Servers from the vCenter
Servers on page 169 link.
In the right pane, the Registered Storage table is displayed. The Registered Storage table
contains the list of all of the arrays and vCenter Servers that are currently registered at the
selected RPA cluster and their storage information.
Procedure
1. Select RPA Clusters, and select the tab of the relevant RPA cluster.
2. In the left pane, select Storage.
Information Description
Name The name of the registered resource pool in the RecoverPoint system.
Information Description
l RAID groups
l Storage pools
l Data stores
l vDisk pools
Available The total capacity of the resource pool minus the capacity of the volumes that
Size were already allocated in the resource pool.
Tiers The physical type of the storage. For example, Fibre Channel, SATA, etc.
Available The tiering policies that are available on storage and can be automatically
Tiering applied to volumes in RecoverPoint when users automatically provision
Policies volumes.
3. In the Registered Storage tab, select the array or vCenter Server whose resource pools
you want to unregister.
The Registered Resource Pools table is displayed in the Registered Storage tab. The
Registered Resource Pools table contains the list of all of the resource pools of the
selected array or vCenter Server, that are currently registered at the selected RPA cluster
and their storage information.
Splitters
Note: This section is not relevant in XtremIO, which is a splitter-less solution.
Select RPA Clusters > RPA-Cluster-Name > Splitters to display all of the splitters that have
been added to RecoverPoint, add and remove splitters, and attach or detach volumes from
splitters.
Figure 6 RPA Clusters: Splitters
In RecoverPoint, all installed splitters are automatically added to the system, and all volumes that
are masked and zoned to the RPA are automatically attached to all existing splitters at a site. In
the rare case that a splitter is added to the system after the system is already installed, you will
need to add the splitter to the system, and attach the relevant volumes to the splitter. Multiple
splitters can be attached to one RPA cluster. See the RecoverPoint Release Notes for the limitation
on the maximum number of splitters that can be attached to a cluster.
Results
The Splitters table is displayed in the right pane, with the following splitter-specific information:
Information Description
RPA Link Whether or not there is connectivity between the RPA and the splitter.
When a VPLEX splitter is selected in the Splitters table, the Directors are displayed above the
Volumes Attached to Selected Splitter section.
Information Description
Group The name of the group that the volume belongs to.
Copy The name of the copy that the volume belongs to.
Replication The name of the replication set that the volume belongs to.
Set
Access The data access state of the volume, with regards to the splitter. Once a
volume is configured in RecoverPoint, including attachment to a splitter, the
RPA can place the volume in any of the displayed states.
Also Whether or not the volumes is also replicated by the Symmetrix replication
Replicated technology, SRDF.
by SRDF
Add splitters
Connects the RecoverPoint write-splitters to RecoverPoint.
Before you begin
l Not relevant for XtremIO, which is a splitter-less solution.
l If splitters have been installed on the arrays before installing RecoverPoint, they are added
automatically to the RecoverPoint system, see splitter installation in the RecoverPoint
Installation and Deployment Guide and the RecoverPoint technical notes for the specific splitter
type. However, if a storage array was added to the system after deployment, the splitter will
need to be added to the system.
l All splitters that are masked and zoned to the RPAs are automatically added to the system,
unless they are already attached to another RPA cluster. VPLEX, VNX, and Symmetrix splitters
are automatically added to the system regardless of masking and zoning, unless they are
already attached to the maximum allowed number of RPA clusters. See the RecoverPoint
Release Notes for the maximum number of RPA clusters that can be attached to a splitter.
l Splitters residing on arrays that are not licensed are not automatically added to the system.
l Splitters that are removed by the user are re-added automatically by the system.
l ScaleIO splitters are added to the system after the automatic SAN rescan cycle is complete. If
the ScaleIO splitter is not visible in the system, manually run the rescan_san CLI command.
Note: The Add button is only enabled when there are splitters that are installed on the
storage and ready to add to the system.
4. In the Add Splitter dialog box; select the splitter that you want to add, and click OK.
If the selected splitter is a Unity/VNXe/VNX splitter, both SP-A and SP-B are added when
one of them is selected.
Remove splitters
About this task
Note: You must Detach volumes from the splitter on page 162 before you can remove it from
the system. Only splitters that are not attached to any volumes can be removed.
Procedure
1. Select RPA Clusters, and select the tab of the relevant RPA cluster.
2. In the left pane, click Splitters.
3. In the right pane; select one or more splitters in the Splitters table, click Remove, and click
Yes in the confirmation dialog box. If the selected splitter is a VNX splitter, both SP-A and
SP-B are removed when one of them is selected.
of the volume. Checking the Attach as Clean checkbox overrides the default
synchronization process by informing the system that the copy volume is known to be
an exact image of its corresponding production volume. If Attach as Clean is checked,
and the copy volume being attached is inconsistent with its corresponding production
volume, it will remain inconsistent. To ensure consistency, best practice is not to select
this checkbox and use the default RecoverPoint synchronization process.
RPAs
Select RPA Clusters > RPA-Cluster-Name > RPAs to display all of the RPAs in the RecoverPoint
system and the status and properties of each RPA.
The RPA table displays the following information for each RPA.
Column Description
Status Indicates if the RecoverPoint appliance, LAN interface card, and WAN
interface card are alive.
ID The ID of the RPA. Each RPA in an RPA cluster has an RPA ID that starts with
the string “RPA” and ends with a number from 1-8. Only RPA1 and RPA2 can
run the cluster control.
Management The LAN IP address of the RPA, in IPv4 format. Use this address to open a
IPv4 direct session with an RPA.
Column Description
Connectivity Indicates if communication to all RPAs in the RPA cluster is alive and if the
storage link, repository volume, data link, and communication with the remote
RPA are all alive; if one RPA is down, connectivity of every RPA in the cluster
will report an error.
When an RPA in the RPA table is selected, the tabs at the bottom of the screen display the RPA:
l Properties on page 163
l Status on page 164
l Interface on page 165
Properties
Displays the main properties of each RPA.
Select an RPA in the RPA table, and then click the Properties tab.
Field Description
RPA Cluster The RPA cluster that the RPA belongs to.
ID The ID of the RPA. Each RPA in an RPA cluster has an RPA ID that starts with
the string “RPA” and ends with a number from 1-8. Only RPA1 and RPA2 can
run the cluster control.
Status
Displays the connectivity statuses of each RPA.
Select an RPA in the RPA table, and then click the Status tab.
Field Description
Repository Whether or not the RPA can access the repository volume.
Volume
WAN Interface Whether or not the physical WAN port is alive, the interface card is
functional, and communication with other local RPAs exists.
Communication Whether or not the RPA has access to the remote RPA that it is paired
with Remote with for replication.
RPA Cluster
Data Link Whether or not data can be replicated to the remote RPA that the selected
RPA is paired with for replication.
LAN IPv4 Whether or not the physical LAN port is alive, the interface card is
Interface functional, and communication with other local RPA (if any) exists.
Interface
The Interface tab displays the Fabric Interface settings of each RPA.
Select an RPA in the RPA table and click the Interface tab to display the Fabric Interface settings
for each RPA HBA port. These settings are required when replacing a faulty RPA.
Traffic Statistics
Select an RPA in the RPA table and click the Traffic Statistics tab to display the RPA’s traffic
statistics.
The Traffic Statistics tab displays the following statistics for the selected RPA:
l Total traffic on page 166
l Application traffic on page 166
l Initialization traffic on page 166
Total traffic
Displays the total amount of data that is transferred by the selected RPA in the SAN and between
clusters, in Mb/s.
Application traffic
Displays the total amount of application data that is transferred by the selected RPA in the SAN
and between clusters, in Mb/s.
Initialization traffic
Displays the total amount of data that is transferred by the selected RPA in the SAN and between
clusters during RecoverPoint initialization, in Mb/s.
Usage Statistics
Select an RPA in the RPA table and click the Usage Statistics tab to display the RPA’s resource
usage statistics.
The Usage Statistics tab displays the following statistics for the selected RPA:
l Incoming writes on page 167
l Bandwidth reduction on page 168
l CPU usage on page 168
Incoming writes
Displays the amount of incoming writes that are transferred by the selected RPA, per second.
Bandwidth reduction
Displays the ratio by which the bandwidth usage of the selected RPA is reduced per minute due to
RecoverPoint.
CPU usage
Displays the percent of the selected RPA’s CPU that is utilized per minute.
vCenter Servers
Select RPA Clusters > RPA-Cluster-Name > vCenter Servers to display the vCenter server
table, monitor, register, or remove vCenter Servers. The vCenter user should have the necessary
privileges to perform the desired tasks.
When the vCenter Server's IP address is selected, the bottom pane displays the vCenter Servers
object, and under it, all VMware vCenter Servers registered with RecoverPoint. The view displays
data extracted from the VMware vCenter Server together with RecoverPoint replication data.
In addition to displaying ESX servers and all their virtual machines, datastores, and RDM drives,
the RecoverPoint vCenter Server view also displays the replication status of each volume. The
RecoverPoint vCenter Servers view is for monitoring only (read-only).
Select the vCenter Servers link to:
l Display vCenter Server information on page 170
l Register vCenter Server on page 170
l Edit vCenter Server Registration on page 171
l Remove vCenter Server on page 171
l Rescan vCenter Server on page 171
l Every LUN and raw device mapping accessed by each virtual machine, with the following
details:
n Replication status: fully configured for replication or not configured for replication.
n For LUNs or devices configured for replication by RecoverPoint, the following are
displayed: consistency group, copy (Production, Local, Remote), replication set, and
which datastore for each LUN or raw device mapping is configured for replication.
Setting Description
vCenter IP address of the vCenter Server. This is also the display name of the vCenter
Server IP Server in the top pane.
Certificate If you wish to specify a certificate, browse to and select the certificate file.
Setting Description
vCenter IP address of the vCenter Server. This is also the display name of the vCenter
Server IP Server in the top pane.
Certificate If you wish to specify a certificate, browse to and select the certificate file.
This section describes how to license and register RecoverPoint, how to manage users, roles, and
user authentication, how to configure system notifications, detect bottlenecks in replication,
analyze the load on each RPA, and collect system information for support purposes. This section
also describes how to export statistics and use the statistics tool through the RecoverPoint CLI.
l RecoverPoint Administration................................................................................................174
l Manage Licenses..................................................................................................................174
l Register RecoverPoint......................................................................................................... 178
l Users and Security...............................................................................................................183
l System Analysis Tools..........................................................................................................196
l System Notifications........................................................................................................... 209
RecoverPoint Administration
Administration of RecoverPoint users and the RecoverPoint system is performed through the
Admin menu.
Manage To add or remove your RecoverPoint license files from the system or view
Licenses your RecoverPoint license details.
Register Fill out or update your RecoverPoint post-deployment form and automatically
RecoverPoin send it to the Install Base Group, registering your RecoverPoint product.
t
Users and To manage users, roles, and user authentication. To log off and log back in as
Security a different user, to change the currently logged in user, the password of the
currently logged in user, or after how much idle time to log off the user.
System To detect bottlenecks in replication, analyze the load on each RPA, and collect
Analysis system information for support purposes.
Tools
System To configure system reports and alerts, manage event filters and call home
Notifications events.
Manage Licenses
Select Manage Licenses to add or remove RecoverPoint licenses from the system.
Install a license
Before you begin
l Access and activate your entitlements.
l Obtain a RecoverPoint license file.
Procedure
1. Select Admin > Manage Licenses to display the Manage Licenses screen.
b. Click Browse...
c. Select the license file.
d. Click OK.
Remove licenses
Procedure
1. Select Admin > Manage Licenses.
2. Select the license that you want to remove, and click Remove.
Note: A warning is issued if removing the license may cause the system to exceed the
allowed replication capacity (for example, when an array license is removed but an
existing consistency group contains volumes that reside on the removed array).
b. Click Download to download the file to your computer, select a location on your
computer to store the file, and click Save.
4. Open the exported file:
a. Open MS Excel.
b. Open the *.csv file from the location you selected in the previous step. The Excel Text
Import Wizard is displayed to help you set the import options.
c. In the Excel dialog box, select Delimited, and click Next.
d. In the Delimiters field, select Comma, and click Next.
e. Click Finish.
Note: Check the displayed information against the license file variables for correctness and
Monitor your license limits on page 176 to ensure that you are replicating well within the limits
of your RecoverPoint license.
Register RecoverPoint
Select the Register RecoverPoint menu to fill out or update the RecoverPoint post-deployment
form and automatically send it to the Install Base Group, registering the RecoverPoint product.
2. Click Update Form to display the Update Post-Deployment Form Details dialog box.
Location The city, state and country where the New York, New York, USA
customer is located.
Connect Home The method used to send Software: ESRS (preferred), E-mail,
configuration reports and alerts to Not Allowed
Customer Support. Enabling this Hardware: Not Applicable
feature is recommended as it allows
Customer Service to pro-actively
address issues within your
RecoverPoint environment, should
they arise.
Configure System Reports and Alerts
on page 219 to establish connectivity
for your RecoverPoint environment.
Connect In The method used to allow remote Software: ESRS (preferred), WebEx,
connectivity to your RecoverPoint or Not Allowed
environment. Enabling this feature is Hardware: ESRS (preferred, WebEx,
recommended as it allows secure or Not Allowed
access to your RecoverPoint
environment to gather logs and
c. Click Apply to save each change to the form, without closing the dialog box.
d. Click OK to save all changes and close the dialog box.
NOTICE If your company does not have SyR connectivity, and therefore, you cannot
Configure system reports and alerts on page 221, you can skip the rest of the steps
in this procedure, Export the post-deployment form to a CSV file on page 182 and
Registering RecoverPoint by email or phone on page 183 now.
4. Click Send Form to automatically send the post-deployment form to the Install Base group.
The Send Form dialog box is displayed.
5. In the Send Form dialog box, enter the email address of the person at your company that is
in charge of RecoverPoint maintenance and operation.
Note: Call home event 8000 is sent with the updated registration information and an
email is sent to the specified email address from Customer Support to verify that your
registration details were updated successfully in the Install Base.
l Software serial ID
l Hardware serial IDs for RPAs 1-8
l RecoverPoint software version
l Cluster name
l License type
l Connect home method
l The System ID (identical for all RPA clusters in a RecoverPoint system)
Manage Users
Select Admin > Users and Security > Manage Users to view, add, remove and modify
RecoverPoint users.
Settings Description
Local User
User Name Name of new user to add for appliance-based authentication. A
user name must start with a lower-case alphabetic character. All
subsequent characters must be lower-case alphabetic, numeric,
or hyphen (-). No other characters are legal in user names.
Password Password for new user. All printing ASCII characters are legal in
passwords.
Confirm Password Password for new user. All printing ASCII characters are legal in
passwords.
Settings Description
LDAP User or To add users that already exist in the Active Directory on the
Group LDAP server, and grant them access to the RecoverPoint
appliance.
User Name Name of a user to add to RecoverPoint user list.
Groups Name of a group or groups (in Active Directory) to add to the
authorized users of RecoverPoint.
User Settings
Role The role of the specified local user, LDAP user, or LDAP group.
Only for selected When checked, limits the access of this local user, LDAP user,
groups or LDAP group to the specified consistency groups.
Groups Select the consistency groups that the specified user or group
may access.
c. Select one of the pre-defined roles from the drop-down in the User Settings section.
d. If required, modify the access to specific consistency groups by selecting Only for
selected groups.
e. Click OK.
Remove users
Before you begin
l Only users with security permissions can remove users.
l You cannot remove pre-defined users.
Procedure
1. Select Admin > Users and Security > Manage Users.
2. Select a user.
3. Click Remove.
Manage Roles
Select Admin > Users and Security > Manage Roles to view, add, remove and modify
RecoverPoint roles.
Each RecoverPoint user is defined by a username, a password, and a role. A role is a named set of
access permissions. By assigning a role to users, the users receive all the access permissions that
are defined by the role.
Note: User authorization grants or denies users access to resources managed by
RecoverPoint. User authorization is identical, regardless of whether the user was
authenticated by RecoverPoint or by a Microsoft Windows Active Directory LDAP server. User
authorization can be limited to specific consistency groups.
The following pre-defined roles exist in RecoverPoint:
Role Permissions
security l Security
l Read only
boxmgmt Boxmgmt
Table 39 Permissions
Permission Description
Group Create and remove consistency groups, and modify all group settings except
Configuration the settings that are included in the data transfer, target image, and
failover permissions, may bookmark images, and resolve settings conflict.
Storage Register arrays and vCenter Servers, and update storage registration details
Management for arrays and vCenter Servers.
Data Transfer Enable and disable access to images, and undo writes to the image access log.
Target Image Enable and disable access to images, resume distribution, and undo writes to
the image access log.
Failover Modify replication direction (in temporary failover and recover production),
begin failover, verify failover.
Permission Description
System Configure and manage email alerts, SNMP, System notifications, alert rules,
Configuration licenses, syslog, and other system configuration settings.
Security All commands dealing with roles, users, LDAP configuration, and security level.
3. Enter a new role name and set the required access permissions using the following settings.
Setting Description
Permissions Select the access permissions to be granted to all persons who are assigned
to this role.
4. Click OK.
Remove a role
Before you begin
l Only pre-defined users with security permissions can remove roles.
l You cannot remove pre-defined roles.
Procedure
1. Select Admin > Users and Security > Manage Roles.
2. Select a role.
3. Click Remove, and click yes in the confirmation dialog box that appears.
Settings Description
LDAP Configuration
Base Distinguished Name Node in the LDAP tree from which to start a
search for users:
dc=Klaba,dc=COM
Search Base Distinguished Name Root of the LDAP user search tree. The suffix
of the Search Base Distinguished Name must
be the Base Distinguished Name. The format
will be similar to the following:
cn=Users,dc=Klaba,dc=COM
Binding Type:
To specify the type of binding (authentication against the Active Directory).
Settings Description
Upload certificate from file Select if you want to enter a path to an Active
Directory certificate to use for secure
communication with LDAP server.
To export the certificate and format it in PEM
format:
On the LDAP server, export a copy of the
server certificate from the Active Directory
server. Use the Certification Authority
application's Copy File to … option to export
the certificate in Base-64 Encoded X.509
(.cer) format.
Copy the server certificate to a system with
OpenSSL Certificate Authority software
installed. You can use any Linux or Windows
system.
Log into the system to which you copied the
certificate, and run the following command:
On Linux:
> /opt/symas/bin/openssl x509 -in
AD_certificate_name -out
OpenLDAP_certificate name
On Windows:
> openssl x509 -in drive:/path/AD_file.cer -
inform d -out drive:/path/
OpenLDAP_file.pem
Advanced settings
The advanced settings are optional and can be left at their default values.
3. Click Apply.
4. Test LDAP settings on page 194 to verify that you have configured LDAP correctly.
Change Password
About this task
Select Admin > Users and Security > Change Password to change the password of the currently
logged-in user.
Procedure
1. Enter your current password.
2. Enter the new password in the New Password and Confirm Password fields according to
the password rules of your user's security level.
3. Click OK.
Switch User
Use the following procedure to log off, and log back in as a different RecoverPoint user.
About this task
Select Admin > Users and Security > Switch User to log off, and log back in as a different
RecoverPoint user.
Procedure
1. In the login screen, type the username and password of the user to log in to RecoverPoint.
2. Click Login.
n cannot be reused until at least ten other passwords have been used.
n expire in 90 days.
l When the security level is set to Basic, user passwords must have a minimum of five
characters.
Procedure
1. Select Admin > Users and Security > Change Security Level.
2. Select either High or Basic.
3. Click OK.
Note: You can also access additional system analysis tools through the RecoverPoint CLI. Use
the RecoverPoint CLI to export statistics , export consolidated statistics , and load the
statistics analysis tool.
Detect Bottlenecks
About this task
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.
Procedure
1. Define the Bottleneck Detection Settings as described below. Note that in bottleneck
detection, the entered times are according to the local time and the analysis output is
according to GMT.
Detection Mode
Default=System overview and bottleneck analysis
Type of analysis to perform.
Possible values are System overview and bottleneck analysis, Initialization periods, High
load periods, Initialization, high load, and peak analysis, Advanced analysis, and Peak
analysis.
Start
Default=Earliest available time
Start time for analysis. Possible values are:
l Earliest available time
l A user-specified date and time, where the date and time, if not specified, is the
current local time today.
Note: Enter times according to local time. Output is according to GMT.
End
Default=The current date and time
End time for analysis, where the date and time, if not specified, is the current local time
today.
Advanced Overview
Default=no
Whether the analysis covers a broader set of system performance indicators (yes) or
not (no).
Detailed Overview
Default=no
Whether the analysis is confined to the RPA cluster only (no) or also includes analysis
of the groups and RPAs (yes).
Peak Duration
Default=5 minutes
Includes an analysis of the periods in which the write peaks were of the specified time
duration.
Groups to Include
Note: Not relevant when System overview and bottleneck analysis is selected.
Default=all
The consistency groups on which to perform the analysis. To analyze only global
statistics, without statistics on individual groups, clear all of the group checkboxes.
Action Description
Start New To stop the current analysis and display the screen containing the bottleneck
Analysis analysis settings.
Note: Only available when analysis is in progress.
Balance Load
Use this procedure to analyze the load on each RPA and display a load balancing strategy.
Before you begin
l Load balancing is only available on the RPA running the cluster control, or through the floating
Cluster Management IP. Load balancing does not work if the RPA running the cluster control is
down. If this RPA goes down, and then back up again, 5 minutes must pass before load
balancing can be performed again.
l For best results, groups should be configured and replicating for 7 days before performing load
balancing, so that a long enough traffic history is available for the load balancing analysis.
l The load balancing analysis is performed on all RPAs at all sites.
l Groups can be excluded from the load balancing recommendation. However, even when
excluded from the recommendation, all groups are included in the analysis.
l The load balancing analysis is performed on all RPAs in the environment. If there are three
RPAs in total, and one of them goes down for a week, and it is the primary RPA of a group
included in the analysis, the load balancing recommendation calculations are still based on the
total number of RPAs, as if they were all working. The load balancing mechanism accumulates
group statistics for its calculations, as if groups were always running on their preferred RPAs,
even if flipovers happened during the week.
l Load balancing can identify cases in which distributed group segments do not actually require
four separate RPAs to run on, and recommend RPA assignments based on requirements.
Distributed group segments can be run on different RPAs, or the same RPA, and each group
segment is treated as a separate group in the load balancing analysis and recommendation. If
you are not familiar with distributed consistency groups, it is recommended that you learn how
they work before using the load balancing tool (see the Glossary in the RecoverPoint Product
Guide for more information about distributed consistency groups).
l To ensure consistency, consistency groups are initialized when moving from RPA to RPA.
During switchover, all groups running on the preferred RPA are initialized once when they
move to the non-preferred RPA, and then another time when they switch back to their
preferred RPAs. Therefore, any re-assignment of RPAs during replication should be carefully
planned out, as not to affect the performance of the production host applications.
l Since modifying preferred RPA assignments causes flipovers that cause initializations, if the
load balancing analysis finds that no significant changes in workload or number of consistency
groups have occurred, the mechanism does not recommend preferred RPA re-assignment.
l The load balancing mechanism smooths-out I/O statistics, so that any sudden peaks or lapses
in traffic do not cause it to recommend unnecessary changes.
Procedure
1. Select Admin > System Analysis Tools > Balance Load.
2. Select the consistency groups to exclude from the analysis.
Note: The groups that you select are preceded by an asterisk in the load balancing
recommendation, and their traffic statistics are included in the analysis on which the
recommendation is based.
Action Description
Start New Analysis To stop the current analysis and display the
screen containing the load balancing settings.
Note: This option is only enabled when
analysis is in progress.
Action Description
l 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.
6. Understand the load balancing results:
l If the load balancing recommendation is based on less than 7 days-worth of data, a note
is displayed indicating so.
l One or more of the following load balancing recommendations are displayed:
n No action is necessary. The environment is stable, and groups are evenly distributed
across all RPAs.
n Action is necessary. The environment is not stable because groups are not evenly
distributed across all RPAs. To correct this problem, manually modify the Preferred
RPA of each group.
n Action may be necessary. The environment is stable, although groups are not evenly
distributed across all RPAs, and this uneven distribution may affect future
performance. To distribute groups evenly across all RPAs, manually modify the
Preferred RPA of each group.
l The current preferred and recommended RPA assignments are displayed per consistency
group, along with each RPAs average throughput and incoming write-rate, in a
Recommended Load Distribution table.
Note: For distributed groups, each consistency group segment is treated as a
separate group, and the performance statistics are displayed per group segment.
l Two tables, Traffic per RPA before Application of Recommendation and Traffic per
RPA after Application of Recommendation, are displayed to aid you in the process of
understanding the performance implications on all RPAs, if you do choose to apply the
recommendation. Each RPAs average throughput and IOPS are displayed, and the RPA
with the least amount of traffic is highlighted, in each of the tables.
balance_load_yyyy-mm-dd_hh-mm.txt
Note: Ten load balancing output files are stored in this location at a time. When 10
files have already been stored, the older files are removed to make way for newer
files. The date and time of the output file is indicated in the file name.
NOTICE You can also collect system information around a specific event by selecting
Dashboard > System Events. Then select an event in the event log and click Collect
System Information. The Collect System Information wizard is displayed and the
collection start and end fields are automatically set to 10 minutes before and after the
selected event.
Setting Description
Advanced Optional
Default= disabled
Setting Description
Setting Description
6. In The Test Connectivity screen, review the displayed information to verify that the
configuration settings are correct, and the system can access all RPAs and splitters:
l Verify that the Collection Settings are configured as intended. If required, click Back to
Define Settings to edit the settings.
l 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. If all splitters and RPAs do not have green check marks in their
Status columns, you can collect the information directly from individual hosts on which
the feature is enabled.
7. Click the Finish button to begin the collection process. A progress bar is displayed, and the
collection process begins.
Note: Be patient. The collection process can take awhile, depending on the time span
and the amount of data being collected.
Option Description
Start New Collection Process To stop the current collection process and
display the screen containing the collection
settings.
11. If you enabled the Copy output file to an FTP server option, you can now retrieve the
remote copy of the output file from the FTP server:
a. Open a web browser window.
b. Type the FTP Server Address or DNS name of the FTP server into the address bar.
c. At the login prompt, type the User Name and Password.
d. Browse to the Remote Path .
System Notifications
Use the System Notifications menu to manage event filters, configure system reports and alerts
and manage call home events.
a. Define the event filter settings according to the instructions in the following table.
Setting Description
Topic Select which events to report, according to the component of the RecoverPoint
system on which the events occur:
l All Topics
l Site
l RPA
l Consistency Group
l Splitter
l Array
Groups Only relevant when ‘Topic’ is set to All Topics or Consistency Group.
Select the names of the groups that are to be subject to this filter. There is no
default value for this parameter.
Setting Description
Scope l Normal: To report selected basic events and root-cause events. A root-cause
event returns a single description for a system event that can spawn an entire
set of detailed and advanced events. When Scope=Normal, all of those
detailed and advanced events are filtered out, leaving only the normal events.
This is the default setting, and in most cases, it is sufficient for effective
monitoring of system behavior.
l Detailed: This category includes all events (that is, detailed and normal), with
respect to all components, that are generated for use by users.
l Advanced: In specific cases (for instance, for troubleshooting a problem)
Customer Support may ask you to retrieve information from the advanced log
events. These events contain information that is intended primarily for the
technical support engineers.
Event IDs to The IDs of the Events that are not subject to this filter.
Exclude Note: Use a comma to separate multiple event IDs.
c. Click Finish to save the event filter and exit the wizard.
5. Configure the transfer method on page 213 for each method of transfer that you defined.
3. Enter the values for the fields in the Email tab according to the instructions in the following
table.
Setting Description
Enable Email Select to enable the events defined in any event filters whose method of
Notifications transfer is set to Email to be transferred to the specified server from the
specified sender.
Note: Selecting this checkbox also enables the sending of email alerts to
the specified server address if you enabled both reports and alerts in the
Configure System Reports and Alerts on page 219 screen.
SMTP server Enter the IP address or DNS name of the server to which to send the emails.
address Note: When you click Apply, any change to this field automatically
updates the SMTP server address field in the Configure System Reports
and Alerts on page 219 screen.
Sender Enter the email address that should appear in the sender field of all emails
address concerning sent to the specified server regarding event notifications.
4. Click Apply.
Results
All of the event filters whose Method of Transfer includes Email will be transferred to the
recipients defined in the filter (at the frequency defined in the filter) using the specified server
address and sender.
3. Enter the values for the fields in the Syslog tab according to the following table.
Setting Description
Enable Syslog Select to enable the events defined in any event filters whose method of
Notifications transfer is set to Syslog to be transferred to the specified servers with the
specified label.
Specify (Optional) Specify the syslog server at each RPA cluster to which you wish to
target host deliver notifications. The address may be either in IP or DNS format. A DNS
for address will work only if a DNS server is configured in the RecoverPoint
system.
4. Click Apply.
Results
All of the event filters whose Method of Transfer includes Syslog will be transferred by Syslog
using the specified target host and facilities.
3. Enter the values in the fields of the SNMP tab according to the following table.
Setting Description
Enable Select to enable the RecoverPoint SNMP agent to send all of the events
SNMP Agent defined in any of the event filters whose method of transfer is set to SNMP to
the specified servers with the specified label.
The RecoverPoint SNMP agent must be enabled in order to send SNMP traps
(notification events) and to respond to host-initiated SNMP queries.
Allow secure When selected, only encrypted SNMP queries over secure transport will be
transports enabled; use of community strings and SNMP over an unsecured port will be
only disabled.
Send event When selected, sends SNMP traps (notification events) to the RecoverPoint
traps SNMP agent according to your SNMP trap configuration on page 216. Does
not affect host queries.
Specify trap (Optional) The network management server to which you wish to deliver
destination notifications. The address may be either in IP or DNS format. A DNS address
for will work only if a DNS server is configured in the RecoverPoint system.
SNMP v1 RO If you are using SNMP version 1, enter an SNMPv1 read-only community
community string to enable the use of SNMPv1 community strings. If not enabled, only
SNMPv3 user names with passwords or certificates are enabled.
Setting Description
Note: OpenManage Server Administrator (OMSA) support is available only for systems in
which the RPAs are running on Dell PowerEdge platforms.
OMSA support provides RecoverPoint customers with the ability to:
l Display Dell hardware event notifications, together with RecoverPoint event notifications, in
real-time, through the same management console.
l Collect System Information on page 203 that includes Dell hardware configuration information.
RecoverPoint generates events that result in Simple Network Management Protocol (SNMP)
traps. When an event with predefined characteristics (defined in RecoverPoint and OMSA MIBs)
occurs on your system, the SNMP subagent sends information about the event, along with trap
variables, to a specified management console.
Use the following procedure to view OMSA and RecoverPoint events in real-time.
Procedure
1. Configure SNMP event notification on page 215 to send event traps to your event
management console. Ensure that the Enable SNMP Agent and Send event traps
checkboxes are checked and that the IP address of the machine that has been dedicated as
the event management console is defined as a Trap destination.
2. Install a MIB browser on the machine dedicated as the event management console.
Note: MIB browsers are used to manage SNMP-enabled devices and applications in a
network. MIB browsers enable users to load MIBs, issue SNMP requests, and receive
SNMP traps.
3. Open the MIB Browser on your management console, and
a. Enter the cluster management IP of the RPA cluster into the address bar. The cluster
management IP is a virtual IP address assigned to the RPA that is currently active in the
cluster. In the event that this RPA fails, the cluster management IP address dynamically
switches to the RPA that assumes operation.
b. Enable the MIB browser’s Trap Receiver. In the Trap Receiver, both the RecoverPoint
and OMSA events are displayed in real-time. RecoverPoint events are preceded with
their severity level (Info, Warning, or Error), the Dell OMSA event OIDs have the prefix
1.3.6.1.4.1.674.
After you finish
See the Dell OpenManage™ Server Administrator Version 1.9 SNMP Reference Guide, which can
be found at the Dell website:
http://support.dell.com/support/edocs/software/svradmin/1.9.2/en/SNMP/
4. Modify the event filter settings according to the instructions in Create an event filter on
page 211.
5. Click Next Define Method of Transfer.
6. If necessary, in the Define Method of Transfer screen, modify the methods of transfer. For
each new method of transfer that you define, Configure the transfer method on page 213.
7. Click Finish to save the new event filter settings and exit the wizard.
Depending on the severity of the event, system alerts automatically open a service request with
Customer Support and attach the latest system report to the service request. System alerts are
sent in real-time (at the time that the event occurs), allowing preemptive support for
RecoverPoint issues.
System reports contain the configuration and state of the RecoverPoint system, and they are sent
to the system report (SyR) database every Sunday. Only one system report is sent at a time
(containing the information of all RPA clusters) unless there are connectivity issues between RPA
clusters, or an RPA cluster in the RecoverPoint system is unable to send a system report. In this
case, the problematic RPA cluster sends its own system report. All system reports contain the
name of the RPA cluster that they are sent from.
The following parameters are sent to the System Report (SyR) database and included in any
opened service requests:
Parameter Description
System ID The unique identifier of all activated RPA clusters in a RecoverPoint system.
The System ID:
l Is generated for the first RPA cluster that is added to the system during
RecoverPoint deployment. When adding additional RPA clusters to the
system, the additional RPA clusters receive the System ID of the first
RPA cluster.
l Does not change with upgrades. When upgrading to RecoverPoint 4.0
from previous RecoverPoint versions, the System ID value is taken from
the value of Account ID in the previous RecoverPoint version.
l Can be displayed by running the get_account_settings CLI
command, and can only be modified by Customer Support.
Also known as: Account ID
SSID The Software Serial ID. The unique identifier of an RPA cluster in the
RecoverPoint system. The SSID is the identification that is used by the Install
Base to support equipment that is installed at customer sites, through the
system reporting and ESRS mechanisms.
Note: The format and function of the SSID has changed from previous
RecoverPoint versions.
The SSID is in the format <SN>EID<RPA cluster ID>, where <SN> and <RPA
cluster ID> are described in the licensing section of the RecoverPoint Product
Guide. Its length can be no more than 22 characters, and therefore, the RPA
cluster ID is truncated as required. The SSID:
l Is generated for each RPA cluster when the first license that is related to
the RPA cluster is added to the system. When additional licenses are
added to the system, the SSID of the RPA cluster does not change.
l If no license was added for an RPA cluster, the SSID of that RPA cluster is
empty.
Parameter Description
Site ID The ID used in various global processes as a unique identifier of the physical
location of an RPA cluster.
l Is obtained from the value of the <Site_Info> parameter in the license file
variables. Its value is set by the first installed license for an RPA cluster.
Note: If no license was installed for an RPA cluster, the Site ID of that
RPA cluster is empty.
l Can be displayed by running the get_system_settings CLI command,
and can only be modified by Customer Support.
l Does not change even if the <Site_Info> from which it was generated no
longer exists in any of the installed licenses.
Procedure
1. Select Admin > System Notifications > Configure System Reports and Alerts.
2. Ensure that the Enable System Reports and Alerts checkbox is selected, and the radio
button is set to System reports and system alerts .
3. Ensure that the Compression and Encryption checkboxes are selected.
4. Define the transfer method.
l To transfer system notifications through an SMTP server:
a. In the Transfer Method section, ensure the SMTP radio button is selected.
b. In the SMTP server address field, specify the IP address or DNS name of your
dedicated SMTP server, in IPv4 or IPv6 format.
c. In the Sender email field, specify the email address from which the system
notifications will be sent.
d. Click Apply.
l To transfer system notifications through RecoverPoint’s built-in FTPS server:
a. In the Transfer Method section, select the FTPS radio button.
b. Click Apply.
l To transfer system notifications through an ESRS gateway:
a. In the Transfer Method section, select the ESRS radio button.
b. In the ESRS gateway IP address field, specify the IP address of your ESRS gateway
in IPv4 format.
c. Click Apply.
Note: The connectivity test, if successful, opens a service request containing call home
event number 30999 and sends an email to the specified verification email address from
Customer Support to verify that the system reports mechanism (SyR) has been
successfully configured.
4. Wait 10 minutes.
5. Select Dashboard > System Events and look for event 1020 “Failed to send system
report.”
l If this event does not appear in the event logs, the system notifications mechanism has
been correctly configured.
l If you do receive event 1020, check whether there is an issue with the selected method
of transfer. If a problem exists, fix it, configure system reports and click Test
Connectivity again. If problem persists contact Customer Support.
The RecoverPoint call home feature enables RPAs to continuously monitor their own health, and
the health of the RecoverPoint system, using a pre-defined set of event-filtering rules. The call
home event mechanism uses secure transmissions to automatically notify Customer Support of
potential issues. If a serious problem arises, the call home mechanism automatically detects it and
opens a service request with Customer Support. When the service request is received, Customer
Support engages personnel to address the issues with relevant customer parties, or uses a
configured ESRS gateway to resolve the issue.
The call home event mechanism can be customized to accommodate specific environmental or
customer requirements. Customer Support personnel can create additional call home events, as
required, to meet specific customer needs. They can also permanently disable or temporarily
suppress call home events. For example, if an RPA cluster keeps reporting a problem that
Customer Support personnel are actively working on, the event reporting the issue can be
suppressed for a specified period of time.
Suppress one call home event until a specific date and time
About this task
Use the following procedure to suppress one call home event for a specific period of time.
Procedure
1. Select Admin > System Notifications > Manage Call Home Events
2. Select the event.
3. In the Status area of the bottom pane, select the Suppress Until radio button, and set the
date and time fields.
4. Click Apply.
NOTICE Note the change in the event status in the Status column of the event table. To
enable suppressed events, select the event in the table, change the date and time fields
to the current date and time, and click Apply.
Suppress all call home events until a specific date and time
About this task
Use the following procedure to suppress all call home events for a specific period of time.
Procedure
1. Select Admin > System Notifications > Manage Call Home Events
2. Select the event.
3. Click the Suppress All button under the event list. The Suppress All dialog box is displayed.
4. In the Suppress All dialog box, set the date and time fields, and click OK.
NOTICE Note the change in the status of all of the events in the Status column of the
event table. To enable all of the suppressed events, click Suppress All, set the date and
time fields to the current date and time, and click OK.
This section describes all of the RecoverPoint support options and how to quickly access your
Recoverpoint documentation, product support, or online community of users from within
Unisphere for RecoverPoint.
l RecoverPoint Support.........................................................................................................230
RecoverPoint Support
Unisphere for RecoverPoint product support is accessed through the Support menu.
RecoverPoint Documentation
Procedure
1. Click Support > RecoverPoint Documentation.
Online Support
Procedure
1. Click Group > EMC Online Support.
When clicked, the RecoverPoint community page is displayed, enabling you to join the
community, start a discussion or view feeds.
2. Interact with other RecoverPoint users and share best practices and tips, or communicate
directly with the experts responsible for the RecoverPoint family.
This section describes occurrences in RecoverPoint, how to identify them, and how to mitigate
them from a user’s perspective.
Licensing RecoverPoint
This section describes how to license new RecoverPoint purchases, and upgrade your
RecoverPoint license.
License RecoverPoint
RecoverPoint license activation is performed through Online Support at http://support.emc.com.
1. Immediately on submission of the sales order, a LAC email is sent to the address provided
during order entry, containing a new License Authorization Code (LAC) for all of the purchased
entitlements. A sales order can contain multiple LACs. In this case, a separate LAC email is sent
for each LAC contained in the sales order.
2. Click the Click here link in the LAC email to automatically access the RecoverPoint licensing
area of the Online Support site and display all of the entitlements that are associated with the
LAC.
3. In the RecoverPoint licensing area of the Online Support site, activate and generate a License
File for each entitlement. You generate a separate license for each RecoverPoint license model
that is associated with each unique array or RPA cluster.
4. Install the license files on the RecoverPoint system through Unisphere for RecoverPoint.
4. In the LAC Request screen, click Manage Entitlements to display the Search
Entitlements screen:
A unique LAC is usually generated and emailed to you for each purchase, but this is not always the
case for evaluation licenses or purchases of certain products. Also, in some cases (such as the
addition of multiple arrays in RecoverPoint/EX), multiple LACs are generated and multiple LAC
email messages are emailed to you.
To start the licensing process:
l If you have the LAC emails, for each LAC, use the Click here link in the LAC email to
automatically access the Powerlink licensing area of Online Support, and display all
entitlements that are associated with the LAC. Then, activate the entitlements.
Note: If you do not have the LAC email, search for an email containing License
Authorization in the subject line. If you still cannot find the LAC email messages, contact
Worldwide Licensing Support at: https://powerlinklicensing.emc.com/poeticWeb/session/
license_request_emc.jsp
l If you have the sales order numbers, search for entitlements associated with a sales order.
The link in the LAC email pre-populates the LAC field and searches for all entitlements that
are associated with the specified LAC. All relevant entitlements are displayed.
a. Select ONE entitlement to activate. Each entitlement must be selected and activated
separately. There can be multiple RecoverPoint models that are listed under each
entitlement.
b. Click Start Activation Process. The Search Machines dialog box is displayed.
c. In the Search Machines dialog box, click Add a Machine. The Add Machine dialog box
is displayed.
d. In the Add Machine dialog box, type a new machine name, and click Save.
A machine name is like a folder, it is used to group items together logically. A unique
machine name must be specified for each entitlement. Machine names can be whatever
unique name you choose but it is best practice to relate the machine name to the Locking
ID. For example, in RecoverPoint/SE and RecoverPoint/EX, the Locking ID is an array
serial number. Therefore, the machine name should be RP-APM00120701240 if
APM00120701240 is the array serial number that is used for the Locking ID. In
RecoverPoint/CL, the Locking ID is the RPA Cluster ID, so the machine name should be
the RPA Cluster ID.
2. In the Register screen, verify the machine name, and click Next.
3. In the Activate screen, enter the Locking ID, and click Next.
The Locking ID is the field that is displayed under the Machine Information column; its
value is whichever entity the license is enforced to.
Depending on the entitlement, the Locking ID can be either an RPA Cluster ID (in
RecoverPoint/CL), or an array serial number (in RecoverPoint/SE and RecoverPoint/EX).
To display instructions for finding your RPA Cluster IDs and array serial numbers, either click
the Locking ID help link or see Find your RPA cluster IDs on page 260, Find your XtremIO
cluster IDs on page 260 and Find your array serial numbers on page 258.
4. In the Confirm screen, type the email addresses of the recipients of the license file in the
Email to field of the Additional Email Options section, and click Finish.
By default, the customer contact that is provided during order entry and the user
performing the entitlement activation are automatically emailed an activation certificate
containing the license file as an attachment. You can type multiple email addresses in the
email to field. Separate multiple email addresses with commas. You can also include optional
comments which are displayed in the certificate email in the email comments field, or add
optional notes which can only be viewed online in Powerlink Licensing in the Notes for this
transaction section.
5. In the Complete screen, click Save to File to download the license file and save the file
locally. The resulting license file has a *.lic extension and is in plain text format (can be
opened in any text editor).
6. Redo this procedure from Step 1: Quickly access entitlements on page 236 for each
entitlement in each LAC email or sales order.
7. After you have turned all of the entitlements into license files, physically transfer the license
files to the computer from which you will be running Unisphere for RecoverPoint, so you can
install them in the RecoverPoint system.
from the date of upgrade. After that, you must have installed one or more permanent license
files to replicate with RecoverPoint appliances.
Procedure
1. Open a Service Request with Customer Support:
You can open the Service Request yourself or have a representative open the Service
Request for you.
To have a representative open the Service Request for you:
l Call 24/7 License Key Live Support for North America, EMEA and APJK by dialing
1-800-782-4362, selecting option 4, and selecting option 4 again.
l Go to http://support.emc.com and click the Live Chat button.
To open the Service Request yourself:
a. Go to http://support.emc.com
l When upgrading to RecoverPoint 4.0, previous licenses will automatically be
converted to the new license format. The new licenses are temporary and valid for 90
days from the date of upgrade. After that, you must have installed one or more
permanent license files to replicate with RecoverPoint appliances.
l Existing Online Support users, when prompted, enter your Support username and
password.
l New Online Support users, click Register Now and complete the registration
process.
b. In Online Support, click Service Center in the main toolbar, and then click Create a
Service Request.
c. Fill out the fields in the service request according to the instructions in the following
table:
Field Value
Search by Site This is the geographical location of the data center for which you are requesting
ID the license. If you know the site ID, enter it in this field.
If you don't know the site ID:
Expand the Advanced Site Search.
Enter your company name and details.
Click Search.
Select the relevant site ID in the Search Results table.
Note: If you don't see your company’s site ID in the list, contact Customer
Support.
Product Select the Choose from all EMC Products radio button.
Details Start typing the product name into the field to bring up all of the relevant
products.
Field Value
Select the product for which you are requesting an upgrade from the search
results.
Version Select the version number of the product that you want to upgrade from the
Number drop-down.
Contact Information
Primary Your license will be emailed to the email address specified here.
Contact Name Select the name of the primary contact person at your company for
RecoverPoint management.
Note: If the email address/es listed under the primary contact name are
incorrect or missing, edit them to update the contact information.
Problem Details
Problem Type the following text into the problem summary field:
Summary License Upgrade Request for SO#: <The Sales Order Number of Your Last
RecoverPoint Purchase>
d. When you’re done filling out the SR details, click the Submit button. An SR Tracking
number is displayed. Write this number down and save it for future reference.
Note: In most cases, 48 hours after submitting your service request, your
RecoverPoint licenses will be emailed to the specified email address. If you have not
received your RecoverPoint licenses within a month from the time you submitted
your service request, contact Customer Support.
If The Getting Started wizard on page 16 is not displayed, install your license files using
Manage Licenses on page 174 and Configure System Reports and Alerts on page 219.
Presalessupportcenter@emc.com
licensing@emc.com
You can enable or disable the display of the Upgrade Recommendation dialog box using the
Admin > System Notifications > System Reports and Alerts screen, by clearing or marking the
Enable New Release Notification checkbox. It is enabled by default.
If you connected to RecoverPoint using the management (floating) IP address, note the relevant
cluster name in the Upgrade Recommendation dialog box, as the dialog box is displayed per RPA
cluster.
n For upgrade to RecoverPoint 4.0.x—Download the Simple Support Matrix from https://
elabnavigator.emc.com/vault/pdf/EMC_RecoverPoint_4.0.x_ESSM.pdf
2. In the Set Time Display dialog box, select the radio button of your preferred time display
option.
NOTICE Local time is the local time at the RPA that Unisphere for RecoverPoint is
connected to.
Results
The time display option you choose will be used by RecoverPoint when performing operations
which require a time stamp such as collecting system information and logging events.
NOTICE First-time initialization can cause changes in the partition table of the copy volume or
volumes. In a Windows environment, you must clear the OS cache before changing the
partition table of a copy volume. To clear the OS cache, disable the LUN or LUNs on which the
volume resides, and re-enable it. You can do so from the “Disk drives” interface of the
Windows Device Manager.
You can initialize new consistency groups by creating a backup of your production volumes,
physically transferring them to the remote site, and copying the backup images onto the remote
storage volumes.
During this process, applications at the production site can be running or not. Although transfer is
paused during this process, unless the production host is completely shut down during the creation
and physical transfer of the production image to the remote site, the host applications keep writing
to storage. In this time, the production and copy volumes become inconsistent, and any writes to
production volumes during this process are subsequently synchronized, upon completion of the
process, and start of transfer.
Only synchronizing the changes made to the production volumes during this time results in a
relatively small amount of additional traffic, and takes substantially less time than to synchronize
over IP or Fibre Channel.
If your consistency group contains more than one non-production copy, for all other
copies, the journal is erased and all journal history is lost.
10. At the remote RPA cluster, if the group contains more than one non-production copy, Start
transfer to a copy on page 114 to all of the other copies.
bottleneck in the system, the system will regulate the host applications instead of entering a High
load state.
Link policies on page 67 includes more information about the RPO setting.
l In the consistency group Status tab of the GUI, the Role of a copy becomes Regulated and is
displayed in red.
n In the consistency group or copy Status tab, the transfer state of a copy becomes High
load.
n In the Consistency Group Transfer State widget in the Dashboard, a state of Init
(orange) is displayed for the group.
l If the system was in initialization mode, and the journal volume became full, while the value of
the allow_long_resync parameter of the config_copy_policy CLI command is set to
no.
– In the consistency group Status tab, by selecting Protection > Manage Protection,
selecting a group, and clicking the group’s Status tab.
– In the Consistency Groups Transfer Status widget of the Dashboard of the Overall
Health tab, groups undergoing temporary high load are labeled Init (orange).
l I/O throttling can only be configured using the RecoverPoint CLI or REST API. You cannot
configure I/O throttling using the Unisphere for RecoverPoint GUI.
l I/O throttling can only be configured for arrays and vCenter Servers that have been mapped
to, and are therefore seen by, the RPA cluster.
l When selecting to configure I/O throttling for all arrays or vCenter Servers seen by an RPA
cluster, the performance of all consistency groups residing on the same array or vCenter
Server is affected. For example, setting the throttling level to high limits the I/O rate of all
RPAs in an RPA cluster to a maximum read-rate of 50 MBps, per array or vCenter Server.
l The higher the throttling level, the longer initialization will take. Ensure that a low throttling
level is insufficient before setting the throttling level to high.
l You must be logged into RecoverPoint as an admin user to configure I/O throttling.
l To ensure efficiency, RecoverPoint sends I/Os to storage in parallel. The I/O throttling
mechanism regulates parallel I/Os in the following way:
n When set to low, the I/O throttling mechanism allows for a maximum of 10 MB of parallel
I/Os per second.
n When set to high, the I/O throttling mechanism allows for a maximum of 1 MB of parallel
I/Os per second.
n When set to custom, the I/O throttling mechanism allows for a maximum of
<CustomValue>/20 of parallel I/Os. For example, if the custom value is 40 MBps, the I/O
throttling mechanism allows for 40/20=2 MB of parallel I/Os per second.
l In previous RecoverPoint versions, I/O throttling was only available per RPA cluster.
Therefore:
n When upgrading to RecoverPoint 4.1 from a previous RecoverPoint version, the I/O
throttling settings in the previous RecoverPoint version are applied per array and vCenter
Server that are seen by the RPA cluster at the time of the upgrade. Any arrays or vCenter
Servers that are mapped to the RPA cluster after upgrade require additional I/O throttling
configuration.
n If the RecoverPoint system contains at least one RPA cluster running a RecoverPoint
version before RecoverPoint 4.1:
– You can not set the I/O throttling level per array or vCenter Server.
– The I/O throttling settings of all RPA clusters are the RecoverPoint 4.0 and earlier
version.
Note: See the RecoverPoint 4.0 version of the RecoverPoint Administrator’s Guide
and the RecoverPoint CLI Guide for the I/O throttling settings if at least one of the
RPA clusters in the RecoverPoint system is running a RecoverPoint version before
4.1.
About this task
Use the following procedure to enable I/O throttling for a specific array or vCenter Server.
Procedure
1. Run the config_io_throttling command in the RecoverPoint CLI.
2. Select the RPA cluster to which the array or vCenter Server is mapped.
3. Select the array or vCenter Server from the list.
4. Set the throttling level: Set the throttling level to low to limit the I/O rate of the specified
array or vCenter Server to a maximum read-rate of 200 MBps.
l Set the throttling level to high to limit the I/O rate of the specified array or vCenter
Server to a maximum read-rate of 50 MBps.
l Set the throttling level to custom, and specify the custom value in MBps to limit the I/O
rate of the specified array or vCenter Server to any other read-rate.
l Set the throttling level to none to disable I/O throttling on the specified array or vCenter
Server.
5. To enable I/O throttling for all arrays or vCenter Servers that are mapped to an RPA cluster:
a. Run the config_io_throttling command in the RecoverPoint CLI.
b. Select the RPA cluster to which the arrays and/or vCenter Servers are mapped.
c. Scroll down to the bottom of the list of seen arrays and vCenter Servers, and select the
last option in the list.
d. Set the throttling level:
l Set the throttling level to low to limit the I/O rate of all RPAs in an RPA cluster to a
maximum read-rate of 200 MBps, per array.
l Set the throttling level to high to limit the I/O rate of all RPAs in an RPA cluster to a
maximum read-rate of 50 MBps, per array.
l Set the throttling level to custom, and specify the custom value in MBps to limit the I/O
rate of all RPAs in an RPA cluster to any other read-rate, per array.
l Set the throttling level to none to disable I/O throttling of all RPAs in the specified RPA
cluster.
Results
The read-rate of the RPA on which the consistency group is running is limited to 50 MBps, 200
MBps, or the specified custom setting divided by the number of RPAs in the cluster.
RecoverPoint requires the following types of volumes at both production and remote copies:
l Replication
l Journal
In VNX storage systems, the number of LUNs per storage group is limited. This limit is typically
256, 512, or 1024, depending on the specific VNX model, as presented in the RecoverPoint Release
Notes.
How can I verify that the storage groups were added successfully?
About this task
Upon successful completion of registration (which may take between several minutes and an
hour), the event, “Registration of all the site RPAs’ initiators with the CLARiiON array is
complete.”, is generated for each site.
NOTICE spaddress is the address of SPA or SPB, not the control station.
Cluster:
SiteC:
Splitters:
SYMM- 000194900874
Status: OK
VPlexcli:/> ls -t /engines/*::top-level-assembly
/engines/engine-2-1:
Name Value
------------------ --------------
top-level-assembly FNM00104500511
/engines/engine-1-1:
Name Value
------------------ --------------
top-level-assembly FNM00104500511
In RecoverPoint, run the get_splitter_states CLI command to display the array serial
number.
Cluster:
ClusterA:
Splitters:
FNM00104500511
Status: OK
Figure 8 on page 262 contains some common examples of RecoverPoint licenses. One license file
can include multiple licenses. Each license starts with the word INCREMENT.
The following table described the variables in the license file, and their possible values.
You can use iostat (UNIX) or perfmon (Windows) to determine the value for D data per second.
The default image access log size is 20%, and it can only be changed using the RecoverPoint CLI.
See the RecoverPoint Release Notes for the minimum and maximum journal size limitations.
Journal sizing with snapshot consolidation must consider the incremental change of data over the
period of consolidation. Therefore, when snapshot consolidation is enabled, the formula for
estimating the minimum required journal size is:
MinJournalSize =
SpaceForMarkingAndReplication
+ AvgHourlyChangeRate
* (UnconsolidatedDuration
+ DailyConsolidations
+ WeeklyConsolidations
+ MonthlyConsolidations)
/ spaceAfterConsolidationProcess
/ spaceAfterImageAccessProcesses
* spaceAfterCompression
Note: See the RecoverPoint Release Notes for the minimum and maximum journal size
limitations, when snapshot consolidation is enabled.
For example, if an application has the following requirements:
l An average data change rate of 0.5MBps
l An image access log size that is 20% of the total journal size
l A distributed consistency group
l A 12-hour unconsolidated duration (protection window)
l 10 daily snapshots
l Two weekly snapshots
l Three monthly snapshots
l Journal compression is disabled
The minimum size for the journal at this copy would be calculated as (if performance data was
unavailable for the localities of reference):
MinJournalSize = 6
+ { [0.5*(60*60/1024)]
* 12
+ [24 + (10-1)*24*(1-0.20)]
+ [7*24*(1-0.20)+ (2-1)*7*24*(1-0.20)*(1-0.20)]
+ [7*24*4*(1-0.20)*(1-0.20)+(3-1)*28*24*(1-0.20)*
(1-0.20)*(1-0.20)]
/ (1-0.25)
/ [1-(0.20 + 0.10)]
* (1-0)}
Where:
Field Description
Field Description
Field Description
Field Description
Field Description
Field Description
Field Description
a. You can use iostat (UNIX) or perfmon (Windows) to determine the value for Δ data per
second.
3. Click Add Copy and follow the instructions in Add a copy to a group on page 101.
4. Add a standby production copy
Results
The group becomes a MetroPoint group.
Note: Follow the instructions in Remove a copy from a group on page 107 and remove the
standby production copy to turn a MetroPoint group into a regular group.
This section describes all of the events issued by the RecoverPoint system.
Normal Events
The following table contains the Normal scope events that are issued by the RecoverPoint
system.
4019 Group Warning Group under high Group in high load -- transfer -
load to be paused temporarily
4021 Group Error Initialization paused Initialization has been paused To complete initialization, add
because the journal is full. journal volumes to the journal
or enable long initialization.
4023 Group Error Transfer paused Transfer has been paused To restart transfer, first
because the journal is full. disable access to the
accessed image.
4027 Group Error Group under high Roll to the physical image will -
load be paused and transfer will be
paused.
4057 Group Error Specified image The specified image has been -
removed from removed from the journal.
journal
4091 Group Error Image access log is Access to copy volumes for -
full this group at this RPA cluster
has been disabled. If you do
not wish to retain the writes
that were added to the copy
image while image access was
enabled, disable image access;
the relevant writes are
automatically undone.
Alternatively, use the undo
writes command to undo the
same writes; image access
remains enabled.
- If, however, you wish to
retain the writes that were
added to the copy image while
image access has been
enabled, you must increase
the size of the copy journal by
adding one or more volumes
to the journal. Alternatively,
you can set the image access
mode to direct; however, in
that case, the copy journal is
erased, and a full sweep
resynchronization will be
required to restore
consistency between the
production and copy images.
- To help prevent this problem
from recurring, increase the
size of your image access log,
using one or both of the
following:
- - Add volumes to the journal.
- - Modify the policy setting
for the portion of the journal
allocated to the image access
log. This is permitted only
when image access is
disabled.
4095 Group Info Writes to image The image access log is being -
access log cannot written to storage, so the
be undone writes to the image access log
cannot be undone.
4097 Group Warning Starting three- Max journal lag exceeded or Check the maximum journal
phase distribution insufficient journal lag setting value, and verify
that the current value is
indeed required. If the
maximum journal lag value has
not been defined or the
current journal lag is lower
than the maximum journal lag
value, this is probably a journal
space or performance issue.
In this case, enlarge your
journal or increase the speed
of the journal by placing it in a
faster array, on faster media,
or any other procedure that
can increase the journal write-
rate.
4119 RPA Error Initiator issued out None Contact Customer Support
of bounds I/O
4135 Group Info Copy entered All copy activities have been -
maintenance mode suspended.
4159 Group Info Volume was resized Replication set will be resized
automatically.
4162 Group Info Replication set You may now resize the
resize enabled replication set capacity in
RecoverPoint.
4301 RPA Warning RPA is unable to None Try to reduce the load on the
handle incoming RPA by lowering the
data rate due to compression level.
high compression Alternatively
level
4302 Group Warning Journal is unable to None If the event recurs, try to
handle incoming configure journal volumes for
data rate better performance.
4303 Group Warning Journal and None If the event recurs, try to
replication volumes configure journal volumes for
at copy are unable better performance.
to handle incoming
data rate
4304 Group Warning Remote storage is In distribution, there are reads If the event recurs, try to
unable to handle and writes to the journal and configure remote storage for
incoming data rate; replication volumes on the better performance.
regulating remote storage. If I/O access
distribution
4305 Group Warning Remote cluster is This may cause high load If the event recurs, try to
unable to handle states at the local cluster. configure remote storage for
incoming data rate better performance.
4306 RPA Warning Data transfer rate This may increase RPO, and If this event recurs, examine
Cluster between clusters is cause a high-load state. the WAN/FC link for possible
slow high latency or packet loss.
Consult your network
administrator if needed.
4307 RPA Warning Reading rate from A slow reading rate during If the event recurs, try to
Cluster local replication resynchronization (which configure local replication
volumes during involves reading a very large volumes for better
resynchronization volume of data from the local performance.
is slow replication volumes) may
increase RPO.
4308 RPA Warning Reading rate from A slow reading rate during If the event recurs, try to
Cluster replication volumes resynchronization (which configure replication volumes
at copy during involves reading a very large at the copy for better
resynchronization volume of data from performance.
is slow replication volumes at the
copy) may increase RPO.
4309 RPA Warning RPA utilization High utilization of RPA If bottleneck detection shows
reached 80% resources may be due to high that compression is using
volume of incoming data, high 80% or more of CPU
volume of incoming IOPS, or resources, reduce the
high compression level. compression setting. If
incoming data is near the limit,
consider adding an RPA or
moving groups to other
RPAs .
4310 Group Warning Link utilization High utilization of the link may If bottleneck detection shows
reached 80% be due to a high volume of that compression for this link
incoming data, high volume of is using 80% or more of CPU
incoming IOPS, or high resources, reduce the
compression level. compression setting. If
incoming data is near the limit,
consider splitting the existing
group onto two or more
RPAs .
5029 Splitter Error LUN mismatch Volume sweep will follow. From the relevant hosts,
detected rescan the SAN.
5046 Splitter Warning Splitter write re- RPA did not acknowledge an Following this event, it is
issued to RPA I/O in a timely manner. As a recommended to:
result, the splitter has re- - Monitor subsequent events,
issued the write. to determine if the problem
recurs.
- If the problem persists, or
increases in frequency,
contact Customer Support .
5052 Splitter Error Splitter does not Group was successfully Replace your current splitter
support configured to replicate with one that supports
synchronous synchronously but since then synchronous replication. If
replication the splitter has been replaced. problem persists contact
The new splitter does not Customer Support.
support synchronous
replication and
consequentially replication
mode has been changed to
asynchronous.
5059 Splitter Info Array roll started An array roll has been No user action is required.
triggered. RecoverPoint
transfer will be paused until
roll is completed.
5060 Splitter Info VPLEX inter- VPLEX inter-cluster link No user action is required.
cluster link recovery started,
recovery started RecoverPoint transfer will be
5061 Splitter Info VNX roll started Failover started at another RP No user action is required.
system attached to VPLEX,
no snapshots can be created
by RecoverPoint.
Detailed events
The following table contains the Detailed scope events that are issued by the RecoverPoint
system.
1004 Mgmt Warning Failed to send email Failed to send email alert to the Check whether there is an issue
alert specified address. with your selected method of
transfer. If a problem exists, fix it
and then, perform a connectivity
test by running the
test_syr_connectivity CLI
command. If problem persists
contact Customer Support.
1011 Mgmt Error License grace period You must obtain a new
expired RecoverPoint license and then
activate each license and enter
your licenses into RecoverPoint.
1020 Mgmt Warning Failed to send system None Check whether there is an issue
report with your selected method of
transfer. If a problem exists, fix it
and then, perform a connectivity
test by running the
test_syr_connectivity CLI
command. If problem persists
contact Customer Support.
3006 RPA Error off Settings conflict The settings conflict between
Cluster between clusters RPA clusters has been resolved by
resolved a user action.
3036 RPA Error RPA clock out of sync None Contact Customer Support.
3157 Group Error Snap based replication Array resources usage exceeded Clear array resources
stopped maximum threshold
3158 Group Error off Snap based replication Array resources usage is back to
resumed normal
3159 RPA Error System was unable to None Remove the snap interface(s)
Cluster remove snap manually
interface(s) from the
array
3160 Group Error System was unable to None Remove the array consistency
remove a consistency group manually
group from the array
3161 Group Error System was unable to None Remove array consistency snap
remove consistency manually
snap from array
3162 Group Error System was unable to None Remove the array consistency
promote consistency group manually
snap on array
3163 Group Error Array operation took too None Array may be loaded. Increase
long snap based replication interval.
4082 Group Warning Next synchronization The copy marked all of its
will be a full sweep replication volumes as dirty.
4083 Group Warning Next synchronization The copy marked some of its
will be a volume sweep replication volumes as dirty. Next
synchronization will be a volume
sweep on these volumes.
4090 Group Warning Image access log 80% Image access is enabled to a non- If you do not wish to retain the
full production copy. writes that were added to the
- The capacity of the copy copy image while image access
journal’s image access log has was enabled, disable image
nearly been reached; only limited access; the relevant writes are
further information can be written automatically undone.
to it. If the log becomes Alternatively, use the undo writes
completely full, the system will command to undo the same
block access by host applications writes; image access remains
to the replication volumes that enabled.
belong to that group (and the - If, however, you wish to retain
application will receive I/O errors). the writes that were added to the
- When the system is in this state, copy image while image access
it is recommended that immediate has been enabled, you can do one
action be taken to prevent the log of the following:
from becoming 100% full. - - Increase the size of the copy
journal by adding one or more
volumes to the journal.
- - Fail over to the copy.
- Note: The copy journal is erased.
- - Set the image access mode to
direct.
- Note: The copy journal is erased,
and a full sweep resynchronization
will be required to restore
consistency between the
production and copy images.
- To help prevent this problem
from recurring, increase the size
of your image access log, using
one or both of the following:
- - Add volumes to the journal.
- - Modify the policy setting for
the portion of the journal allocated
to the image access log. This is
permitted only when image access
is disabled.
4106 Group Warning Starting full sweep Cannot write additional replication
data for this group to volume
because its capacity has been
reached. Starting full sweep.
4117 Group Warning Virtual writes buffer is When virtual writes buffer
90% full becomes full virtual access is
disabled.
4121 Group Error Error writing to volume Ensure that RecoverPoint has If you extended a storage pool or
write permission to all volumes. attached a device to a storage
System will retry automatically. If pool, run the CLI command
the problem recurs repeatedly, rescan_san’ If problem persists,
possible causes may be: volume contact Customer Support.
contains bad sector; volume is thin
device not attached to any
storage pool; volume is attached
to storage pool that is full.
4123 Group Error Read and write to Read from and write to volume
volume failed failed. System retried and failed
again. System will retry
automatically. If the problem
recurs repeatedly, contact
Customer Support.
4133 Group Error Starting copy regulation The system has detected an
unstable state in this copy and
therefore the copy is being
regulated for a period of <x>
minutes in order to allow for the
environment to stabilize. See
Details for cause of regulation.
Event logs can also be a good
source for the detection of system
issues. Look for repetitive errors,
that may indicate a specific
problem in the system. Also,
4134 Group Error off Copy regulation has Copy regulation has ended due to
ended a user action or internal timeout.
4139 Splitter Warning Storage unreachable The configured login credentials Ensure that there is connectivity
are incorrect or the storage is between the RPA cluster and the
unreachable. storage, and that the entered
credentials are correct, and try
again.
4163 Group Error Snap-based replication The storage cannot perform the See the More Information area for
has been disabled operations necessary for snap- a description of the exact
based replication. Snap-based problem. After fixing the problem,
replication has been paused for a run the
period of % clear_all_storage_errors
%t_SC_ArrayOperationsFreezeInt CLI command to restart snap-
erval%% minutes in order to allow based replication. If problem
you to fix any issues with the persists, collect system
storage. information, and contact
Customer Support.
4164 Group Error off Snap-based replication Snap-based replication error has
has been restored ended due to user action or
internal system timeout.
4175 RPA Info System has entered The RecoverPoint system is No action required.
maintenance mode adding an RPA to the cluster.
4176 RPA Info System has entered The RecoverPoint system is No action required.
Cluster maintenance mode performing a major version
upgrade.
4177 RPA Info System has entered The RecoverPoint system is No action required.
Cluster maintenance mode performing a minor version
upgrade.
4178 RPA Info System has entered The RecoverPoint system is No action required.
maintenance mode performing an RPA replacement.
4179 RPA Info System has exited The RecoverPoint system is no No action required.
maintenance mode longer adding an RPA to the
cluster.
4180 RPA Info System has exited The RecoverPoint system is no No action required.
Cluster maintenance mode longer performing a major version
upgrade.
4181 RPA Info System has exited The RecoverPoint system is no No action required.
Cluster maintenance mode longer performing a minor version
upgrade.
4182 RPA Info System has exited The RecoverPoint system is no No action required.
maintenance mode longer performing an RPA
replacement.
4183 RPA Info System has entered The RecoverPoint system is No action required.
maintenance mode performing an RPA conversion
from class to RPSE.
4184 RPA Info System has entered The RecoverPoint system is no No action required.
maintenance mode longer performing an RPA
conversion from class to RPSE.
4185 RPA Info System has entered System has entered user-initiated No action required.
Cluster maintenance mode maintenance mode
4186 RPA Info System has exited System has exited user-initiated No action required.
Cluster maintenance mode maintenance mode
4230 RPA Info All initiators registered All RPAs initiators were
Cluster with storage successfully registered with the
storage system.
4232 RPA Info Storage group created Storage group was successfully
Cluster on storage created on the storage system
4233 RPA Info All storage groups All storage groups were
Cluster created on storage successfully created on the
storage system
4501 Mgmt Warning License invalid in You have installed a To benefit from RecoverPoint/SE
RecoverPoint RecoverPoint/SE license although simplifications and the Unisphere
the system was installed with the RecoverPoint/SE plug-in, you
Deployment Manager must perform one of the following
RecoverPoint Installer Wizard. actions:
- - If using a release earlier than
3.4 SP1: 1) upgrade the system to
release 3.4 SP1 or later using the
Deployment Manager Upgrade
RPAs Wizard, 2) convert the
environment to RecoverPoint/SE
using the Deployment Manager
Converter Wizard.
4502 Mgmt Warning License invalid in You have installed a RecoverPoint To benefit from full RecoverPoint
RecoverPoint/SE license although the system was functionality, such as bandwidth
installed with the Deployment reduction and support for
Manager RecoverPoint/SE additional capacity, you must
Installer Wizard. perform the following actions:
- - If using a release earlier than
3.4 SP1: 1) upgrade the system to
release 3.4 SP1 or later using the
Deployment Manager Upgrade
RPAs Wizard, 2) convert the
environment to RecoverPoint
using the Deployment Manager
Converter Wizard.
- - If using release 3.4 SP1 or later:
1) convert the environment to
RecoverPoint using the
Deployment Manager Converter
Wizard, 2) upgrade the existing
RecoverPoint/SE license to a
RecoverPoint license.
5050 Splitter Warning Failed to collect system None Verify that all arrays and vCenter
info Severs have been registered with
the correct credentials.
5057 Group Warning Volume configuration Consistency group contains a Reconfigure the replication set so
not supported by VNX/ replication set with volumes that that all of its volumes are of the
CLARiiON splitter are not equal in size, and this is same size. Note: Modifying the
version not supported by the VNX/ volumes in a replication set causes
CLARiiON splitter version a volume sweep on all of the
currently installed on the system. volumes in the replication set.
6000 Group Error Image cannot be An unrecognised error has Try accessing a different image. If
accessed occurred. The specified image of you cannot access any other
your distributed group cannot be images, contact Customer
accessed. Service.
6001 Group Error off Stopped trying to The system has stopped trying to No user action is required.
access inaccessible access an inaccessible image of a
image distributed group.
8000 Mgmt Error Calling home None A service request is being opened
for you with Customer Service.
8001 Mgmt Error Call home event failure None Contact Customer Support.
8105 RPA Warning Lost connectivity to None Ensure that there is connectivity
Cluster storage with the storage and that the
entered credentials are correct,
and try again. If problem persists,
contact Customer Support.
10210 RPA Error High load occurring High load situation is ongoing. Run detect_bottlenecks for
during group the consistency group in which
initialization the high load condition has been
10211 RPA Error SAN communication None Temporary issue on the SAN
problem between caused communication problems
splitters and RPAs between splitters and RPAs at the
existed but has resolved specified cluster. The problem
itself resolved itself.
10212 RPA Error off Fibre Channel is back up Temporary problem in Fibre
Channel link between splitters and
RPAs has been resolved.
10213 RPA Error off High load occurring High load situation is ongoing. Run detect_bottlenecks for
during group the consistency group in which
initialization the high load condition has been
detected. Consider enabling fast
first-time initialization (for details,
see RecoverPoint Administrator’s
Guide).
10506 RPA Info Roll to physical image Logged access to physical image
complete now enabled.
10507 RPA Info Journal available again Due to system changes the journal
was temporarily out of service, but
it is now available again.
10508 RPA Info Data flushed from All data has been flushed from the
source RPA source RPA. Failover will proceed.
cleared to restart
transfer
12002 RPA Error Error in links to all other None - Check if other cluster is down.
clusters - - In case of IP connectivity:
- o Check RecoverPoint gateways
and IPs configuration.
- o Check if there are any ISP-
related issues.
- o Check RecoverPoint firewall
configuration.
- - In case of FC connectivity,
check RecoverPoint zoning.
- - If you recently changed the
network configuration, please
verify that RecoverPoint
configuration matches the new
network configuration.
- - If none of the above
instructions resolve this issue,
collect system information from all
clusters experiencing connectivity
issues, and contact Customer
Service.
-
12004 RPA Error Error in data link to Error in data link. All RPAs at 1. Check if replication process at
other cluster(s) cluster are unable to transfer other cluster is down.
replicated data to other cluster(s) - 2. In case of IP connectivity:
due to communication failure over - a. check RP gateways/IPs
the WAN link. Data transfer configuration.
between RPA clusters has - b. Check firewall configuration.
stopped. - 3. If you recently changed
network configuration, please
verify that RP configuration
matches the new network
configuration.
-
12005 RPA Error Error in data link over None 1. Check if replication process at
WAN. RPA is unable to other cluster is down.
transfer replicated data - 2. In case of IP connectivity:
to other cluster - a. check RP gateways/IPs
configuration.
- b. Check firewall configuration.
- 3. If you recently changed
network configuration, please
verify that RP configuration
matches the new network
configuration.
-
12009 RPA Error Link entered high load Due to heavy I/O activity a link If high load persists, consider
entered a high load state in order running the balance_load
to prevent I/O failures on that link. command and applying the load
The following are among the balancing recommendation, or
possible causes of the high load:- manually modifying the preferred
RPA is unable to handle the large RPA of each group according to
volume of incoming data. (RPA the recommendation. Check for
performance statistics are scheduled activities in your
presented in the Release Notes environment. When schedule
that accompany each permits, run
RecoverPoint product release.) - detect_bottlenecks for the
Journal reaches capacity, because consistency group in which the
the rate of the distribution high load condition was detected.
process consistently lags behind If relevant, consider enabling fast
the rate of incoming data to the first-time initialization. (For
copy journal. details, see the RecoverPoint
- - WAN is too slow to handle the Administrator’s Guide).
data rate. - Compression for WAN
optimization is too high, such that
the RPA is unable to handle the
volume of incoming data. Peak I/O
activity in the SAN causes a
temporary bottleneck in the
environment. This can be
considered normal behavior, and
does not necessarily require user
action.
12011 RPA Error Image access log or Access to copy volumes for this If you do not wish to retain the
virtual buffer is full group at this RPA cluster has been writes that were added to the
disabled. copy image while image access
was enabled, disable image
access; the relevant writes are
automatically undone.
Alternatively, use the undo writes
command to undo the same
writes; image access remains
enabled.
- If, however, you wish to retain
the writes that were added to the
copy image while image access
has been enabled, you must
increase the size of the copy
journal by adding one or more
volumes to the journal.
Alternatively, you can set the
image access mode to direct;
however, in that case, the copy
journal is erased, and a full sweep
resynchronization will be required
to restore consistency between
the production and copy images.
- To help prevent this problem
from recurring, increase the size
of your image access log, using
one or both of the following:
- - Add volumes to the journal.
- - Modify the policy setting for
the portion of the journal allocated
to the image access log. This is
permitted only when image access
is disabled.
12013 RPA Error Cannot enable image Cannot enable image access to
access the specified image.
12014 RPA Error Fibre Channel is down Fibre Channel link between all
RPAs and all splitters and storage
is down.
12016 RPA Error Fibre Channel is down Fibre Channel link between all
RPAs and all storage is down.
12022 RPA Error Fibre Channel is down Fibre Channel link between RPA
and splitters or storage volumes
(or both) is down.
12023 RPA Error Fibre Channel is down Fibre Channel link between RPA
and all splitters and storage is
down.
12024 RPA Error Fibre Channel is down Fibre Channel link between RPA
and all splitters is down.
12025 RPA Error Fibre Channel is down Fibre Channel link between RPA
and all storage is down.
12027 RPA Error RPAs are unable to RPAs cannot complete I/O Suggestions: Check your SAN and
access any volume at operations at this cluster to any storage configurations for any
this cluster that belongs volume -- replication or journal -- irregularities; for example,
to this consistency in the consistency group. incorrect LUN masking or zoning.
group Ensure that the Reservations
Support policy parameter setting
(enabled/not enabled) is
appropriate for your environment,
as described in the RecoverPoint
Administrator’s Guide.
12029 RPA Error Fibre Channel is down Fibre Channel link between all
RPAs and one or more replication
volumes is down.
12030 RPA Error Fibre Channel is down Fibre Channel link between all
RPAs and one or more journal
volumes is down.
12031 RPA Error Error occurred in link None Ensure that at RPA(s) cluster are
between one or more connected properly to the other
RPAs at cluster and all cluster(s).
RPAs at other cluster(s)
12032 RPA Error Error occurred in link None Ensure that all RPAs at cluster are
Cluster between all RPAs at connected properly to the other
cluster and all RPAs at cluster(s)
other cluster(s)
12035 RPA Error Cluster control at other Error occurred in link to cluster
cluster(s) unavailable leader RPA at other cluster(s).
12036 RPA Error Negotiation of transfer Negotiation of transfer protocol If problem persists, check your
protocol failed failed due to network issues in TCP network.
TCP layer between clusters
12041 RPA Error Error writing to volume Ensure that RecoverPoint has If you extended a storage pool or
write permission to all volumes. attached a device to a storage
Possible causes: volume is read- pool, run the rescan_san CLI
only; volume contains bad sector; command. If problem cannot be
volume is thin device not attached solved, contact Customer
to any storage pool; volume is Support.
attached to storage pool that is
full.
now be initialized.
During initialization data
is not transferred
synchronously
12072 RPA Error Fibre Channel is down FC link between RPAs down.
12078 RPA Error Splitter communication Although the RPA sees the To ensure data integrity, it is
error splitter, the cluster control has highly recommended that any
been unable to communicate with snapshots created in the past five
it for the past five minutes, and minutes are not selected for
therefore, cannot detect whether failover.
or not any writes have passed
through it.
12080 RPA Error Communications The cause of this problem may be:
problem in internal Failure of a RecoverPoint process
process - Disconnection between internal
RecoverPoint processes, To
determine the cause of this
problem, collect logs for the
period when the event occurred,
and contact Customer Support.
12081 RPA Error Communications The cause of this problem may be:
problem in internal Failure of a RecoverPoint process
process - Disconnection between internal
RecoverPoint processes, To
determine the cause of this
problem, collect logs for the
period when the event occurred,
and contact Customer Support.
12082 RPA Error off Communications The cause of this problem may be:
problem in internal Failure of a RecoverPoint process
process - Disconnection between internal
RecoverPoint processes, To
determine the cause of this
problem, collect logs for the
period when the event occurred,
and contact Customer Support.
12083 RPA Error Communications with Communications with Symmetrix Check for communication failure,
Symmetrix director director has failed repeatedly. port failure, faulty zoning, or
failed configuration errors.
12087 RPA Warning RPA fan failure None Contact Customer Support.
detected
14005 RPA Error off Data link over WAN has None
been restored. RPA is
able to transfer
replicated data to other
cluster
14009 RPA Error off Link was in high load, Due to heavy I/O activity, the link If high load persists, consider
but has now retuned to entered a high load state in order running the balance_load
normal operation to prevent I/O failures on that link. command and applying the load
14014 RPA Error off Fibre Channel is back up Fibre Channel link between all
RPAs and all splitters and storage
is restored.
14016 RPA Error off Fibre Channel is back up Fibre Channel link between all
RPAs and all storage is restored.
14022 RPA Error off Fibre Channel is back up Fibre Channel link that was down
between RPA and splitters is
restored.
14023 RPA Error off Fibre Channel is back up Fibre Channel link between RPA
and all splitters and storage is
restored.
14024 RPA Error off Fibre Channel is back up Fibre Channel link between RPA
and all splitters is restored
14025 RPA Error off Fibre Channel is back up Fibre Channel link between RPA
and all storage is restored
14029 RPA Error off Fibre Channel is back up Fibre Channel link between all
RPAs and one or more user
volumes is restored.
14030 RPA Error off Fibre Channel is back up Fibre Channel link between all
RPAs and one or more journal
volumes is restored.
14033 RPA Error off Access to volume Restored repository data integrity.
restored
14035 RPA Error off Cluster control at other The link to cluster leader RPA at
cluster(s) available other cluster(s) has been
restored.
14072 RPA Error off Fibre Channel is up FC link between RPAs restored
again
14078 RPA Error off End of splitter The cluster control is able to No user action is required.
communication error communicate with the splitter
again. To ensure consistency
between the copy and production,
initialization or full sweep will
follow.
14089 Array Error off The RPA cluster has None None
restored connection to
all volumes and splitters
on the array
14090 Site Error off The RPA cluster has None None
restored connection to
specific host
14098 Site Error off RPA has lost connection None None
to all data stores
16001 RPA Brief Brief splitter error Splitter was down. Problem has
error corrected. Problem has been corrected.
been corrected.
16002 RPA Brief Brief error in links to all Error occurred in all links to all
error other clusters corrected other clusters. Problem has been
corrected.
16003 RPA Brief Brief error in link to an Error occurred in link to an RPA at
error RPA at other cluster(s) other cluster(s). Problem has
corrected been corrected.
16004 RPA Brief Brief error in data link to Error in data link. All RPAs at
error other cluster(s) cluster are unable to transfer
corrected replicated data to other cluster(s).
Problem has been corrected.
16009 RPA Brief Link was in high load but Due to heavy I/O activity, a link If high load persists, consider
error has now returned to entered a high load state in order running the balance_load
normal operation to prevent I/O failures on that link. command and applying the load
The link has since exited the high balancing recommendation, or
load state, and has returned to manually modifying the preferred
normal operation. The following RPA of each group according to
are among the possible causes of the recommendation. Check for
the high load: RPA is unable to scheduled activities in your
handle the large volume of environment. When schedule
incoming data. (RPA performance permits, run
statistics are presented in the detect_bottlenecks for the
Release Notes that accompany consistency group in which the
each RecoverPoint product high load condition was detected.
release.) Journal reaches capacity, If relevant, consider enabling fast
16011 RPA Brief Briefly image access log Problem has been corrected.
error or virtual buffer was full
16012 RPA Brief Briefly unable to enable Problem has been corrected.
error virtual access to image
16014 RPA Brief Fibre Channel is back up Fibre Channel link between all
error again RPAs and all splitters and storage
was down. Problem has been
corrected.
16016 RPA Brief Fibre Channel is back up Fibre Channel link between all
error again RPAs and all storage was down.
Problem has been corrected.
16022 RPA Brief Fibre Channel is back up Fibre Channel link between RPA
error again and splitters was briefly down.
Problem has been corrected.
16023 RPA Brief Fibre Channel is back up None Fibre Channel link between RPA
error again and all splitters and storage was
down. Problem has been
corrected.
16024 RPA Brief Fibre Channel is back up Fibre Channel link between RPA
error again and all splitters was down.
Problem has been corrected.
16025 RPA Brief Fibre Channel is back up Fibre Channel link between RPA
error again and all storage was down. Problem
has been corrected.
16026 RPA Brief Brief RPA and all Error occurred in link to an RPA at
error storage error corrected other cluster(s). Problem has
been corrected.
16027 RPA Brief Brief group(s) volumes All volumes in the consistency
error accessibility error group (or groups) were not
corrected accessible. Problem has been
corrected.
16029 RPA Brief Fibre Channel is back up Fibre Channel link between all
error again RPAs and one or more replication
volumes was down. Problem has
been corrected.
16030 RPA Brief Fibre Channel is back up Fibre Channel link between all
error again RPAs and one or more journal
volumes was down. Problem has
been corrected.
16031 RPA Brief Brief link error between Error occurred in link between one
error RPA(s) at cluster and all or more RPAs at cluster and all
RPAs at other cluster(s) RPAs at the other cluster(s).
corrected Problem has been corrected.
16032 RPA Brief Brief link error between Error occurred in link between all
Cluster error all RPAs at cluster and RPAs at cluster and all RPAs at
all RPAs at other other cluster(s). Problem has
cluster(s) corrected been corrected.
16034 RPA Brief Brief write consistency Writes to storage may have
error error corrected occurred without corresponding
writes to RPA. Problem has been
corrected.
16035 RPA Brief Cluster control at other Error occurred in link to cluster
error cluster(s) available leader RPA at other cluster(s).
again Problem has been corrected.
16038 RPA Brief Brief group(s) journal All journal volumes in the
error volumes accessibility consistency group (or groups)
error corrected were not accessible. Problem has
been corrected.
16072 RPA Brief Fibre Channel is back up Fibre channel link between RPAs
error again was down but problem has been
corrected and the link is back up
again.
16078 RPA Brief Brief splitter A temporary splitter No user action is required.
error communication error communication error occurred,
but the problem has since been
corrected. To ensure consistency
between the copy and production,
initialization or full sweep will
follow.
16080 RPA Brief Internal process The cause of this problem may be: To determine the cause of this
error communication problem Failure of a RecoverPoint process problem, collect logs for the
- Disconnection between internal period when the event occurred,
RecoverPoint processes. and contact Customer Support.
16081 RPA Brief Internal process The cause of this problem may be: To determine the cause of this
error communication problem Failure of a RecoverPoint process problem, collect logs for the
- Disconnection between internal period when the event occurred,
RecoverPoint processes. and contact Customer Support.
16082 RPA Brief Internal process The cause of this problem may be: To determine the cause of this
error communication problem Failure of a RecoverPoint process problem, collect logs for the
briefly resolved - Disconnection between internal period when the event occurred,
RecoverPoint processes. and contact Customer Support.
16083 RPA Brief Communications with Communications with a Symmetrix If this recurs frequently, contact
error Symmetrix director director failed briefly and has now Customer Support.
restored again been restored
16085 RPA Warning Brief RPA power supply None Check electrical power to both
off failure resolved power supplies. If problem
persists, contact Customer
Support.
16087 RPA Warning Brief generic hardware None Contact Customer Support.
off failure resolved
18004 RPA Error Error in data link. All Due to communication failure over
RPAs at cluster are the WAN link, data transfer
unable to transfer between the clusters has stopped.
replicated data to other
cluster(s). Problem was
temporarily corrected,
but has since returned
18014 RPA Error Fibre Channel is down Fibre Channel link between all
again RPAs and all splitters and storage
was temporarily restored but
problem has returned
18016 RPA Error Fibre Channel is down Fibre Channel link between all
again splitters and all storage was
temporarily restored but problem
has returned.
18022 RPA Error Fibre Channel is down Fibre Channel link that was down
again between RPA and splitters or
storage volumes (or both) was
temporarily restored but problem
has returned.
18023 RPA Error Fibre Channel is down Fibre Channel link between RPA
again and all storage was temporarily
restored but problem has
returned.
18024 RPA Error Fibre Channel is down Fibre Channel link between RPA
again and all splitters was temporarily
restored but problem has
returned.
18025 RPA Error Fibre Channel is back Fibre Channel link between RPA
down again and all storage was temporarily
restored but problem has
returned.
18029 RPA Error Fibre Channel is back Fibre Channel link between all
down again RPAs and one or more user
volumes was temporarily restored
but problem has returned
18030 RPA Error Fibre Channel is back up Fibre Channel link between all
again RPAs and one or more journal
volumes was temporarily restored
but problem has returned
18035 RPA Error Cluster control at other Error occurred in link to cluster
cluster(s) unavailable leader RPA at other cluster(s).
again Problem was temporarily
corrected, but has since returned.
18072 RPA Error off Fibre Channel is down Fibre channel link between RPAs
again was temporarily restored but the
problem has returned and the link
is back down again.
18074 RPA Error Fibre Channel is down Fibre Channel link between all
again RPAs and repository volume was
temporarily restored but problem
has returned.
18078 RPA Error Splitter communication The cluster control was To ensure data integrity, it is
error returned temporarily able to communicate highly recommended that any
with the splitter, but since then, it snapshots created in the past five
has lost communication with the minutes are not selected for
splitter again. failover.
- To ensure consistency between
the copy and production, transfer
will be paused. When the system
re-starts transfer, an initialization
or full sweep will follow.
18080 RPA Error Internal process The cause of this problem may be: To determine the cause of this
communication problem Failure of a RecoverPoint process problem, collect logs for the
- Disconnection between internal period when the event occurred,
RecoverPoint processes. and contact Customer Support.
18081 RPA Error Internal process The cause of this problem may be: To determine the cause of this
communication problem Failure of a RecoverPoint process problem, collect logs for the
- Disconnection between internal period when the event occurred,
RecoverPoint processes. and contact Customer Support.
18082 RPA Error Internal process The cause of this problem may be: To determine the cause of this
communication problem Failure of a RecoverPoint process problem, collect logs for the
- Disconnection between internal period when the event occurred,
RecoverPoint processes. and contact Customer Support.
18083 RPA Error Communication with After a brief recovery, Check for communication failure,
Symmetrix director communications with a Symmetrix port failure, faulty zoning, or
failed again director has failed again. configuration errors.
Advanced events
The following table contains the Normal scope events that are issued by the RecoverPoint system.
4100 RPA Info Group created Creating a new group modifies the To balance the write load across
Cluster load distribution across RPAs. all RPAs run the balance_load
10002 RPA Info Issuing intermediate System activity has not stabilized
report and therefore, an intermediate
report is being issued.
10101 RPA Error Unrecognised system Cause of system activity unclear. To obtain more information filter
activity events using Detailed scope.
10202 RPA Info System changes at System changes have occurred at For details of the system changes,
other cluster the another cluster. refer to the event log at the other
cluster(s).
12042 RPA Error Splitter write may have Splitter write may have failed
failed during transfer (while group was transferring
data). Synchronization will be
required.