EMC-RP CLI v4.3.1

EMC®
RecoverPoint for VMs

Version 4.3.1
CLI Reference Guide

P/N 302-002-664
REV 02
Copyright © 2016 EMC. All rights reserved. Published in the USA.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other
countries. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com
2 RecoverPoint for VMs 4.3.1 CLI Reference Guide

CONTENTS
Tables 7
Chapter 1 Introduction 9
Changes to commands..................................................................................10
Functions available only in the CLI.................................................................10
Managing the EMC RecoverPoint system....................................................... 11
Getting Started with the RecoverPoint CLI...................................................... 11
Connecting to the EMC RecoverPoint CLI........................................................12
Working with the EMC RecoverPoint CLI in CLI mode...................................... 13
CLI modes........................................................................................ 17
Chapter 2 List of Commands 21

Commands....................................................................................................22
Chapter 3 Splitters 27
get_splitter_states........................................................................................ 28
rescan_san................................................................................................... 28
Chapter 4 RPAs 31
config_cluster_ids.........................................................................................32
get_clusters_topology................................................................................... 33
get_internal_cluster_name............................................................................33
get_internal_cluster_uids..............................................................................33
get_rpa_settings........................................................................................... 34
get_rpa_states.............................................................................................. 34
get_rpa_statistics..........................................................................................35
sleep.............................................................................................................36
hijack_cluster................................................................................................37
Chapter 5 Storage 39
get_storage................................................................................................... 40
register_storage............................................................................................ 40
Chapter 6 Volumes 43
get_volume_states........................................................................................44
Chapter 7 Consistency Groups 47

balance_load................................................................................................ 48
bookmark_image.......................................................................................... 48
config_copy_policy....................................................................................... 50
config_group_policy......................................................................................53
config_link_policy......................................................................................... 54
config_preferred_rpas................................................................................... 60
RecoverPoint for VMs 4.3.1 CLI Reference Guide 3

CONTENTS
clear_markers............................................................................................... 61
disable_image_access.................................................................................. 61
get_group_settings....................................................................................... 62
get_group_state............................................................................................ 64
get_group_statistics......................................................................................66
get_images................................................................................................... 67
pause_transfer..............................................................................................68
set_image_access_mode.............................................................................. 69
set_markers.................................................................................................. 70
set_snapshot_consolidation_policy.............................................................. 71
show_integrity_check_status........................................................................ 72
start_integrity_check.....................................................................................73
start_transfer................................................................................................ 73
stop_integrity_check..................................................................................... 74
undo_writes.................................................................................................. 74
Chapter 8 System 77
clear_security_settings..................................................................................78
config_automatic_snapshot_consolidation................................................... 78
config_io_throttling.......................................................................................79
config_long_term_statistics.......................................................................... 80
config_system_reports.................................................................................. 81
detect_bottlenecks....................................................................................... 82
export_consolidated_statistics..................................................................... 83
export_statistics........................................................................................... 84
get_groups....................................................................................................85
get_raw_statistics......................................................................................... 86
get_security_settings.................................................................................... 86
get_system_report........................................................................................ 87
get_system_report_settings.......................................................................... 87
get_system_settings..................................................................................... 88
get_system_status........................................................................................ 89
get_versions................................................................................................. 90
set_advanced_action_regulation...................................................................90
set_smtp_server............................................................................................91
unregulate_all_copies...................................................................................91
Chapter 9 Maintenance 93
finish_maintenance_mode............................................................................94
start_maintenance_mode............................................................................. 94
Chapter 10 Virtual Machine 95

update_vcenter_server_registration.............................................................. 96
Chapter 11 Events 97
add_email_users.......................................................................................... 98
config_email................................................................................................. 98
clear_events_log........................................................................................... 99
config_snmp_global......................................................................................99
config_snmp_trap_dest.............................................................................. 100
config_syslogs_global.................................................................................100

CONTENTS
config_syslogs_target_host.........................................................................101
create_event_filter...................................................................................... 101
disable_email............................................................................................. 102
disable_snmp............................................................................................. 103
disable_syslogs.......................................................................................... 103
edit_event_filter..........................................................................................104
enable_email.............................................................................................. 105
enable_snmp.............................................................................................. 105
enable_syslogs........................................................................................... 105
get_events_log............................................................................................106
get_monitored_parameters......................................................................... 108
remove_email_users................................................................................... 109
remove_event_filter.................................................................................... 109
set_snmp_community.................................................................................109
test_email...................................................................................................110
test_snmp...................................................................................................110
test_syr_connectivity.................................................................................. 110
test_syslogs................................................................................................ 111
Chapter 12 Users 113

add_role..................................................................................................... 114
add_ssh_key...............................................................................................115
add_user.....................................................................................................115
clear_ldap_configuration............................................................................ 116
config_ldap.................................................................................................117
config_user_account................................................................................... 118
get_account_settings.................................................................................. 119
get_ldap_configuration............................................................................... 119
modify_role.................................................................................................120
regenerate_encryption_keys....................................................................... 121
remove_role................................................................................................ 121
remove_ssh_key......................................................................................... 122
remove_user............................................................................................... 122
set_password..............................................................................................122
set_security_level....................................................................................... 123
set_user......................................................................................................123
test_ldap_connection................................................................................. 124
unlock_user................................................................................................ 125
Chapter 13 General 127

get_current_time.........................................................................................128

CONTENTS

TABLES
1 Commands changed since last revision......................................................................... 10

2 Functions available only in the CLI ................................................................................ 10
3 Function of keyboard keys in CLI mode.......................................................................... 15
4 Function of special characters in CLI mode.....................................................................15
5 Accepted forms for units of measurement......................................................................16
6 Help output conventions................................................................................................17
7 Useful command line flags in Interactive mode.............................................................. 18
8 Useful command line flags in expert mode.....................................................................20
9 List of CLI Commands.................................................................................................... 22

TABLES

CHAPTER 1
Introduction
This chapter includes the following topics:
l Changes to commands..........................................................................................10
l Functions available only in the CLI.........................................................................10
l Managing the EMC RecoverPoint system............................................................... 11
l Getting Started with the RecoverPoint CLI.............................................................. 11
l Connecting to the EMC RecoverPoint CLI................................................................12
l Working with the EMC RecoverPoint CLI in CLI mode.............................................. 13
Introduction 9
Introduction
Changes to commands
A list of changes since the last revision of this document helps users understand
important updates to the CLI.
Table 1 Commands changed since last revision
Commands What changed

edit_event_filter on page 104 Command was added to the guide.
config_copy_policy on page 50 Removed journal_size_limit parameter.
hijack_cluster on page 37 Command was added to the guide.
Functions available only in the CLI

The functions available through the CLI commands are usually also available in the GUI.
However, some functions are available only in the CLI.
Table 2 Functions available only in the CLI
CLI command or parameter Notes

acquire_management_ip
add_ssh_key
bandwidth_limit parameter within: This capability does not exist in the GUI.
l config_link_policy
bookmark_image Bookmarks cannot be created in the GUI, but they

can be created using the CLI bookmark commands
and parameters.
clear_markers
clear_security_settings
config_cluster_ids
config_io_throttling
config_long_term_statistics
detect_bottlenecks The long-term effects of deduplication on your

export_consolidated_statistics bandwidth can only be monitored through the
RecoverPoint CLI.
finish_maintenance_mode
get_internal_cluster_uids
get_internal_cluster_name
get_ssh_keys
hijack_cluster

Introduction
Table 2 Functions available only in the CLI (continued)
CLI command or parameter Notes

regenerate_encryption_keys
remove_ssh_key
resume_writes_after_srm
set_advanced_action_regulation
set_backup_copy_retention_policy
set_markers
set_stream_quota
show_integrity_check_status
start_integrity_check
start_maintenance_mode
stop_integrity_check
stop_snapshot_consolidation
unlock_user
unregulate_all_copies
Managing the EMC RecoverPoint system

The Command Line Interface (CLI) is an EMC RecoverPoint interface through which all
functions of the EMC RecoverPoint system can be managed.
EMC RecoverPoint Command Line Interface
The EMC RecoverPoint Command Line Interface is used to communicate with all RPAs in
the RecoverPoint environment.
Use the EMC RecoverPoint Command Line Interface to:
l Display all of the commands in RecoverPoint, and the help for each command in Help
mode on page 17.
l Run CLI commands in Expert mode on page 19.
l Run CLI commands interactively in Interactive mode on page 18.
Unisphere for RecoverPoint
Management activities are also carried out, and most CLI functions are also accessible
through Unisphere for RecoverPoint. See the EMC RecoverPoint Administrator’s Guide for
more information.
Getting Started with the RecoverPoint CLI

This sections describes how to communicate with the EMC RecoverPoint Command Line
Interface. In order to communicate with the EMC RecoverPoint CLI, you will first need to
establish a secure connection to the CLI using an RS232 port or an SSH connection.
Get started by verifying that you have the tools necessary to connect to a CLI session in
both CLI work modes.
Managing the EMC RecoverPoint system 11

Introduction
These are the main modes of work in a CLI session:

l CLI mode — for getting help and generally interacting with the system using CLI
commands. CLI mode includes:
n help mode — used to retrieve information regarding each CLI command, its
parameters and usage.
n interactive mode — used to guide the user when running single commands,
allowing them to view each command parameter and its possible values while
running the command.
n expert mode — used to input multiple parameters and their values for a single
command.
What you need for Linux or Solaris OS
Make sure you have the following tools, if you’re working in Linux or Solaris:
l To communicate with the CLI in CLI mode, download, install and use the free SSH
connection utility PuTTY for Linux or Unix, to connect from the PuTTY interface.
What you need in Windows operating systems
Make sure you have the following tools, if you’re working in Microsoft Windows:
l To communicate with the CLI in CLI mode, download, install and use the free SSH
connection utility PuTTY for Windows, to connect from the Microsoft Windows GUI.
Connecting to the EMC RecoverPoint CLI

This sections describes how to connect to the RecoverPoint CLI through a secure RS232
port or SSH connection.
If this is your first time connecting, you will be logging in with:
l User admin with password admin. User admin is permitted to run all of the
commands, including those that modify the system settings.
Note
The <cluster management IP> is a floating IP address assigned to the RPA that is currently
active at the specified RPA cluster. In the event of a failure by this RPA, this floating IP
address dynamically switches to the RPA that assumes operation at the specified cluster,
which will either be RPA1 or RPA2.
See After logging in for the first time on page 13.

Logging into the CLI in CLI mode
To run RecoverPoint commands in CLI mode from Microsoft Windows, Solaris or Linux,
use PuTTY (see Getting Started with the RecoverPoint CLI on page 11).
Note
Scripts cannot be run in this manner.
In the PuTTY Configuration dialog box, fill in the following details:

l Host name: <cluster management IP>
l Connection type: SSH
l Port: 22
A login screen is displayed.
In the Login screen, fill in the following details:

Introduction
l User: admin
l Password: admin
A connection is established with the primary RPA and the CLI prompt is displayed as RPA
cluster>.
Every time you log into the RecoverPoint CLI, any monitored system limitations that have
reached major or critical severity will be displayed at the CLI prompt.
From Linux or Solaris
From a Linux or Solaris (Unix) command prompt, open a CLI session with an RPA using the
following SSH login:
$ ssh <cluster management IP> -l user
For example:
$ ssh 10.10.10.70 -l admin
cluster>.
From MS Windows command prompt

From a Microsoft Windows command prompt, open a CLI session with an RPA using the
following SSH login:
c:\> plink -ssh <cluster management IP> -l user -pw user
For example:
c:\> plink -ssh 10.10.10.70 -l admin -pw admin
cluster>.
After logging in for the first time

Once connected as user admin, it is recommended to change the admin password to
improve the security of the EMC RecoverPoint management interface.
To change the password, run set_password on page 122.
Additionally, it is recommended to run add_ssh_key on page 115 to add a public SSH
key to your profile. The public key, used in conjunction with the private key (held by the
machine on which the user is working), enables you to carry out a secure dialog using
SSH with the RecoverPoint system.
After adding the public key, you only need to enter a username to open an SSH session
with the CLI; a password is not required.
Before running add_ssh_key on page 115, use an SSH-keygen to generate a key pair
(private and public). The SSH-keygen facility writes the public key to a file. When you run
add_ssh_key on page 115, enter the public key at the key prompt.
Working with the EMC RecoverPoint CLI in CLI mode

This section describes how to work in CLI mode of the EMC RecoverPoint Command Line
Interface. The features, input and output of CLI mode are discussed in detail.
Introduction
CLI mode is used to display system help information, and enter commands into the EMC
RecoverPoint Command Line Interface interactively as well as non-interactively.
Working with the EMC RecoverPoint CLI in CLI mode 13

Introduction
Command prompts
Throughout this EMC RecoverPoint CLI Reference Guide, the command prompts of the
different operating environments, are represented as:
RPA cluster> – a CLI session prompt (CLI mode)
CLI mode input

The following input options are available in CLI mode.
Autocomplete
RecoverPoint CLI provides an autocomplete feature—activated with the Tab key—that
effectively speeds up interaction with the RPA.
Press Tab after typing the first letters of a command or parameter. If there are a number of
possible commands or parameters, autocomplete displays all possible completions to
what has previously been typed.
Additionally, when typing commands with only one parameter, after having typed the
command, press the Tab key to bring up the possible parameter values.
In the following example, the user entries are in bold type:
1. RPA cluster>
2. RPA cluster> remove_g and press Tab.
remove_group remove_group_set
RPA cluster> remove_group
3. RPA cluster> remove_group and press ENTER.
Enter consistency group name

z
4. Press Tab.
cg_1 cg_2 groupx

z
5. c and press Tab.
cg_1 cg_2
cg_
6. cg_1 and press ENTER.
The auto-completion feature can also be used with single-parameter commands, as
shown in the following example:
1. RPA cluster> get_group_se and press Tab.
get_group_sets get_group_settings
RPA cluster> get_group_settings
2. RPA cluster>get_group_settings and press Tab.
cg_1 cg_2 groupx

3. RPA cluster> get_group_settings g and press Tab.
RPA cluster> get_group_settings groupx

4. RPA cluster> get_group_settings groupx and press ENTER.
Case sensitivity
The CLI is case-sensitive in that:

Introduction
l CLI command and parameter names must be typed exactly as they appear in the CLI
command and parameter list of help mode.
l User specified command and parameter names—such as those of consistency
groups, volumes, splitters, and RPA clusters—must subsequently be typed accurately
with regard to uppercase and lowercase letters.
l Parameter values are not case sensitive, unless the value has been defined by a user.
For example, the system makes no distinction between a parameter value of "lag",
"LAG", "Lag", or "lAG".
Keyboard keys
The following keyboard keys perform special functions in CLI mode.
Table 3 Function of keyboard keys in CLI mode
Keyboard key Function
Enter l submits commands

l scrolls down one line
Spacebar scrolls down one page
Up and Down arrows l When used at the prompt, scroll through previously entered
commands.
l Within a command, scroll through previously entered parameter
values.
Tab Activates the Autocomplete feature; see Autocomplete on page 14.

l When entering a command.
l When entering a parameter value for which there is a limited set of
possible values, and where the options are not presented in a
sequentially numbered list.
CTRL-C Aborts the current command.
CTRL-A Moves to the first character in the line.
CTRL-E Moves to the end of the line.
CTRL-U Deletes the current line.
CTRL-D Deletes the character following the cursor’s current position.
CTRL-K Deletes text from the cursor’s position to the end of the line.
CTRL-W Deletes text from the cursor’s position to the beginning of the line.
Special characters
The following characters perform special functions for commands issued at the CLI
prompt.
Table 4 Function of special characters in CLI mode
Character Function
'' or ' Use quotation marks (single or double) to separate multi-word parameter values; see
Expert mode on page 19.
Working with the EMC RecoverPoint CLI in CLI mode 15

Introduction
Table 4 Function of special characters in CLI mode (continued)
Character Function
, Use a comma to separate multiple values of a parameter.
; Use a semicolon to separate commands when there are multiple commands in a

single command line; see Expert mode on page 19.
? When a command followed by a question mark (?) is typed, and Enter is pressed,
the system returns a description of the command and the syntax required for its
usage; see Help mode on page 17.
The same information is returned when help is typed before a command; for
example, help create_replica_copy; see Help mode on page 17.
Parameter values containing spaces

If a value is entered for a parameter that includes spaces—such as a bookmark name, or
a timeout value and unit—the entire expression must be surrounded with quotation
marks. Alternatively, you can eliminate the space.
For example:
A bookmark name for bookmark_image on page 48 could be either:
bookmark=121216production
or
timeout="121216 production"
It is good practice to use quotation marks for all values, even with those that do not
contain a space. As such, quotation marks are not valid characters in parameter values.
Units of measurement
The CLI is flexible in its recognition of units of measurement that are entered along with
parameter values.
There is no case-sensitivity for measurement units— the units can be entered in
uppercase, lowercase, or any mix of the two.
If there is a space between the value and its unit, you must surround the value and unit
with quotation marks, as described in Parameter values containing spaces on page 16.
Note
In all cases, 1 KB is equal to 1024 bytes.
The following table shows the acceptable forms for entering various units of
measurement in the CLI.
Table 5 Accepted forms for units of measurement
Unit Accepted forms

