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

Protecting multiple machines manually

Use this procedure to manually enter each machine that you want to protect. This is used, for example, when protecting Linux machines.

1.
On the Rapid Recovery Core Console, click the Protect drop-down menu, and then click Protect Multiple Machines.
2.
On the Welcome page, select one of the following options:
3.
Click Next.
4.
On the Connection page of the wizard, from the Source drop-down list, select Manually.
5.
Click Next.
6.
On the Select Machines page, enter the machine details in the dialog box in the format hostname::username::password::port. The port setting is optional. Examples include:
7.
Click Next.
If the Protection page appears next in the Protect Multiple Machines Wizard, skip to Step 11.

If the Agent software is not yet deployed to the machines you want to protect, or if any of the machines you specified cannot be protected for another reason, then the selected machines appear on the Warnings page.

8.
Optionally, on the Machines Warnings page, you can verify any machine by selecting the machine and then clicking Verify in the toolbar.
9.
Optionally, on the Machines Warnings page, select After Agent installation, restart the machines automatically.
NOTE: Quest recommends this option. You must restart agent machines before they can be protected. Restarting ensures that the Agent service is running, and that proper kernel module is used to protect the machine, if relevant.
10.
The Protection page appears.
11.
On the Protection page, select the appropriate protection schedule as described below.
If you selected a Typical configuration for the Protect Machine Wizard and specified default protection, then click Finish to confirm your choices, close the wizard, and protect the machine you specified.

The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) will transfer to the repository on the Rapid Recovery Core following the schedule you defined, unless you specified to initially pause protection.

13.
On the Repository page, the following:
1.
Select Use an existing repository.
3.
Click Next.

The Encryption page appears. Skip to Step 19 to optionally define encryption.

If you want to create a repository, select Create a Repository, and then complete the following steps.
1.
On the Repository, enter the information described in the following table.

Table 79. Add New Repository settings

Text Box

Description

Repository Name

Enter the display name of the repository.

By default, this text box consists of the word Repository and a number, which corresponds to the number of repositories for this Core. For example, if this is the first repository, the default name is Repository 1. Change the name as needed.

Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases .

Concurrent Operations

Define the number of concurrent requests you want the repository to support. By default the value is 64.

Comments

Optionally, enter a descriptive note about this repository. You can enter up to 254 characters. For example, type DVM Repository 2.

2.
Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location.
CAUTION: Define a dedicated folder within the root for the storage location for your repository. Do not specify the root location. For example, use E:\Repository\, not E:\. If the repository that you are creating in this step is later removed, all files at the storage location of your repository are deleted. If you define your storage location at the root, all other files in the volume (e.g., E:\) are deleted, which could result in catastrophic data loss.
The Add Storage Location dialog box appears.
3.
Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location.
4.
In the Storage Location area, specify how to add the file for the storage location. You can choose to add a locally attached storage volume (such as direct attached storage, a storage area network, or network attached storage). You could also specify a storage volume on a Common Internet File System (CIFS) shared location.
Select Add file on local disk to specify a local machine, and then enter the information as described in the following table.

Table 80. Local disk settings

Text Box

Description

Data path

Enter the location for storing the protected data.

For example, type X:\Repository\Data.

When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

Metadata path

Enter the location for storing the protected metadata.

For example, type X:\Repository\Metadata.

When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table.

Table 81. CIFS share credentials

Text Box

Description

UNC path

Enter the path for the network share location.

If this location is at the root, define a dedicated folder name (for example, Repository).

The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

User name

Specify a user name for accessing the network share location.

Password

Specify a password for accessing the network share location.

5.
In the Storage Configuration area, click More Details and enter the details for the storage location as described in the following table.

Table 82. Storage configuration details

Text Box

Description

Size

Set the size or capacity for the storage location. The minimum size is 1 GB. The default is 250 GB. You can choose from the following:

If the storage location is a New Technology File System (NTFS) volume using Windows XP or Windows 7, the file size limit is 16 TB.

If the storage location is a NTFS volume using Windows 8, 8.1, Windows 10, or Windows Server 2012, 2012 R2, the file size limit is 256 TB.

NOTE: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.

Write caching policy

The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations.

Set the value to one of the following:

If set to On, which is the default, Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.

If set to Off, Rapid Recovery controls the caching.

If set to Sync, Windows controls the caching as well as the synchronous input/output.

Bytes per sector

Specify the number of bytes you want each sector to include. The default value is 512.

Average bytes per record

Specify the average number of bytes per record. The default value is 8192.

6.
Click Next.
If you chose the Advanced option in Step 1, the Encryption page appears.
14.
Optionally, on the Encryption page, to enable encryption, select Enable Encryption.

Encryption key fields appear on the Encryption page.

CAUTION: Rapid Recovery uses AES 256-bit encryption in the Cipher Block Chaining (CBC) mode with 256-bit keys. While using encryption is optional, Quest highly recommends that you establish an encryption key, and that you protect the passphrase you define. Store the passphrase in a secure location, as it is critical for data recovery. Without a passphrase, data recovery is not possible.
15.
If you want to encrypt these protected machines using an encryption key that is already defined on this Rapid Recovery Core, select Encrypt data using an existing Encryption key, and select the appropriate key from the drop-down menu.

