Not backed up successfully or restore chain is corrupted

[BCT-Tech]

Did a Google search for this error, but came up with nothing. Getting this error from 2 different VMs.

Code: Select all

Error: Item [4AD6C300] either was not backed up successfully or restore chain is corrupted. Failed to download disk. Reconnectable protocol device was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. 

Tried a Server reboot, and also a uninstall / re-install of VEB. Other VEB backups are succeeding fine.

Any ideas?

[Mike Resseler]

This looks more like an issue with your backup chain than the need to uninstall / re-install. Just for clarification... You have multiple backups for that server? And when are you getting this error? During backup or during a restore?

Thanks

Mike

[BCT-Tech]

This looks more like an issue with your backup chain than the need to uninstall / re-install. Just for clarification... You have multiple backups for that server? And when are you getting this error? During backup or during a restore?

Just took a look at VBR Console - we have 14 backups for that Server (job is set to 14) but the last successful one was 15 days ago. Getting the error during backup, as reported in the email notification.

[Mike Resseler]

Can you log a support call through the VEB UI for that server? You still should have 14 days of valid recovery points (the 14 in the retention is not days, but amount of days you have a SUCCESFULL backup).
If you have done this, please come back here with the support case ID and the outcome of the support call. We do provide support on this free solution, but it comes without SLA, but we will certainly come back to you, depending on support availability

Cheers
Mike

[BCT-Tech]

Took a while for the Control Panel to recognize my email, but done. Support case number is 01929662.

[Mike Resseler]

Thanks! PS: This registration piece only needs to be done once... But we need to do this to arm ourselves against bots

[BCT-Tech]

Got a resolution to this:

I would like to see if clearing the SQL database will help get this backup running again for you. Here are the steps to set this up.

Step 1 - Open up RegEdit
Step 2 - Look for HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Step 3 - Look for the DWORD value called ReCreateDatabase and assign to it 1 (decimal) Step 4 - Close regedit, open up the services.msc console, and re-start the Veeam Endpoint Backup service manually or just reboot the machine.

Please note that after performing these steps, it will be required to reconfigure the Endpoint backup. Also too, this will create a brand new backup chain. The previous chain may still be used for restoration purposes. But otherwise, can be discarded.

That seems to have worked. Since this was happening to other VMs, and these VMs are not yet in production, I did some other testing to try and troubleshoot the issue:

In Veeam B&R Console, I went to Backup & Replication, Backups, Disk and right-clicked on the VM and chose "Remove from configuration". I ran another backup and this time it was successful.

I think what caused this, is we disabled the backups from Veeam B&R Console for about 2 weeks. Maybe you guys can look into if people do this, that the backups can still complete successfully without having to delete the old restore points?

[Mike Resseler]

Awesome news that it is fixed! Good to hear. (You got to love our Support team... )

And thanks for coming back to us, this might certainly benefit some other users!

Have a great weekend

M/

[Vitaliy S.]

I think what caused this, is we disabled the backups from Veeam B&R Console for about 2 weeks. Maybe you guys can look into if people do this, that the backups can still complete successfully without having to delete the old restore points?

Disabled or not running backup jobs cannot cause this behavior, as, for example, you can schedule to your backup job once a month and this will not interrupt your backup job chain.