Gigabyte gb, gbyte, gbytes, gigabyte, gigabytes
Megabyte mb, mbyte, mbytes, megabyte, megabytes
Kilobyte kb, kbyte, kbytes, kilobyte, kilobytes

Introduction
Table 5 Accepted forms for units of measurement (continued)
Unit Accepted forms

Byte b, byte, bytes
Week wk, wks, week, weeks
Day d, day, days
Hour h, hr, hrs, hour, hours
Minute min, mins, minute, minutes
Second s, sec, secs, second, seconds
CLI modes
The following are the main modes of work in CLI mode:
l Help mode — used to display the full list of CLI commands in the RecoverPoint
system, and the system help information for each CLI command.
l Interactive mode — used to guide the user when running single commands, allowing
him to view each command parameter and its possible values, while running the
command.
l Expert mode — used to input multiple parameters and values for a single command.
Help mode
Help mode is a CLI mode accessed from the CLI session prompt RPA cluster>.
In help mode, users can display the full list of CLI commands in the RecoverPoint system,
and the system help information for each CLI command.
In help mode:
l Display a listing of all CLI commands by pressing:
<Tab>
l Display a list of all of the RecoverPoint CLI commands, together with a brief
description of each command by typing:
help <Enter>
l Display the required syntax and usage for a particular command by typing:
help <command> <Enter>
or
<command> ? <Enter>
Help mode output

EMC uses the following conventions in the CLI help output:
Table 6 Help output conventions
Output Example Indicate

parameter= copy=<copy name> Mandatory parameter and value. Parameters that are
<value> NOT enclosed in square brackets are mandatory. If a
value is not specified for a mandatory parameter, the
system issues an error message.
[...] [product=<...>] Optional parameter and value.
CLI modes 17
Introduction
Table 6 Help output conventions (continued)
Output Example Indicate

<> copy=<copy name> Parameter values. The contents of the angle brackets
<num> port=<integer> indicate the type to which the parameter value should
rpa=RPA<n> conform. For example:
<...>
l <copy name> must be the name of an existing copy
splitter=<...>
l <integer> must be an integral value
bookmark=<...>
l <...> indicates that any string or free text will be
accepted
| type=replication | journal Parameter value separator - alternate options.

priority=high | normal |
low
Interactive mode
Interactive mode is a CLI mode accessed from the CLI session prompt RPA cluster>.
Interactive mode is used to guide the user when running single commands.
In interactive mode, users are presented with each command’s parameters, syntax and
possible values, as they are requested by the system.
In interactive mode:
l Type the command, and press <Enter>. The system prompts you for the first parameter
value, if any.
l For mandatory parameters: If you press <Enter> without entering a value, the system
will display an error message, and prompt you again to enter a value. If you fail to
enter a value a second time, the system exits the command.
l For optional parameters: If you press <Enter> without entering a value, the system will
accept the default value for the parameter.
l CLI flags can be included in the command line; see Useful flags on page 18.
To display the system help information for a particular command, see Help mode on page
17.
Useful flags
The following flags are useful for inclusion in the command line in interactive mode.
Table 7 Useful command line flags in Interactive mode
Flag Example Description

Interactive flag -n Instructs system to use the default value for every parameter. If the
command includes mandatory parameters that are not specified, an
error is displayed.
XML flag -xml Instructs system to formulate output in XML and issue a return codes.
The following is an example of a command run in interactive mode:
RPA cluster> pause_transfer <Enter>

Enter consistency group name
group_1 <Enter>

Introduction
Enter copy name, or press ’ENTER’ for all copies of group

copy_1 <Enter>
Request to pause group data transfer registered successfully.
The following is an example of the same command with two mandatory parameters and a
force flag run in expert mode; see “Expert mode” on page 19:
RPA cluster> pause_transfer group=group_1 copy=copy_1 -f

Expert mode
CLI expert mode is a CLI mode accessed from the CLI session command prompt RPA
cluster>.
Expert mode is used to quickly input multiple parameters and their values for a single
command, simultaneously. Commands with more than one parameter can be run in
expert mode to speed up input efficiency, as you become more familiar with the
RecoverPoint CLI.
Expert mode is also used to quickly input CLI commands with only one mandatory
parameter.
In expert mode:
l Enter all mandatory and optional command parameters in a single statement
following the CLI prompt.
l The command must start with the command name, and can then be followed by
relevant parameters. Each parameter must have the format <parameter name>=value.
For example:
apply_parallel_bookmark groups=group1 bookmark=blue
l For commands with only one parameter, it is not necessary to include the parameter
name. You can just enter the parameter value after the command name.
For example:
config_io_throttling unlimited
l All mandatory parameters must be specified or the command will not run.
l There is no required order in which the parameters must appear in the command line,
and it is permissible to mix between the locations of mandatory and optional
parameters.
l When running a command that includes multiple-word parameter values, it is
mandatory to surround the command and the multiple-word value with double and
single quotes, respectively.
For example:
" get_rpa_states RPA cluster='New York'"
l CLI flags can be included in the command line; see Useful flags on page 20.
l To display the system help information for a particular command, see Help mode on
page 17.
Relevant commands
It is common to run the following commands in expert mode, after becoming more
familiar with their syntax.
CLI modes 19
Introduction
Commands with multiple mandatory parameters

CLI commands with multiple mandatory parameters are good candidates for running in
expert mode.
Commands with one mandatory parameter

It is also common to run commands with only one parameter in expert mode. This is
because for commands with only one parameter, it is not necessary to include the
parameter name. You can just enter the parameter value after the command name.
For example:
start_transfer group1
Note
All CLI commands that can be run in expert mode can also be run in interactive mode.
However, CLI commands with no parameters can only be run in interactive mode; see
Interactive mode on page 18.
Useful flags
The following CLI flags are useful for inclusion in the command line in expert mode:
Table 8 Useful command line flags in expert mode
Flag Example Description

Force flag -f Instructs system to suppress user confirmation prompts and any other
warnings or interactive queries related to the command.
XML flag -xml Instructs system to formulate output in XML and issue a return code.
The following is an example of a command run in expert mode with two mandatory
parameters and a force flag:
RPA cluster> pause_transfer group=group_1 copy=copy_1 -f


CHAPTER 2
List of Commands
l Commands............................................................................................................22
List of Commands 21
List of Commands
Commands
Table 9 List of CLI Commands
Command name Description
add_email_users on page 98 Assign filters to emails group.
add_role on page 114 Defines a new management role in the system, and sets the permissions
for that role.
add_ssh_key on page 115 Adds a public key to the current management user’s profile, allowing
him to open secure SSH sessions with the CLI, without specifying a
password.
add_user on page 115 Defines a new management user in the system, and sets the
permissions and password for that user.
balance_load on page 48 Assigns preferred RPAs to the specified consistency groups, to enable a
balanced distribution of writes across all RPAs.
bookmark_image on page 48 Creates a bookmark for the snapshot at the current point-in-time, and
sets its consolidation policy.
clear_events_log on page 99 Clears the events log.
clear_ldap_configuration on page 116 Removes all LDAP configurations
clear_markers on page 61 Clears markers from the journal volume, for a specified copy of a
specified group.
clear_security_settings on page 78 Removes all users, roles from the system. Clears LDAP settings and
security level.
config_automatic_snapshot_consolidation on page 78 Configures automatic snapshot consolidation for the specified group, at
the specified copy.
config_cluster_ids on page 32 Defines the software serial ID and location ID of a specified cluster for
the system reports mechanism (SyR).
config_copy_policy on page 50 Configures the replication policy for the specified copy of the specified
consistency group.
config_email on page 98 Configures the system alert mechanism settings.
config_group_policy on page 53 Configures the replication policy for the specified consistency group.
config_io_throttling on page 79 Sets the maximum storage read-rate and storage-awareness, per cluster
in a RecoverPoint configuration.
config_ldap on page 117 Defines the LDAP configurations.
config_link_policy on page 54 Configures the protection policy for the specified link of the specified
consistency group.
config_long_term_statistics on page 80 Sets whether or not to collect long term statistics.
config_preferred_rpas on page 60 Designates which RPA(s) to use when transferring the writes of the
specified group. Also used to define the group as a distributed
consistency group.
config_snmp_global on page 99 Configures the SNMP event trap global mechanism.

List of Commands
Table 9 List of CLI Commands (continued)
config_snmp_trap_dest on page 100 Configures the SNMP trap destination for the specified cluster.
config_syslogs_global on page 100 Configures the global syslog settings.
config_syslogs_target_host on page 101 Configures the syslog settings.
config_system_reports on page 81 Defines the configuration of system notifications sent to the system
report mechanism (SyR).
config_user_account on page 118 Defines the specified company name and contact email in the user
account settings.
create_event_filter on page 101 Creates new event filter for use with email/snmp/syslog.
detect_bottlenecks on page 82 Detects bottlenecks in the system.
disable_email on page 102 Disables the sending of system alerts through email, according to the
specified alert rules.
disable_image_access on page 61 Disables access to the replica image for which access is currently
enabled in the specified copy.
disable_snmp on page 103 Disables the SNMP agent.
disable_syslogs on page 103 Disables the syslog mechanism.
edit_event_filter on page 104 Edits the specified event filter.
enable_email on page 105 Enables the sending of system alerts by email.
enable_snmp on page 105 Enables the SNMP agent.
enable_syslogs on page 105 Enables the syslog mechanism.
export_consolidated_statistics on page 83 Exports system statistics and information on detected bottlenecks to a

file, for specified granularities and time frames.
export_statistics on page 84 Exports raw system statistics to the specified file.
finish_maintenance_mode on page 94 Finish the current mode of upgrade.
get_account_settings on page 119 Displays the user's account settings, for use in technical support
situations.
get_clusters_topology on page 33 Displays the connectivity topology between the environment's clusters.
get_current_time on page 128 Displays the current system date and time stamp, as used by the RPAs.
get_events_log on page 106 Displays the event logs.
get_group_settings on page 62 Displays the current settings of the specified group.
get_group_state on page 64 Displays the current state of the specified group, its copies, and its
links, in the RecoverPoint system.
get_group_statistics on page 66 Displays the current performance statistics of the specified group, its
copies and its links.
get_groups on page 85 Displays a list of all of the groups in the system, and the copies of each
group.
get_images on page 67 Displays information about the snapshots of the specified copy.
get_internal_cluster_name on page 33 Get the internal name of the specified cluster.
Commands 23
List of Commands
get_internal_cluster_uids on page 33 Displays the unique identifier(s) of the specified RPA cluster(s).
get_ldap_configuration on page 119 Displays the LDAP configurations.
get_monitored_parameters on page 108 Display monitored parameters whose value exceeds the specified
minimum severity.
get_raw_statistics on page 86 Displays unprocessed system statistics, for use in support situations.
get_rpa_settings on page 34 Displays the settings for the specified RPA(s) at the specified cluster(s).
get_rpa_states on page 34 Displays the state of communication between the RPAs at a specified
cluster, and other components of the system.
get_rpa_statistics on page 35 Displays the performance statistics of the RPAs at the specified RPA
cluster.
get_security_settings on page 86 Displays the current RPA communication security level.
get_splitter_states on page 28 Displays the current state of splitters in the system.
get_storage on page 40 Displays all of the arrays and vCenter servers that have been registered
at the specified RPA cluster.
get_system_report on page 87 Displays the current system report and sends it to the specified email
address.
get_system_report_settings on page 87 Displays the current system notification settings.
get_system_settings on page 88 Displays the settings of all of the clusters in the RecoverPoint system.
get_system_status on page 89 Displays the current problems in the system, by category, for the
specified RPA cluster.
get_versions on page 90 Displays the versions of RecoverPoint running on each cluster of the
environment.
get_volume_states on page 44 Displays the current state of RPA access to all replication volumes in the
specified group.
hijack_cluster on page 37 Hijacks a specified cluster by a given internal cluster name. Removes all
splitter volumes from a specified cluster. In virtual environments,
supports a user-activated, automated hijack procedure.
modify_role on page 120 Modifies an existing management role in the system. Can modify role
name and/or permissions.
pause_transfer on page 68 Pauses data transfer to the specified copy of the specified group.
regenerate_encryption_keys on page 121 Regenerate the keys used to encrypt and decrypt confidential data.
register_storage on page 40 Registers the specified arrays or vCenter servers on the specified RPA
cluster.
remove_email_users on page 109 Removes specified email users.
remove_event_filter on page 109 Remove selected event filter.
remove_role on page 121 Removes a management role from the system.
remove_ssh_key on page 122 Removes a public key from user’s authorized keys.
remove_user on page 122 Removes a management user from the system.

List of Commands
rescan_san on page 28 Refreshes the info in the SAN discovery cache.
set_advanced_action_regulation on page 90 Overrides the copy regulation setting defined for the system.
set_markers on page 70 Creates markers in the journal volume, for the specified replication set
in the specified copy and group.
set_password on page 122 Resets the password of the currently logged-in user.
set_security_level on page 123 Defines the security level for the currently logged-in management user.
set_smtp_server on page 91 Defines the server through which system email notifications, such as
system alerts and system reports, are sent.
set_snapshot_consolidation_policy on page 71 Sets the consolidation policy for the specified snapshot.
set_snmp_community on page 109 Defines the SNMPv1 community string.
set_user on page 123 Resets the password and/or permissions of an existing management
user.
show_integrity_check_status on page 72 Shows the progress of any integrity check running on the specified copy
of the specified group.
start_integrity_check on page 73 Starts checking the replication consistency between the source volumes
of the specified group and the volumes of the specified copy.
start_maintenance_mode on page 94 Switch to upgrade mode.
start_transfer on page 73 Starts data transfer to the specified copy of an enabled group.
stop_integrity_check on page 74 Stops checking the replication consistency between the source volumes
of the specified group and the volumes of the specified copy.
test_email on page 110 Sends a test mail item to the specified email address.
test_ldap_connection on page 124 Tests the LDAP configurations.
test_snmp on page 110 Tests whether SNMP traps can be sent.
test_syr_connectivity on page 110 Tests the connectivity of the system report mechanism (SyR) and opens
a Service Request with EMC Support.
test_syslogs on page 111 Tests the syslog mechanism.
undo_writes on page 74 Undoes all production writes saved in the image access log of the
specified copy journal since image access was enabled, without
disabling image access.
unlock_user on page 125 Unlocks system users that have been locked out of the system after
three failed attempts to log in.
unregulate_all_copies on page 91 Releases all copies from regulation.
update_vcenter_server_registration on page 96 Update the registration details for the specified vCenter Server at the
specified RPA cluster.
Commands 25
List of Commands

CHAPTER 3
Splitters
l get_splitter_states................................................................................................ 28
l rescan_san........................................................................................................... 28
Splitters 27
Splitters
get_splitter_states
Displays the current state of splitters in the system.
Permission
Read Only
Parameters
[cluster=<cluster name>]
[splitter=<splitter name>]
Descriptions
cluster (optional)
Name of the RPA cluster at which the splitter is located.
Default is all RPA clusters.
splitter (optional)
Name of a specific splitter for which to obtain state information.
Default is all splitters.
Notes
If no cluster is specified, the states of all splitters at all clusters are displayed. If no
splitter is specified, the states of all splitters at the specified cluster are displayed.
When using a VPLEX splitter, the splitter status of each VPLEX director is also displayed.
A VNX/CLARiiON splitter can be shared by multiple RPA clusters. The Number of
attached RPA clusters field indicates how many RPA clusters are sharing a
splitter.
If a volume is masked to more than one RPA cluster sharing the same VNX/CLARiiON
splitter, it can be attached to more than one RPA cluster. The volume, however, can only
be used by the first RPA cluster to which it is attached. It is in an error state for all other
RPA clusters, indicated by the Attached to other RPA cluster(s) state in the
Volume Access field. Use the detach_splitter command to detach the faulted
volume from the RPA cluster.
Note
To avoid this problem, a volume should be masked to a single RPA cluster. A volume that
is masked for one RPA cluster should not be masked for another RPA cluster.
rescan_san
Refreshes the info in the SAN discovery cache.
Permission
Read Only
Parameters
[cluster=<cluster names>]
[volumes=full | basic | none] (Default: basic)

Splitters
[splitters=yes | no] (Default: yes)

[splitter_volumes=<...> | all | none] (Default: all)
Descriptions
cluster (optional)
Name of the RPA cluster to be rescanned.
Default value is all RPA clusters.
volumes (optional)
Whether to scan the SAN at the specified RPA clusters for LUNs.
Possible values are full, basic, and none.
Default is basic.
splitters (optional)
Whether to scan the SAN at the specified RPA clusters for splitters - machines on
which the splitter has been installed.
Default is yes.
splitter_volumes (optional)
Splitter for which information on available paths to RecoverPoint volumes is to be
rescanned.
A splitter can be specified; other possible values are all and none.
Default is all.
Notes
The SANs in all clusters will be rescanned if no cluster is specified.
The volumes and splitters parameters specify whether or not to rescan the volumes
and/or splitters in the SAN respectively.
The basic volumes rescan detects new volumes, but not changes to existing volumes.
The full volumes rescan includes changes to existing volumes, and so can take several
minutes.
If splitters are being rescanned, the splitter_volumes parameter can be used to
rescan splitter-volume connections as well.
Either a particular splitter name can be specified or all or none.
If any error is encountered, the command will exit with return code 2 (Operation failed).
rescan_san 29
Splitters

