
Note: Double-check other VMs to confirm that all have the same problem. Upon investigating the Backup Chain(full backup and its incremental) is official that you have a Broken Backup Chain and needs to be fixed. Go to Backups, then Disk, and select the Job that you are trying to restore.Īs you can check in the next image lot of Incremental restore points are not available.Next is to check the Backup Repository and check if any restore points are not in the chain and if you have a Broken Chain Backup, fix it. Since the chain in this backup is broken, so cannot restore the VM. This can only happen if there are issues with your Storage Repository, or you put one Repository Offline in maintenance mode, and some files will be unavailable, or someone deleted the files manually in the wrong sequence.Įven if you choose a different restore point or even the full restore point, you get the same error. The VM was created in the vCenter, but you cannot power it on, and there is no Virtual Disk. When checking the last line in the restore log, the incremental. When you try to restore the VM, you get a backup with a broken chain and get the error: “Backup files are unavailable.”Įven when you get this error, the VM restore continues and finishes with the next image. You can now choose one of the restore points to restore the VM. I will discuss in this article when you try to restore a VM with a Backup that has a broken chain, you get an error: “Backup files are unavailable.”Īs you can see in the next screenshot, this VM had four restore points. Note: “Reverse Incremental” is always a slow backup compared with “Incremental.” Since the last backup will always be a full backup and all incremental will be injected in the last backup.

With this option is more difficult to have a Broken Backup Chain.



Mainly if you are not using “Reverse Incremental.” Increments are always injected in the last backup to create a full backup. This article will explain How to fix Broken backup chain in Veeam Backup & Replication.Ī Broken Backup Chain is when you have a full Backup(.vbk) and several (can be 2 or more) incremental(.vib) that were deleted or corrupted.
