Chat now with support
Chat with Support

Rapid Recovery 6.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings
Core settings key functions Rapid Recovery Core settings Core-level tools
Repositories Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery 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 Enabling application support 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 Verifying a bare metal restore
Managing aging data Archiving Cloud accounts The Local Mount Utility Core Console references REST APIs About us Glossary

Pausing and resuming protection

When you pause protection, you temporarily stop all transfers of data from the selected machine to the Rapid Recovery Core. When you resume protection, the Rapid Recovery Core follows the requirements in the protection schedule, backing up your data regularly based on that schedule.

You can pause protection for any Rapid Recovery protected machine:

From the Protected Machines drop-down menu in the left navigation area of the Rapid Recovery Core (pausing protection for all protected machines).

If you pause protection using the Protect Machine Wizard or the Protect Multiple Machines Wizard, protection is paused until explicitly resumed.

If you pause protection outside of a wizard, you can choose whether to pause protection until resumed, or to pause it for a designated amount of time (specified in any combination of days, hours and minutes). If you pause for a period of time, then when that time expires, the system resumes protection based on the protection schedule automatically.

You can resume protection for any paused Rapid Recovery protected machine:

From the Protected Machines drop-down menu in the left navigation area of the Rapid Recovery Core (resuming protection for all protected machines).

Use the procedure below to pause or to resume protection, as appropriate.

1.
In the Rapid Recovery Core Console, to pause protection for all machines, click the Protected Machines drop-down menu in the left navigation area, and then do the following:
a.
Select Pause Protection.

The Pause Protection dialog box appears.

If you want to pause protection for a specified period, select Pause for and then, in the Days, Hours, and Minutes controls, type or select the appropriate pause period as appropriate.
a.
Select Resume Protection.

The Resume Protection dialog box appears.

The Resume Protection dialog box closes, and protection is resumed for all machines.

a.
Select Pause Protection.

The Pause Protection dialog box appears.

If you want to pause protection for a specified period, select Pause for and then, in the Days, Hours, and Minutes controls, type or select the appropriate pause period as appropriate.
a.
Select Resume Protection.

The Resume Protection dialog box appears.

The Resume Protection dialog box closes, and protection is resumed for the selected machine.

The Summary page displays for the selected machine.

The Pause Protection dialog box appears.

If you want to pause protection for a specified period, select Pause for and then, in the Days, Hours, and Minutes controls, type or select the appropriate pause period as appropriate.

The Resume Protection dialog box closes, and protection resumes for the selected machine.

About protecting multiple machines

You can add two or more Windows machines for protection on the Rapid Recovery Core simultaneously using the Protect Multiple Machines Wizard. To protect your data using Rapid Recovery, you need to add the workstations and servers for protection in the Rapid Recovery Core Console; for example, your Exchange server, SQL Server, Linux server, and so on.

As with protecting individual machines, protecting multiple machines simultaneously requires you to install the Rapid Recovery Agent software on each machine you want to protect.

Protected machines must be configured with a security policy that makes remote installation possible.

To connect to the machines, they must be powered on and accessible.

There is more than one method to deploy the Agent software to multiple machines simultaneously. For example:

The process of protecting multiple machines includes optional steps that you can access if you select an advanced configuration. Advanced options include repository functions and encryption. For example, you can specify an existing Rapid Recovery repository to save snapshots, or you can create a new repository. You can also specify an existing encryption key (or add a new encryption key) to apply to the data saved to the Core for the machines you are protecting.

The workflow of the Protect Multiple Machines Wizard may differ slightly based on your environment. For example, if the Rapid Recovery Agent software is installed on the machines you want to protect, you are not prompted to install it from the wizard. Likewise, if a repository already exists on the Core, you are not prompted to create one.

When protecting multiple machines, follow the appropriate procedure, based on your configuration. See the following options for protecting multiple machines:

Protecting multiple machines on an Active Directory domain

Use this procedure to simultaneously protect one or more machines on an Active Directory domain.

1.
On the Rapid Recovery Core Console, click the Protect drop-down menu, and then click Protect Multiple Machines.
2.
On the Welcome page of the wizard, select one of the following options:
3.
Click Next.
4.
On the Connection page of the wizard, from the Source drop-down list, select Active Directory.

Table 53. Domain information and credentials

Text Box

Description

Host

The host name or IP address of the Active Directory domain.

User name

The user name used to connect to the domain; for example, Administrator or, if the machine is in a domain, [domain name]\Administrator).

Password

The secure password used to connect to the domain.