CHAPTER 4
RPAs
l config_cluster_ids.................................................................................................32
l get_clusters_topology........................................................................................... 33
l get_internal_cluster_name....................................................................................33
l get_internal_cluster_uids......................................................................................33
l get_rpa_settings................................................................................................... 34
l get_rpa_states...................................................................................................... 34
l get_rpa_statistics..................................................................................................35
l sleep.....................................................................................................................36
l hijack_cluster........................................................................................................37
RPAs 31
RPAs
config_cluster_ids
Defines the software serial ID and location ID of a specified cluster for the system reports
mechanism (SyR).
Permission
System Configuration
Parameters
cluster=<cluster name>
[software_serial_id=<...>]
[location_id=<...>]
Descriptions
cluster
Name of the RPA cluster in the RecoverPoint system whose software serial ID or
location ID you want to set.
software_serial_id (optional)
The Software Serial ID (SSID) is the unique identifier of an RPA cluster in the
RecoverPoint system. The SSID is the identification used by the install base to
support EMC equipment installed at customer sites, through the system reporting
and ESRS mechanisms. The SSID is in the format <SN>EID<RPA cluster ID>.
The format and function of the SSID has changed from previous RecoverPoint
versions.
The SSID:
l Is generated for each RPA cluster when the first license 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. If no license was added for an RPA
cluster, the SSID of that RPA cluster will be empty.
l Can be displayed by running the get_system_settings CLI command, and
can only be modified by EMC Customer Support.
l Does not change with upgrades. When upgrading to RecoverPoint 4.0 from
previous RecoverPoint versions, the SSID value is taken from the value of the
SSIDs in the previous RecoverPoint version.
l Does not change even if the SN from which it was generated no longer exists in
any of the installed licenses.
location_id (optional)
Name of the geographical location at which the RecoverPoint system is installed.
Usually, this is the address of the company, as designated in the EMC sales order.
The location_id is the Site ID used in various EMC global processes. The
location ID:
l Is obtained from the value of the Site_Info parameter in the license file. Its
value is set by the first installed license for an RPA cluster. If no license was
installed for an RPA cluster, the Location ID of that RPA cluster will be empty.
l Can be displayed by running the get_system_settings CLI command, and
can only be modified by EMC Customer Support.

RPAs
l Does not change even if the Site_Info from which it was generated no longer
exists in any of the installed licenses.
Notes
DO NOT MODIFY THIS SETTING. This setting is for use only by EMC Customer Service.
get_clusters_topology
Displays the connectivity topology between the environment's clusters.
Permission
Read Only
Parameters
None
Notes
None
Example
To display the connectivity topology between RPA clusters:
RPA cluster> get_clusters_topology

Clusters topology:
New York -- London: IP
get_internal_cluster_name
Get the internal name of the specified cluster.
Permission
Upgrade
Parameters
Descriptions
cluster (optional)
Name of an existing RPA cluster.
Notes
None
get_internal_cluster_uids
Displays the unique identifier(s) of the specified RPA cluster(s).
Permission
Read Only
get_clusters_topology 33
RPAs
Parameters
Descriptions
cluster (optional)
Notes
Multiple RPA cluster names can be entered. Separate multiple cluster names with a
comma.
get_rpa_settings
Displays the settings for the specified RPA(s) at the specified cluster(s).
Permission
Read Only
Parameters
[rpa=RPA<n>]
Descriptions
cluster (optional)
rpa (optional)
Number of an existing RPA at the specified RPA cluster.
Default is all RPAs.
Notes
If a cluster is specified and no RPAs are specified, all RPAs at the cluster will be
presented.
If no cluster is specified, RPAs cannot be specified. In such case, all RPAs at all clusters
will be presented.
get_rpa_states
Displays the state of communication between the RPAs at a specified cluster, and other
components of the system.
Permission
Read Only
Parameters

RPAs
Descriptions
cluster (optional)
Notes
Displays the state of communication between the RPAs at the specified cluster, and:
l the repository volume
l other RPAs
l the replication and journal volumes
If no cluster is specified, the state of the RPAs at all clusters is displayed.
get_rpa_statistics
Displays the performance statistics of the RPAs at the specified RPA cluster.
Permission
Read Only
Parameters
[rpa=RPA<n>]
Descriptions
cluster (optional)
rpa (optional)
Number of an existing RPA in the specified RPA cluster.
Default is all RPAs.
Notes
If an RPA cluster is specified but no RPAs are specified, the statistics of all RPAs at the
cluster are displayed. If no RPA cluster is specified, RPAs cannot be specified. In such a
case, the statistics of all RPAs at all clusters are displayed.
For each RPA, the following information is displayed:
l SAN traffic handled by the cluster or RPA
l WAN/FC traffic generated by the cluster or RPA
l Compression ratio between the input and output for the cluster or RPA
l RPA CPU usage
l WAN latency to the peer RPA
l Packet loss experienced over the WAN to the peer RPA
get_rpa_statistics 35
RPAs
Note
The WAN field in the output shows all outgoing connections (either WAN or Fibre
Channel).
Example
RPA cluster> get_rpa_statistics

Enter cluster name, or press 'ENTER' for all clusters:
All RPAs:
London:
Cluster's RPAs:
RPA 1:
Traffic:
Application throughput:
SAN: 0 bps
WAN: None
Application incoming writes: 0
Compression ratio: None
Compression CPU usage: 20.00%
Computed connection:
New York:
Latency (ms): 0
Packet loss: 9.28%
RPA 2:
Traffic:
SAN: 0 bps
WAN: None
New York:
Latency (ms): 0
Packet loss: 9.28%
RPA 3:
Traffic:
SAN: 0 bps
WAN: None
New York:
Latency (ms): 0
Packet loss: 9.90%
sleep
Sets the number of seconds for the CLI session to sleep.
Permission
Read Only
Parameters
seconds<=integer> (Default: 3)

RPAs
Descriptions
seconds
Enter the number of seconds during which the CLI session will be in sleep mode.
Notes
This command can be run only non-interactively.
hijack_cluster
Hijacks a specified cluster by a given internal cluster name. Removes all splitter volumes
from a specified cluster. In virtual environments, this command supports an automated
hijack procedure that is user-activated.
Permission
Admin
Parameters
internal_cluster_name=<...>
Descriptions
cluster
Name of the vRPA cluster in the system.
internal_cluster_name
Internal name of the vRPA cluster.
Notes
This command is used when the internal cluster name was changed and the attached
splitters still have attached volumes to the old cluster, thus preventing the new cluster
from attaching volumes.
In virtual environments, this command supports an automated hijack procedure that is
user-activated. In this use case, the hijack includes:
l Removing license VM count
l Removing the cluster single sign-on token from the VC fields
l Cleaning the VMs
l Deleting the JUKE hierarchy tree for the specified cluster from every accessible
datastore
This is useful for cases in which a user incorrectly deletes a cluster.
hijack_cluster 37
RPAs

CHAPTER 5
Storage
l get_storage........................................................................................................... 40
l register_storage.................................................................................................... 40
Storage 39
Storage
get_storage
Displays all of the arrays and vCenter servers that have been registered at the specified
RPA cluster.
Permission
Storage Management
Parameters
Descriptions
cluster
The name of an existing RPA cluster in RecoverPoint.
Notes
None
register_storage
Registers the specified arrays or vCenter servers on the specified RPA cluster.
Permission
Storage Management
Parameters
name=<...>
type=<storage type>
[storage_unit=<...>]
[serial_number=<...>]
[ip_list=<...>]
primary_ip=<...>
[secondary_ip=<...>]
[use_fc=yes | no] (Default: no)
[port=<...>]
[authentication_scope=Local | Global | LDAP]
username=<...>
password=<...>
[array_mgmt_provider=<array provider name>]
[certificate=<...>]
Descriptions
cluster
The name of the RPA cluster where the array or vCenter Server is located
name
The name that you want to give the array or vCenter Server in RecoverPoint.
type
The type of the storage. Valid storage types are VNX, CLARiiON, ScaleIO, VPLEX,
XtremIO, vCenter Server, and DataDomain. In RecoverPoint/SE, only XtremIO, VNX,
CLARiiON and vCenter Server are valid types.

Storage
storage unit (optional)

Name of the DataDomain storage unit.
serial number (optional)

Serial number of the array or vCenter Server.
ip list (optional)
For ScaleIO environments only. This is a comma-separated list of one to eight IP
addresses of ScaleIO storage.
primary_IP
In VNX/CLARiiON environments, this is the IP address of SP A. For all other arrays,
this is the IP address of the array. For vCenter Servers, this is the IP address of the
vCenter Server.
secondary_IP (optional)
VNX/CLARiiON storage only. In VNX/CLARiiON environments, this is the IP address of
SP-A. This parameter is not relevant for all other arrays and vCenter Servers.
use_fc=yes | no (optional)
Specify whether or not to use Fibre Channel for DataDomain arrays. Default is yes.
port (optional)
When registering a vCenter Server, this is the TCP port number of the vCenter Server.
authentication_scope (optional)
VNX/CLARiiON storage only. Possible values are Global, Local and LDAP.
username
Login name of the user to the array or vCenter Server. In VNX/CLARiiON
environments, this is the Unisphere/Navisphere username. In VPLEX, this is the
platform username.
password
Password of the user to the array or vCenter Server. In VNX/CLARiiON environments,
this is the Unisphere/Navisphere password. In VPLEX, this is the platform password.
array_mgmt_provider (optional)
Name of the storage array provider.
certificate (optional)
For VPLEX arrays only. Path to the Active Directory certificate to use for secure
communication with the LDAP server. RecoverPoint accepts LDAP certificates only in
PEM format.
Notes
The certificate parameter is only relevant for VPLEX arrays.
The parameters secondary_ip and authentication_scope are only relevant for
VNX/CLARiiON storage.
The port parameter is only relevant for vCenter Servers.
register_storage 41
Storage

CHAPTER 6
Volumes
l get_volume_states................................................................................................44
Volumes 43
Volumes
get_volume_states
Displays the current state of RPA access to all replication volumes in the specified group.
Permission
Read Only
Parameters
[group=<group name>]
Descriptions
group (optional)
Name of an existing consistency group.
Default is all.
Notes
If no group is specified, the volume states of all volumes of all groups are displayed.
Example
RPA cluster> get_volume_states

Enter the group name, or press 'ENTER' for all groups:
Group:
cg1:
Copy:
copy1:
Volume:
Vplex lun # 0012:
RPA access: OK
Vplex lun # 0017:
Replication set: RSet0
RPA access: OK
copy2:
Volume:
Vplex lun # 0010:
RPA access: OK
Vplex lun # 0018:
RPA access: OK
prod:
Volume:
Vplex lun # 0001:
RPA access: OK
Vplex lun # 0025:
RPA access: OK
cg2:
Copy:
copy1:
Volume:
Vplex lun # 0010:
RPA access: OK
Vplex lun # 0028:
RPA access: OK
prod:
Volume:
Vplex lun # 0008:
RPA access: OK

Volumes
Vplex lun # 0011:

RPA access: OK
get_volume_states 45
Volumes

CHAPTER 7
Consistency Groups
l balance_load........................................................................................................ 48
l bookmark_image.................................................................................................. 48
l config_copy_policy............................................................................................... 50
l config_group_policy..............................................................................................53
l config_link_policy................................................................................................. 54
l config_preferred_rpas........................................................................................... 60
l clear_markers....................................................................................................... 61
l disable_image_access.......................................................................................... 61
l get_group_settings............................................................................................... 62
l get_group_state.................................................................................................... 64
l get_group_statistics..............................................................................................66
l get_images........................................................................................................... 67
l pause_transfer...................................................................................................... 68
l set_image_access_mode...................................................................................... 69
l set_markers.......................................................................................................... 70
l set_snapshot_consolidation_policy...................................................................... 71
l show_integrity_check_status................................................................................ 72
l start_integrity_check.............................................................................................73
l start_transfer........................................................................................................ 73
l stop_integrity_check............................................................................................. 74
l undo_writes.......................................................................................................... 74
Consistency Groups 47
Consistency Groups
balance_load
Assigns preferred RPAs to the specified consistency groups, to enable a balanced
distribution of writes across all RPAs.
Permission
Group Configuration
Parameters
[exclude_groups=<group names>]
[apply_recommendation=yes | no] (Default: no)
Descriptions
exclude_groups (optional)
The consistency groups to exclude from the recommendation.
apply_recommendation (optional)
Whether (yes) or not (no) to apply the load balancing suggestion.
Default is no.
Notes
This process can take several minutes.
When exclude_groups is specified, although groups are excluded from the
recommendation, they are included in the analysis.
Enter multiple group names in the form of a comma-separated list (For example: GroupA,
GroupB, GroupC).
When apply_recommendation is set to yes, every group whose preferred RPA is
modified as a result of the process will be initialized.
bookmark_image
Creates a bookmark for the snapshot at the current point-in-time, and sets its
consolidation policy.
Permission
Group Configuration
Parameters
[protection_entity=group | group_set] (Default: group)

groups=<group names>
[group_set=<group set name>]
bookmark=<...>
[consolidation_policy=never | survive_daily | survive_weekly |
survive_monthly | always] (Default: always)
[retention_time=<num>months | <num>weeks | <num>days] (Default:
forever)
[kvm=<...>]
[consistency_type=application_consistent | crash_consistent]
(Default: crash_consistent)

Consistency Groups
Descriptions
protection_entity
The RecoverPoint-protected entity that you wish to bookmark. Valid values are group
or group_set.
Default is group.
groups
The name of one or more existing group(s) in RecoverPoint.
group_set (optional)
The name of an existing group set in RecoverPoint.
bookmark
Bookmark name string.
Note
The word ’latest’ cannot be used as a bookmark name.
consolidation_policy (optional)
Consolidation policy to apply. Valid values are:
l never — Snapshot is never consolidated.
l survive_daily — Snapshot remains after daily consolidations, but is consolidated
in weekly, monthly, and manual consolidations.
l survive_weekly — Snapshot remains after daily and weekly consolidations, but
is consolidated in monthly and manual consolidations.
l survive_monthly — Snapshot remains after daily, weekly, and monthly
consolidations, but is consolidated in manual consolidations.
l always — Snapshot is consolidated in every consolidation process, whether
manual or automatic.
The default policy is always. If the consolidation_policy parameter is not

