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

StartExport

The startexport command forces a one-time export of data from a protected machine to a virtual server. You can export to an ESXi, VMware Workstation, Hyper-V, or VirtualBox virtual machine. If exporting to ESXi, you must specify thick or thin disk provisioning.

Usage

The usage for the command is as follows:

Command Options

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

Table 224. StartExport command options

Option

Description

Display this help message.

Perform export of data from protected server to an ESXi server ('esxi'), VMware Workstation server ('vm'), Hyper-V server ('hyperv'), or VirtualBox server ('vb').

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 with recovery points to be exported.

Optional. List of volume names to be exported. If not specified, all volumes will be exported. Values must be enclosed in double quotes and separated with spaces; for example: “c:” “d:”. Do not use trailing slashes in volume names.

Optional. The sequential number of a recovery point to be exported (use Get-RecoveryPoints command to get the numbers). If neither the ‘time’ nor the ‘rpn’ option is specified, then the most recent recovery point is exported.

Optional. Determines the recovery point or points to be selected for export. You need to specify the exact time in the format "mm/dd/yyyy hh:mm tt" (for example, "2/24/2012 09:00 AM"). Be sure to specify the date time values of the time zone set on your PC. Note: if neither the 'time' nor the 'rpn' option is specified, then the most recent recovery point is exported.

The Windows name of the virtual machine.

For ESXi and Hyper-V virtual exports only. The virtual server host name.

For VirtualBox exports only. The virtual server host name.

For ESXi and Hyper-V virtual exports only. The virtual server port number.

For ESXi and Hyper-V virtual exports only. The user name for the virtual server host.

For ESXi and Hyper-V virtual exports only. The password for the virtual server host.

Use this option to allocate a specific amount of RAM on the virtual server.

Optional. Use this option to allocate the same amount of RAM on the virtual server that the source machine contains.

Use this option for ESXi exports only. Optional. The amount of disk space that you want to allocate on the virtual machine. Use one of the two following specifications:

The default specification is "thin."

Use this option for ESXi exports only. Optional. This option determines how to map the disks from the protected machine to the virtual machine. Use one of the following values:

The default value is "auto."

For VMware Workstation and VirtualBox exports only. This option specifies the local or network path—or Linux path, for VirtualBox only—to the folder where you want to store the virtual machine files

For VMware Workstation exports only. It is the user name for the network machine. It is only required when you specify a network path in the -targetpath option.

For VMware Workstation exports only. It is the password for the network machine. It is only required when you specify a network path in the -targetpath option.

For Hyper-V exports only. Optional. Use this command to connect to the local Hyper-V server. This option ignores the -hostname, -hostport, -hostusername, and -hostpassword options.

Examples:

Export data to an ESXi virtual machine with a specific name and the same amount of RAM and disk size as the source protected server:

Create a VMware Workstation machine file on the local drive with protected data from recovery point #4:

Create a Hyper-V machine files to be stored on a remote machine:

UpdateRepository

The updaterepository command adds a new storage location to an existing DVM repository.

Usage

The usage for the command is as follows:

Command Options

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

Table 225. UpdateRepository command options

Option

Description

Display this help message.

Repository name.

Size of repository storage location. Available units are b, Kb, Mb, Gb, Tb, and Pb.

For local location only. Determines data path of repository storage location.

For local location only. Determines metadata path of repository storage location.

For share location only. Determines data and metadata paths of repository storage location.

For share location only. Determines user name to share location.

For share location only. Determines password to share location.

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.

Examples:

Create a new storage location in a local DVM repository:

Create a storage location for a DVM repository at a shared location:

Version

The version command displays information about the version of the Rapid Recovery software installed on the specified server. If you do not specify a core or protected server, the information returned applies to the Core on which you are currently working.

Usage

The usage for the command is as follows:

Command Options

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

Table 226. Version 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.

Optional. The protected machine for which you want to view version information. If you do not specify a protect machine, the return is information about the Core machine on which you are working.

Example:

Display information about the version of Rapid Recovery installed on the current Rapid Recovery Core:

VirtualStandby

You can use the virtualstandby command to export data from a Rapid Recovery protected machine to a compatible virtual machine.

Usage

The usage for the command is as follows:

Command Options

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

Table 227. VirtualStandby command options

Option

Description

Display this help message.

This option exports data from a protected machine to one of the following specified virtual servers:

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.

Use this option to specify the protected machine whose recovery points you want to export.

Optional. Use this option to list the names of the volumes that you want to export. If you do not specify volumes, then all volumes in the recovery point will export. Enclose values in double quotes and separate them with a space; for example: "c:" "d:". Do not use trailing slashes in volumes names.

Use this option to allocate a specific amount of RAM on the virtual server.

Optional. Use this option to allocate the same amount of RAM on the virtual server that the source machine contains.

The Windows name of the virtual machine.

Optional. This option specifies Generation 2 of the VM server. If you do not specify the generation, the command uses Generation 1. The following operating systems support Generation 2:

For ESXi and Hyper-V virtual exports only. The virtual server host name.

For VirtualBox exports only. The virtual server host name.

For ESXi and Hyper-V virtual exports only. The virtual server port number.

For ESXi and Hyper-V virtual exports only. The user name for the virtual server host.

For ESXi and Hyper-V virtual exports only. The password for the virtual server host.

For ESXi exports only. Optional. The amount of disk space that you want to allocate on the virtual machine. Use one of the two following specifications:

The default specification is "thin."

For ESXi exports only. Optional. This option determines how to map the disks from the protected machine to the virtual machine. Use one of the following values:

The default value is "auto."

For VMware Workstation and VirtualBox exports only. This option specifies the local or network path—or Linux path, for VirtualBox only—to the folder where you want to store the virtual machine files.

For VMware Workstation exports only. It is the user name for the network machine. It is only required when you specify a network path in the -targetpath option.

For VMware Workstation exports only. It is the password for the network machine. It is only required when you specify a network path in the -targetpath option.

For Hyper-V exports only. Optional. Use this command to connect to the local Hyper-V server. This option ignores the -hostname, -hostport, -hostusername, and -hostpassword options.

Optional. This option lets you edit existing virtual machines. It ignores the -exporttype and -initialexport options.

Optional. This option specifies whether to start an initial on-demand virtual machine export after you configure a continuous virtual standby.

Examples:

Set up a virtual standby export to an ESXi virtual machine with the name, amount of RAM, and disk size of the source protected server:

Set up a virtual standby export to a VMware Workstation machine file on the local drive:

Set up a virtual standby export to a Hyper-V machine files and store them on a remote machine:

Related Documents