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

DismountArchiveRepository

After retrieving the information you want from a mounted archive, you should dismount the archive to avoid potential issues.

Usage

The usage for the command is as follows:

Command Options

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

Table 193. DismountArchiveRepository 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 archive repository.

Examples:

Dismount the repository named "NewArchive:"

EditEsxServer

You can use the editesxserver command whenever you want to make changes to the number of VMware ESX(i) virtual machines that you want to protect agentlessly.

Usage

The usage for the command is as follows:

Command Options

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

Table 194. EditEsxServer 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.

Use this option to edit vCenter and ESX(i) objects for a specific protected machine.

Use this option to add a specified vCenter or ESXi object.

Use this option to remove a specified vCenter or ESXi object.

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

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

Examples:

Automatically protect specific vCenter or ESXi objects of a vCenter or ESXi server with the Core:

Force

The force command forces a snapshot of a specified protected server. Forcing a snapshot lets you force a data transfer for the current protected machine. When you force a snapshot, the transfer will start immediately or will be added to the queue. Only the data that has changed from a previous recovery point will be transferred. If there is no previous recovery point, all data on the protected volumes will be transferred.

Usage

The usage for the command is as follows:

Command Options

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

Table 195. Force command options

Option

Description

Display this help message.

Optional. Type of snapshot to create. Available values: 'snapshot' (incremental snapshot) and 'base' (base image snapshot). By default, an incremental snapshot is performed.

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.

Force snapshots for all machines on the core.

Force a snapshot for a specific protected machine.

Example:

Force a snapshot for all machines on the Core:

ForceAttach

The forceattach command lets you force a SQL database files attachability check. When you force an attachability check, the check begins immediately.

Usage

The usage for the command is as follows:

Command Options

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

Table 196. ForceAttach 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.

Protected machine against which to perform the attachability check.

The sequential number of a recovery point against which to perform checks (run command /list rps to obtain the numbers). To perform checks against multiple recovery points with a single command, you can specify several numbers separated by spaces.

Select a recovery point by its creation time. You must specify the exact time in the format “mm/dd/yyyy hh:mm tt” (for example, “2/24/2012 09:00 AM”). Keep in mind to specify the date and time values of the time zone set on your PC.

Example:

Perform attachability checks for recovery points with numbers 5 and 7:

Related Documents