specified, the snapshot is consolidated in both automatic and manual consolidation
processes.
retention_time (optional)
Only for DataDomain groups. Retention time to apply to this snapshot. Valid values
are:
l <num>months — Number of months to retain the snapshot.
l <num>weeks — Number of weeks to retain the snapshot.
l <num>days — Number of days to retain the snapshot.
Default is forever.
kvm (optional)
Key-Value Metadata. Only for DataDomain groups. Enter key value pairs using the
key:value format. Separate multiple key-value pairs with commas. For example:
key1:value1,key2:value2.
bookmark_image 49
Consistency Groups
consistency_type (optional)
A tag used to identify RecoverPoint snapshots as either crash-consistent or
application-consistent. Valid values are:
l application_consistent — Snapshot has been marked as application-consistent
by the user or by KVSS. Note that marking a snapshot as application-consistent
does not create an application-consistent snapshot.
l crash_consistent — Snapshot is known to be crash-consistent. All RecoverPoint
snapshots are crash-consistent.
l Default is crash_consistent.
Notes
This command enables the same point-in-time to be identified at the other cluster.
This command is available whenever data transfer for the specified group is active.
'latest' is a reserved word and cannot be used as a bookmark name. The
consolidation_policy parameter sets the snapshot consolidation policy.
Valid values are:
l never - The snapshot will never be consolidated. Any consolidation process that
includes a snapshot with a consolidation policy of 'never' will fail.
l survive_daily - The snapshot will remain after automatic daily consolidations, but can
be consolidated during automatic weekly and monthly consolidations, or manual
consolidations.
l survive_weekly - The snapshot will remain after daily or weekly automatic
consolidation, but can be consolidated during automatic monthly consolidations, or
manual consolidations.
l survive_monthly - The snapshot will remain after daily, weekly or monthly
consolidation, but can be consolidated in any manual consolidation.
l always - The snapshot will be consolidated in every consolidation process, whether
The default snapshot consolidation policy is always.
This command allows you to bookmark an image for single group, multiple groups, or a
group-set.
The paramters groups and group_set cannot be set together.
The parameters retention_time and kvm are relevant only for DataDomain groups; in
this case consolidation_policy is not relevant.
config_copy_policy
Configures the replication policy for the specified copy of the specified consistency
group.
Permission
Group Configuration
Parameters
group=<group name>
copy=<copy name>
[protection_window=<num>months | <num>weeks | <num>days | <num>hrs |

Consistency Groups
none]
[max_journal_lag=<num>bytes | <num>KB | <num>MB | <num>GB | <num>TB |
unlimited]
[journal_size_limit=<integer>]
[journal_compression=high | medium | none]
[image_access_log_size=<number>]
[allow_long_resync=yes | no]
[allow_replication_with_self_mirroring=yes | no]
[hosts_os=AIX | HPUX | Linux 2.4 | Linux 2.6 | Solaris | VMware ESX |
VMware ESX Windows | Windows | Other/Mixed] (Default: Other/Mixed)
[max_number_of_snapshots=<number>]
[enable_cleanup=yes | no]
Descriptions
group
copy (optional)
Name of an existing copy.
protection_window (optional)
The consistency group protection window policy setting indicates the required
protection window, or in other words, how far in time the copy image can be rolled
back. This setting is used by RecoverPoint to trigger event alerts if the requirement
can not be obtained. The events table in the EMC RecoverPoint Administrator’s Guide
lists the events that will be triggered. Possible values are <num>months, <num>weeks,
<num>days, <num>hrs, or none.
Default is none.
The protection window setting must be greater than 24 hours for the predicted
protection window feature to function and generate events.
max_journal_lag (optional)
The maximum lag allowed in distributing replication data received by the journal.
When this limit is reached, the system accelerates distribution of data to copy
storage. Any snapshots, however, that are distributed in this accelerated mode (or
that were distributed before entering this accelerated mode) are not available for
rollback.
To prevent the system from entering the accelerated distribution mode, set this
parameter to unlimited. Otherwise, enter one of the following values, including a
number and a unit: bytes, kb, mb, or gb (with minimum granularity of 512 bytes—a
SCSI block).
Initial default is unlimited.
journal_size_limit (optional)
The maximum size in GB for the journal on each side of a consistency group.
journal_compression (optional)
The level of compression applied to the journal at the copy.
Possible values are high, medium, or none.
To change the value, one of the following states should exist for the group: the group
is disabled, both the production and the copy RPA clusters are active, or there is no
access to the copy image (while distributing).
Initial default is none.
config_copy_policy 51
Consistency Groups
image_access_log_size (optional)
Percentage of the available journal capacity at the copy that is allocated for use by
the target-side log.
Possible values are between 20 and 80.
To change the value, one of the following states should exist for the group: the group
is disabled, both sides are active, or there is no access to the copy image (while
distributing).
Initial default is 20.
allow_long_resync (optional)
Instructs the system how to proceed in the case that a snapshot is too large to be
completely contained in the journal. Possible values are yes and no.
When yes, the system starts writing the data of the snapshot to the copy storage
while the additional data of the same snapshot is still being received by the copy
journal. In this case, if a disaster were to strike at the production site before the
complete image was transferred to the copy storage, it would not be possible to fail
over to the copy.
When no, the system automatically pauses transfer when the last complete image is
about to be removed from the copy, providing the opportunity to; increase the
journal’s capacity, and then re-enable transfer, or prepare a backup and then re-
enable this policy.
Initial default is yes.
allow_replication_with_self_mirroring (optional)
Only relevant with Symmetrix splitter.
If yes, and only one RPA is available, if that RPA fails, the system will initiate a full
sweep. If no, and only one RPA is available, the spllitter will go into marking mode.
Replication will resume as soon as a second RPA in the cluster is available.
Do not change the default value unless instructed to do so by Customer Service.
hosts_os (optional)
Defines the Operating System (OS) of the host system from which the data is saved
and copied. Possible values are AIX, HPUX, Linux 2.4, Linux 2.6, Solaris, VMware
ESX, Windows, or Other/Mixed.
max_number_of_snapshots
Only relevant for non-production copies in XtremIO.
Specify the maximum number of XtremIO snapshots to preserve at the copy (2–500).
enable_cleanup
Specifies whether or not to enable cleanup. Possible values are yes and no.
Notes
None

Consistency Groups
config_group_policy
Configures the replication policy for the specified consistency group.
Permission
Group Configuration
Parameters
group=<group name>
[priority=critical | high | normal | low | idle]
[transfer_by_non_preferred=yes | no]
[allow_read_only=yes | no]
[metropoint_preferred_cluster=<...>]
Descriptions
group
priority (optional)
The priority assigned to the specified consistency group, in relation to other
consistency groups, with regard to allocation of available bandwidth resources for a
designated RPA. The parameter values are translated into a percentage of the
resources. Only relevant for remote replication over the WAN or Fibre Channel, when
two or more consistency groups are using the same Primary RPA. Possible values are
critical, high, normal, low, and idle.
Default is normal.
transfer_by_non_preferred (optional)
Determines whether data will transfer (yes) or not (no) when replication is switched
to another RPA, that is, when the preferred RPA is not handling replication for the
group.
Default is yes.
allow_read_only (optional)
Allows the user to change the accessibility mode of XtremIO and VNX volumes.
Set allow_read_only = yes to set volume accessibility to Read-Only for the
XtremIO and VNX volumes in the consistency group.
Set allow_read_only = no to set volume accessibility to No Access for the
XtremIO and VNX volumes in the consistency group.
metropoint_preferred_cluster (optional)
In a VPLEX MetroPoint group, sets the preferred cluster to either the active
production or standby production. Set to none to inform the system that it should
follow the VPLEX detach rules for the consistency group. To do a production
switchover, this parameter needs to be changed to the standby production.
Notes
The value of priority is in relation to other consistency groups. Groups with a priority
of critical are provided ten times the priority of normal groups. Groups with a priority of
high are provided three times the priority of normal groups. Groups with a priority of low
are provided 50% of the priority of normal groups. Groups with a priority of idle are
provided 1% of the priority of normal groups.
config_group_policy 53
Consistency Groups
The priority influences the allocation of available bandwidth only in asynchronous

replication.
In a VPLEX MetroPoint group, the metropoint_preferred_cluster parameter sets
the preferred cluster to either the active production or standby production. The parameter
can also be set to none, informing the system that it should follow the VPLEX detach rules
for the consistency group. To do a production switchover, this parameter needs to be
changed to the standby copy.
config_link_policy
Configures the protection policy for the specified link of the specified consistency group.
Permission
Group Configuration
Parameters
group=<group name>
copy_1=<copy name>
copy_2=<copy name>
[mode=sync | async]
[snap_based_replication=on_highload | continuous | periodic |manual |
disabled]
[periodic_snap_based_replication_interval=<number>]
[dynamic_by_latency=yes | no]
[start_async_above_latency=<integer>]
[resume_sync_below_latency=<integer>]
[dynamic_by_throughput=yes | no]
[start_async_above_throughput=<integer>]
[resume_sync_below_throughput=<integer>]
[rpo=<num>hrs | <num>mins | <num>secs | <num>bytes | <num>KB |
<num>MB | <num>GB | <num>TB | <num>writes | ]
[regulate_application=yes | no]
[minimize=lag | bandwidth]
[measure_lag_to_rpa=yes | no]
[snapshot_granularity=dynamic | fixed_per_second | fixed_per_write]
[fast_first_init=yes | no]
[compression=none | low | medium | high]
[deduplication=yes | no]
[bandwidth_limit=<number> | unlimited]
Descriptions
group
copy_1
Name of the first copy that serves as the endpoint of the link.
copy_2
Name of the second copy that serves as the endpoint of the link.
mode
Mode in which to replicate consistency group data between copy_1 and copy_2 of
the link. Possible values are sync or async. Default is async.
snap_based_replication (optional)
Mode in which to replicate array snaps between copy_1 and copy_1 . Possible
values are disabled, on_highload, periodic, continuous, or manual.

Consistency Groups
Default is disabled.
periodic_snap_based_replication_interval (optional)
When snap_based_replication is set to periodic, this parameter sets the
interval between snaps.
Default is 30 min.
dynamic_by_latency (optional)
Whether (yes) or not (no) to alternate between synchronous and asynchronous
replication modes, as necessary, according to latency conditions (the number of
milliseconds between the time the production data is written to the source RPA
cluster and the time that it is written to the RPA or journal at the target RPA cluster).
When enabled, RecoverPoint adheres to the limits specified for
start_async_above_latency and resume_sync_below_latency.
Default is no.
start_async_above_latency (optional)
Only relevant when dynamic_by_latency=yes.
The threshold (in milliseconds) at which to allow asynchronous replication. When

the specified limit is reached, the system automatically starts replicating in
asynchronous replication mode until the limit defined in
resume_sync_below_latency is reached.
resume_sync_below_latency (optional)
Only relevant when dynamic_by_latency=yes.
The threshold (in milliseconds) at which to allow synchronous replication. When the
specified limit is reached, the system automatically goes back to replicating in
synchronous replication mode.
dynamic_by_throughput (optional)
Whether (yes) or not (no) to alternate between synchronous and asynchronous
replication modes, as necessary, according to throughput conditions. When
enabled, RecoverPoint adheres to the limits specified for
start_async_above_throughput and
resume_sync_below_throughput.
Default is no.
start_async_above_throughput (optional)
Only relevant when dynamic_by_throughput=yes.
The threshold at which to allow asynchronous replication. When the specified limit is
reached, the system automatically starts replicating in asynchronous replication
mode until the limit defined in resume_sync_below_throughput is reached.
resume_sync_below_throughput (optional)
Only relevant when dynamic_by_throughput=yes.
The threshold at which to allow synchronous replication. When the specified limit is
reached, the system automatically goes back to replicating in synchronous
replication mode.
config_link_policy 55
Consistency Groups
rpo (optional)
The link recovery point objective (RPO) defines the lag of the consistency group link,
expressed in terms of time, quantity of data, or number of writes. In RecoverPoint,
lag starts being measured when a write made by the production host reaches the
local RPA, and stops being measured when the write reaches either the target RPA or
the target journal. Possible values are: hrs, mins, secs, bytes, KB, MB, GB, TB, and
writes. If any other solution is needed, contact EMC Customer Support. Default is
25sec.
regulate_application (optional)
When set to yes, the system slows or halts operation of the host applications upon
approaching a policy bound.
Initial default is no.
minimize (optional)
Possible values are lag or bandwidth.
When set to lag, the system uses as much bandwidth as it can to keep the lag to a
minimum. When set to bandwidth, the system expends additional bandwidth only as
necessary to keep the lag under its maximum allowable value.
Initial default is lag.
Note
This parameter is not applicable for local replication.
measure_lag_to_rpa (optional)
Only relevant for remote replication over the WAN or Fibre Channel. Possible values
are yes and no.
Whether to measure lag and generate ACKs when writes reach the remote RPA (yes)
or when they reach the remote journal (no).
When enabled, this policy provides faster performance in both synchronous and
asynchronous replication modes, by reducing both latency and lag. When
regulate_application is set to yes, and lag is reduced, so is the potential
requirement to regulate the host applications. In synchronous replication mode,
write performance is substantially higher with this policy enabled. However, when
this policy is enabled, RecoverPoint does provide a slightly lower level of data
security in the rare case of a simultaneous local and remote RPA disaster.
Initial default is yes. It is recommended to leave this setting as is.
This parameter is not relevant for local replication.
snapshot_granularity (optional)
When set to dynamic, the system determines the snapshot granularity of the
specified link according to available resources. When set to fixed_per_second, one
snapshot is created per second for the specified link. When set to fixed_per_write, a
snapshot is created for ever write operation for the specified link. Possible values
are dynamic, fixed_per_second, and fixed_per_write.
Default is fixed_per_second.

Consistency Groups
fast_first_init (optional)
Only relevant for initializations that occur for the first time, for the specified link.
Possible values are yes and no.
When set to yes, RecoverPoint transfers data directly to the copy storage. The data is
not stored in the journal first, and consequently, the initialization process is
substantially shorter. In this case, the non-production copy is not consistent with
production until the transfer of the whole image to the copy storage is complete.
Therefore, if a disaster were to strike at the production cluster before the transfer of
the image was complete, it would not be possible to fail over to the non-production
copy.
When set to no, RecoverPoint transfers data to the copy journal, and only then from
the copy journal to the copy storage. Disabling this policy is useful, for example,
when disabling and then enabling an existing consistency group, causing the group
to be initialized. In this case, RecoverPoint may be able to use the existing data at
the non-production cluster (journal and storage) to construct a complete image,
which is required for failover purposes.
To enable failover during initialization, it is recommended to disable both this policy
and the allow_long_resync policy parameter in the config_copy_policy
command. Possible values are yes and no.
Default is yes.
compression (optional)
The level of compression applied to replication data of the specified link prior to the
transfer of the data to a remote cluster. Can reduce transfer time significantly. 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. Possible values are none, low, medium, and high. When set to
no, compression is disabled.
Default is low if the license supports compression, or none if the license does not
support compression.
This parameter is only applicable for remote replication, in asynchronous replication
mode.
deduplication (optional)
Whether repetetive data of the specified link should be eliminated prior to the
transfer of the data to a remote cluster. Can reduce transfer time significantly.
Compression must be enabled before deduplication can be enabled. Both the
enabling and disabling of deduplication causes a short pause in transfer and a short
initialization. Deduplication decreases transfer time, but increases the source RPA’s
CPU utilization.
Possible values are: yes (enabled) or no (disabled). Default is yes if the license
supports compression, or no if the license does not support compression.
This parameter is only applicable for remote replication, in asynchronous replication
mode.
bandwidth_limit (optional)
The maximum bandwidth available in Mbps for use by the specified link. Possible
values are a number or unlimited. If there is no effective limit in available bandwidth,
enter unlimited. Otherwise, enter a number value. Default is unlimited. Read
Bandwidth limit on page 58 to understand important limitations of this parameter.
Consistency Groups
Notes
Asynchronous and dynamic synchronous modes

The following parameters are relevant only for asynchronous and dynamic synchronous
mode:
l rpo
l regulate_application
l minimize
Any change to the values of these parameters will cause transfer for the group to be
briefly paused.
Remote links
The following parameters are relevant only for remote links:
l minimize
l compression
l deduplication
l bandwidth_limit
Measure lag to RPA

For any link, it is highly recommended that measure_lag_to_rpa be set to yes in both
replication modes. Specifically, in synchronous replication, setting
measure_lag_to_rpa to no will cause substantially higher latency for the writes of
the production application.
Snap-based replication
Before setting the snap_based_replication parameter to anything other than
disabled, ensure you have registered the vCenter server of the specified group by running
the register_vcenter_server command.
The parameter periodic_snap_based_replication_interval is only relevant
when setting snap_replication to periodic. The interval value must be between 1
and 1440 minutes (1 day). When setting an interval, the RPO setting must be specified in
time, and the specified interval value must be less than half of the specified RPO value.
Snap-based replication cannot be enabled if:
l One or more of the RPA clusters in the specified group are running a RecoverPoint
version that does not support snap-based replication.
l The replication mode is set to synchronous.
l Storage awareness is not supported by the array or vCenter Server on which this
group's production volumes are located.
l The array or vCenter server on which the production copy resides does not support
snaps. In this case, RecoverPoint asynchronous replication mode will be used
instead.
Note
The application regulation will be disabled when the link is configured with snap-based
replication.
In XtremIO environments, the snap_based_replication parameter cannot be set to

on_highload.
Bandwidth limit
The bandwidth limitation applies to a specific RPA on a specific global link (a global link
is defined as all of the group links between two clusters). The actual limitation is the sum

Consistency Groups
of the group-link limitations of all enabled groups that run on this RPA for the given global
link. The group-link limitation defines the contribution of the specified group to the
overall limitation of the RPA(s) that replicates this group.
The specified limit is enforced only if each of the CG links on the RPA is set to a specific
value (other than default).
For example, an RPA has 3 CG links running on it, and you set a bandwidth limit on each
of the CG links as follows:
l CG1 link > bandwidth_limit = 30 Mbps
In this case, the overall bandwidth limit on the RPA is 100 Mbps. Note that CG1 may
consume more than 30 Mbps if CG2 and CG3 are consuming less than their allocated
amounts.
The next example shows CG1 and CG2 links set to specific bandwidth limits, but the CG3
link is not specified by the user and defaults to unlimited:
l CG3 link > bandwidth_limit = unlimited
In this case, even though CG links 1 and 2 are set to specific values, those values are not
enforced, and there is no bandwidth limitation on those links or on the RPA.
Latency and throughput
When both dynamic_by_latency and dynamic_by_throughput are enabled, the
system will start replicating asynchronously if EITHER of the values specified for
start_async_above_latency or start_async_above_throughput are true.
However, after the group starts replicating asynchronously, BOTH
resume_sync_below_latency and resume_sync_below_throughput must be
true before the group automatically reverts to synchronous replication mode.
The parameters start_async_above_throughput and
resume_sync_below_throughput are only relevant when
dynamic_by_throughput is set to YES. The parameters
start_async_above_latency and resume_sync_below_latency are only
relevant when dynamic_by_latency is set to YES.
The system will issue an error in the following cases:
l If the value of resume_sync_below_latency is not lower than the value of
start_async_above_latency.
l If the value of resume_sync_below_throughput is not lower than the value of
start_async_above_throughput.
l If the value of resume_sync_below_throughput or
resume_sync_below_latency equals zero.
Consistency Groups
config_preferred_rpas
Designates which RPA(s) to use when transferring the writes of the specified group. Also
used to define the group as a distributed consistency group.
Permission
Group Configuration
Parameters
group=<group name>
[primary_rpa=RPA<n>]
[distributed_group=yes | no]
[secondary_rpas=RPA<n>]
Descriptions
group
primary_rpa (optional)
Specifies the RPA to handle replication for the consistency group, at an RPA cluster.
The <n> symbol represents the number of the RPA at the RPA cluster. Specification of
a different RPA while replication is in progress causes immediate switchover.
distributed_group (optional)
Whether (yes) or not (no) to define this group as a distributed consistency group,
enabling the specification of preferred secondary RPAs, and distributing group traffic
among multiple RPAs. Both enabling and disabling this setting causes the journal of
all copies in the consistency group to be lost.
secondary_rpas (optional)
Specifies the secondary RPAs to handle replication for the consistency group, at an
RPA cluster. The <n> symbol represents the number of the RPA at the RPA cluster.
Specification of a different RPA while replication is in progress causes immediate
switchover.
One to three secondary RPAs can be defined. For best performance, it is not
recommended to specify two secondary RPAs. Best practice is to specify an even
number of preferred RPAs including the primary RPA (that is, either one or three
secondary RPAs.)
Notes
When the value of distributed_group is yes, enter at least one, but no more than
three values for the secondary_rpas parameter. Enter multiple values in the form of a
comma-separated list.
WARNING
Whenever the value of distributed_group is modified from yes to no or vice-versa,

