How To Clean Up Old Veeam Vbk And Vib Files

This article will explain How to fix Cleaved backup chain in Veeam Backup & Replication.

A Cleaved Backup Chain is when y'all have full Backup(.vbk), and several (can be ii or more) incremental (.vib) that were deleted or corrupted. Mainly if you are not using "Reverse Incremental." Increments ever injected in the last backup to create a full fill-in. With this option is more than difficult to accept a Broken Backup Chain.

Examples:

Note: "Reverse Incremental" is e'er a slow backup compared with "Incremental." Since last fill-in will e'er exist a total backup and all incremental will be injected in the last backup.

In this case that nosotros volition discuss in this article is when nosotros try to restore a VM with a Backup that has a broken chain we go an error: "Fill-in files are unavailable."

• Restore

Just check the restore points and restore.

As we tin check in the adjacent image, this particularly VM had four restore points. Then we choose one to restore the VM.

When we attempt to restore the VM, we get a Backup with a broken chain, and we become an error: "Fill-in files are unavailable."

Even nosotros get this error, the VM restore continue and and so stop with the next image.

As we can check in the final line in the log, the incremental .vib file doesn't exist.

The VM was created in the vCenter, but nosotros cannot power on, and there is no Virtual Deejay.

So somehow this .vib file disappear from the Repository. This can only happen if there are any bug with your Storage Repository, or you put i Repository Offline in maintenance mode, and some files will be unavailable, or someone deleted the files manually in a incorrect sequence (In this example, I bet on this one).

Even if yous choose a different restore point or even the full restore point we go the aforementioned error. Since the concatenation in this backup is cleaved, so cannot restore the VM.

Next is to check the Backup Repository and check if there is any restore points are not in the chain and if nosotros have a Broken Chain Backup, fix it.

• Check Backup Repository.
• Go to Backups , then Deejay  and select the Job that yous are trying to restore.
• Right click and select Properties .

Every bit we tin can check in the next prototype lot of Incremental restore points are not bachelor. The only is available is the Full Backup.

Investigating the Backup Chain(full backup and its incremental) is official that we accept a Broken Backup Chain and needs to be fixed.

Note: Double check other VMs to confirm that all have the same problem.

• Fix Backup Chain

Now to set up this Broken Backup Chain we demand to select one of the cleaved/miss files and choose to Forget or to Delete to miss incremental files.

• Forget — you can remove records about missing restore points from the configuration database. Veeam Backup & Replication will "forget" about these restore points and will not display them in the console. The fill-in files volition remain on disk.
• Delete —  y'all can remove records about missing restore points from the configuration database and delete fill-in files from disk.

For the Forget and Delete options there also an choice to perform this task merely in the select Job/Restore Betoken, or do for all.

• To remove only the selected restore point and restore points that depend on it (that is, a part of the backup concatenation starting from this restore point), select This and dependent backups.
• To remove all restore points from the unavailable extent, select All unavailable backups.

For this item instance, I choose to selection Forget and with the select All unavailable backups .

Just confirm and let Veeam remove all corrupted restore points and fix the Backup Concatenation.

Notation: Depending on your system and the size of your backups, this procedure can take a while.

Afterwards Veeam remove all corrupted files, the only restore indicate that was available was the initial Full Fill-in. So information technology ways that all incremental were decadent, or files were delete (for instance 2 and 3 from our initial Incremental epitome).

Every bit we can check in the side by side paradigm, all VMs have only 1 restore indicate available.

Note: It could even happen if you lot accept new VMs that were backup in those corrupted incremental will no longer exist available(we had xx VMs with this). So, no backups for those VMs.

Subsequently you fix the Broken Backup Concatenation, we can now restore any VM (using the bachelor restore points).

Hope this helps y'all to fix your Broken Backup Concatenation in Veeam Fill-in & Replication.

Annotation: Share this article, if yous think information technology is worth sharing.

Almost done…

We merely sent yous an email. Please click the link in the email to ostend your subscription!

OKSubscriptions powered by Strikingly

How To Clean Up Old Veeam Vbk And Vib Files,

Source: https://www.omarrao.com/blog/how-to-fix-broken-backup-chain

Posted by: abellhableartur.blogspot.com

Share this post