I wouldn't normally worry too much when this occurrs, as normally we use DataRecovery only as a "just in case" tool, but all our customers have a mandatory system and file remote backup in place. BUT, with this particular customer, some super-duper-intelligent salesman decided to sell them DataRecovery as a backup solution, which, not only is it crazy and unreliable, but also makes it complicated to manage, as we cannot count on all backups running smoothly every time...
Anyway (enough about complaints), back to the point. If you MUST no matter how have a DR backup for a machine and it's giving you problems, the only way to solve the issue without having to should down the server (because as our friend Murphy know, backup only fails on production servers, never on development) is what our vmware friends tell us on KB 1031200 and 1031298, disabling VSS writers usage on VMware tools.
For my particular case, this is how it went:
1. You detect a really nice message saying your backup is f*?¿ up:
7/5/2013 9:31:05 AM: Normal backup using 3 Wednesday Bck
7/5/2013 9:32:20 AM: Failed to create snapshot for CUSTOMER-EX02, error -3960 ( cannot quiesce virtual machine)