data transfer is briefly paused and a full sweep begins.

Consistency Groups
clear_markers
Clears markers from the journal volume, for a specified copy of a specified group.
Permission
Data Transfer
Parameters
group=<group name>
[copy=<copy name>]
Descriptions
group
copy (optional)
Notes
Before using this command, ensure that transfer is paused and the consistency group is
enabled.
If no copy is specified, the markers for all copies are cleared.
Use this command only when you are certain that the source and target replication
volumes are identical (for example, when initializing from tape). If the volumes are not
identical, they will become and will remain inconsistent when transfer resumes. All
cleared markers are unrecoverable.
disable_image_access
Disables access to the currently accessed image of the specified copy and and resumes
distribution.
Permissions
Target Image
Parameters

[copy=<target copy name>]
[start_transfer=yes | no] (Default: yes)
Descriptions
protection_entity
The RecoverPoint-protected entity that you wish to disable image access for. Valid
values are group or group_set.
Default is group.
group
clear_markers 61
Consistency Groups
Name of an existing group set.
cluster (optional)
When selecting a group set, this parameter defines the RPA cluster at which you
want to disable image access. Image access will be disabled for all accessed copies
at this RPA cluster in the specified group set.
copy (optional)
When selecting a group, this parameter defines the copy for which you want to
disable image access.
start_transfer (optional)
Whether (yes) or not (no) to start replication for the specified groups or group set
after image access is disabled.
Default is yes.
Notes
If the host is directly accessing the storage, run this command and set
start_transfer to yes to disable direct access and resume replication.
The following parameters are relevant only for group:
l group
l copy
The following parameters are relevant only for group-set:
l group_set
l cluster
get_group_settings
Displays the current settings of the specified group.
Permission
Read Only
Parameters
[output_entity=group | copy | link | replication_set] (Default: group)

[copy=<copy name>]
[copy_2=<copy name>]
[replication_set=<replication set name>]
Descriptions
output_entity (optional)
Name of the entity (of the specified group) whose settings you want to display.
Possible values are group, copy, link and replication set. If the value of
output_entity is group, you must also define a value for group. If the value of
output_entity is copy, you must also define the values of group and copy. If the
value of output_entity is link, you must also define the values of group, copy,
and copy_2. If the value of output_entity is replication_set, you must also
define the values of group and replication_set.
Default is group.

Consistency Groups
group (optional)
Name of an existing consistency group. When the group is specified is a MetroPoint
group, the settings for both the active and standby productions will be displayed, as
well as the preferred MetroPoint cluster.
Default is all existing consistency groups.
copy (optional)
Name of an existing copy in the specified consistency group. This parameter is only
valid when the value of output_entity is copy.
Default is all existing copies in the specified consistency group.
copy_2 (optional)
valid when the value of output_entity is link.
Default is all existing links in the specified consistency group.
replication_set (optional)
Name of an existing replication set in the specified consistency group. This
parameter is only valid when the value of output_entity is replication_set.
Default is all existing replication sets in the specified consistency group.
Notes
If no group is specified, the current settings of all groups are displayed.
Example

Enter the output entity:
1) group
2) copy
3) link
4) replication_set
Select, or press 'ENTER'
Enter a consistency group name, or press 'ENTER' for all groups:
Groups:
cg:
Enable: YES
Production Copy: P1
Preferred primary RPA: RPA 2
Distributed group: NO
Reservation support: YES
Fail all production: NO
Policy:
Priority: NORMAL
Advanced Policies:
Non-preferred RPA transfer: YES
Allow read only: NO
External mgmt:N/A
Copies:
L1:
Cluster: London
Role: REMOTE COPY
Enable: YES
Hosts OS: Other/Mixed
Data transfer: YES
Image Access:
Enable access: NO
Policy:
Journal compression: NONE
get_group_settings 63
Consistency Groups
Automatic snapshot consolidation:

Enabled: NO
Unconsolidated duration: 2 days
Daily consolidations: 5
Weekly consolidations: 4
Monthly consolidations: ALL
Required protection window:N/A
Advanced policies:
Max Journal lag: UNLIMITED
Allow long resync: YES
Logged writes proportion: 20.00%
Reservations policy: Auto
P1:
Cluster: Paris
Role: PRODUCTION
Enable: YES
Hosts OS: Other/Mixed
Policy:
Journal compression: NONE
Automatic snapshot consolidation:
Enabled: NO
Unconsolidated duration: 2 days
Daily consolidations: 5
Weekly consolidations: 4
Monthly consolidations: ALL
Required protection window:N/A
Advanced policies:
Max Journal lag: UNLIMITED
Allow long resync: YES
Logged writes proportion: 20.00%
Reservations policy: Auto
Replication sets:
RSet0:
Size: 6.00 GB
RSet1:
Size: 5.00 GB
Links:
P1->L1:
Copy 1: P1
Copy 2: L1
Protection settings:
Active: YES
Mode: ASYNC
Regulate application: NO
Minimize: LAG
RPO: 25 sec
Snapshot granularity: DYNAMIC
Fast first-time init: YES
Measure lag to RPA: YES
Compression: low
Deduplication: NO
Bandwidth limit: UNLIMITED
Snap-based replication:N/A
Integrity validation policy: DISABLE
get_group_state
Displays the current state of the specified group, its copies, and its links, in the
RecoverPoint system.
Permission
Read Only

Consistency Groups
Parameters
[output_entity=group | copy | link] (Default: group)

[copy=<copy name>]
[copy_2=<copy name>]
Descriptions
output_entity (optional)
Name of the entity (of the specified group).
group (optional)
Default is all existing consistency groups.
copy (optional)
valid when the value of output_entity is copy.
copy_2 (optional)
valid when the value of output_entity is link.
Notes
If no group is specified, the state of all consistency groups is displayed.
Example
RPA Cluster> get_group_state

Enter the consistency group name, or press 'ENTER' for all groups:
Group:
cg1:
Enabled: YES
Transfer source: prod
Copy:
copy1:
Enabled: YES
Active primary RPA: RPA 3
Journal: DISTRIBUTING IMAGES TO STORAGE
Storage access: NO ACCESS
copy2:
Enabled: YES
Journal: DISTRIBUTING IMAGES TO STORAGE
Storage access: NO ACCESS
prod:
Enabled: YES
Storage access: DIRECT ACCESS (marking data)
Link:
prod->copy1:
Data Transfer: ACTIVE
Sync mode: NO
prod->copy2:
Data Transfer: ACTIVE
Sync mode: NO
get_group_state 65
Consistency Groups
get_group_statistics
Displays the current performance statistics of the specified group, its copies and its links.
Permission
Read Only
Parameters
Descriptions
group (optional)
Default is all.
Notes
If no group is specified, the performance statistics of all groups are displayed.
Example
RPA cluster> get_group_statistics

Enter the group name, or press 'ENTER' to display the statistics of
all consistency groups:
Group:
cg1:
Copy stats:
copy1:
Journal:
Usage: 154.07GB
Total: 204.10GB
Latest image: Thu Aug 1 07:33:40.732718 2013
Journal lag: 1.81GB
Protection window:
Current:
Value: 5 min 43 sec
Status:N/A
Predicted:
Value:N/A
Status:N/A
Average journal compression ratio:N/A
Mode: Normal
copy2:
Journal:
Usage: 225.40GB
Total: 298.30GB
Journal lag: 1.91GB
Protection window:
Current:
Value: 5 min 43 sec
Status:N/A
Predicted:
Value:N/A
Status:N/A
Mode: Normal
prod:
SAN traffic:
Current throughput: 72 Mbps
Average throughput: 72 Mbps

Consistency Groups
Current write IOPS: 2050

Average write IOPS: 0
Link stats:
prod->copy1:
Replication:
Lag:N/A
WAN traffic:N/A
Current bandwidth reduction ratio:N/A
Average bandwidth reduction ratio:N/A
Current deduplication ratio:N/A
Average deduplication ratio:N/A
prod->copy2:
Replication:
Lag:
Time: 5 sec
Data: 49.70MB
Writes: 13170
WAN traffic: 10 Mbps
Current bandwidth reduction ratio: 7.24282
cg2:
Copy stats:
copy1:
Journal:
Usage: 334.73GB
Total: 455.30GB
Journal lag: 1.91GB
Protection window:
Current:
Value: 30 sec
Status:N/A
Predicted:
Value:N/A
Status:N/A
Mode: Normal
prod:
SAN traffic:
Current throughput: 71 Mbps
Average throughput: 71 Mbps
Current write IOPS: 2033
Average write IOPS: 0
Link stats:
prod->copy1:
Replication:
Lag:
Time: 6 sec
Data: 54.53MB
Writes: 14484
WAN traffic: 9 Mbps
Current bandwidth reduction ratio: 6.75498
get_images
Displays information about the snapshots of the specified copy.
Permission
Read Only
get_images 67
Consistency Groups
Parameters
group=<group name>
[copy=<copy name>]
[from=HH:MM[:SS[:MICROS]] [DD/MM/YYYY]]
[to=HH:MM[:SS[:MICROS]] [DD/MM/YYYY]]
[bookmark=<...>]
Descriptions
group
copy (optional)
from (optional)
Start time.
Default date is no earliest bound. Default time is no earliest bound.
to (optional)
End time.
Default date is today.
Default time is the present time.
bookmark (optional)
Name of a specific snapshot bookmark.
Default is all.
Notes
Up to 1000 snapshots are displayed. Use the optional parameters to filter the results.
If the copy parameter is not specified, the snapshot information of all copies in the
group is displayed.
The from and to parameters can also take the format wks|days|hrs|mins ago. For
example: 5 mins ago. MICROS is a six-digit value for microseconds.
If the bookmark parameter is specified, only images matching the bookmark are
displayed.
pause_transfer
Pauses data transfer to the specified copy of the specified group.
Permission
Data Transfer
Parameters


Consistency Groups
Descriptions
protection_entity
The RecoverPoint-protected entity that you wish to stop replicating to. Valid values
are group or group_set.
Default is group.
group
copy (optional)
Name of the existing copy to stop replicating to.
Default is all.
Notes
If no copy is specified, data transfer is paused to all copies in the group.
When data transfer is paused, the transfer of replication data stops. However, the host
application continues to write data to storage, and the RPA continues to write markers
regarding the data to the repository volume.
set_image_access_mode
Changes the access mode of the currently accessed image at the specified copy.
Permission
Target Image
Parameters

mode=virtual_with_roll | direct
Descriptions
protection_entity
The protected entity that you wish to set the image access mode for. Valid values are
group or group_set.
Default is group.
group
set_image_access_mode 69
Consistency Groups
cluster (optional)
want to set the image access mode. The image access mode will be set for all
accessed copies at this RPA cluster in the specified group set.
copy (optional)
When selecting a group, this parameter defines the copy at which you want to set the
image access mode.
start_transfer (optional)
After setting the image access, whether to start replication (yes) or not (no) for the
specified group or group set.
Default is yes.
mode
The way the copy accesses the image.
Notes
Before using this command, make sure image access is enabled or a request to enable
image access is pending.
l group
l copy
The following parameters are relevant only for group-set:
l group_set
l cluster
set_markers
Creates markers in the journal volume, for the specified replication set in the specified
copy and group.
Permission
Data Transfer
Parameters
group=<group name>
[copy=<copy name>]
[replication_sets=<replication set names>]
Descriptions
group
copy (optional)
Default is all.
replication_sets (optional)
Name of an existing replication set.
Default is all.

Consistency Groups
Notes
Before using this command, ensure that transfer is paused and the consistency group is
enabled.
If no copy is specified, markers are created for all copies of all replication sets in the
specified group.
If no replication sets are specified, markers are created for all replication sets in the
specified copy of the group.
Create markers for multiple replication sets by providing multiple values in the
replication_sets parameter, separated by commas.
set_snapshot_consolidation_policy
Sets the consolidation policy for the specified snapshot.
Permission
Group Configuration
Parameters
group=<group name>
copy=<copy name>
[new_consolidation_policy=never | survive_daily | survive_weekly |
survive_monthly | always]]
[retention_time=<num>months | <num>weeks | <num>days] (Default:
forever)
[kvm=<...>]
[consistency_type=application_consistent | crash_consistent]
Descriptions
group
copy
new_consolidation_policy (optional)
Consolidation policy to apply to this snapshot. Valid values are:
l never — Snapshot is never consolidated.
l survive_daily — Snapshot remains after daily consolidations, but is consolidated
in weekly, monthly, and manual consolidations.
l survive_weekly — Snapshot remains after daily and weekly consolidations, but
is consolidated in monthly and manual consolidations.
l survive_monthly — Snapshot remains after daily, weekly, and monthly
consolidations, but is consolidated in manual consolidations.
l always — Snapshot is consolidated in every consolidation process, whether
If the new_consolidation_policy parameter is not specified, the snapshot is

consolidated in both automatic and manual consolidation processes.
retention_time (optional)
Only for DataDomain. Retention time to apply to this snapshot. Valid values are:
set_snapshot_consolidation_policy 71
Consistency Groups
l <num>months— Number of months to retain the snapshot.

l <num>weeks— Number of weeks to retain the snapshot.
l <num>days— Number of days to retain the snapshot.
Default is forever.
kvm (optional)
Only for DataDomain. Key-Value Metadata. Enter key value pairs using the key:value
format. Separate multiple key-value pairs with commas. For example:
key1:value1,key2:value2.
consistency_type (optional)
Consistency type to apply to this snapshot. Valid values are:
l application_consistent— Application consistent snapshot.
l crash_consistent— Crash consistent snapshot.
Notes
This command can only be run interactively. When prompted, select a snapshot from the
list and set a new consolidation policy for the selected snapshot.
The new_consolidation_policy parameter sets the snapshot consolidation policy.
Valid values are:
l never - The snapshot will never be consolidated. Any consolidation process that
includes a snapshot with a consolidation policy of 'never' will fail.
l survive_daily - The snapshot will remain after automatic daily consolidations, but can
be consolidated during automatic weekly and monthly consolidations, or manual
consolidations.
l survive_weekly - The snapshot will remain after daily or weekly automatic
consolidation, but can be consolidated during automatic monthly consolidations, or
manual consolidations.
l survive_monthly - The snapshot will remain after daily, weekly or monthly
consolidation, but can be consolidated in any manual consolidation.
l always - The snapshot will be consolidated in every consolidation process, whether
show_integrity_check_status
Shows the progress of any integrity check running on the specified copy of the specified
group.
Permission
Security
Parameters
group=<group name>
copy=<target copy name>
Descriptions
group

Consistency Groups
copy
Name of the copy at which an integrity check is in progress, whose progress status
you want to check.
Notes
None
start_integrity_check
Starts checking the replication consistency between the source volumes of the specified
group and the volumes of the specified copy.
Permission
Security
Parameters
group=<group name>
Descriptions
group
copy
Name of the copy whose integrity you want to check.
Notes
Cannot perform replication integrity check on XtremIO arrays or during snap-based
replication.
If a possible replication integrity issue is detected, use the set_markers command to
trigger a full sweep. If problem persists, contact EMC Customer Support.
start_transfer
Starts data transfer to the specified copy of an enabled group.
Permission
Data Transfer
Parameters

Descriptions
protection_entity
The protected entity that you wish to start replication for. Valid values are group or
group_set.
Default is group.
start_integrity_check 73
Consistency Groups
group
copy (optional)
Defines the copy to which you want to start replicating.
Notes
If no copy is specified, data transfer is started to all copies in the group.
l group
l copy
The following parameters are relevant only for group set:
l group_set
l cluster
stop_integrity_check
Stops checking the replication consistency between the source volumes of the specified
group and the volumes of the specified copy.
Permission
Security
Parameters
group=<group name>
Descriptions
group
copy
Name of the copy with an integrity check in progress, that you want to stop.
Notes
None
undo_writes
Undoes all production writes saved in the image access log of the specified copy journal
since image access was enabled, without disabling image access.
Permission
Target Image
Parameters


Consistency Groups

Descriptions
protection_entity
The protected entity that you wish to undo writes for. Valid values are group or
group_set.
Default is group.
group
cluster (optional)
want to undo writes. The writes will be undone for all accessed copies at this RPA
cluster in the specified group set.
copy (optional)
When selecting a group, this parameter defines the copy at which you want to undo
writes.
Notes
Before using this command, at the host, shut down all applications and unmount all
volumes belonging to the specified consistency group.
l group
l copy
The following parameters are relevant only for group set:
l group_set
l cluster
undo_writes 75
Consistency Groups

