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

Start-ProtectCluster

The Start-ProtectCluster command lets an administrator add a server cluster under protection by a Core.

Usage

Usage for the command is as follows:

Command Options

The following table describes the options available for the Start-ProtectCluster command:

Table 286. Start-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 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 user name. If none are provided, then the logged-on user's credentials will be used.

Name of a repository on the Core where the protected machine's data is stored. The name must be enclosed in double quotes.

The name of the cluster to protect.

User name for the cluster to be protected.

Password to the cluster to be protected.

Port number for the cluster to be protected.

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

List of cluster nodes with volumes to protect. First specify label “nodename” and then type the name of the node. Then, specify label “volumes” and then type a list of volumes for the node.

For example: “nodename”, “10.10.10.10”, “volumes”, “c:”, “e:”, “nodename”, “10.10.10.11,” “volumes”, “c:”

Example:

Put volumes of a server under protection:

Start-RepositoryCheck

The Start-RepositoryCheck PowerShell command lets you check the integrity of a repository.

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the Start-RepositoryCheck command:

Table 287. Start-RepositoryCheck 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.

Required. The name of the repository that you want to check.

Optional. Check all repositories associated with this Core.

Optional. Perform the repository check without confirmation.

Example:

Start checking a repository:

Start-RestoreArchive

Businesses often use long-term storage to archive both compliant and non-compliant data. The archive feature in Rapid Recovery is used to support the extended retention for compliant and non-compliant data. The administrator can save an archive on the local storage or network location by specifying the -Path command and credentials.

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the Start-RestoreArchive command:

Table 288. Start-RestoreArchive 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.

Archive recovery points for all protected machines.

The protected machine with recovery points that you want to archive. You can specify multiple machine names enclosed in double quotes and separated by commas.

The name of the repository where you want to place restored recovery points. You must enclose the name in double quotes; for example, "Repository1."

Optional. The user name for logging in to the remote machine. It is required for a network path only.

Optional. The password for logging in to the remote machine. It is required for a network path only.

The path to where to save the archived data. For example:

Optional. Use only for cloud archiving. The name of the cloud account where you want to save the archive.

Optional. Use only for cloud archiving. The name of the cloud container in the chosen cloud account, where the archive will be saved. When you use this option, you should also specify the "-cloudaccountname" parameter.

Optional. Specify the Core that you want to use from the manifest of the restored archive.

Example:

Archive all recovery points for all machines on the Core and store them on the local machine:

Start-ScheduledArchive

The Start-ScheduledArchive PowerShell command lets you force a Rapid Recovery scheduled archive to begin on demand, regardless of the pre-established schedule.

Usage

The usage for the command is as follows:

Command Options

The following table describes the options available for the Start-ScheduledArchive command:

Table 289. Start-ScheduledArchive 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.

Force all scheduled archives.

The identification number or space-separated identifiers of the scheduled archives that you want to force.

Example:

Start multiple scheduled archive jobs:

Related Documents