Ever since we have upgraded to vSphere 6.0, we have been getting corrupted trans log errors while taking transaction log backups of a SQL instance running on a VM. The error message from SQL is: Backup detected log corruption in database Department. Context is FirstSector. LogFile: 2 'F:\Sqldata\Department_log.ldf' I can work around this by setting the SQL DB to Simple Recovery Model and then back to Full and taking a new full backup followed by a trans log backup thereby restarting the chain. This error is happening every night and appears to be kicked off by our nightly VM level backups taken by CommVault which takes a snapshot, backs up the VMDk and then removes the snapshot. However, I can replicate this problem without our backup solution by doing a storage vMotion followed by an in-SQL backup of the transaction logs which will error out with trans log corruption. This was not occurring prior to the upgrade to vSphere 6.0 from 5.5. I have ensured that the VM Tools are up to date as well as the VM Hardware version. Hopefully someone has some insight into what could be going on here as I am stumped and would hate to go backwards to vSphere 5.5.
Relevant VM and vSphere info
VM
Windows 2008 R2
SQL Server 2008 R2 - SP3 (10.50.6220.0)
VM Tools 9536
VM hardware v11
vSphere
C7000 Blade Enclosure with 3 x BL460c Gen8
VMware ESXi, 6.0.0, 2494585 (Custom HP image)