CHAPTER 8
System
l clear_security_settings..........................................................................................78
l config_automatic_snapshot_consolidation........................................................... 78
l config_io_throttling...............................................................................................79
l config_long_term_statistics.................................................................................. 80
l config_system_reports.......................................................................................... 81
l detect_bottlenecks............................................................................................... 82
l export_consolidated_statistics............................................................................. 83
l export_statistics....................................................................................................84
l get_groups............................................................................................................85
l get_raw_statistics................................................................................................. 86
l get_security_settings............................................................................................ 86
l get_system_report................................................................................................ 87
l get_system_report_settings.................................................................................. 87
l get_system_settings............................................................................................. 88
l get_system_status................................................................................................ 89
l get_versions......................................................................................................... 90
l set_advanced_action_regulation...........................................................................90
l set_smtp_server....................................................................................................91
l unregulate_all_copies...........................................................................................91
System 77
System
clear_security_settings
Removes all users, roles from the system. Clears LDAP settings and security level.
Permission
Security
Parameters
None
Descriptions
None
Notes
WARNING
This command removes all external users. You cannot run this command if you are not
local user.
Example
To clear all users and roles currently defined in the system:
RPA cluster> clear_security_settings

Are you sure you want to clear all security settings(y/n)? Y
Security settings cleared successfully.
config_automatic_snapshot_consolidation
Configures automatic snapshot consolidation for the specified group, at the specified
copy.
Permission
Group Configuration
Parameters
group=<group name>
copy=<copy name>
[enable=yes | no]
[unconsolidated_duration=<num>months | <num>weeks | <num>days |
<num>hrs]
[daily_consolidations=<integer> | ALL]
[weekly_consolidations=<integer> | ALL]
Descriptions
group
copy
enable (optional)
Whether automatic snapshot consolidation for the specified group at the specified
copy is to be enabled (yes) or disabled (no).
Default is initially no, and then current value.

System
Note
When automatic snapshot consolidation is enabled, the predicted protection

window is not calculated.
unconsolidated_duration (optional)
The period of time for which data should not be consolidated.
The period’s start time is always today, and the period’s end time is expressed in n
hours/days/weeks, with a 12 hour minimum.
Default is 2 days, and then current value.
daily_consolidations (optional)
The number of days in which to consolidate snapshots on a daily basis. Daily
consolidations happen every 24 hours, give or take a couple of hours. Possible
values are n days or all.
Default is 5, and then current value.
weekly_consolidations (optional)
The number of weeks in which to consolidate images on a weekly basis. Weekly
consolidations happen every 168 hours, give or take a couple of hours. Possible
values are n weeks or all.
Default is 4, and then current value.
Notes
For automatic snapshot consolidation to occur, the specified group cannot be part of a
group set.
For the unconsolidated_duration parameter, enter a value of 12 hours or more.
After the total period of time specified by the unconsolidated_duration,
daily_consolidations and/or weeky_consolidations parameters has passed,
all consolidations will be done on a monthly, unless:
l the value of the daily_consolidations parameter is set to ALL, in which case
weekly consolidations are not allowed, and the remaining snapshots are
consolidated daily.
l the value of the weeky_consolidations parameter is set to ALL, in which case
the remaining snapshots are consolidated weekly.
config_io_throttling
Sets the maximum storage read-rate, per array in the SANView.
Permission
Data Transfer
Parameters
[array_serial_number=<...>]
[throttling=low | high | custom | none]
[custom_value=<integer>]
config_io_throttling 79
System
Descriptions
cluster (optional)
Name of the RPA cluster for which you want to configure throttling. If no value is
entered, the specified throttling level is applied at all RPA clusters.
array_serial_number (optional)
The serial number of the array whose I/Os to throttle to the specified throttling level
or custom value.
throttling (optional)
The maximum rate that the specified array or RPA cluster can read from a storage
device during initialization.
Possible values are low, high, custom, and none:
l When set to high, the read-rate of the specified arrays or RPAs in your
RecoverPoint cluster is limited to 50 MBps. In the case of an RPA cluster, this
means that the read-rate of a single RPA is limited to 50 MBps divided by the
number of RPAs in the RecoverPoint cluster, per array.
l When set to low, the read-rate of the specified arrays or all RPAs in your
RecoverPoint cluster is limited to 200 MBps. In the case of an RPA cluster, this
means that the read-rate of a single RPA is limited to 200 MBps divided by the
number of RPAs in the RecoverPoint cluster, per array.
l When set to custom, use the custom_value parameter to enter the read-rate.
l If no value is entered, the current value is displayed, per RPA cluster.
l Initial default value is none and then keep current value.
custom_value (optional)
When throttling is set to custom, a custom value can be entered in MBps.
Notes
When setting the throttling level, remember that the higher the throttling level, the longer
initializations will take. Ensure that a low throttling level is insufficient before setting the
throttling level to high.
config_long_term_statistics
Sets whether or not to collect long term statistics.
Permission
Read Only
Parameters
[enabled=yes | no]
Descriptions
enabled (optional)
When enabled, RecoverPoint collects system statistics.
Default is yes.

System
Notes
None
config_system_reports
Defines the configuration of system notifications sent to the system report mechanism
(SyR).
Permission
Parameters
[enable=reports_and_alerts | reports_only | none]

[compression=yes | no]
[encryption=yes | no]
[transfer_method=ESRS | SMTP | FTPS]
[server_address=<...>]
[sender_email=<...>]
Descriptions
enable (optional)
Enables or disables reports and/or alerts.
Possible values are reports_and_alerts, reports_only, and none.
Default is reports_and_alerts
compression (optional)
Whether to compress the output (yes) or not (no).
Default is yes, and then current value
encryption (optional)
Whether to encrypt the output of the system report with RSA encryption using a 256-
bit key before sending (yes) or not (no).
Default is yes, and then current value
transfer_method (optional)
The means by which to send system reports. Possible options are FTPS (to send
reports through RecoverPoint’s built in FTPS server), ESRS (to send reports through
an ESRS gateway, which requires the specification of an IP address in the
server_address parameter), or SMTP (to send reports through email, which
requires the specification of an SMTP server through set_smtp_server on page 91).
Default is SMTP, and then current value.
server_address (optional)
Only valid when the transfer_method parameter value is ESRS. Enter an IP
address in IPv4 format.
Default is disabled, and then current value.
sender_email (optional)
Defines the email address that appears as the sender’s email for alerts and reports.
Notes
To use an email (SMTP) server to send system notifications, before you begin, run
set_smtp_server on page 91 to define your email server. The server_address
config_system_reports 81
System
parameter is only relevant when transfer_method is set to ESRS. The value of

server_address should be entered in IPv4 format only.
detect_bottlenecks
Detects bottlenecks in the system.
Permission
Read Only
Parameters
[mode=System overview and bottleneck analysis | Detection of

initialization periods | Detection of high load periods | General
detection including initialization and high load periods with peak
writing analysis | Advanced and detailed general detection | Peak
writing analysis] (Default: System overview and bottleneck analysis)
[advanced_overview=yes | no]
[detailed_overview=yes | no]
[peak_duration=<num>months | <num>weeks | <num>days | <num>hrs |
<num>mins | <num>secs] (Default: 5mins)
[groups=<group names>]
Descriptions
mode (optional)
Type of analysis.
Possible values are System overview and bottleneck analysis, Detection of
initialization periods, Detection of high load periods, General detection including
initialization and high load periods with peak writing analysis, Advanced and
detailed general detection, and Peak writing analysis.
Default is System overview and bottleneck analysis.
from (optional)
Start time for analysis is in hh:mm [:ss[:micros]] [dd/mm/yyyy] format, where the date,
if not specified with the time, is today. Alternatively, it can be expressed in n wks/
days/hrs/mins ago .
Default is no specified start time; that is, use the earliest statistics available.
Enter times according to local time. Output is according to GMT.
to (optional)
End time for analysis is in hh:mm [:ss[:micros]] [dd/mm/yyyy] format, where the date,
if not specified with the time, is today. Alternatively, it can be expressed in n wks/
days/hrs/mins ago.
Default is no specified end time; that is, the current time.
Enter times according to local time. Output is according to GMT.
advanced_overview (optional)
Whether the analysis covers a broader set of system performance indicators (yes) or
does not (no).
Default is no.

System
detailed_overview (optional)
Whether the analysis is confined to the specified RPA cluster only (no) or to also
includes the analysis of all groups and RPAs (yes).
Default is no.
peak duration (optional)

Length of the peak load period, expressed as n hrs/mins/secs.
Default is 5 mins.
groups (optional)
List of one or more existing consistency groups. Use commas to separate groups. To
analyze only global statistics, without statistics on individual groups, enter none.
Default is all.
Notes
None
export_consolidated_statistics
Exports system statistics and information on detected bottlenecks to a file, for specified
granularities and time frames.
Permission
Read Only
Parameters
[granularity=minute | hour | day | all] (Default: all)

[interval_start=HH:MM[:SS[:MICROS]] [DD/MM/YYYY]]
[interval_end=HH:MM[:SS[:MICROS]] [DD/MM/YYYY]]
Descriptions
granularity (optional)
Granularity of the exported statistics. Possible values are minute, hour, and day.
Default is all granularities.
interval_start (optional)
Time from which statistics at the specified granularity should be collected for export.
Value should be entered in hh:mm [:ss[:micros]] [dd/mm/yyyy] format, where if the
date is not specified with the time, the date is today. Alternatively, it can be
expressed in n wks/days/hrs/mins ago.
Default is earliest time available.
interval_end (optional)
Time until which statistics at the specified granularity should be collected for export.
Value should be entered in hh:mm [:ss[:micros]] [dd/mm/yyyy] format, where if the
date is not specified with the time, the date is today. Alternatively, it can be
Default is latest time available.
Notes
You are notified if there are no statistics available for the specified time frame.
export_consolidated_statistics 83
System
The name of the exported file is long_term_stats.tar.gz, and is located in the /

home/www/info/long_term_stats directory. The file is rewritten each time the
command is executed.
NOTICE
The time filtering parameters (interval_start and interval_start) should be

specified in local time, while the times in the resulted statistics file presented in GMT.
export_statistics
Exports raw system statistics to the specified file.
Permission
Read Only
Parameters
[include_global_statistics=yes | no] (Default: yes)
[rpa=RPA<n>]
[groups=<group names> | none]
[categories=<...>] (Default: overview)
[frequency=<num>months | <num>weeks | <num>days | <num>hrs |
<num>mins | <num>secs]
[file=<file name>]
Descriptions
from (optional)
Start time for filtering the statistics is in hh:mm [:ss[:micros]] [dd/mm/yyyy] format,
where the date, if not specified with the time, is today. Alternatively, it can be
Default is no time filter.
to (optional)
End time for filtering the statistics is in hh:mm [:ss[:micros]] [dd/mm/yyyy] format,
where the date, if not specified with the time, is today. Alternatively, it can be
expressed in n wks/days/hrs/mins ago format.
Default is no time filter; that is, the current time.
include_global_statistics (optional)
Statistics that are not specific to particular group or groups.
Default is yes.
cluster (optional)
rpa (optional)
List of one or more RPAs. Use commas to separate RPAs. Possible values are RPAn,
where n is the number of the RPA at the RPA cluster.

System
groups (optional)
List of one or more existing consistency groups. Use commas to separate groups. To
export only global statistics, without statistics on an individual group (or groups),
enter none.
Default is all groups.
categories (optional)
Possible values are compression, highload, init, overview, performance, regulation,
and wan.
Default is all categories.
frequency (optional)
Frequency (in hrs/mins/secs) at which to sample the statistics for inclusion in the
exported statistics.
Minimum frequency is 1 min.
Default is 1 min.
file (optional)
Name of file system to which you want to export the statistics. The file, <file>.csv, is
created in the folder named <file>.
Notes
None
get_groups
Displays a list of all of the groups in the system, and the copies of each group.
Permission
Read Only
Parameters
None
Descriptions
None
Notes
None
Example
To display the groups defined in the system, and their copies:
RPA cluster> get_groups

Groups:
Group1:
Copies:
Local Site: Group1 Prod, Group2 Copy
Group2:
Copies:
Local Site: Production
Remote Site: Remote Copy
Group3:
Copies:
Local Site: Remote copy
Remote Site: Production, Local copy
get_groups 85
System
get_raw_statistics
Displays unprocessed system statistics, for use in support situations.
Permission
Read Only
Parameters
[rpa=RPA<n>]
[categories=<...>]
[accumulators=<accumulator name>]
Descriptions
cluster (optional)
rpa (optional)
The RPA number of the RPA that handles replication for the consistency group.
Possible values are RPAn, where n is the number of the RPA at the RPA cluster.
group (optional)
categories (optional)
Possible values are global, lag, dataflow, diskManager, acker, pinger, ponger,
snapshot, deltaMarker, application, compression, distributor, highload, and ctrl.
accumulators (optional)
One or more accumulator names.
Notes
EMC Customer Support can instruct you about how to use the optional parameters to
filter the information returned by the command.
The categories and accumulators parameters are space-separated lists containing
one or more items.
Possible values for categories are: global, lag, dataflow, diskManager, acker, pinger,
ponger, snapshot, deltaMarker, application, compression, distributor, highLoad, and ctrl.
get_security_settings
Displays local users' security level and RPA communications security level.
Permission
Security
Parameters
None

System
Notes
RPA communication security level can be changed in the Installation Manager (boxmgmt
menu).
get_system_report
Displays the current system report and sends it to the specified email address.
Permission
Read Only
Parameters
[address=<...>]
Descriptions
address (optional)
A valid email address in the format user@company.com.
Notes
If you want to send the current system report to a specified email address, before you
begin, run set_smtp_server on page 91 to define your email server.
To send the current system report to an email address right now, enter a valid email
address in the address field, in the format user@company.com. If no address is specified,
the system report is only displayed on the screen.
The system report is sent to the specified email address in XML format.
get_system_report_settings
Displays the current system notification settings.
Permission
Read Only
Parameters
None
Descriptions
None
Notes
To define the system notification settings, run config_system_reports on page 81.
Example
To display the system report settings:
RPA cluster> get_system_report_settings

Enabled: Reports and alerts
Compressed: YES
Encrypted: YES
Transfer method: SMTP
Server address:
Sender email:
get_system_report 87
System
get_system_settings
Displays the settings of all of the clusters in the RecoverPoint system.
Permission
Read Only
Parameters
None
Descriptions
None
Notes
None
Example
To display all of the system settings:
RPA cluster> get_system_settings

Clusters:
London:
Software serial ID:N/A
Location ID:N/A
Cluster management IPv4: 12.34.56.86
Repository volume:
Type: VNX
UID: 60,b6,01,6a,c4,a1,1e,80,05,c1,e6,1d,ba,d7,dc,1c,f6
Vendor: DGC
Product: CX
Model: CX3-40
Size: 300.00GB
Name: VOL ID: 0000
Array Serial: Ser#100
RPA To volume paths map: None
vCenter Server settings:
vCenter Servers: None
IO throttling:
Throttling level: none
Enabled storage awareness: YES
New York:
Software serial ID:N/A
Location ID:N/A
Cluster management IPv4: 12.34.56.78
Repository volume:
Type: VNX
UID: 60,b6,01,6a,c4,a1,1e,80,05,c1,e6,1d,ba,d7,dc,1c,f6
Vendor: DGC
Product: CX
Model: CX3-40
Size: 300.00GB
Name: VOL ID: 0000
Array Serial: Ser#100
RPA To volume paths map: None
vCenter Server settings:
vCenter Servers: None
IO throttling:
Throttling level: none
Enabled storage awareness: YES

System
get_system_status
Displays the current problems in the system, by category, for the specified RPA cluster.
Permission
Read Only
Parameters
[category=system | splitters | RPAs | volumes | WANs | groups | all]

[summary=yes | no] (Default: no)
Descriptions
category (optional)
Component of the system for which you are requesting status information. Possible
values are RPAs, volumes, splitters, WAN, and system.
Default is all categories.
cluster (optional)
Name of the RPA cluster for which you are requesting status information.
summary (optional)
Whether the output consists of a tally of the problems for each category at each RPA
cluster (yes) or specific information is displayed for each problem (no).
Default is no.
Notes
A summary of the current issues in the system is displayed automatically upon logging
into the CLI.
Use category to filter the displayed issues by system, splitters, RPAs, volumes, WANs,
or groups.
Example
RPA cluster> get_system_status

Select the category of issues to display: (default is all categories)
1) system
2) splitters
3) RPAs
4) volumes
5) WANs
6) groups
7) all
Select, or press 'ENTER':
Enter the RPA cluster name, or press 'ENTER' for all RPA clusters:
Display summarized output? (Default: no)
1) yes
2) no
System problems: OK
Clusters problems:
London:
RPAs: OK
Volumes: OK
get_system_status 89
System
Splitters:
WARNING: Splitter FNM00104100108 doesn't have login
credentials. To minimize user configuration errors, provide splitter
logi
n credentials.
logi
n credentials.
New York:
RPAs: OK
Volumes: OK
Splitters:
logi
n credentials.
logi
n credentials.
WANs problems: OK
Groups problems: OK
get_versions
Displays the versions of RecoverPoint running on each cluster of the environment.
Permission
Read Only
Parameters
None
Descriptions
None
Notes
N/A will appear when there is no communication with the cluster or when the RPAs in the
cluster are running different versions (during upgrade).
Example
To display the RecoverPoint version:
RPA cluster> get_versions

