Skip to main content

VMProtect9 and DFSR backup

Thread needs solution

One of my domain controllers suddenly stopped doing DFSR replication right after I backed it up with VMProtect. I finally just built a new server as it was faster than trying to fix it (besides the old one was server 2003, new is server 2008 R2 now). I saw a link where Microsoft tells us to NOT backup using programs that use snapshots in VMWARE or their virtualization platform...
http://support.microsoft.com/kb/2517913
http://blogs.technet.com/b/filecab/archive/2013/04/05/safely-virtualizi…

What is the right way in VMProtect??? Any others have any issues??? Tips? Suggestions?

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Bill,

The articles you are referring to are describing a situation when the DC is _restored_ from default VMware snapshot. Specifically to avoid such issues there was quiescing mechanizm implemented (snapshot option), which utilizes VSS inside the guest OS of the snapshotted VM and makes such snapshot valid for proper DC recovery. vmProtect automatically always uses quiescing option (the snapshot we use in vSphere is created with quiesced=on, memory=off options).

The problem you've run into (stopped DFSR replication after backup) is likely related to either VSS malfunctioning inside the guest OS or to snapshot conslidation stage, though it's hard to say without thorough investigation.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager