Replication From a Protected Site AWS to a Recovery Site vCloud Director
You can protect virtual machines to a recovery site vCloud Director. The procedure is the same whether you intend to protect one virtual machine or multiple virtual machines.
When creating a VPG from AWS to a vCloud Director, all recovery operations bring up the recovered machines on VMware vCenter Server hosts.
The hardware version of the virtual machine must be the same or less than the hardware version supported by the vDC in vCloud Director (vCD), otherwise recovery of the virtual machine in vCD is not permitted.
Zerto uses SCSI for vCenter Server virtual machine disks.
When protecting virtual machines from AWS to vCloud Director, the operating systems of the protected machines must be supported by vCenter Server. Refer to the VMware documentation for a list of supported operating systems.
The following conversions are done to a protected virtual machine in when it is recovered in vCD:
|
•
|
The SCSI controller type is operating system dependent. |
|
•
|
All disks are thin provisioned. |
|
•
|
Recovered virtual machines use the VMware Virtual E1000 network adapter. |
|
•
|
Operating systems will be either Windows 2012 (64-bit) or Linux Other (64-bit) |
|
•
|
(Public cloud environments) Memory and CPU properties will be extracted from the instance type in Azure and AWS. |
|
•
|
(Azure environments) In Azure VMs, each data disk has a Logical Unit Number (LUN) whereas in the recovered VMs there are no LUNs. |
To create a virtual protection group (VPG) to recover in vCD:
|
1.
|
In the Zerto User Interface, select ACTIONS>CREATE VPG. |
The GENERAL step of the Create VPG wizard is displayed.
|
2.
|
Specify the name of the VPG and the priority of the VPG. |
|
•
|
VPG Name: The VPG name must be unique. The name cannot be more than 80 characters. |
|
•
|
Priority: Determine the priority for transferring data from the protected site to the recovery site when there is limited bandwidth and more than one VPG is defined on the protected site. |
|
•
|
High Priority: When there are updates to virtual machines protected in VPGs with different priorities, updates from the VPG with the highest priority are passed over the WAN first. |
|
•
|
Medium Priority: Medium priority VPGs will only be able to use whatever bandwidth is left after the high priority VPGs have used it. |
|
•
|
Low Priority: Low priority VPGs will use whatever bandwidth is left after the medium priority VPGs have use it. |
Updates to the protected virtual machines are always sent across the WAN before synchronization data, such as during a bitmap or delta sync.
During synchronization, data from the VPG with the highest priority is passed over the WAN before data from medium and low priority VPGs.
The VMs step is displayed.
|
•
|
The list of unprotected VMs includes VMs that were in the ZCA’s account and region during installation. |
|
•
|
A VPG can include virtual machines that are already protected by another ZCA in the same account and region. |
|
•
|
The size of the disk is defined by data disks and the OS disk. |
|
•
|
AWS Instance Store disks (Temp disks) are not included in the list of unprotected VMs. |
|
4.
|
From the Unprotected VMs list, select the VMs to include in this VPG and click the arrow to move them to the Selected VMs. |
|
•
|
When using the Search field, you can use the wildcards; * or ? |
|
5.
|
To define the boot order of the virtual machines in the VPG, click DEFINE BOOT ORDER, otherwise go to the next step. |
When virtual machines in a VPG are started in the recovery site, by default these machines are not started up in a particular order. If you want specific virtual machines to start before other machines, you can specify a boot order. The virtual machines are defined in groups and the boot order applies to the groups and not to individual virtual machines in the groups. You can specify a delay between groups during startup.
|
Note:
|
Up to 20 virtual machines may boot on a host simultaneously. Following the boot, a 15 second (default) delay occurs until the next boot batch. |
Initially, virtual machines in the VPG are displayed together under the Default group. If you want specific machines to start before other virtual machines, define new groups with one or more virtual machines in each group.
|
6.
|
Click ADD GROUP to add a new group. Then, do the following: |
|
a.
|
To change the name of a group, click the Pencil icon next to the group. |
|
b.
|
To delete a group, click the delete icon on the right side. You cannot delete the Default group nor a group that contains a virtual machine. |
|
c.
|
Drag virtual machines to move them from one group to another. |
|
d.
|
Drag groups to change the order the groups are started, or, optionally, in Boot Delay, specify a time delay between starting up the virtual machines in the group and starting up the virtual machines in the next group. |
For Example: Assume three groups, Default, Server, and Client, defined in this order. The boot delay defined for the Default group is 10, for the Server group is 100, and for the Client group 0. The virtual machines in the Default group are started together and after 10 seconds the virtual machines in the Server group are started. After 100 seconds the virtual machines in the Client group are started.
|
e.
|
Click OK to save the boot order. |
Click NEXT.
The REPLICATION step is displayed.
|
7.
|
Select the Recovery Site, and select vCD from the drop-down list. (If there is only one site available, it’s displayed by default. |
The REPLICATION step is re-displayed, with additional fields relevant for vCD.
|
8.
|
Select the Recovery Org vDC to use in the recovery site. |
|
Note:
|
You cannot select a recovery site if any of the virtual machines you selected are already in VPGs that recover to that site. |
|
Note:
|
At least one VRA needs to be installed on a host within a resource pool being used by a Recovery Org vDC. |
|
9.
|
In the SLA area, you define the Service Level Agreement for which this VPG is associated. |
|
•
|
When Zerto Cloud Manager is used, select the Service Profile to use. |
The Service Profile determines the VPG SLA settings for the group. This applies predefined settings for the Journal History, Target RPO Alert and the Test Reminder. These settings apply to every virtual machine in the group.
|
•
|
When a Custom service profile is available, the VPGSLA settings are editable, and the Advanced button becomes available. When you change these settings, they apply to every virtual machine in the group. |
|
10.
|
Click ADVANCED. The Advanced Journal Settings dialog is displayed. |
Setting & Description |
Select... |
Journal History
|
The time that all write commands are saved in the journal.
The longer the information is saved in the journal, the more space is required for each journal in the VPG. |
|
•
|
Number of hours from 1 to 23 |
|
|
•
|
Number of days from 1 to 30 |
|
Default Journal Storage (Hyper-V), or Default Journal Datastore (vSphere) |
The storage/datastore used for the journal data for each virtual machine in the VPG. | Note: | This field is not relevant when replicating to a vCD recovery site. |
|
|
•
|
Select the storage/datastore accessible to the host.
|
When you select a specific journal storage/datastore, the journals for each virtual machine in the VPG are stored in this storage/datastore, regardless of where the recovery storage/datastore is for each virtual machine. All protected virtual machines are recovered to the hosts that can access the specified journal storage/datastore. |
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. | Note: | 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. |
|
•
|
Target RPO Alert: The maximum desired time between each automatic checkpoint write to the journal before an alert is issued. |
|
•
|
Test Reminder: The amount of time in months recommended between each test, where you test the integrity of the VPG. A warning is issued if a test is not performed within this time frame. |
To change the replication settings per virtual machine, click VM SETTINGS.
The Advanced VM Replication Settings window is displayed.
In this window, you can edit the values of one or more of the virtual machines in the VPG.
|
12.
|
To edit information for a single VM, click the field Storage Policy, or Journal Storage Policy, and update the information. |
|
13.
|
To edit information for several virtual machines at the same time, select the virtual machines and click EDIT SELECTED. |
The Edit VM window is displayed.
|
14.
|
When selecting Storage Policy, consider the following: |
|
•
|
Zerto will select a datastore from the selected Storage Policy in which to place these files, unless the datastore is excluded in the Configure Provider vDCs Dialog. |
|
•
|
Zerto will try to determine a default Storage Policy according to: |
|
•
|
A Storage Policy with the same name as the protected Storage Policy. |
|
•
|
The default Orgvdc Storage Policy. |
If Zerto did not manage to determine a default Storage Policy, this field appears empty.
|
•
|
When you click to edit, a list of Storage Policies appear. These Storage Policies: |
|
•
|
Were defined in VMware vCloud Director and are configured in the Orgvdc. |
|
•
|
Have at least one Datastore that was not excluded as a Recovery Volume in the Configure Provider vDCs Dialog. |
|
15.
|
When selecting Journal Storage Policy, consider the following: |
|
•
|
Zerto will select a datastore from the selected Storage Policy in which to place the Journal files, unless the datastore is excluded in the Configure Provider vDCs Dialog. |
|
•
|
The default Journal Storage Policy is the same as the default VM Storage Policy. |
|
•
|
If Zerto did not manage to determine a default Journal Storage Policy, this field appears empty. |
|
•
|
When you click to edit, the option Auto Select appears, and a list of Storage Policies. |
|
•
|
The list of Storage Policies associated with the Journal: |
|
•
|
Were defined in VMware vCloud Director and are configured in the Orgvdc. |
|
•
|
Have at least one Datastore that was not excluded as a Journal in the Configure Provider vDCs Dialog. |
|
•
|
Auto Select: Selecting this means that the journal can be placed in any datastore visible to the host that Zerto selected for recovery, unless the datastore is excluded in the Configure Provider vDCs Dialog. |
Setting & Description |
Select... |
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. I |
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. |
|
16.
|
In the Advanced VM Replication Settings window, click OK. |
The Storage step is displayed.
By default the storage used for the virtual machine definition is also used for the virtual machine data.
For each virtual machine in the VPG, Zerto displays its storage-related information.
|
18.
|
To edit storage information for one of the virtual machines volumes, select the volume/s and click EDIT SELECTED. |
|
•
|
For Hyper-V recovery environments, the following window appears. For details, click here. |
|
•
|
For vSphere recovery environments, the following window appears. For details, click here. |
|
•
|
For vCD recovery environments, the following window appears. For details, click here. |
Setting & Description |
Select... |
Volume Source
|
|
•
|
(Hyper-V) Select a Volume Source for recovery from one of the drop-down options: |
|
|
•
|
Volume Source > Storage: A new volume is used for replicated data. |
|
•
|
From the Storage drop-down list, specify the storage to use to create disks for the replicated data.
|
The storage specified for the replication must have at least the same amount of space as the protected volume and then an additional amount for the journal.
The amount of additional space needed for the journal can be fixed by specifying a maximum size for the journal, or can be calculated as the average change rate for the virtual machines in the VPG, multiplied by the length of time specified for the journal history.
For more details, see Zerto Scale and Benchmarking Guidelines, in the section Estimating WAN Bandwidth for VMware and Hyper-V. |
|
•
|
Volume Source > Preseeded volume: Whether to copy the protected data to a virtual disk in the recovery site. |
Zerto recommends using this option particularly for large disks so that the initial synchronization will be faster since a Delta Sync can be used to synchronize any changes written to the recovery site after the creation of the preseeded disk.
When not using a preseeded disk, the initial synchronization phase must copy the whole disk over the WAN.
When using a preseeded virtual disk, you select the storage and exact location, folder, and name of the preseeded disk.
Zerto takes ownership of the preseeded disk, moving it from its source folder to the folder used by the VRA.
Only disks with the same size as the protected disk can be selected when browsing for a preseeded disk.
The storage where the preseeded disk is placed is also used as the recovery storage for the replicated data. |
(vSphere) Select a Volume Source for recovery from one of the drop-down options: |
Volume Source > Datastore: A new volume is used for replicated data. 
| • | Specify the Datastore to use to create disks for the replicated data. |
| • | If the source disk is thin provisioned, the default for the recovery volume is also thin provisioned. |
| • | The datastore specified for replication must have at least the same amount of space as the protected volume and an additional amount for the journal. |
| • | The amount of additional space needed for the journal can be fixed by specifying a maximum size for the journal, or can be calculated as the average change rate for the virtual machines in the VPG, multiplied by the length of time specified for the journal history. |
| • | Zerto supports the SCSI protocol. Only disks that support this protocol can be specified. |
Then, define the following: | • | Datastore: The Datastore where the preseeded disk is located. Only disks with the same size as the protected disk can be selected when browsing for a preseeded disk. |
For more details, see Zerto Scale and Benchmarking Guidelines, in the section Estimating WAN Bandwidth for VMware and Hyper-V. |
Volume Source > RDM: The VMware RDM (Raw Device Mapping) which will be used for the replication.
 By default, RDM is recovered as thin-provisioned VMDK in the datastore specified in the VM Recovery Datastore/Storage field in the Edit VM dialog, and not to RDM.
Only a raw disk with the same size as the protected disk can be selected from the list of available raw disks. Other raw disks with different sizes are not available for selection.
The RDM is always stored in the recovery datastore, used for the virtual machine.
The following limitations apply to protecting RDM disks: | • | RDM disks with an even number of blocks can replicate to RDM disks of the same size with an even number of blocks and to VMDKs. |
| • | RDM disks with an odd number of blocks can only replicate to RDM disks of the same size with an odd number of blocks and not to VMDKs. |
| • | You cannot define an RDM disk to be protected to a cloud service provider via a Zerto Cloud Connector nor if the virtual machine uses a BusLogic SCSI controller, nor when protecting or recovering virtual machines in an environment running vCenter Server 5.x with ESX/ESXi version 4.1 hosts. |
|
(vSphere) Volume Source continued |
Volume Source > Preseeded volume: Select this when you want to copy the protected data to a virtual disk in the recovery site.  Consider the following, then proceed to define the Datastore and the Path: | • | Zerto recommends using this option particularly for large disks so that the initial synchronization is faster since a Delta Sync can be used to synchronize any changes written to the recovery site after the creation of the preseeded disk. |
| • | If a preseeded disk is not selected, the initial synchronization phase must copy the whole disk over the WAN. |
| • | If you use a preseeded virtual disk, you select the datastore and exact location, folder, and name of the preseeded disk, which cannot be an IDE disk. Zerto takes ownership of the preseeded disk, moving it from its source folder to the folder used by the VRA. |
| • | The datastore where the preseeded disk is placed is also used as the recovery datastore for the replicated data. |
| • | If the preseeded disk is greater than 1TB on NFS storage, the VPG creation might fail. This is a known VMware problem when the NFS client does not wait for sufficient time for the NFS storage array to initialize the virtual disk after the RPC parameter of the NFS client times out. The timeout default value is 10 seconds. See VMware documentation, http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027919, which describes the configuration option to tune the RPC timeout parameter by using the command: esxcfg-advcfg -s <Timeout> /NFS/SetAttrRPCTimeout |
| • | If the protected disks are non-default geometry, configure the VPG using preseeded volumes. |
| • | If the protected disk is an RDM disk, it can be used to preseed to a recovery VMDK disk. Zerto makes sure that the VMDK disk size is a correct match for the RDM disk. |
| • | If the VPG is being defined for a Zerto Organization, ZORG, the location of the preseeded disk must be defined in the Zerto Cloud Manager. See Zerto Cloud Manager Administration Guide.
| Then, define the following: | • | Datastore: The Datastore where the preseeded disk is located. Only disks with the same size as the protected disk can be selected when browsing for a preseeded disk. |
| • | Path: The full path to the preseeded disk. |
|
(vCD) Select a Volume Source for recovery from one of the drop-down options: | • | vCD managed storage policy |
|
Volume Source > vCD managed storage policy: Zerto will select a datastore, from the list of available datastores, in the selected Storage Policy in which to place the Volume, unless the datastore is excluded in the Configure Provider vDCs Dialog. | • | If there are several valid datastores, the datastore with the most available space is selected. |
| • | Zerto recalculates the datastore available space for each volume sequentially, taking into consideration previously allocated volumes.
| Volume Source > Preseeded volume:
Select this when you want to copy the protected data to a virtual disk in the recovery site. | • | Zerto recommends using this option particularly for large disks so that the initial synchronization is faster since a Delta Sync can be used to synchronize any changes written to the recovery site after the creation of the preseeded disk. |
| • | If a preseeded disk is not selected, the initial synchronization phase must copy the whole disk over the WAN. |
| • | The preseeded volume is a virtual disk (the VMDK flat file and descriptor) in the recovery site that has been prepared with a copy of the protected data. |
| • | Browse to the preseed folder configured for the customer and the disk name, of the preseeded disk.
| In order to use a preseeded VMDK, do the following: | • | Create a folder in vCD to use for the preseeded disks in the datastore you want to use for the customer. |
| • | Specify this datastore as a provider datastore for preseeded disks in the Configure Provider vDCs window, from the Advanced Settings window, as described in Zerto Cloud Manager Administration Guide. |
| • | In the Zerto Cloud Manager specify the Preseed Folder Name for the ZORG, in the Manage ZORG tab. |
| • | Zerto searches for the preseeded folder in the available datastores in the Org vDCs specified in the vCD Cloud Resources for the ZORG in the Zerto Cloud Manager and takes ownership of the preseeded disk, moving it from its source folder to the folder used by the VRA.
| If the virtual machine has more than one preseeded disk, these disks must reside on the same datastore. | • | If the preseeded disk is greater than 1TB on NFS storage, the VPG creation might fail. This is a known VMware problem when the NFS client does not wait for sufficient time for the NFS storage array to initialize the virtual disk after the RPC parameter of the NFS client times out.
| The timeout default value is 10 seconds. See VMware documentation, http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027919, which describes the configuration option to tune the RPC timeout parameter by using the command: esxcfg-advcfg -s <Timeout> /NFS/SetAttrRPCTimeout | • | If the VPG is being defined for a Zerto Organization, ZORG, the location of the preseeded disk must be defined in the Zerto Cloud Manager. See Zerto Cloud Manager Administration Guide. |
| • | Zerto supports the SCSI protocol. Only disks that support this protocol can be specified. Virtual machine RDMs in a vCenter Server are replicated as VMDKs in a vCD environment. |
|
(vCD) continued |
Storage Policy: Specify the Storage Policy for recovery from one of the options: | • | Storage Policy per volume is supported only in vCD supported versions, and when the selected Orgvdc is not configured for fast provisioning. |
| • | Zerto will select a datastore from the selected Storage Policy in which to place these files, unless the datastore is excluded in the Configure Provider vDCs Dialog. |
| • | The Storage Policies which appear in the drop-down list: |
| • | Include the Use VM Default option (default), which will apply the VM’s storage policy to this volume. This is also the Storage Policy default value. |
| • | Were defined in VMware vCloud Director and are configured in the Orgvdc. |
| • | Have at least one Datastore that was not excluded as a Recovery Volume in the Configure Provider vDCs Dialog. |
|
Temp Data disk
|
If the virtual machine to be replicated includes a temp data disk as part of its configuration. |
Specify a mirror disk for replication that is marked as a temp data disk.
In this case, data is not replicated to the temp data disk after initial synchronization. |
Thin provisioning (vSphere) |
If the recovery volumes are thin-provisioned or not. |
If the source disk is thin provisioned, the default for the recovery volume is also thin provisioned.
vCD only: Unless the Org vDC only supports thin-provisioned volumes. |
Dynamic provisioning (Hyper-V) |
If the recovery volumes are dynamic-provisioned or not. |
If the source disk is dynamic provisioned, the default for the recovery volume is also dynamic provisioned.
vCD only: Unless the Org vDC only supports dynamic-provisioned volumes. |
The RECOVERY step is displayed. Recovery details include the scripts that should be run either at the start or end of a recovery operation.
|
21.
|
Select the default recovery settings. |
|
•
|
vCD Guest Customization: When selected, VMware Guest OS Customization is enabled for the virtual machine in vCloud Director. Enabling guest customization means that the computer name and network settings configured for this virtual machine are applied to its Guest OS when the virtual machine is powered on. vCD Guest Customization must be selected to enable re-IPing the recovered virtual machines. |
When checked, NAT rules on source vCD vApp networks are copied to the recovery vCD vApp during recovery. One of the following options can be selected:
|
22.
|
To run pre and post recovery scripts, enter the path to the script to run. |
|
•
|
Pre-recovery Script: The information about a script that should run at the beginning of the recovery process. |
|
•
|
Post-recovery Script: The information about a script that should run at the end of the recovery process. |
For both types of scripts, enter the following information:
Text Box |
Description |
Script path
|
The full path to the script. The script must be located on the same machine as the Zerto Virtual Manager for the recovery site. |
Params
|
The parameters to pass to the script. Separate parameters with a space. |
Timeout
|
The time-out, in seconds, for the script to run. | • | If the script runs before executing a failover, move, or test failover, and the script fails or the timeout value is reached, an alert is generated and the failover, move, or test failover is not performed. |
| • | If the script runs after executing a failover, move, or test failover, and the timeout value is reached, an alert is generated. |
| • | The default time-out value is specified in Site Settings > Throttling tab. |
|
|
Note:
|
Pre and post recovery scripts run in parallel. Therefore, ensure that the pre and post recovery scripts don’t use common resources. |
The NICs step is displayed. In this step, you can specify the NIC details to use for the recovered virtual machines after a failover, a test failover, or migration.
|
24.
|
To edit information in one field, click the required field and update the information. |
|
25.
|
To edit information for several virtual machines at the same time, select the virtual machines, and click EDIT SELECTED. |
The Edit VNIC window is displayed.
|
27.
|
Specify the network details to use for the recovered virtual machines after a failover or move operation, in the Failover/Move column, and for the recovered virtual machines when testing replication, in the Test column. |
In each column, specify the following:
|
•
|
Create New MAC Address?: Whether the Media Access Control address (MAC address) used on the protected site should be replicated on the recovery site. The default is to use the same MAC address on both sites. |
|
•
|
Change vNIC IP Configuration?: Which IP mode to use. Specify the IP address if you choose static IP pool. |
See the Zerto Interoperability Matrix for the list of operating systems for which Zerto supports Re-IPing.
During a failover, move, or test failover, if the recovered virtual machine is assigned a different IP than the original IP, then after the virtual machine has started, it is automatically rebooted so that it starts up with the correct IP. If the same network is used for both production and test failovers, Zerto recommends changing the IP address for the virtual machines started for the test, so that there is no IP clash between the test machines and the production machines.
|
•
|
Copy to failover test: Select this to copy the settings in the Failover/Move column to the Test column. |
|
•
|
Copy to failover/move: Select this to copy the settings in the Test column to the Failover/Move column. |
The SUMMARY step is displayed. It shows the VPG configuration that you defined in previous steps.
|
30.
|
Click DONE. The VPG is created. |
For details of what happens after saving the VPG, see What Happens After the VPG is Defined.
The virtual machines in the VPG are protected as a vCD vApp in the recovery site. When recovering the VPG, reverse protection is configured back the virtual machines.