Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings Repositories Encryption keys Protecting machines
About protecting machines with Rapid Recovery Support for dynamic and basic volumes Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Viewing the recovery progress Starting a restored target server Troubleshooting connections to the Universal Recovery Console Repairing boot problems Performing a file system check on the restored volume
Managing aging data Archiving Cloud storage accounts The Local Mount Utility The Central Management Console Core Console references Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Scripting REST APIs About us Glossary

Pause

An administrator can pause snapshots, export to virtual machines, or replicate a Core. The pause command accepts three parameters: snapshot, vmexport, and replication. Only one parameter can be specified. A snapshot can be paused until a certain time, if a time parameter is specified.

A user can pause replication in three ways:

The administrator must specify the remote machine name with the outgoing replication pairing to pause outgoing replication on the source Core:

On target Core (-incoming).

If the local Core is a target Core, the administrator can pause replication by specifying the source Core using the incoming parameter:

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the pause command:

Table 208. Pause command options

Option

Description

Display this help message.

[snapshots], [replication] or [vmexport].

Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine.

Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used.

Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used.

Optional. Pause all agents on the selected Core.

Optional. Pause current protected server.

Optional. Host name of the remote core that replicates to the core machine.

Optional. Host name of the remote target core to which data is replicated.

Optional. The time in the format ‘Day-Hours-Minutes’ when the snapshots will be resumed (only for snapshots pause).

Examples:

Pause creating snapshots for a specific protected server:

Pause creating snapshots for a protected machine and resume it after three days, 20 hours, and 50 minutes:

Pause export to virtual machine for all protected machines on the core:

Pause outgoing replication on the core for a specific protected machine:

Pause outgoing replication for all protected machines on the target core:

Pause incoming replication for all machines on the target core:

Protect

The protect command adds a server under protection by a core.

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the protect command:

Table 209. Protect command options

Option

Description

Display this help message.

Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine.

Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used.

Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used.

Name of a repository on the Core to which the protected machine data should be stored. The name must be enclosed in double quotes.

Name or IP address of the server you want to protect.

User name for the server to be protected.

Password for the server to be protected.

Protected server port number.

List of volumes to protect. Values must be enclosed in double quotes and separated by a space. Do not use trailing slashes in volume names; for example: “c:” “d:”.

Example:

Protect specific volumes of a server with the Core:

ProtectCluster

The protectcluster command adds a cluster under protection by a core.

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the protectcluster command:

Table 210. ProtectCluster command options

Option

Description

Display this help message.

Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine.

Optional. User name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used.

Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used.

Name of a repository on the Core to which the protected machine data should be stored. The name must be enclosed in double quotes.

Name or IP address of the cluster you want to protect.

User name for the cluster to be protected.

Password for the cluster to be protected.

Protected cluster server port number.

List of volumes to protect. Values must be enclosed in double quotes and separated by a space. Do not use trailing slashes in volume names; for example: “c:” “d:”.

List of the cluster nodes and the volumes you want to protect on each node.

Example:

Protect specific volumes of a cluster server with the Core:

ProtectEsxServer

You can use the protectesxserver command whenever you want to add a VMware ESX(i) virtual machine to protection.

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the protectesxserver command:

Table 211. ProtectEsxServer command options

Option

Description

Display this help message.

Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine.

Optional. The user name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used.

Optional. The password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used.

Required. The name of the repository that is associated with the Core that you want to use to protect the virtual machine.

The name or IP address for the vCenter or ESXi server you want to protect.

The user name for logging in to the vCenter or ESXi server that you want to protect.

The password for logging in to the vCenter or ESXi server that you want to protect.

Optional. The port number for the vCenter or ESXi server that you want to protect.

Optional. This option lets you list the virtual machines that you want to protect.

Optional. This option lets you list new virtual machines that you want to automatically protect.

Examples:

Protect specific virtual machines from a vCenter or ESXi server with the Core:

Related Documents