Are you using RDM attached to the vm's that are failing?

-KjB

-KjB

-KjB

Message was edited by: kjb007 : added Max

-KjB

-KjB

I might be teaching you to suck eggs here, but..

Can you check your snapshot manager to see if you already have active snaps for that VM, if not or if so , can you confirm that checking the contents of your .vmx file for that VM reflects the amount of/lack of snaps that you expect to see compared to what snapshot manager sees?

Have you zoned your VCB proxy so it can see all the LUNS that are presented to that VM?

It just feels like VCB is inspecting your machine and expecting to see snap files which the VCB cannot see because they never were or it cannot get access to.

Regards

Paul.

If you get this message when backing up a windows host, please check your event logs - particularly the windows application log - if you have SQL server running and there is a configuration problem (in a case we solved it was that the user had deleted the SQL database files during testing but not deleted the SQL database config in the SQL Manager, so the SQL config was orphaned).

Whereas a straight snapshot will work, it does not try to do anything clever with the SQL transactions via the VMTools that you have installed, whereas via VCB, it proxies the VMTools to make sure that the SQL is instructed to complete all transactions fully before the snapshot is made - if the SQL config has orphaned databases, this cannot be completed and it generates loads of SQLVSS errors in the application log.

To solve this, deal with the SQL server config issues and then it will work just fine.

Good Luck

Neill Lawson-Smith VCP

Oxford UK