Swap Disk – If the virtual machine to be replicated includes a swap disk as part of its configuration, you can specify a mirror disk for replication that is marked as a swap disk. In this case, data is not replicated to the swap disk after initial synchronization.

Use vCD Managed Storage Profile – The datastore is allocated based on the available free space. You can specify whether the recovery volume is thin provisioned or not. If the Org vDC only supports thin-provisioned volumes, you cannot change the setting. If Zerto Virtual Replication cannot find a storage profile that can be used as target storage, the value is set to Zerto_Any. In this case, any of the datastores configured in the Configure Provider vDCs dialog can be selected as recovery datastores, provided they are exposed to the relevant recovery hosts. Upon recovery, Zerto Virtual Replication chooses a storage profile available to the Org vDC, for the recovered vApp, that contains all of the datastores on which recovery volumes of the VPG reside. If there is no such storage profile, the recovery operation cannot start. The storage profile can be set to Zerto_Any for a number of reasons, such as adding a virtual machine to the VPG which does not have a storage profile that can be used as the target.

Preseed – A virtual disk (the vmdk flat file and header file) in the recovery site that has been prepared with a copy of the protected data, so that the initial synchronization is much faster since a Delta Sync is used to synchronize any changes written to the recovery site after the creation of the preseeded disk. When using a preseeded VMDK, you specify the exact location, the preseed folder configured for the customer and the disk name, of the preseeded disk. A provider datastore must have been specified for preseeded disks in the Configure Provider vDCs Dialog dialog. Zerto Virtual Replication takes ownership of the preseeded disk, moving it from its source folder to the folder used by the VRA. Note that 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. Refer to the 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 using the esxcfg-advcfg -s <Timeout> /NFS/SetAttrRPCTimeout command.

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. For details, refer to Zerto Cloud Manager Administration Guide.