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 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 59. 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, select one of the following options from the drop-down menu:
A notification appears if Rapid Recovery detects that a machine is offline or does not have VMware Tools installed.
9.
Click Next.
10.
On the Adjustments page, enter the credentials for each machine in the following format: hostname::username::password.
11.
Click Next.
If the Protection page appears next in the Protect Multiple Machines Wizard, skip to Step 15.

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.

12.
Optionally, on the Warnings page, you can verify any machine by selecting the machine and then clicking Verify in the toolbar.
13.
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.
14.
The Protection page appears.
15.
On the Protection, 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.

17.
Click Next.
18.
On the Repository page, do one of 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 60. 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 61. 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 62. 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 63. 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.

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.
20.
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 23.

Table 64. 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.

22.
Click Finish to save and apply your settings.

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

Protecting vCenter/ESXi virtual machines using agentless protection

Complete the following procedure to agentlessly protect ESXi virtual machines.

NOTE: Rapid Recovery recommends that VMware Tools be installed on virtual machines (VMs) you want to protect on vSphere or ESXi hosts. When VMware Tools are installed on a VM using a Windows operating system (OS), the backups that the Rapid Recovery Core captures use Microsoft Volume Shadow Services (VSS). For information on the behavior of agentless VMs with or without VMware Tools, see Benefits of installing VMware Tools for agentless protection.
CAUTION: Quest recommends that you limit agentless 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 / ESX(i).

Table 65. vCenter/ESX(i) connection settings

Text Box

Description

Host

The name or IP address of the 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.
Ensure that Protect selected VMs Agentlessly is selected. (This option is selected by default).
7.
On the Select Machines page, select the VMs you want to protect. You can use the drop-down menu to display a tree of Hosts and Clusters or of VMs and Templates.
8.
If you want to automatically protect new VMs when they are added to the host, select Auto protect new machines, and then complete the following steps.
a.
Click Next.
b.
On the Auto Protection page, select any containers in which you expect to add new machines.
9.
Click Next.
10.
On the Protection page, select one of the following protection schedules as appropriate:
If you selected a Typical configuration and specified default protection, continue to Step 17 to confirm your choices, close the wizard, and protect the machine you specified.
If you selected a Typical configuration and specified custom protection, click Next to set up a custom protection schedule. For details on defining a custom protection schedule, see Creating a custom protection schedule from a wizard in Simple Mode.
12.
Click Next.
13.
On the Repository page, the following:
1.
Select Use an existing repository.
3.
Click Next.
The Encryption page appears.
4.
Proceed to Step 15 to 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 66. Create a 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 a path for the new repository.

User name

For network path only, enter the user name for the network share.

Password

For network path only, enter the password for the network share.

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.

2.
Click Next.
3.
On the Repository Configuration page, use one of the following options to determine the size of the repository:
4.
Optionally, select Show advanced options, and then complete the information described in the following table.

Table 67. Repository 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:

On. Default value. Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.
Off. Rapid Recovery controls the caching.
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.

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.
a.
Select Encrypt data using Core-based encryption wtih an existing key.
16.
If you want to add an encryption key to the Core and apply that key to the protected machines, select Encrypt data using Core-based encryption with a new key, and then enter the information described in the following table.

Table 68. 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.

The best practice is to avoid special characters listed in the Name description of this table.

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.

Rapid Recovery adds the selected VMs and their host to the list of Protected Machines.

NOTE: The first time you add protection for a machine, a base image (a snapshot of all data on the protected volumes) transfers to the repository on the Rapid Recovery Core. If you selected Custom schedule, the base image occurs at the time that you specified, unless you opted to initially pause protection.

Protecting multiple machines on a Hyper-V virtual host

Use this procedure to simultaneously protect one or more machines on a Hyper-V 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.
3.
Click Next.
4.
On the Connection page of the wizard, from the Source drop-down list, select one of the following options:

Table 69. Hyper-V connection settings

Text Box

Description

Host

The name or IP address of the 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.

