| Recovery Host (not relevant when replicating to vCD) |
| (Hyper-V) The cluster or host that will host the recovered virtual machine. |
|
(vSphere) The cluster, resource pool, or host that will host the recovered virtual machine.
If the site is defined in Zerto Cloud Manager, only a resource pool can be specified and the resource pool must also have been defined in Zerto Cloud Manager.
For details about Zerto Cloud Manager, see Zerto Cloud Manager Administration Guide.
When a resource pool is specified, Zerto checks that the resource pool capacity is enough for all the virtual machines specified in the VPG |
When a resource pool is specified, Zerto checks that the resource pool capacity is enough for all the virtual machines specified in the VPG.
If a resource pool is specified and DRS is disabled for the site later on, all the resource pools are removed by VMware and recovery is to any one of the hosts in the recovery site with a VRA installed on it.
All resource pool checks are made at the level of the VPG and do not take into account multiple VPGs using the same resource pool. If the resource pool CPU resources are defined as unlimited, the actual limit is inherited from the parent but if this inherited value is too small, failover, move, and failover test operations can fail, even without a warning alert being issued by Zerto Virtual Manager. |
| VM Recovery Datastore (vSphere) (not relevant when replicating to vCD) |
| The datastore where the VMware metadata files for the virtual machine are stored, such as the VMX file. |
If a cluster or resource pool is selected for the host, only datastores that are accessible by every ESX/ESXi host in the cluster or resource pool are displayed. This is also the datastore where RDM backing files for recovery volumes are located. |
| Recovery Storage (Hyper-V) (not relevant when replicating to vCD)
|
| The location where the metadata files for the virtual machine are stored, such as the VHDX file. |
If a cluster is selected for the host, only storage that are accessible by every host in the cluster are displayed. |
| Journal Size Hard Limit
|
The maximum size that the journal can grow, either as a percentage or a fixed amount. | • | The journal is always thin-provisioned. |
| • | The Journal Size Hard Limit applies independently both to the Journal History and also to the Scratch Journal Volume. |
For Example: If the Journal Size Hard Limit is configured to a maximum size of 160 GB limit, then during Failover Test, both the Journal History and the Scratch Journal Volume together can take up to 320 GB. Each one with a maximum size of 160 GB limit. |
Unlimited: The size of the journal is unlimited and it can grow to the size of the recovery storage/datastore.
If Unlimited is selected, Size and Percentage options are not displayed. |
Size (GB): The maximum journal size in GB. | • | The minimum journal size, set by Zerto, is 8GB for Hyper-V and vSphere environments, and 10GB for Microsoft Azure environments. |
|
Percentage: The percentage of the virtual machine volume size to which the journal can grow. | • | This value can be configured to more than 100% of the protected VM's volume size. |
|
| Journal Size Warning Threshold
|
| The size of the journal that triggers a warning that the journal is nearing its hard limit. |
Unlimited: The size of the journal is unlimited and it can grow to the size of the recovery storage/datastore.
If Unlimited is selected, Size and Percentage options are not displayed. |
| Size* (GB): The size in GB that will generate a warning. |
| Percentage*: The percentage of the virtual machine volume size that will generate a warning. |
*The values of Size and Percentage must be less than the configured Journal Size Hard Limit so that the warning will be generated when needed.
In addition to the warning threshold, Zerto will issue a message when the free space available for the journal is almost full. |
| Journal Storage (Hyper-V), or Journal Datastore (vSphere) (not relevant when replicating to vCD) |
| The storage/datastore used for the journal data for each virtual machine in the VPG. |
(vSphere) To change the default, specify a host and then select one of the datastores accessible by this host to be used as the journal datastore. When you select specific journal datastore, the journals for each virtual machine in the VPG are stored in this datastore, regardless of where the recovery datastores are for each virtual machine. In this case, all the protected virtual machines must be recovered to hosts that can access the specified journal datastore.
(Hyper-V) To change the default, specify a host and then select the storage location accessible by this host to be used as the journal storage. When you select specific journal storage, the journals for each virtual machine in the VPG are stored in this storage, regardless of where the recovery storage is for each virtual machine. In this case, all the protected virtual machines must be recovered to hosts that can access the specified journal storage. |
