VBK corrupted?

[m.novelli]

Tonight, during Veeam backup, after about 10 - 15 VM saved correctly, I started to get this error on one VM:

Backing up file "[LUN_VM_3] lnx-glpi/lnx-glpi.vmdk" BackupText failed Client error: Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.

The next 2 VM gave me this error:

Backing up file "[LUN_VM_2] SRV-DC2/SRV-DC2-aux.xml" BackupFile failed Client error: All instances of the storage metadata are corrupted. Cannot backup file in the service console mode. File: [nfc://conn:srv-vcenter2,nfchost:host-97,stg:datastore-59@SRV-DC2/SRV-DC2-aux.xml]. VBK: [veeamfs:6:3bd79151-740a-4ca8-9bc1-e8ca5f3b773b (vm-111)\SRV-DC2-aux.xml@D:\IST\BACKUPS\VM\Backup SCI.vbk]. RBK: [veeamfs:6:3bd79151-740a-4ca8-9bc1-e8ca5f3b773b (vm-111)\SRV-DC2-aux.xml@D:\IST\BACKUPS\VM\Backup SCI2010-07-12T170048.vrb]. Server error: End of file

Backing up file "[LUN_VM_1] SRV-AUTOVUE3D/SRV-AUTOVUE3D.vmx" BackupText failed Client error: All instances of the storage metadata are corrupted. Failed to backup text locally. Backup: [veeamfs:6:3bd79151-740a-4ca8-9bc1-e8ca5f3b773b (vm-117)\SRV-AUTOVUE3D.vmx@D:\IST\BACKUPS\VM\Backup SCI.vbkVBK: 'veeamfs:6:3bd79151-740a-4ca8-9bc1-e8ca5f3b773b (vm-117)\SRV-AUTOVUE3D.vmx@D:\IST\BACKUPS\VM\Backup SCI.vbk'RBK: 'veeamfs:6:3bd79151-740a-4ca8-9bc1-e8ca5f3b773b (vm-117)\SRV-AUTOVUE3D.vmx@D:\IST\BACKUPS\VM\Backup SCI2010-07-12T170048.vrb']. Server error: End of file

Then all subsequent VM gave me this error:

Initializing target session Backup file "D:\IST\BACKUPS\VM\Backup SCI.vbk" is corrupted. Perform full backup by selecting "Full Backup" option from job's shortcut menu. CheckStorage failed Client error: All instances of the storage metadata are corrupted.

May I have a problem with the storage where I'm saving VBK? I have many customers with Veeam Backup but I never saw this error

Thanks,

Marco

[m.novelli]

I have checked the storage where Veeam Backups are saved and is OK, both at physical level and logical level (NTFS)

Now I'm running a full backup

At this customer I have only one Veeam backup job and the associated VBK is about 1.1 TB, maybe it's too big?

Should I configure two or three backup jobs?

Marco

[Vitaliy S.]

Hi Marco,

You may want to split the backup job by grouping VMs based on their OS, purpose etc, if it still fits your backup window. But having all VMs grouped together would also work.

And I'd recommend you to send us all the log files to see what was the exact reason for the corruption, so you could avoid such situations in the future.

Thanks!