Now we can create the actual backup job. Let’s go back to Home–>Jobs and add a CDP Policy
Add the computer we created in the protection group.
Next we choose our Datastore, Host, and Resource Pool. Under Policy settings we can choose our replica suffix. Note this has to be unique, I had the job fail during testing because it already existed.
Finally, we can set our RPOs and retention.
After I deployed the policy the first time I was very excited, only to see error messages coming in that after the initial sync the io driver on the hosts failed. Lesson learned, you must reboot the host after deploying the driver!
The next run was successful!
Looks great. What is the amazing part, let’s say that server died, and we have to recover from Veeam, or restore files from it. We can go to replica and failover to a point in time.
You can scroll through the timeline or use the latest point of time.
This is pretty sweet in my book!
This concludes this post. We now have CDP running and can restore any workload we are able to back up to a point in time, controlled by our RPO’s we defined. This is perfect for mission-critical workloads where every moment of downtime costs the business money.
Let me know your questions and thoughts in the comments! Hope you enjoyed it.