6.
Click Next.
7.
On the Select Machines page of the wizard, select the machines you want to protect.
8.
Click Next.
If the Protection page appears next in the Protect Multiple Machines Wizard, skip to Step 12.

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.

9.
Optionally, on the Warnings page of the wizard, you can verify any machine by selecting the machine and then clicking Verify in the toolbar.
10.
Optionally, on the 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.
11.
If the status indicates that the machine is reachable, click Next to install the Rapid Recovery Agent software.
The Protection page appears.
12.
Optionally, on the Protection page, if you want a name other than the IP address to display in the Rapid Recovery Core Console for this protected machine, then in the Display name field, type a name in the dialog box.

You can enter up to 64 characters. Do not use the special characters described in the topic . Additionally, do not begin the display name with any of the character combinations described in the topic .

With a default protection schedule, the Core will take snapshots of all volumes on the protected machine once every hour. To change the protection settings at any time after you close the wizard, including choosing which volumes to protect, go to the Summary page for the specific protected machine.

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.

15.
On the Protection Volumes page, select which volumes you want to protect. If any volumes are listed that you do not want to include in protection, click in the Check column to clear the selection. Then click Next.
16.
On the Protection Schedule page, define a custom protection schedule and then click Next. For details on defining a custom protection schedule, see Creating custom protection schedules in Simple Mode.
17.
On the Repository page, do the following:
1.
Select Use an existing repository.
3.
Click Next.

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

If you want to create a repository, then on the Repository page, enter the information described in the following table, and then click Next or Finish, as appropriate.

Table 54. Repository settings

Text Box

Description

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.

Location

Enter the location for storing the protected data. This volume should be a primary storage location. The location could be local (a drive on the Core machine) or it could be a CIFS share network drive.

For a CIFS share, 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.

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.

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.

User name

Enter a user name for a user with administrative access. This information is only required when the repository location specified is a network path.

Password

Enter the password for the user with administrative access. This information is only required when the repository location specified is a network path.

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.

18.
On the Repository Configuration page, configure the amount of space on the disk to allocate to the repository. Quest recommends reserving 20 percent of the volume for metadata, which is the default. Optionally, using the slider control or the Size field, you can allocate more or less space on the volume for the repository.
19.
Optionally, if you want to view and enter detailed information regarding storage location settings, select Show advanced options, and adjust the settings as described in the following table. To hide these options, clear the option Show advanced options. When you have completed your repository configuration, click Next or Finish, as appropriate.

Table 55. Storage configuration details

Text Box

Description

Bytes per sector

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

Bytes per record

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

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.

If you chose the Advanced option in Step 1, the Encryption page appears.
20.
Optionally, on the Encryption page, if you want to use encryption keys for data stored in the repository, select Encrypt the data at rest in a repository, and then do one of the following:
To select an existing encryption key to apply to all new data stored in your repository, select Encrypt data using Core-based encryption with an existing key, and from the Select encryption key drop-down menu, select the encryption key.
To define a new encryption key at this time to apply to all future data stored in your repository, select Encrypt data using Core-based encryption with a new key, and then enter information about the key as described in the table below:

Table 56. Define new encryption key

Text Box

Description

Name

Enter a name for the encryption key.

Encryption key names must contain between 1 and 64 alphanumeric characters. Do not use prohibited characters or prohibited phrases.

Description

Enter a descriptive comment for the encryption key. This information appears in the Description field when viewing a list of encryption keys in the Rapid Recovery Core Console. Descriptions may contain up to 254 characters.

Best practice is to avoid using prohibited characters and prohibited phrases.

Passphrase

Enter a passphrase used to control access.

Best practice is to avoid using prohibited characters.

Record the passphrase in a secure location. Quest Data Protection 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. It is used to confirm the passphrase entry.

21.
Optionally, on the Encryption page, to encrypt all data that transports over a network, select Encrypt the data in transport over a network. This option is enabled by default, so if you do not want to encrypt data in this fashion, clear this option.
22.
Click Finish to save and apply your settings.

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.

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

Protecting multiple machines on a VMware vCenter/ESXi virtual host

Use this procedure to simultaneously protect one or more machines on a VMware vCenter/ESXi virtual host.

CAUTION: If you use agentless protection, Quest recommends that you limit protection to no more than 200 VMs at once. For example, do not select more than 200 VMs when using the Protect Multiple Machines Wizard. Protecting more than 200 VMs results in slow performance. There is no limit to how many VMs a Core can agentlessly protect over time. For example, you could protect 200 VMs today and another 200 VMs tomorrow.
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 vCenter / ESXi.

Table 57. vCenter/ESXi connection settings

Text Box

Description

