- Go to the Protected Domains tab. If multiple protected domains have been created, select a specific domain to work with from the drop-down menu.
- Click the Start Protection button. A pop-up dialog box will appear displaying all the VMs from the cluster that can be protected.
- Select the checkboxes of the VMs to be protected.
NOTE: After the VMs are protected, it is possible to go back to select a different protected domain and repeat the process to protect additional VMs.
- Specify a protection mode to use for each VM. Write-through or write-back protection modes are available.
NOTE: It is a best practice to use the same protection mode for all VMs of a protected domain.
VMs selected for protection will use write-through protection mode by default. This mode can be considered “failsafe” because write operations from protected VMs are marked complete only after data have been written to both the replication log store and primary storage.
Write-back protection mode can offer a higher level of performance than write-through protection mode if the replication log store resides on faster storage than primary storage. This is because write operations from protected VMs are marked complete upon receiving acknowledgement from the replication log store alone. Writes to primary storage are asynchronous and do not hold back overall write performance. To ensure the integrity of data and a higher level of performance, it is recommended that write-back protection is used with SSD-based iSCSI LUN that is accessible by both DRVA and all ESXi hosts in the cluster. Furthermore, safeguards should be implemented, such as the use of mirrored RAID on the replication log store to guard against any possible failure of the replication log store. Write-back protection can also be done using VMDK storage; however, ISCSI LUN typically offers the highest level of performance.