The backup was successful but in the log we see the log entry below and concerns users that the backup is not quiesced:
Guest within VM '<vm name>' uuid '<vm uuid>' will not be quiesced
The log entry can be ignored.
If quiescing fails, users will get a fatal error as the snapshot will fail, this will be "Failed to quiesce VM <vmname>" it is very obvious if it happens. The most common cause of it failing is if a server is running under such a heavy load that the VSS providers on the client are unable to complete. In that case rather than fall back to a crash consistent backup, which could have inconsistent data, we will tell you it's failed to quiesce and then the administrator can investigate allocating more resources to that VM, if possible, or scheduling the backup at a different time when the VM is in a quieter state.
The VMware tools VSS component should cause the SQL/Excange Server to quiesce properly. The only case it doesn't seem to work is the case described above.
Note that Quiescing is at the OS level and backup interaction takes place between NVBU & Vmware and not at the application level . So this should not affect the SQl or Exchange DB and will not be in dirty shutdown state during restore .
Waiting for fix in a future release of NetVault Backup - VMware Plugin