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

New-Snapshot

The New-Snapshot command forces a snapshot resulting in 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 New-Snapshot command:

Table 262. New-Snapshot command options

Option

Description

Display this help message.

Force all protected machines.

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. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none are provided, then the logged-on user's credentials will be used.

Force for the current protected machine’s name.

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

Example:

Force a snapshot for all protected machines:

New-VBVirtualStandby

The New-VBVirtualStandby command lets you use PowerShell to create a new virtual export to a VirtualBox virtual machine (VM).

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the New-VBVirtualStandby command:

Table 263. New-VBVirtualStandby 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 also have to provide a password.

If none are provided, then the logged-on user's credentials will be used.

Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.

If none are provided, then the logged-on user's credentials will be used.

Show jobs for a specific protected machine, indicated by IP address.

Optional. List the volume names you want to export. If not specified, all volumes in the recovery point(s) are exported. Values must be enclosed in double quotes and separated by space; for example, "c:", "d:".

The Microsoft Windows name of the virtual machine.

Allocate a specific amount of RAM on the virtual server.

Optional. Allocate the same amount of RAM on the virtual server that the source protected machine has.

The Linux VirtualBox server host name.

The Linux VirtualBox server port.

The local, network, or Linux path to the folder where you want to store the virtual machine files.

The user name for logging in to the network machine. It is only required when you specify a network location for the target path.

The password for logging in to the network machine. It is only required when you specify a network location for the target path.

Optional. You can specify a user account with which to register the exported virtual machine. It is the user name for logging in to the user account. Use this option for a local or network machine only.

Optional. You can specify a user account with which to register the exported virtual machine. It is the password for logging in to the user account. Use this option for a local or network machine only.

Optional. Specify this option if you need to start an initial on-demand virtual machine export after configuring the virtual standby.

Example:

Create a VirtualBox virtual standby machine named ExportedMachine1 in a specified location:

New-VMVirtualStandby

The New-VMVirtualStandby PowerShell command lets you create a new VMware Workstation virtual standby machine using Rapid Recovery.

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the New-VMVirtualStandby command:

Table 264. New-VMVirtualStandby 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 also have to provide a password.

If none are provided, then the logged-on user's credentials will be used.

Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.

If none are provided, then the logged-on user's credentials will be used.

Show jobs for a specific protected machine, indicated by IP address.

Optional. List the volume names you want to export. If not specified, all volumes in the recovery point(s) are exported. Values must be enclosed in double quotes and separated by space; for example, "c:", "d:".

The Microsoft Windows name of the virtual machine.

Allocate a specific amount of RAM on the virtual server.

Optional. Allocate the same amount of RAM on the virtual server that the source protected machine has.

The user name for logging in to the network machine. It is only required when you specify a network location for the target path.

The password for logging in to the network machine. It is only required when you specify a network location for the target path.

Optional. Specify this option if you need to start an initial on-demand virtual machine export after configuring the virtual standby.

Example:

Create a new VMware Workstation virtual standby:

Script pauses, requiring user to specify an index number for the appropriate workstation. Enter the index number for the script to complete (in this case, 2). Example continues:

Push-Replication

The Push-Replication command forces replication for one or more protected machines.

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the Push-Replication command:

Table 265. Push-Replication command options

Option

Description

Display this help message.

Force replication for all machines being replicated to the target Core.

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. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none are provided, then the logged-on user's credentials will be used.

Protected machine name on the target Core against which to force replication.

Optional. Login for the remote Core host machine. If you specify a login, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used.

Example:

Push replication for a single protected machine:

Push replication for all protected machines:

Related Documents