Disaster Recovery and Replication + backup for VMware

Hard to say as it depends on what you want to achieve. Typically I’d recommend short term retention for your DR copy - you are more than likely just wanting to boot the latest working copy of the machine in a disaster. You could keep a couple of recovery points around in case you replicated something bad and need to boot a slightly older replica.

Hi Damian,

I think most important question for me is:

Should I run traditional backup job for VMs which has DR jobs configured?

regards,

Przemek

HOw did you go with this ​@Przemek 

I was asked by commvault support to exclude VMs from traditional backup groups, but if we do that wont we would lose the traditional backups currently in place. That could be an issue for things like accidental deletions, data corruption, or even quick restores on the local site. How do we make sure the primary backups are still covered in this setup? Additionally, if the replication setup encounters issues or becomes unavailable, wouldn’t the absence of primary backups leave us with no immediate recovery options?

The docs ( Creating a Replication Group Using the Recovery Configuration Tool ) mention excluding VMs, but they don’t really explain what happens to the primary backups or how we’re supposed to handle retention policies in this setup. Could you share a validated design document or some sort of reference guide that outlines how to plan this properly?

​@Damian Andre ​@commvault  any advise on this?