Chat now with support
Chat with Support

The Quest and One Identity Support Portals will be unavailable on Friday July 10, 2020 from 5:30 PM to 6:30 PM for website maintenance.

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

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 hypervisor 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 61. 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, 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.
On the Auto Protection page, select any containers in which you expect to add new machines.
9.
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.

10.
Optionally, on the Warnings page, you can verify any machine by selecting the machine and then clicking Verify in the toolbar.
11.
Click Next.
The Protection appears.

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.

14.
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.
15.
On the Repository page, do the following:
1.
Select Use an existing repository.
3.
Click Next.

The Encryption page appears. Skip to Step 18 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 62. 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.

16.
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.
17.
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 63. 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.
18.
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 64. 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.

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

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.

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 65. 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 8006.

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.
Optionally, if you want 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.
7.
Click Next.
8.
On the Machines page, select the VMs that you want to protect.
10.
Click Next.
11.
On the Adjustments page, enter the credentials for each machine in the following format: hostname::username::password.
12.
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.

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

19.
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.
20.
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.
21.
On the Repository page, do the following:
1.
Select Use an existing repository.
3.
Click Next.

The Encryption page appears. Skip to Step 23 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 66. 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.

22.
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.
23.
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 67. 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.
24.
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 68. 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.

25.
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.
26.
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 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).

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 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 8006.

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.
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 prohibited characters. Additionally, do not begin the display name with any of the character combinations described in the topic prohibited phrases.

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.

14.
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.
15.
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.
16.
On the Repository page, do 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, then on the Repository page, enter the information described in the following table, and then click Next or Finish, as appropriate.

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

17.
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.
18.
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 71. 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.
19.
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 72. 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.

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

Protecting multiple machines manually

Use this procedure to manually specify details for multiple machines that you want to protect simultaneously using the Agent software. The details identify each machine on the network uniquely, and include connection information and credentials. This approach is often used when protecting Linux machines. However, using this process, you can protect only Windows machines, only Linux machines, or a combination of both.

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, for each machine you want to protect, enter the machine details in the dialog box. Press Enter to separate information for each machine you want to add. Use the format hostname::username::password::port. The port setting is optional. The default port for installing Agent on Windows or Linux machines is 8006. 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.
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.

14.
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.
15.
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.
16.
On the Repository page, do 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, then on the Repository page, enter the information described in the following table, and then click Next or Finish, as appropriate.

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

17.
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.
18.
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 74. 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.
19.
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 75. 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.

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