Backup Repair utility

Hi ​@Nikks,

In general (not depending on specific jobs types) Veeam has mechanisms like health check and Sure Backup to check the recoverability of backups.

In case that there’s a corruption it is not always possible to restore this since source data can be missing and if this is the case a backup file (or a chain) cannot be repaired. Veeam cannot “guess” the source data.

As ​@Andanet mentioned there are ways but please do not try to modify the files on a Windows Explorer level.

Best

Lukas

Thanks Andanet. Just want to check all these tools are only diagnostic one and not repair utilities. For repair we need to check with support , correct?

Error is :Error: An unexpected network error occurred.
Failed to flush file buffers. File:   .vbk

To repair your files, it depends on what happened, but you should open a case with Veeam for further assistance. However, you can use Veeam Validator to check if the file is corrupted by running the following command:

 %ProgramFiles%\Veeam\Backup and Replication\Backup\Veeam.Backup.Validator.exe\[/vmname:vmname][/file:path][/point:pointid][/date:pointdate]

For more information, you can refer to the user guide at this link.

The error log suggests a network issue. Is the repository you are using local, on the VBR server, or located on another server or network? It seems that Veeam cannot find the .vbk file to continue creating a restore point in the backup chain.

If possible, share your structure with us so we can better understand your scenario.

You’re welcome ​@Nikks 

I never wrote support can repair your backup file but only it can verify. 

As per your last phrase 

An unexpected network error occurred.
Failed to flush file buffers. File:   .vbk

consider network errors are usually communication issues but I'm pretty sure your backup chain is corrupt. You can try running an active full and see if it completes.

In my opinion, the support response would be the same. Run an active full. 

I agree with Antonio. Until support evaluates your case, try running an active full backup to create a new chain and resolve potential issues with corrupted files.

By the way, do you have other jobs using the same repository, or is this the only job showing errors? I'm asking to confirm whether it's a file corruption issue.

Don't forget to open a support case. When dealing with file issues, it's best to rely on support, as it might involve a binary file, and they can assist you. Avoid making changes yourself, as it could worsen the problem.

​@Nikks  - were you able to get an answer to your question?  Please update the thread so we can select the best answer for the post to close out the question.  If not answered please continue the discussion.