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. |
◦ |
3. |
4. |
The name or IP address of the VMware vCenter Server/ESXi virtual host. | |
◦ |
To use agentless protection, select Protect selected VMs Agentlessly, and then see Protecting vCenter/ESXi virtual machines using agentless protection. |
6. |
7. |
9. |
10. |
On the Adjustments page, enter the credentials for each machine in the following format: hostname::username::password. |
11. |
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. |
15. |
◦ |
If you want to use the default protection schedule, then in the Schedule Settings option, select Default protection (hourly snapshots of all volumes). |
◦ |
◦ |
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.
◦ |
If you selected a Typical configuration for the Protect Machine Wizard 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. |
◦ |
If you selected Advanced configuration for the Protect Machine Wizard, and default protection, then click Next and proceed to Step 18 to see repository and encryption options. |
◦ |
If you selected Advanced configuration for the Protect Machine Wizard and specified custom protection, then 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. |
17. |
18. |
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. |
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. |
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. |
Enter the location for storing the protected data. For example, type X:\Repository\Data. | |
Enter the location for storing the protected metadata. For example, type X:\Repository\Metadata. |
▪ |
Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table. |
5. |
In the Storage Configuration area, click More Details and enter the details for the storage location as described in the following table. |
| |||||||||
Set the value to one of the following:
If set to Off, Rapid Recovery controls the caching. If set to Sync, Windows controls the caching as well as the synchronous input/output. | |||||||||
Specify the number of bytes you want each sector to include. The default value is 512. | |||||||||
Specify the average number of bytes per record. The default value is 8192. |
6. |
Click Next. |
19. |
Encryption key fields appear on the Encryption page.
NOTE: If you enable encryption, it will be applied to data for all protected volumes on this machine.
You can change the settings later from the Encryption Keys page in the Rapid Recovery Core Console.
For more information about encryption, see the topic Encryption keys. |
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. |
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. | |
22. |
23. |
The Rapid Recovery Agent software is deployed to the specified machines, if necessary, and the machines are added to protection on the Core.
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. |
◦ |
3. |
4. |
6. |
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. |
NOTE: VMware Changed Block Tracking (CBT) must be enabled on each of the VMs you want to protect. If it is not enabled, Rapid Recovery automatically enables CBT to ensure protection. |
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. |
b. |
9. |
10. |
◦ |
If you want to use the default protection schedule, then in the Schedule Settings option, select Default protection (hourly snapshots of all volumes). |
◦ |
◦ |
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. |
◦ |
If you selected Advanced configuration for the Protect Machine Wizard, and default protection, then click Next and proceed to Step 13 to see repository and encryption options. |
◦ |
If you selected Advanced configuration for the Protect Machine Wizard and specified custom protection, then 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. |
13. |
1. |
Select Use an existing repository. |
3. |
Click Next. |
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. |
2. |
Click Next. |
3. |
On the Repository Configuration page, use one of the following options to determine the size of the repository: |
▪ |
To allocate a percentage of the storage location for the repository, use the Percentage of available space slider tool. |
4. |
Optionally, select Show advanced options, and then complete the information described in the following table. |
Specify the number of bytes you want each sector to include. The default value is 512. | |||||||||
Specify the average number of bytes per record. The default value is 8192. | |||||||||
Set the value to one of the following:
|
14. |
Encryption key fields appear on the Encryption page.
NOTE: If you enable encryption, it is applied to data for all protected volumes for this agent machine.
You can change the settings later from the Encryption Keys page in the Rapid Recovery Core Console.
For more information about encryption, see the topic Encryption keys. |
CAUTION: Rapid Recovery uses AES 256-bit encryption in the Cipher Block Chaining (CBC) mode with 256-bit keys. While using encryption is optional, Quest highly recommends that you establish an encryption key, and that you protect the passphrase you define. Store the passphrase in a secure location as it is critical for data recovery. Without a passphrase, data recovery is not possible. |
15. |
If you want to encrypt these protected machines using an encryption key that is already defined on this Rapid Recovery Core, complete the following steps: |
a. |
c. |
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. |
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. | |
17. |
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. |
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. |
4. |
On the Connection page of the wizard, from the Source drop-down list, select one of the following options: |
◦ |
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. |
7. |
8. |
Optionally, if you want to automatically protect new VMs when they are added to the host, select Auto protect new virtual machines. |
9. |
10. |
On the Adjustments page, enter the credentials for each machine in the following format: hostname::username::password. |
11. |
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. |
15. |
◦ |
If you want to use the default protection schedule, then in the Schedule Settings option, select Default protection (hourly snapshots of all volumes). |
◦ |
◦ |
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.
◦ |
If you selected a Typical configuration for the Protect Machine Wizard 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. |
◦ |
If you selected Advanced configuration for the Protect Machine Wizard, and default protection, then click Next and proceed to Step 18 to see repository and encryption options. |
◦ |
If you selected Advanced configuration for the Protect Machine Wizard and specified custom protection, then 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. |
17. |
18. |
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. |
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. |
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. |
Enter the location for storing the protected data. For example, type X:\Repository\Data. | |
Enter the location for storing the protected metadata. For example, type X:\Repository\Metadata. |
▪ |
Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table. |
5. |
In the Storage Configuration area, click More Details and enter the details for the storage location as described in the following table. |
| |||||||||
Set the value to one of the following:
If set to Off, Rapid Recovery controls the caching. If set to Sync, Windows controls the caching and the synchronous input/output. | |||||||||
Specify the number of bytes you want each sector to include. The default value is 512. | |||||||||
Specify the average number of bytes per record. The default value is 8192. |
6. |
Click Next. |
19. |
Encryption key fields appear on the Encryption page.
NOTE: If you enable encryption, it is applied to data for all protected volumes on this machine.
You can change the settings later from the Encryption Keys page in the Rapid Recovery Core Console.
For more information about encryption, see the topic Encryption keys. |
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. |
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. | |
22. |
23. |
The Rapid Recovery Agent software is deployed to the specified machines, if necessary, and the machines are added to protection on the Core.
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. |
◦ |
3. |
4. |
On the Connection page of the wizard, from the Source drop-down list, select one of the following options: |
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. |
8. |
9. |
Optionally, if you want to automatically protect new VMs when they are added to the host, select Auto protect new virtual machines. |
10. |
11. |
◦ |
If you want to use the default protection schedule, select Default protection (hourly snapshots of all volumes). |
◦ |
If you want to define a different protection schedule, select Custom protection. |
◦ |
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. |
◦ |
If you selected Advanced configuration for the Protect Machine Wizard and Default protection, then click Next and proceed to Step 14 to see repository and encryption options. |
◦ |
If you selected Advanced configuration for the Protect Machine Wizard and specified Custom protection, then 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. |
14. |
1. |
Select Use an existing repository. |
3. |
Click Next. |
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. |
2. |
Click Next. |
3. |
On the Repository Configuration page, use one of the following options to determine the size of the repository: |
▪ |
To allocate a percentage of the storage location for the repository, use the Percentage of available space slider tool. |
4. |
Optionally, select Show advanced options, and then complete the information described in the following table. |
Specify the number of bytes you want each sector to include. The default value is 512. | |||||||||
Specify the average number of bytes per record. The default value is 8192. | |||||||||
Set the value to one of the following:
|
5. |
Click Next. |
15. |
Encryption key fields appear on the page.
NOTE: If you enable encryption, it is applied to data for all protected volumes for this machine. You can change the settings later from the Encryption Keys page in the Rapid Recovery Core Console. For more information about encryption, see Encryption keys. |
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. |
16. |
If you want to encrypt these protected machines using an encryption key that is already defined on this Rapid Recovery Core, complete the following steps: |
a. |
c. |
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. |
Enter the passphrase used to control access. The best practice is to avoid special characters listed in the Name description of this table. | |
18. |
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. |
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy