No quiesce option for VM backup

Along TSM-VE implementation, I have observed that lots of errors are generated due to virtual machine quiescence errors. Beause TSM has no control on how the operating systems are configured, and if there is any issue with the in guest VSS tools, I would excpect TSM to take the snapshot anyway, or at least to have the possibility to control this.<br /> Since TSM relies on VMware and Virtual machine operating system tools for this quiesce activity, I would imagine TSM vm backup , when this quiesce error happens, can retry the snapshot without quiescing the virtual machine, thus avoid error and take a crash consistent backup, which is better than having no backup.<br />In addition, I would suggest to have these kind of option on the datamover to control how it behaves:<br />1/ snapshotretry {number} : to allow tsm to retry the snapshot operation . Number could be limit to 3 as a maximum for instance. In addition to this paramter, we can have either a hardcoded intervall between each retry, or let the user specifiy a value in second. <br />2/ Quiesce Yes|No|Retry . No means    tsm would perform a snapshot whithout quiescing the virtual machine. Yes means that tsm would force to quiesce the virtual machine when taking the snaphot, and if the quiesce fails, TSM backup fails, and finally Retry could give the possibility to TSM to retry the operation. Combination of TSM quiesce=retry and snapshotretry=2 would allow TSM to retry two times with the quiesce option before to take the snapshot without quiescing the virtual machine (means crash consistent backup), as a default backup.