Ordinary VM Backup

In the figure below, the RPO is longer than 1 hour. You can choose CDP or an ordinary datastore as the backup repository.

Ordinary VM backup requires a local backup repository (backup storage space on the local VM) and a remote backup repository (backup storage space on the placeholder VM). It is recommended to use a datastore that differs from the production datastore as the local backup repository. For example, if the VMs on the primary site run in a virtual datastore, it is recommended to use an EDS external datastore as the local backup repository to ensure sufficient storage space for data backup. If the backup repository uses the production datastore, when the production datastore is unavailable, data backup also fails. In this scenario, no backup can be used for recovery. This also prevents backups from degrading the performance of the virtual datastore, ensuring the performance of your business.

CDP

In the figure below, the RPO is 30 minutes or shorter. CDP must be used as the local backup repository.

CDP not only requires a local backup repository and a remote backup repository, but also requires a datastore to store IO activity logs. It is recommended to store IO activity logs in a dedicated EDS external datastore, which differs from virtual datastores of production VMs. IO data is written into IO activity logs in real time to ensure consistency with business IO data. Therefore, using a dedicated IO activity log datastore can prevent frequent IO activity logging from degrading the performance of virtual datastores of production VMs.