Proceed to Step 17.

Table 83. Encryption key settings

Text Box

Description

Name

Enter a name for the encryption key.

Encryption key names must contain between 1 and 130 alphanumeric characters. You may not include special characters such as the back slash, forward slash, pipe, colon, asterisk, quotation mark, question mark, open or close brackets, ampersand or hash.

Description

Enter a comment for the encryption key.

This information appears in the Description field when viewing encryption keys from the Core Console.

Passphrase

Enter the passphrase used to control access.

Best practice is to avoid special characters listed above.

Record the passphrase in a secure location. Quest Support cannot recover a passphrase. Once you create an encryption key and apply it to one or more protected machines, you cannot recover data if you lose the passphrase.

Confirm Passphrase

Re-enter the passphrase you just entered.

17.
Click Finish to save and apply your settings.
18.
If the Warning page appeared and you are still satisfied with your selections, click Finish again.

The Rapid Recovery Agent software is deployed to the specified machines, if necessary, and the machines are added to protection on the Core.

Monitoring the protection of multiple machines

You can monitor the progress as Rapid Recovery applies the protection polices and schedules to the machines.

1.
In the Rapid Recovery Core Console, navigate to the Rapid Recovery Home page and then click [Events] (Events).

The Events page displays, broken down by Tasks, Alerts, and Events. As volumes are transferred, the status, start times, and end times display in the Tasks pane.

You can also filter tasks by status (active, waiting, completed, queued, and failed). For more information, see Viewing tasks.

As each protected machine is added, an alert is logged, which lists whether the operation was successful or if errors were logged. For more information, see Viewing alerts.

For information on viewing all events, see Viewing a journal of all logged events.

Settings and functions for protected Exchange servers

If you are protecting a Microsoft Exchange Server in your Core, there are additional settings you can configure in the Rapid Recovery Core Console, and there are additional functions you can perform.

A single setting, Enable automatic mountability check, is available in the Core Console related to Exchange Server. If enabled, Exchange server mountability checks are conducted automatically. This setting is available when the status for the protected machine is green (active) or yellow (paused).

For more information, see About Exchange database mountability checks.

You can also perform a mountability check on demand, from the Recovery Points pane on a protected Exchange server machine. For more information, see Forcing a mountability check of an Exchange database.

Following are functions you can perform for an Exchange server protected by the Core.

Specify Exchange server credentials. Rapid Recovery Core lets you set credentials so the Core can authenticate to the Exchange server to obtain information.

For more information about setting credentials for Exchange servers, see Setting credentials for an Exchange server machine.

Truncate Exchange logs. When you force log truncation of Exchange server logs, this process identifies the available space and reclaims space on the protected Exchange server.

For more information about truncating Exchange server logs on demand, see Forcing log truncation for an Exchange machine. This process can also be performed as part of the nightly jobs.

Force a mountability check of an Exchange database. This function checks that Exchange databases are mountable, to detect corruption and alert administrators so that all data on the Exchange server can be recovered successfully.

For more information about forcing a mountability check on demand, see Forcing a mountability check of an Exchange database.

You can also force a mountability check to occur automatically after each snapshot. For more information about mountability checks, see About Exchange database mountability checks.

Force a checksum check of Exchange Server recovery points. This function checks the integrity of recovery points containing Exchange database files.

For more information about forcing a checksum check on demand, see Forcing a checksum check of Exchange database files.

You can truncate Exchange logs and force a checksum check as part of nightly jobs. For more information about the tasks you can schedule as nightly jobs, see Understanding nightly jobs. For information on configuring nightly jobs, see Configuring nightly jobs for the Core.

Setting credentials for an Exchange server machine

In order to set login credentials, an Exchange server must be present on a protected volume. If Rapid Recovery does not detect the presence of an Exchange server, the Set Credentials function does not appear in the Core Console.

Once you protect data on a Microsoft Exchange server, you can set login credentials in the Rapid Recovery Core Console.

Complete the steps in this procedure to set credentials for each Exchange Server.

1.
In the left navigation area of the Rapid Recovery Core Console, select the protected Exchange server machine for which you want to set credentials.

The Summary page appears for the protected Exchange server.

2.
On the Summary page, from the links at the top of the page, click the downward-facing arrow [Expand] to the right of the Exchange menu, and then from the resulting drop-down menu, select Set Credentials.
The Edit Exchange Credentials dialog box for the protected Exchange server appears.
3.
In the Edit Exchange Credentials dialog box, enter your credentials as follows:
a.
In the User name text field, enter the user name for a user with permissions to the Exchange server; for example, Administrator (or, if the machine is in a domain, [domain name]\Administrator).
b.
In the Password text field, enter the password associated with user name you specified to connect to the Exchange server.
c.
Click OK to confirm the settings and close the dialog box.
Related Documents