It seems that a major issue with the current version of Veeam Backup and Replication has been identified over the last few days.
It was first discussed on Veeam’s own forum on Saturday, with the main problem being data corruption when restoring Linux VMs on Veeam 4.
The user (tsightler) quoted the problem as “disasterous”, moving on to elabourate that “each and every filesystem reported tons and tons of corruption, so bad that it was uncorrectable”.
The problem is alledged to also occur with a Veeam replicated VM as well. Using the Veeam replication feature produces a VM that appears to be OK, but will fail any attempt to run. The VM starts ‘fsck’ which generates errors on disk operations to free space. Cloning a running VM using vCenter, did produce a clean copy.
Veeam’s product manager Anton Gustev has since theorised that the issue might lie soley with ESX4, only affecting linux VMs, and that it’s only the ‘free space’ that gets corrupted because it’s not zeroed out properly.
Other user’s posts seem to point to a potentially deeper issue of corrupt data when using CBT in Windows VMs leading to the dreaded BSOD. Stay tuned as we look into these reports of corrupt data.
Other Veeam forum users described the critical issue with Veeam Backup & Replication as “a major, major problem”, going on to say that this was Veeam’s highest bug fix priority.
