Hello,
When using VMware ASC, we can protect Exchange/Sharepoint/SQL by ticking the applicable option in the VMware tab, enabling us to create a consistent / recoverable image for active or passive DB's.
The scenario here is: we're trying to capture the state of active or passive DB's wherever they might reside, and don't care about the actual backup of the .vmdk file for recovery. As a result of this requirement, if the DB's are not mounted on a particular node, then an error 13 (error 2) occurs: the Application State Capture job therefore 'legimately' fails, but the backup job continues to backup the .vmdk file. This backup job will never be used for recovery as all we care about is the capture of the DB's.
What I think is necessary is:
If a ASC job fails with an error, regardless of whether we're trying to capture active or passive DB's, we should be given an option to not run the backup job.
Glen.