Error during backupjob

[klavenes]

Hi,

I have som problems with one server in av backupjob. There are 3 servers in this job and only one of them fails with the following error:

<Error message:>
Verifying changed block tracking...
Disk "Hard disk 2" has incorrect changed block tracking configuration.
One or more VM disks have incorrect changed block tracking configuration. To resolve this, open VMware vSphere Client, right-click the VM, choose Edit Settings, Options tab, select General, click Configuration Parameters, and set all entries with ‘ctkEnabled’ substring to false. Veeam Backup will then automatically re-enable changed block tracking with the correct settings during the next job run.
<End Of Error Message>

I have change the block trackchanging on the SCSIx:x,ctkEnabled (all SCSI devices) and the ctkEnabled under Configuration Parameters serveral times as described above, but Veeam resett these settings when the backup runs and comes up with the same error message.

Does anyone have a solution to this problem?

[Vitaliy S.]

Hello Simen,

Could you tell us what type of a virtual harddrive is your "Hard disk 2"?

Thanks!

[klavenes]

Hi Vitaliy,

The SCSI controller is LSI Logic SAS. Hard disk 1 (SCSI 0:0) and Hard disk 2 (SCSI 0:1) uses this controller. The virtual machine is running hardware 7. The physical storage is iSCSI.

To isolate the problem further I separated the "troublesome" VM in it own backupjob. The backupjob uses VM quiescence and VSS. The result from the last backup gave this result (se below). I have masked the domain name some of the ipadresses and the datacenter name with XXXXXX. I could not change the block tracking now because the VM is running.

<error message>

Verifying changed block tracking... Disk "Hard disk 2" has incorrect changed block tracking configuration. One or more VM disks have incorrect changed block tracking configuration. To resolve this, open VMware vSphere Client, right-click the VM, choose Edit Settings, Options tab, select General, click Configuration Parameters, and set all entries with ‘ctkEnabled’ substring to false. Veeam Backup will then automatically re-enable changed block tracking with the correct settings during the next job run. Backing up file "[iscsiSANdisk2] Windows 2008 std 64bit/Windows 2008 std 64bit_1-flat.vmdk" BackupDisk failed Client error: Failed to open VDDK disk [[iscsiSANdisk2] Windows 2008 std 64bit/Windows 2008 std 64bit_1.vmdk] ( is read-only mode - [true] ) Failed to open VMDK. Logon attempt with parameters [VC/ESX: [192.XXX.X.19];Port: 443;Login: [XXX\administrator];VMX Spec: [moref=vm-145];Snapshot mor: [snapshot-1021];Transports: [san]] failed because of the following errors: Failed to open VMDK. Logon attempt with parameters [VC/ESX: [192.XXX.X.19];Port: 443;Login: [XXX\administrator];VMX Spec: [moref=vm-145];Snapshot mor: [snapshot-1021];Transports: [nbd]] failed because of the following errors: Server error: Failed to open VDDK disk [[iscsiSANdisk2] Windows 2008 std 64bit/Windows 2008 std 64bit_1.vmdk] ( is read-only mode - [true] ) Failed to open VMDK. Logon attempt with parameters [VC/ESX: [192.168.2.19];Port: 443;Login: [XXX\administrator];VMX Spec: [moref=vm-145];Snapshot mor: [snapshot-1021];Transports: [san]] failed because of the following errors: Failed to open VMDK. Logon attempt with parameters [VC/ESX: [192.168.2.19];Port: 443;Login: [XXX\administrator];VMX Spec: [moref=vm-145];Snapshot mor: [snapshot-1021];Transports: [nbd]] failed because of the following errors: Failed to process VM disk backup. VMDK path: [vddk://<vddkConnSpec><viConn name="192.168.2.19" authdPort="443" vicPort="443" /><vmxPath vmRef="vm-145" datacenterRef="datacenter-116" datacenterInventoryPath="xxxxxxxxxxxxx" snapshotRef="snapshot-1021" datastoreName="iscsiSANdisk1" path="Windows 2008 std 64bit/Windows 2008 std 64bit.vmx" /><vmdkPath datastoreName="iscsiSANdisk2" path="Windows 2008 std 64bit/Windows 2008 std 64bit_1.vmdk" /><transports seq="san;nbd" /><readBuffer size="2097152" /></vddkConnSpec>].

</error message>

[Gostev]

Hello Simen, it would be best if you open a support case to troubleshoot this. We do not provide support on technical issues via forum, as explained when you click New Topic. Most issues require full logs to troubleshoot, not just error's summary. Thanks!