<RPA cluster>: 4.1
<RPA cluster>: 4.0
set_advanced_action_regulation
Overrides the copy regulation setting defined for the system.
Permission
Group Configuration
Parameters
[enable=yes | no]

System
Descriptions
enable (optional)
Whether to regulate all groups at all copies (yes) or not (no).
Notes
Do not run this command unless specifically instructed to do so by the Customer
Support.
set_smtp_server
Defines the server through which system email notifications, such as email alerts and
system reports, are sent.
Permission
Parameters
[server_address=<...>]
Descriptions
server_address (optional)
The IP address or DNS name of a dedicated SMTP server.
Notes
The server_address value must be defined to enable the sending of email
notifications. Enter the server address in the form of an IP address or DNS name. Enter an
empty value for server_address to display the current SMTP server IP address or DNS
name.
unregulate_all_copies
Releases all copies from regulation.
Permission
Group Configuration
Parameters
None
Descriptions
None
Notes
Do not run this command unless specifically instructed to do so by the Customer
Support.
set_smtp_server 91
System

CHAPTER 9
Maintenance
l finish_maintenance_mode....................................................................................94
l start_maintenance_mode......................................................................................94
Maintenance 93
Maintenance
finish_maintenance_mode
Finish the current mode of upgrade.
NOTICE
This command is for internal use only and should not be used.
Permission
Upgrade
Parameters
Descriptions
cluster (optional)
Notes
This command is for internal use only and should not be modified.
start_maintenance_mode
Switch to upgrade mode.
NOTICE
This command is for internal use only and should not be used.
Permission
Upgrade
Parameters
mode=major_upgrade | minor_upgrade | rpa_addition | rpa_replacement |

rpse_conversion | system_modification | user_initiated |
connect_cluster | migrate_repository
Descriptions
mode
Type of upgrade.
Possible values are major_upgrade, minor_upgrade, rpa_addition, rpa_replacement,
rpse_conversion, system_modification, user_initiated, connect_cluster, and
migrate_repository.
cluster
Notes
This command is for internal use only and should not be modified.

CHAPTER 10
Virtual Machine
l update_vcenter_server_registration...................................................................... 96
Virtual Machine 95
Virtual Machine
update_vcenter_server_registration
Updates the registration details for the specified vCenter Server at the specified RPA
cluster.
Permission
Splitter Configuration
Parameters
name=<vCenter name>
[new_name=<...>]
[new_ip=<...>]
[new_port=<number>]
[new_user_name=<...>]
[password=<...>]
[new_certificate=<...>]
[validate_credentials=yes | no] (Default: yes)
Descriptions
cluster
The RPA cluster where the vCenter Server is located.
name
The name of the vCenter Server.
new_ip (optional)
If the IP address of the vCenter Server has changed, enter the new IP address.
new_port (optional)
If the TCP port number of the vCenter Server has changed, enter the new port
number.
new_user_name (optional)
If the vCenter Server username has changed, enter the new username.
password (optional)
The password of the vCenter Server.
new_certificate (optional)
If the vCenter Server certificate has changed, paste the new vCenter Server certificate
at the command line, then press Enter, enter one period (.), and press Enter again.
Paste the entire vCenter Server certificate at the command line, then press Enter,
enter one period (.), and press Enter again.
validate_credentials (optional)
Whether or not to validate vCenter Server credentials.
Notes
None

CHAPTER 11
Events
l add_email_users...................................................................................................98
l config_email......................................................................................................... 98
l clear_events_log................................................................................................... 99
l config_snmp_global..............................................................................................99
l config_snmp_trap_dest.......................................................................................100
l config_syslogs_global.........................................................................................100
l config_syslogs_target_host.................................................................................101
l create_event_filter.............................................................................................. 101
l disable_email..................................................................................................... 102
l disable_snmp..................................................................................................... 103
l disable_syslogs.................................................................................................. 103
l edit_event_filter..................................................................................................104
l enable_email...................................................................................................... 105
l enable_snmp...................................................................................................... 105
l enable_syslogs................................................................................................... 105
l get_events_log....................................................................................................106
l get_monitored_parameters................................................................................. 108
l remove_email_users........................................................................................... 109
l remove_event_filter............................................................................................ 109
l set_snmp_community......................................................................................... 109
l test_email........................................................................................................... 110
l test_snmp...........................................................................................................110
l test_syr_connectivity.......................................................................................... 110
l test_syslogs........................................................................................................ 111
Events 97
Events
add_email_users
Assign filters to emails group.
Permission
Parameters
emails=<...>
type=immediate | daily
event_filters=<event filter names>
Descriptions
emails
Set of email addresses that are to receive event notifications subject to the settings
for the type and event_filters parameters.
type
The alert frequency.
Possible values are immediate or daily.
event_filters
Defines the set of events that are to be sent to this email group.
There is no default value for this parameter.
Notes
None
config_email
Configures the system alert mechanism settings.
Permission
Parameters
[sender=<...>]
[system_info_support_daily=yes | no]
Descriptions
sender (optional)
Email address from which system alerts and reports originate.
system_info_support_daily (optional)
Whether to send a daily report of system information to the EMC System Report
Database for monitoring and pre-emptive support (yes) or not (no).
Initial default is no.

Events
Notes
Before you begin, to enable the sending of emails, run enable_email on page 105 to
enable the emails mechanism. Then, run and enter your SMTP server IP or DNS name as
the server_address.
To display a specific email address in the from field of email alerts, enter a valid email
address in the format user@company.com as the sender value. Note that your SMTP
server may require additional configuration to forward messages for the specified sender.
Customers that have signed a remote maintenance agreement can configure
system_info_support_daily to send alert messages regarding RecoverPoint
operations to the Customer Service on a daily basis.
To disable the sending of emails, run disable_email on page 102.
clear_events_log
Clears the events log.
Permission
Security
Parameters
None
Descriptions
None
Notes
None
Example
To clear the events log:
RPA cluster> clear_events_log

Are you sure you want to clear all of the events from the event log
(y/n)? y
Event log cleared successfully.
config_snmp_global
Configures the SNMP event trap global mechanism.
Permission
Parameters
[enabled=yes | no]
[event_filters=<event filter names>]
[enable_secure_transport=yes | no]
Descriptions
enabled (optional)
Whether RecoverPoint events generate SNMP traps (yes) or do not generate SNMP
traps (no).
Default is no.
clear_events_log 99
Events
event_filters (optional)
Defines the set of events that can generate SNMP traps.
enable_secure_transport (optional)
If enabled, port 10161 is available for Transport Layer Security on TCP. Use of
community strings and port 161 are disabled.
If disabled, port 161 is available and community strings are accepted.
Notes
When enabled, a trap destination must be specified for at least single cluster. Use
config_snmp_trap_dest on page 100 for such configuration.
config_snmp_trap_dest
Configures the SNMP trap destination for the specified cluster.
Permission
Parameters
trap_dest=<...>
Descriptions
cluster
trap_dest
The Internet address (IP address or DNS) of a host at the specified RPA cluster to
which to send SNMP traps.
Notes
The value of trap_dest is the Internet address (IP address or DNS) of a host at that
specified cluster, to which to send SNMP traps.
When enabled, a value must be specified for the cluster and trap_dest parameters.
config_syslogs_global
Configures the global syslog settings.
Permission
Parameters
[facility=auth | authpriv | cron | daemon | ftp | kern | local0 |

local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr |
mail | news | syslog | user | uucp]
[event_filters=<event filter names>]

Events
Descriptions
facility (optional)
Specifies the type of program that is logging the message.
Possible values are according to the syslog standard list, including: auth, authpriv,
cron, daemon, ftp, kern, local0, local1, local2, local3, local4, local5, local6, local7,
lpr, mail, news, syslog, user, and uucp.
Default is local6.
event_filters (optional)
Defines the set of events to be sent to the syslog servers.
Notes
None
config_syslogs_target_host
Configures the syslog settings.
Permission
Parameters
target_host=<...>
Descriptions
cluster
target_host
The IP address of the intended receiver of the log at the specified RPA cluster.
Notes
target_host is the name of the host to which to forward the syslogs in the specified
cluster.
create_event_filter
Creates new event filter for use with email/snmp/syslog.
Permission
Parameters
name=<...>
[topic=all | management | cluster | rpa | group | splitter] (Default:
all)
level=info | warning | error
[scope=normal | detailed | advanced] (Default: normal)
[excluded_events=<...>]
config_syslogs_target_host 101
Events
Descriptions
name
Name of the event filter to be created.
topic (optional)
The general area of the problem within the EMC RecoverPoint system.
Possible unique values are management, cluster, RPA, group, and splitter.
Default is all topics.
level
The severity of the event.
Possible values, in ascending order of severity, are info, warning, and error.
Recipients receive alerts of all events on the specified level, as well as any events of
greater severity.
scope (optional)
The required level of detail of the alert output. Possible values, in ascending order of
elaboration are normal, detailed or advanced.
Default is normal.
excluded_events (optional)
IDs of events that are not subject to this filter.
groups (optional)
The set of groups that are subject to this filter.
There is no default value for this parameter. When topic is all or group, it is
mandatory to designate one or more groups on which the filter is to be applied. For
other topics, this parameter is not relevant.
Notes
The group parameter is relevant only when topic is all or group.
Example
In the following example, a filter is created to send notifications regarding the specified
groups of all normal and detailed warning and error events, regardless of topic, except for
the events specified.
To create a new event filter:
RPA cluster> create_event_filter filter1 level=warning scope=detailed

excluded_events=8240,12222,14222,16222,18222
groups=exchange1,exchange2
Filter created successfully.
disable_email
Disables the sending of system alerts through email, according to the specified alert
rules.
Permission

Events
Parameters
None
Descriptions
None
Notes
None
Example
To disable the sending of e-mail alerts:
RPA cluster> disable_email

Are you sure you want to disable email alert? (y/n)y
Email alerts disabled successfully.
disable_snmp
Disables the SNMP agent.
Permission
Parameters
None
Descriptions
None
Notes
This command can only be run interactively.
Example
To disable the SNMP agent:
RPA cluster> disable_snmp

Are you sure you want to disable the SNMP agent? (y/n)y
SNMP agent disabled successfully.
disable_syslogs
Disables the syslog mechanism.
Permission
Parameters
None
Descriptions
None
Notes
None
disable_snmp 103
Events
Example
To disable the syslog mechanism:
RPA cluster> disable_syslogs

Are you sure you want to disable the syslog mechanism? (y/n)y
Syslog mechanism disabled successfully.
edit_event_filter
Edits the specified event filter.
Permission
Parameters
event_filter=<event filter name>

[name=<...>]
[topic=all | management | cluster | rpa | group | splitter]
[level=info | warning | error]
[scope=normal | detailed | advanced] (Default: normal)
Descriptions
event_filter
Name of an existing event filter.
name (optional)
New name for the event filter.
topic (optional)
The general area of the problem within the EMC RecoverPoint system.
Possible unique values are management, cluster, RPA, group, and splitter.
level (optional)
The severity of the event.
Possible values, in ascending order of severity, are info, warning, and error.
Recipients receive alerts of all events on the specified level, as well as any events of
greater severity.
scope (optional)
The required level of detail of the alert output. Possible values, in ascending order of
elaboration are normal, detailed or advanced.
IDs of events that are not subject to this filter.
groups (optional)
The set of groups that are subject to this filter.
When topic is all or group, it is mandatory to designate one or more groups on
which the filter is to be applied. For other topics, this parameter is not relevant.
Notes
None

Events
enable_email
Enables the sending of system alerts by email.
Permission
Parameters
None
Descriptions
None
Notes
To enable the sending of email alerts through email, before you begin, run
set_smtp_server on page 91 to define your email server.
To disable the sending of email alerts through email, run disable_email on page 102.
Example
To enable alerts:
RPA cluster> enable_email

Email alerts enabled successfully.
enable_snmp
Enables the SNMP agent.
Permission
Parameters
None
Descriptions
None
Notes
None
Example
To enable the SNMP agent:
RPA cluster> enable_snmp

SNMP agent enabled successfully.
enable_syslogs
Enables the syslog mechanism.
Permission
Parameters
None
enable_email 105
Events
Descriptions
None
Notes
None
Example
To enable the syslog mechanism:
RPA cluster> enable_syslogs

Syslog mechanism enabled successfully.
get_events_log
Displays the event logs.
Permission
Read Only
Parameters
[topic=management | cluster | rpa | group | splitter]
[level=info | warning | error] (Default: info)
[scope=normal | detailed | advanced]
[search_text=<...>]
[terse=yes | no] (Default: no)
[gmt_override=yes | no] (Default: no)
Descriptions
from (optional)
Start time for filtering the events log inhh:mm[:ss[:micros]] [dd/mm/yyyy] format,
where the date, if not specified, is today. Alternatively, it can be expressed in
n hours ago format.
Default is 24 hours ago.
to (optional)
End time for filtering the events log either in hh:mm[:ss[:micros]] [dd/mm/yyyy]format,
where the date, if not specified, is today. Alternatively, it can be expressed in n
hours ago format.
Default is the present time (0 hours ago).
topic (optional)
Possible values are management, cluster, RPA, group, and splitter.
Default is all topics.
level (optional)
Possible values, in ascending order of severity, are info, warning, and error. Each
value includes all of those logs that have more severe levels.
Default is info.

Events
scope (optional)
The required level of detail in the log output. Possible values, in ascending order of
elaboration are normal, detailed, and advanced.
Default is normal.
IDs of events that are not to be displayed.
search_text (optional)
Text strings to match with contents of event summary. The match should be exact,
including case. Multiple strings can be entered, separated by commas.
Default is no text.
terse (optional)
Whether to display one event per line (yes) or to use multiple lines per event (no).
Default is no.
gmt_override (optional)
Whether to override (yes) or use the system gmt settings (no).
Default is no.
Notes
The optional filter parameters can be used to narrow the results.
The from and to parameters can also take the format wks/days/hrs/mins ago (for
example, '5 mins ago').
The default value for the from parameter is 24hrs ago.
The topic parameter can be a list of topics (separated by ','). The default is all topics.
The search_text parameter is a string (or a comma separated list of strings) which can
be the name of any of the system components, for example, cluster, RPA, volume, host,
group, user or a specific string in the event summary.
The gmt_override parameter can be used to display event times in GMT, overriding
the current configuration.
Example
To display all events logged to the events log:
RPA cluster> get_events_log

Enter earliest time, or press 'ENTER' for 24hrs ago
(Format: HH:MM [DD/MM/YYYY] OR wks/days/hrs/mins ago)
Enter latest time, or press 'ENTER' for now
(Format: HH:MM [DD/MM/YYYY] OR wks/days/hrs/mins ago)
Topic: (default is all topics)
1) management
2) cluster
3) rpa
4) group
5) splitter
Select (separate with spaces if more than one), or press 'ENTER':
Level: (Default: info)
1) info
2) warning
3) error
get_events_log 107
Events

Scope: (default is normal)
1) normal
2) detailed
3) advanced
Enter a list of event ids to exclude
Enter search text(s) to match, or press 'ENTER' (separate with commas
if more than one)
Terse display? (Default: no)
1) yes
2) no
Display event times in GMT, overriding the current time display
configuration? (Default: no)
1) yes
2) no
System event logs:
Time: Thu Aug 1 03:26:57 2013
Topic: RPA
Scope: NORMAL
Level: CLEAR
Event ID: 3000
Cluster: London
Global links: None
RPA: RPA 8
Summary: RPA is successfully communicating with its
cluster.
Service Request info:N/A
Time: Thu Aug 1 03:26:57 2013
Topic: RPA
Scope: NORMAL
Level: CLEAR
Event ID: 3000
Cluster: London
Global links: None
RPA: RPA 7
Summary: RPA is successfully communicating with its
cluster.
Service Request info:N/A
get_monitored_parameters
Display monitored parameters whose value exceeds the specified minimum severity.
Permission
Read Only
Parameters
[min_severity=ok | minor | major | critical] (Default: ok)
Descriptions
min_severity (optional)
To display all monitored parameters that have at least the severity specified.
Default is ok.
Notes
None

Events
remove_email_users
Permission
Parameters
emails=<...>
Descriptions
emails
Email addresses that are to be removed from receiving email event notifications.
Notes
None
remove_event_filter
Remove selected event filter.
Permission
Parameters
event_filter=<event filter name>
Descriptions
event_filter
Name of the existing event filter that is to be removed.
Notes
None
set_snmp_community
Defines the SNMPv1 community string.
Permission
Parameters
enabled=yes | no
[community=<...>]
Descriptions
enabled
Enables the use of an SNMPv1 community string. For optimum security, do not
enable.
community (optional)
Community string of the specified user.
remove_email_users 109
Events
Notes
test_email
Sends a test email to the specified email address.
Permission
Parameters
address=<...>
Descriptions
address
Email address to which the test message will be sent.
Notes
Enter a valid email address in the format user@company.com as the address. To verify
that the alert system settings, as configured with the config_email command, are
defined successfully; a test email message will arrive at the specified address.
test_snmp
Tests whether SNMP traps can be sent.
Permission
Parameters
destination=<...>
Descriptions
destination
Internet address (IP address or DNS) of a host to which to send the SNMP trap.
Notes
None
test_syr_connectivity
Tests the connectivity of the system report mechanism (SyR) and opens a Service Request
with EMC Support.
Permission
Parameters
[recipient_email=<...>]

