Hello, I hope somebody can help with this!
Configuration SRM side:
Configuration Backupexec job side:
ISSUE:
Findings:
I already tried:
Next:
Thanks!
Solution:
Questions:
thanks
Your test basically confirms that there is a VSS confilict going on.
No quiesce would get you crash-consistent backups. This can be a big deal, but it is most important for apps that have VSS capability like SQL. Other apps that don't have VSS support won't really matter, as they are going to be crash consistent anyway. With either approach it comes down to understanding exactly what you get/have, and making sure that you have tested it to verify that you can get it to work. With the BE and vSphere Replication combo, then it might make more sense to have the replicas the most consistent, as that should be the fastest recovery time.
We are using Acronis vmProtect 8. This backed up fine for many months.
We started using vSphere Replication with the 'MS Shadow Copy' quiescing enable. After two days the vmProtect backups started to fail. We noticed a lot of change block tracking .ctk files per virtual disk and snaphot delta vmdk.
In the end we had to delete the .ctk files and consolidate as per kb article 2013520.
Can vSphere Replication using quiescing ever work with backup software?