Host

The name or IP address of the VMware vCenter Server/ESXi virtual host.

Port

The port used to connect to the virtual host.

The default setting is 443.

User name

The user name used to connect to the virtual host; for example, Administrator or, if the machine is in a domain, [domain name]\Administrator.

Password

The secure password used to connect to this virtual host.

6.
Click Next.
7.
On the Select Machines page, do one of the following:
To navigate through the VMware tree structure to locate more VMs, click View Tree and then select either Hosts and Clusters or VMs and Templates. Select the VMs you want to protect.
A notification appears if Rapid Recovery detects that a machine is offline or does not have VMware Tools installed.
8.
Click Next.
9.
On the Adjustments page, enter the credentials for each machine in the following format: hostname::username::password.
10.
Click Next.
If the Protection page appears next in the Protect Multiple Machines Wizard, skip to Step 14.

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.

11.
Optionally, on the Warnings page, you can verify any machine by selecting the machine and then clicking Verify in the toolbar.
12.
Optionally, on the 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.
13.
The Protection page appears.
14.
Optionally, on the Protection page, if you want a name other than the IP address to display in the Rapid Recovery Core Console for this protected machine, then in the Display name field, type a name in the dialog box.

You can enter up to 64 characters. Do not use the special characters described in the topic . Additionally, do not begin the display name with any of the character combinations described in the topic .

With a default protection schedule, the Core will take snapshots of all volumes on the protected machine once every hour. To change the protection settings at any time after you close the wizard, including choosing which volumes to protect, go to the Summary page for the specific protected machine.

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.

17.
On the Protection Volumes page, select which volumes you want to protect. If any volumes are listed that you do not want to include in protection, click in the Check column to clear the selection. Then click Next.
18.
On the Protection Schedule page, define a custom protection schedule and then click Next. For details on defining a custom protection schedule, see Creating custom protection schedules in Simple Mode.
19.
On the Repository page, do the following:
1.
Select Use an existing repository.
3.
Click Next.

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

If you want to create a repository, then on the Repository page, enter the information described in the following table, and then click Next or Finish, as appropriate.

Table 58. Repository settings

Text Box

Description

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.

Location

Enter the location for storing the protected data. This volume should be a primary storage location. The location could be local (a drive on the Core machine) or it could be a CIFS share network drive.

For a CIFS share, 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.

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.

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.

User name

Enter a user name for a user with administrative access. This information is only required when the repository location specified is a network path.

Password

Enter the password for the user with administrative access. This information is only required when the repository location specified is a network path.

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.

20.
On the Repository Configuration page, configure the amount of space on the disk to allocate to the repository. Quest recommends reserving 20 percent of the volume for metadata, which is the default. Optionally, using the slider control or the Size field, you can allocate more or less space on the volume for the repository.
21.
Optionally, if you want to view and enter detailed information regarding storage location settings, select Show advanced options, and adjust the settings as described in the following table. To hide these options, clear the option Show advanced options. When you have completed your repository configuration, click Next or Finish, as appropriate.

Table 59. Storage configuration details

Text Box

Description

Bytes per sector

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

Bytes per record

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

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.

If you chose the Advanced option in Step 1, the Encryption page appears.
22.
Optionally, on the Encryption page, if you want to use encryption keys for data stored in the repository, select Encrypt the data at rest in a repository, and then do one of the following:
To select an existing encryption key to apply to all new data stored in your repository, select Encrypt data using Core-based encryption with an existing key, and from the Select encryption key drop-down menu, select the encryption key.
To define a new encryption key at this time to apply to all future data stored in your repository, select Encrypt data using Core-based encryption with a new key, and then enter information about the key as described in the table below:

Table 60. Define new encryption key

Text Box

Description

Name

Enter a name for the encryption key.

Encryption key names must contain between 1 and 64 alphanumeric characters. Do not use prohibited characters or prohibited phrases.

Description

Enter a descriptive comment for the encryption key. This information appears in the Description field when viewing a list of encryption keys in the Rapid Recovery Core Console. Descriptions may contain up to 254 characters.

Best practice is to avoid using prohibited characters and prohibited phrases.

Passphrase

Enter a passphrase used to control access.

Best practice is to avoid using prohibited characters.

Record the passphrase in a secure location. Quest Data Protection 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. It is used to confirm the passphrase entry.

23.
Optionally, on the Encryption page, to encrypt all data that transports over a network, select Encrypt the data in transport over a network. This option is enabled by default, so if you do not want to encrypt data in this fashion, clear this option.
24.
Click Finish to save and apply your settings.

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.

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

Related Documents