Events
Descriptions
recipient_email (optional)
The email address to which EMC Customer Support sends an email, verifying that the
system reports mechanism (SyR) has been successfully configured. The connectivity
test, if successful, opens a service request containing call home event number
30999 and sends an email to the specified email address from EMC Customer
Support to verify that the system reports mechanism (SyR) has been successfully
configured.
Notes
Before running this command, define your email server by running set_smtp_server on
page 91, and specify a transfer method by running config_system_reports on page 81.
To open a Service Request with EMC Customer Support, enter a valid email address in the
recipient_email field, in the format user@company.com.
After testing connectivity:
l EMC Customer Support will contact you to verify that they received the Service
Request and SyR has been correctly configured.
l Wait ten minutes. Then, check your event logs to ensure that event 1020 Failed to
send system report was not logged.
test_syslogs
Tests the syslog mechanism.
Permission
Parameters
[level=info | warning | error] (Default: info)
Descriptions
level (optional)
The event level of the syslog notification message.
Possible values are:
l info - tests information, warning, and error logs.
l warning - tests warning and error logs.
l error - tests error logs.
Default is info.
Notes
None
test_syslogs 111
Events

CHAPTER 12
Users
l add_role............................................................................................................. 114
l add_ssh_key.......................................................................................................115
l add_user.............................................................................................................115
l clear_ldap_configuration.................................................................................... 116
l config_ldap......................................................................................................... 117
l config_user_account........................................................................................... 118
l get_account_settings.......................................................................................... 119
l get_ldap_configuration....................................................................................... 119
l modify_role.........................................................................................................120
l regenerate_encryption_keys............................................................................... 121
l remove_role........................................................................................................ 121
l remove_ssh_key................................................................................................. 122
l remove_user....................................................................................................... 122
l set_password......................................................................................................122
l set_security_level............................................................................................... 123
l set_user.............................................................................................................. 123
l test_ldap_connection..........................................................................................124
l unlock_user........................................................................................................ 125
Users 113
Users
add_role
Defines a new management role in the system, and sets the permissions for that role.
Permission
Security
Parameters
name=<...>
[permissions=Splitter Configuration | Group Configuration | Data
Transfer | Target Image | Failover | System Configuration | Security
| Upgrade | Storage Management ]
Description
name
Name of the new management role.
permissions (optional)
Permission level granted to the newly defined role.
Default permission level is Read Only.
Notes
When prompted, enter the required role name, and permissions.
Management user permissions include:
l Splitter Configuration - User may add or remove splitters, and may attach or detach
splitters to volumes.
l Group Configuration - User may create/remove groups, and may modify all group
settings except those that are included in the Data Transfer, Target Image, and
Failover permissions, may bookmark images, and may resolve settings conflict.
l Data Transfer- User may enable/disable group, start/pause transfer, and clear/set
markers.
l Target Image - User may enable/disable access to image, and undo writes to the
target-side log.
l Failover - User may modify replication direction.
l System Configuration - User may configure and manage email alerts, SNMP, and
syslog utilities.
l Security - User may add/remove users, modify passwords (for all users), modify
permissions (for non-preconfigured users), install product activation code, set
account ID, set contact info, add/remove SNMP users, set the SNMP community, and
set number of streams.
l Upgrade - Used for system maintenance and upgrades. Commands with this
permission are for internal use only. Storage Management- Used for array awareness.
Read Only - By default, each role includes this permission. User may view system
information. You receive Read Only permission only, by pressing Enter without entering
any permissions.

Users
add_ssh_key
Adds a public key to the current management user's profile, allowing him to open secure
SSH sessions with the CLI, without specifying a password.
Permission
Read Only
Parameters
name=<...>
key=<...>
Descriptions
name
Name of the key to be added.
key
Key generated by the ssh-keygen facility.
Notes
Before running this command, generate a key pair (private and public) using the ssh-
keygen facility. This command adds a public key of type RSA to the user's profile in the
system. The type of key—RSA1 or RSA2—is determined by the –t flag in ssh-keygen. The
public key, used in conjunction with the user's private key (held by the machine on which
the user is working), enables the user of SSH to carry out a secure dialog with the system.
After adding the public key, the user only needs to enter a username to open an SSH
session with the CLI; a password is not required.
The ssh-keygen facility writes the public key to one of the following files:
l $user/.ssh/identity (for RSA1)
l $user/.ssh/id_rsa.pub (for RSA2)
The file contains the key that you must enter (copy and paste) at the Enter the key
prompt that is displayed when you run the add_ssh_key command.
add_user
Defines a new management user in the system, and sets the permissions and password
for that user.
Permission
Security
Parameters
type=local user | LDAP user | LDAP group (Default: local user)

[name=<...>]
[password=<...>]
[role=<...>]
Descriptions
type
Type of user to add.
add_ssh_key 115
Users
name (optional)
Name of the new user or group.
password (optional)
Password to assign to the new user or group.
role (optional)
Role (permissions) to assign to the new user or group.
groups (optional)
Groups to which the new user or group belongs.
Notes
This command can only be run interactively. When prompted, enter the required
username, password, role, and groups. The required password format depends on the
security level that is specified for the new management user. See help for
set_security_level on page 123 for more information.
l Data Transfer - User may enable/disable group, start/pause transfer, and clear/set
markers.
target-side log.
syslog utilities.
permission are for internal use only. Storage Management- Used for array awareness.
l Read Only - By default, each role includes this permission. User may view system
information.
You receive Read Only permission only, by pressing Enter without entering any
permissions.
clear_ldap_configuration
Removes all LDAP configurations
Permission
Security
Parameters
None

Users
Descriptions
None
Notes
None
Example
RPA1> clear_ldap_configuration
Are you sure you want to clear LDAP configuration(y/n)?y
LDAP configuration cleared successfully
config_ldap
Defines the LDAP configurations.
Permission
Security
Parameters
[enabled=yes | no]
[protocol_type=LDAP | LDAPs]
[primary_LDAP_Server=<...>]
[primary_LDAP_port=<integer>]
[secondary_LDAP_Server=<...>]
[secondary_LDAP_port=<integer>]
[base_dn=<...>]
[search_base_dn=<...>]
[bind_DN=<...>]
[password=<...>]
[certificate=<...>]
[search_time_limit=<integer>]
Descriptions
enabled (optional)
Activates RecoverPoint authentication and authorization using an LDAP server.
protocol_type (optional)
LDAP - To send LDAP queries over an unsecured port
LDAPs - To send LDAP queries over a secure SSL port
primary_LDAP_Server (optional)
IP address of primary LDAP server
primary_LDAP_port (optional)
Default secure port = 636
Default non-secure port = 389
secondary_LDAP_server (optional)
IP address of secondary LDAP server
secondary_LDAP_port (optional)
Default secure port = 636
Default non-secure port = 389
config_ldap 117
Users
base_dn (optional)
Base Distinguished Name: root of the LDAP directory tree.
search_base_dn (optional)
Search Base Distinguished Name: the root of the LDAP user search tree.
bind_DN (optional)
When using binding_type = simple, distinguished name to use for initial binding
when querying the LDAP server.
password (optional)
When using binding_type = simple, password of the bind distinguished name to use
for initial binding when querying the LDAP server.
certificate (optional)
If protocol_type = LDAPs, path to the Active Directory certificate to use for secure
communication with the LDAP server. RecoverPoint accepts LDAP certificates only in
PEM format.
search_time_limit (optional)
To set a time limit for the search.
Notes
None
config_user_account
Defines the specified company name and contact email in the user account settings.
Permission
Parameters
[company_name=<...>]
[contact_info=<...>]
Descriptions
company_name (optional)
The company name to be used by the vendor to provide technical support.
contact_info (optional)
Email address of the primary contact person at your company for all matters related
to the EMC RecoverPoint system.
Notes
To display the currently configured account settings, run get_account_settings on page
119.
The specified email address appears in the account information that is displayed by
running get_account_settings on page 119. This information is intended primarily to
assist the vendor in providing efficient technical support to the user.

Users
get_account_settings
Displays the user's account settings, for use in technical support situations.
Permission
Read Only
Parameters
None
Descriptions
None
Notes
Displays the Account ID, company name and RecoverPoint contact email associated with
the user's account. To define your company's account settings, run
config_user_account on page 118. The Account ID value is defined by EMC Customer
Support.
Example
To display the current account settings information:
RPA cluster> get_account_settings

Account ID: 100707
Company Name: EMC
Contact Info: user@company.com
get_ldap_configuration
Displays the LDAP configurations.
Permission
Read Only
Parameters
None
Descriptions
None
Notes
None
Example
RPA cluster> get_ldap_configuration

Active directory support enabled: YES
Primary server name: KLABD.COM
Primary server port: 389
Secondary server name: KLABD.COM
Secondary server port: 389
Base distinguish name: dc=KLABD,dc=COM
Search base distinguish name: cn=Users,dc=KLABD,dc=COM
Bind type: Simple
Bind distinguished name: cn=Administrator,cn=Users,dc=KLABD,dc=COM
Protocol type: LDAP
LDAP search scope: Sub tree
Search time limit: 30 seconds
Users object class: user
get_account_settings 119
Users
Username attribute name: sAMAccountName

Group attribute name: memberOf
modify_role
Modifies an existing management role in the system. Can modify role name and/or
permissions.
Permission
Security
Parameters
None
Descriptions
None
Notes
You cannot remove preconfigured roles like admin or boxmgmt.
When prompted, enter the required role name, new role name and permissions.
l Data Transfer - User may enable/disable group, start/pause transfer, and clear/set
markers.
target-side log.
syslog utilities.
permission are for internal use only.Storage Management- Used for array awareness.
l Read Only - By default, each role includes this permission. User may view system
information.
permissions.
Example
RPA1> modify_role
Select role to modify:
1) role test
2) role_mgmt
Select: 1
Enter new role name, or press 'ENTER' for current name: chnged_role

Users
The current permissions for this role are:

View
Do you want to change these permissions? (y/n)y
Available permissions:
1: Splitter Configuration
2: Group Configuration
3: Data Transfer
4: Target Image
5: Failover
6: System Configuration
7: Security
8: Upgrade
Select (separate with spaces if more than one), or press 'ENTER': 1 8
Role modified successfully.
regenerate_encryption_keys
Regenerates the cluster-level key(s) used to encrypt RPA communication, array
credentials, LDAP credentials, CHAP credentials. and RPA-level SSH host keys for the
specified cluster(s).
Permission
Security
Parameters
Descriptions
cluster (optional)
Name of the cluster for which the encryption keys are regenerated.
Notes
If no cluster is specified, all clusters will be considered.
remove_role
Removes a management role from the system.
Permission
Security
Parameters
None
Descriptions
None
Notes
You cannot remove preconfigured roles like admin, or boxmgmt, and you cannot remove
roles that are currently in use.
Example
RPA1> remove_role
Select role to remove:
1) chnged_role
2) role_mgmt
regenerate_encryption_keys 121
Users
Select: 1
Remove role chnged_role? (y/n)y
Role removed successfully.
remove_ssh_key
Removes a public key from user's authorized keys.
Permission
Read Only
Parameters
name=<...>
Descriptions
name
Name of the user.
Notes
None
remove_user
Removes a management user from the system.
Permission
Security
Parameters
None
Descriptions
None
Notes
You cannot remove preconfigured users such as admin or boxmgmt.
Example
RPA cluster> remove_user

1) anna
2) frank
3) robert
Select: 1
Remove user anna? (y/n)y
User removed successfully.
set_password
Resets the password of the currently logged-in user.
Permission
Read Only

Users
Parameters
None
Descriptions
None
Notes
Example
To set a new password:
RPA cluster> set_password

Enter old password:
Enter password (min. 5 characters):
Confirm:
Password set successfully.
Note
The passwords you type are not echoed on the screen.
set_security_level
Defines the security level for the currently logged-in management user.
Permission
Security
Parameters
[level=basic | high]
Descriptions
level (optional)
The system security level.
Possible values are basic or high.
Notes
The command can only be run interactively.
When you run the command, the current user's security level will be displayed.
Select whether to set it to basic or to high:
l basic - user passwords to access RPA must have a minimum of five characters.
l high - user passwords to access the RPA must have a minimum of eight characters; at
least two must be lower case, at least two must be upper case, and at least two must
be non-alphabetical (either digits or special characters).
All user passwords expire in 90 days. The same password cannot be reused until at least
ten other passwords have been used.
set_user
Resets the password, changes the role, or limits the CGs of an existing management user.
Permission
Security
set_security_level 123
Users
Parameters
None
Descriptions
None
Notes
When prompted, specify the management user whose password or permissions you
would like to reset.
permissions.
Then, modify the password and/or each permission for the specified management user.
Example
Select user to modify:

1) Local-Ziv
2) admin
3) boxmgmt
4) security-admin
5) CN=LDAP_test,CN=Users,DC=KLABD,DC=COM
6) Clar
7) LDAPUSER
8) LDAP_2
9) ZIV-LDAP
10) Ziv
11) user1
Select: 9
The current role for this user is: admin
Do you want to change this role? (y/n)y
Choose role:
1) admin
2) boxmgmt
3) integration
4) security
Select: 4
Enter group name(s), separated by ',' if more than one, or press
'ENTER' for all groups :
User modified successfully.Select (separate with spaces if more than
one), or press
'ENTER': 1 2 3 4 5
User modified successfully.
test_ldap_connection
Tests the LDAP configurations
Permission
Security
Parameters
None
Descriptions
None
Notes
None

Users
Example
RPA1> test_ldap_connection
LDAP settings are valid.
unlock_user
Unlocks system users that have been locked out of the system after three failed attempts
to log in.
Permission
Security
Parameters
None
Descriptions
None
Notes
The list of all users locked out by the system is displayed.
unlock_user 125
Users

CHAPTER 13
General
l get_current_time.................................................................................................128
General 127
General
get_current_time
Displays the current system date and time stamp, as used by the RPAs.
Permission
Read Only
Parameters
None
Descriptions
None
Notes
Example
To obtain the current local date and time:
RPA cluster> get_current_time

Wed Nov 02 12:00:02 2008 (America/New_York)

EMC-RP CLI v4.3.1

Uploaded by

Copyright:

Available Formats

EMC-RP CLI v4.3.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EMC-RP CLI v4.3.1

Uploaded by

Copyright:

Available Formats

EMC®

RecoverPoint for VMs

CLI Reference Guide

2 RecoverPoint for VMs 4.3.1 CLI Reference Guide

Chapter 2 List of Commands 21

Chapter 7 Consistency Groups 47

RecoverPoint for VMs 4.3.1 CLI Reference Guide 3

Chapter 10 Virtual Machine 95

4 RecoverPoint for VMs 4.3.1 CLI Reference Guide

Chapter 12 Users 113

Chapter 13 General 127

RecoverPoint for VMs 4.3.1 CLI Reference Guide 5

6 RecoverPoint for VMs 4.3.1 CLI Reference Guide

1 Commands changed since last revision......................................................................... 10

RecoverPoint for VMs 4.3.1 CLI Reference Guide 7

8 RecoverPoint for VMs 4.3.1 CLI Reference Guide

This chapter includes the following topics:

Table 1 Commands changed since last revision

Commands What changed

config_copy_policy on page 50 Removed journal_size_limit parameter.

hijack_cluster on page 37 Command was added to the guide.

Functions available only in the CLI

Table 2 Functions available only in the CLI

CLI command or parameter Notes

bookmark_image Bookmarks cannot be created in the GUI, but they

detect_bottlenecks The long-term effects of deduplication on your

10 RecoverPoint for VMs 4.3.1 CLI Reference Guide

Table 2 Functions available only in the CLI (continued)

CLI command or parameter Notes

Managing the EMC RecoverPoint system

Getting Started with the RecoverPoint CLI

Managing the EMC RecoverPoint system 11

These are the main modes of work in a CLI session:

Connecting to the EMC RecoverPoint CLI

See After logging in for the first time on page 13.

Scripts cannot be run in this manner.

In the PuTTY Configuration dialog box, fill in the following details:

12 RecoverPoint for VMs 4.3.1 CLI Reference Guide

$ ssh <cluster management IP> -l user

$ ssh 10.10.10.70 -l admin

From MS Windows command prompt

After logging in for the first time

Working with the EMC RecoverPoint CLI in CLI mode

Working with the EMC RecoverPoint CLI in CLI mode 13

CLI mode input

Enter consistency group name

cg_1 cg_2 groupx

cg_1 cg_2 groupx

RPA cluster> get_group_settings groupx

14 RecoverPoint for VMs 4.3.1 CLI Reference Guide

Table 3 Function of keyboard keys in CLI mode

Keyboard key Function

Enter l submits commands

Spacebar scrolls down one page

Tab Activates the Autocomplete feature; see Autocomplete on page 14.

CTRL-C Aborts the current command.

CTRL-A Moves to the first character in the line.

CTRL-E Moves to the end of the line.

CTRL-U Deletes the current line.