This procedure applies to Hyper-V hosts or nodes that use Rapid Recovery Rapid Snap for Virtual (agentless protection) to protect virtual machines (VMs).
A Hyper-V host that is using Rapid Snap for Virtual (agentless protection) to protect VMs is indicated in the left navigation area by the host icon 
.
The settings for a Hyper-V host with VMs that are protected agentlessly are not the same as a typical protected machine. All changes made to the settings for a host apply to the VMs on that host.
- On the Core Console, under Protected Machines in the left navigation area, click the Hyper-V host whose settings you want to change.
The Summary page for the host opens.
- On the menu bar for the host, click Settings.
The Settings page opens.
- Under General, click the setting you want to change.
The setting you selected becomes editable, as a text field or a drop-down menu.
- Enter the configuration information as described in the following table.
Table 68: General settings information
|
Display Name |
The name that displays for a protected machine in the Rapid Recovery Core Console. You can enter up to 64 characters. By default, it is the host name of the machine. You can change the display name to something more user-friendly if needed. Do not use prohibited characters or prohibited phrases. |
|
Host Name |
The name of the protected machine as it appears in the machine's metadata.
|
|
NOTE: Do not change this setting, as doing so could break the connection between the protected machine and the Core. | |
- Under Transfer Queue, to change the number of transfer jobs that can occur on the host at one time, click the setting for Maximum concurrent transfers.
|
|
NOTE: For best performance, it is recommended that the maximum concurrent transfers for the Hyper-V host or node be set to 1, which is the default setting. |
- Under Nightly Jobs, to change the settings for the available nightly jobs, click Change.
The Nightly Jobs windows appears.
- Enter the configuration information as described in the following table.
Table 69: Nightly Jobs settings information
|
Clear orphaned registry keys on protected Hyper-V host |
Removes the unnecessary files from the registry that result from attaching and detaching virtual disks during data transfers. |
|
Check integrity of recovery points |
Conducts an integrity check of each recovery point created for the virtual machines on the Hyper-V host. |
- Click OK.
- Under Auto Protection, to determine whether to automatically protect new virtual machines when they are added to the Hyper-V host, click the setting for Auto protect new virtual machines.
This procedure applies to Hyper-V virtual machines (VMs) that are protected using Rapid Recovery Rapid Snap for Virtual (agentless protection).
A Hyper-V VM that is being protected by Rapid Snap for Virtual (agentless protection) is indicated in the left navigation area by the host icon 
.
The settings for a Hyper-V agentless VM the same as a typical protected machine with the exception of the Hyper-V section at the bottom of the Settings page. The following task provides instructions for only the Hyper-V section settings. For all other protected machine settings, see Viewing and modifying protected machine settings.
- On the Rapid Recovery Core Console, in the left navigation area under Protected Machines, click the Hyper-V VM whose settings you want to change.
The Summary page for the VM opens.
- On the menu bar for the host, click Settings.
The Settings page opens.
- In the list on the left side, click Hyper-V.
The setting you selected becomes editable, as a text field or a drop-down menu.
- Under Hyper-V, click Snapshot configuration.
The setting you selected becomes editable a drop-down menu.
- From the drop-down menu, select one of the options described in the following table.
Table 70: Hyper-V settings information
| Try to create VSS snapshot during transfer first, if it fails, create a checkpoint |
If the VSS snapshot succeeds, the recovery point will be in an application-consistent state. If the VSS snapshot fails and a checkpoint is created, the recovery point will be in a crash-consistent state. |
| Do not create VSS snapshot during transfer |
Generates a recovery point in a crash-consistent state. |
| Use only VSS snapshots during transfers. If VSS snapshot creation fails, the entire transfer will fail |
Generates only application-consistent recovery points. If the VSS snapshot fails, no recovery point is generated. |
This procedure applies to VMware ESXi or Workstation virtual machines (VMs) that are protected using Rapid Recovery Rapid Snap for Virtual (agentless protection).
The settings for a VMware VM that is protected agentlessly include the same settings that are used for a typical protected machine, with one exception. The
vSphere section of the
Settings page includes settings that apply only to agentlessly protected VMware VMs. The following task provides instructions for only the
vSphere section of the
Settings page. For all other protected machine settings, see
Viewing and modifying protected machine settings.
- On the Rapid Recovery Core Console, under Protected Machines in the left navigation area, click the display name of the Hyper-V host you want to change.
The Summary page for the host opens.
- On the menu bar for the host, click Settings.
The Settings page opens.
- In the list on the left side, click vSphere.
The setting you selected becomes editable, as a text field or a drop-down menu.
- Under vSphere, click the setting that you want to change.
The setting you selected becomes editable, as a text field or a drop-down menu.
- Enter the configuration information as described in the following table.
Table 71: vSphere settings information
| Allow Rapid Recovery to delete user created in VMware |
The default setting is No. |
| Allow transfer for volumes with invalid used capacity |
The default setting is Yes. |
| Allow quiesced snapshots |
The default setting is Yes. |
Active Block Mapping (ABM) is a patent-pending technology that filters out inactive blocks of data from managed images, thereby letting Rapid Recovery protect only the active blocks, which optimizes function and performance. This feature is only available for agentless (Rapid Snap for Virtual) protection of ESXi or vCenter virtual machines (VMs) and Hyper-V servers and clusters.
ABM delivers a query to the file system header of a volume. The query returns a list of active blocks within the image. For this reason, ABM only works with NTFS file systems. When protecting ESXi and vCenter VMs, ABM can be combined with Changed Block Tracking (CBT), to read only active and changed blocks when taking incremental or differential snapshots.
When configuring agentless protection of a VM with the Protect Multiple Machines wizard, you have the option to enable ABM. If you opt to automatically protect new VMs added to the specified host, then the ABM rule also applies to any new VMs subsequently added to protection on the host.
You can change your ABM choice at any time in the Settings page for the host or VM. For more information, see Changing ABM settings.
