When you protect a virtual machine, the platform creates recovery points with the frequency, replication and retention period in the chosen SLA policy.


To protect a virtual machine:

1. Browse the Virtual Machines page.


Hint: Go to the SLA policies page first to check that you have the right SLA policy configured on the platform.


2. Select the virtual machine that you want to protect from the list on the right. Unprotected virtual machines don't have a policy name in the SLA Policy column.

3. Click on the Protect tab in the right pane.


4. Click on the Protect link. 



Choose the relevant options in the Protect modal window.



5. Select the SLA Policy. 

6. Select the storage pool 

7. Select Recovery point consistency for the VM


Application consistent - the snapshot for the recovery point is taken with a VMWare snapshot that uses VMware Tools. It instructs compatible applications inside the VM to flush all their data to the drive and the snapshot will be taken after the flush operation finishes. This feature requires VMware tools installed.

Crash consistent - the snapshot for the recovery point is taken on the storage itself. This does not impact VM or host performance and is instantaneous. When restoring, the virtual machine will be in a state similar after a power outage.


If the virtual machine does not have VMware Tools installed, recovery points will always be crash consistent. 


8. Choose when to Start protection.


  • Choose now to have the protection start. The snapshot is immediately taken and a recovery point is created. A full replica is started to the target replication if it was configured in the 
  • Choose Later to select the date and time to start the first protection and the first full replica to the other appliance


9. Click Protect.


Your virtual machine is now protected with the chosen SLA policy and recovery point consistency. 


 

Best Practice Recommendations    


Hint: Run the first protection during the night if you plan to replicate to an offsite DR server. This optimizes network usage for the first replica.