VBR6.1 W2K8r2sp1 corrupt after Backup

[Novell2]

HI,
we had a big problem with a SQL-VM (W2K8r2SP1). The Backup VBR6.1 was started, created the snapshot, and was working with copying files, after that maybe an interruption, the Backup did retry a new backup again with a new snapshot. When the people sarted their work the server was extremly slow, nobody could work and the console was showing deleting snapshot. After several hour we decided to kill the VM and restore the hole VM. This happens twice a time (monthly).
I am not shure if the new version VBR6.1 is stable enough, or is VBR6.1 to sensitive for network interruption?

Thanks for your answer!

[Gostev]

Hi, actually snapshot deletion is not handled by Veeam, it is performed solely by VMware. This has been discussed many times before, please search for the existing topics. Also, VBR6.1 is definitely not "new", as current version is 6.5 already. But yes, answering your questions 6.1 has been one of the most stable releases we had to date. Thanks!

[pendragoncrw]

Are you using Veeam One or vCenter alerst to verify the actual snapshot status of the VM in question? We have had instances in the past where an old VM (usually a P2v machine) has acquired many snapshots over its lifetime and eventually it hits snapshot critical mass resulting in performance problems.

The way to check this manually would be to look in the datastore folder for the VM in question and see how many snapshot VMDK's are in there (they usually end in 000X).