We are sorry you had this problem. This is not something we see typically. We are concerned that you may have other issues on your backup server that could possibly cause this to happen again.

For example if you have a bad hard disk somewhere (either source or destination) we have seen VMware Virtual Disk Manager completely fill the drive where vBackup is installed because of all of the disk errors being logged. When the drive fills this can keep vBackup from being able to properly update and save the datastore file and it can become corrupted.

In vBackup version 4.0.2 we added a new option under settings that allows you to disable logging in VMware Virtual Disk Manager. It might be a good idea to consider this upgrade if this sounds like what may have happened.

Hope this helps. Please let us know if we can be of further assistance.