VM Corruption through Backup after Upgrade to ESX4.1

[ThomasFachtan]

Hi there,

I currently got a problem concerning Veeam Backup & Replication 4.0 after Upgrade of ESX4.0 to ESX4.1..
We got a test environment running on the vsphere infrastructure,including several oracle database servers..
2 veeam jobs are backing up these vms (~20) every sunday morning. we never got any problems (neither on the database, nor the application servers)..
after we upgraded all of our esx servers to 4.1, the two backup jobs fail and furthermore corrupt the VMs, so some of them won`t boot anymore after chkdsk+restart and the database instances crash and got block corruption.. mostly the corruption could first be recognized when we restarted on of the vms..
yesterday we decided to upgrade veeam from 4.0 to 4.1.2 and scheduled one of the two jobs for last night.. the same thing happened. seems like the temporary snapshots arent working correctly when veeam tries to create orremove them from the vms, as we got these errors in the log:

Creating snapshot CreateSnapshot failed, vmRef "vm-4469", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "True" Es kann kein Snapshot eines stillgelegten Prozesses erstellt werden, weil beim Erstellen des Snapshots das Zeitlimit für das Zurückhalten von E/A in der stillgelegten virtuellen Maschine überschritten wurde.

Creating snapshot CreateSnapshot failed, vmRef "vm-4394", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "True" Zeitüberschreitung beim Vorgang.

Our next step would be to re-create the backup jobs and try if this could fix our problem.. but before we do this (and all the vms are corrupted again) i wanted to ask if someone ever had the same problems and has a possible solution.

summary:

- 5 ESX Servers: 4.0 updated to 4.1 -> corruption through veeam backup job
- Veeam B&R: 4.0 - updated to 4.1.2 -> didnt help out

Thanks in advance,
Thomas

[Gostev]

Hi Thomas, do you have Veeam VSS enabled? If for any reason you cannot do this, please disable VMWare Tools quiescence in the Advanced job settings (see Destination step of the wizard). According to the error (thanks to Google Translate) this is what is causing the issues. Vast majority of our customers are using Veeam VSS for quiescence (which is highly recommended anyway), which may explain why this was not reported before. Thanks!