Robert



In my experience, this can also be a hard fault that can't be avoided by
increasing retries or re-scheduling backups.



Diagnosis is difficult, but if you can capture the temporary files created
on the guest VM during the backup it may give some pointers. There's a
transient file C:\USERS\guest_admin_id\APPDATA\LOCAL\TEMP\TSM\vmtsmvss_0.sf
(depending on your value of %TEMP%) that only exists for the duration of the
backup. It lists the volumes that the quiesce is trying to freeze which may
bear no relation to the volumes actually containing the SQL databases. In
our case there were orphaned mount points that needed tidying up which were
causing the ANS9417E errors.



With regards to your previous post about the requirement to install DP for
SQL on the guest to truncate the logs, you're going to need that anyway to
recover individual databases from the VM snapshots. You're also going to
need TSM for VE installing in the guest VM. The docs get a bit muddled at
this point (eg confusing DP for SQL and DP for Exchange, omitting the
requirement to install the Recovery Agent Command Line, using the
dsm.setaccess.opt in step 5a that isn't created until step 5b, etc) so it's
a bit of a minefield.



We're still working our way through this in development so look forward to
seeing your results.



Regards

Neil Schofield

Tivoli Storage Manager SME, Lloyds Banking Group