To use agentless protection, select Protect the Hyper-V Server without requiring an Agent in the guest VMs, and then see Protecting Hyper-V virtual machines using agentless protection.
6.
Click Next.
7.
On the Machines page, select the VMs that you want to protect.
9.
Click Next.
10.
On the Adjustments page, enter the credentials for each machine in the following format: hostname::username::password.
11.
Click Next.
If the Protection page appears next in the Protect Multiple Machines Wizard, skip to Step 15.

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

12.
Optionally, on the Warnings page, you can verify any machine by selecting the machine and then clicking Verify in the toolbar.
13.
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.
14.
The Protection page appears.
15.
On the Protection page, select the appropriate protection schedule from the following options:
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 (snapshot of all the data in the protected volumes) transfers to the repository on the Rapid Recovery Core following the schedule you defined, unless you specified to initially pause protection.

17.
Click Next.
18.
On the Repository page, do one of 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 70. 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 entry 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 (for example, 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 71. 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 72. 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 73. 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 an 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 setting 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 and 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.

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.
20.
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 21.

Table 74. 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 in the Name description.

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.

22.
Click Finish to save and apply your settings.
23.
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.

Protecting Hyper-V virtual machines using agentless protection

The Rapid Snap for Virtual feature lets you protect Hyper-V virtual machines or clusters agentlessly by installing the Rapid Recovery Agent on only the Hyper-V host instead of every virtual machine (VM).

CAUTION: Quest recommends that you limit agentless 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 one of the following options:

Table 75. Hyper-V connection settings

Text Box

Description

Host

The name or IP address of the 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.
Ensure that Protect the Hyper-V Server without requiring an Agent in the guest VMs or Protect the Hyper-V Cluster without requiring an Agent in the guest VMs, depending on your choice from Step 4, is selected. (This option is selected by default).
7.
Click Next.
8.
On the Select Machines page, select the VMs that you want to protect.
10.
Click Next.
11.
On the Protection page, select one of the following protection schedule options:
If you want to use the default protection schedule, select Default protection (hourly snapshots of all volumes).
If you selected a Typical configuration and specified default protection, continue to Step 18 to confirm your choices, close the wizard, and protect the machine you specified.
If you selected a Typical configuration and specified Custom protection, click Next to set up a custom protection schedule. For details on defining a custom protection schedule, see Creating a custom protection schedule from a wizard in Simple Mode.
13.
Click Next.
14.
On the Repository page, complete one of the following options:
1.
Select Use an existing repository.
3.
Click Next.
The Encryption page appears.
4.
Proceed to Step 15 to define encryption.
If you want to use a new repository, select Create a Repository, and then complete the following steps.

Table 76. Create a 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 a path for the new repository.

User name

For network path only, enter the user name for the network share.

Password

For network path only, enter the password for the network share.

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.

2.
Click Next.
3.
On the Repository Configuration page, use one of the following options to determine the size of the repository:
4.
Optionally, select Show advanced options, and then complete the information described in the following table.

Table 77. Repository 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:

On. Default value. Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.
Off. Rapid Recovery controls the caching.
Sync. Windows controls the caching as well as the synchronous input/output.
5.
Click Next.
If you chose the Advanced option in Step 1, the Encryption page appears.
15.
Optionally, on the Encryption page, select Enable Encryption.

Encryption key fields appear on the 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.
a.
Select Encrypt data using Core-based encryption wtih an existing key.
17.
If you want to add an encryption key to the Core and apply that key to the protected machines, select Encrypt data using Core-based encryption with a new key, and then enter the information described in the following table.

Table 78. 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.

The best practice is to avoid special characters listed in the Name description of this table.

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.

18.
Click Finish.

Rapid Recovery adds the selected VMs and their host to the list of Protected Machines.

NOTE: The first time you add protection for a machine, a base image (a snapshot of all data on the protected volumes) transfers to the repository on the Rapid Recovery Core. If you selected Custom schedule, the base image occurs at the time that you specified, unless you opted to initially pause protection.
Related Documents