In some cases we have Hosted Customer backups where we cannot enable Guest Interaction for application aware processing. This could be for many reasons including but not limited to:
* Customer doesn't want to provide us credentials
* Customer doesn't want firewall ports to be opened

In these cases we can enable VMware Tools quiescence in the job settings, which is better than nothing at all, right?
If a customer vm fails to back up 3 times in a row with VMware Tools quiescence, there is no backup of that server.
If a customer has 10 vm's and only 1 fails, we cannot exclude the 1 server, instead we have to turn off quiescence at the job level.

To work around this issue I have a powershell script that detects jobs that failed due to VMware Tools quiescence issues, and re-runs them with quiescence disabled (and then re-enables quiescence after it's done). This is reliable but less than ideal. There are multiple negative side effects of this entire process that are too long winded to mention here.

There are two things that would benefit us in these cases:
1) Ability to selectively exclude individual VM's from having VMware Tools quiescence utilized
2) Option to revert to non-quiesced backup after n fails