Backup file <filename>.vib is corrupted or unreadable.
The corrupted files are four different vibs of the chain.
However, the job is proceeding. The first run is still ongoing after the crash, but about 50% of the vms have already been successfully processed.
I am confused. If there are unrecoverable restore points in the chain, how can the job proceed and the vms be flagged as successfully processed? Will I have recoverable backups at the end?
Also if backup restore point is corrupted for some reaason, backup copy job will know that and will transfer VM data that you can use during recovery process.
Vitaliy, the server that crashed is the Veeam B&R server AND source repository. The files that are shown as corrupted or unreadable are on the target repository.
It looks like no jobs were running at the moment of crash except the backup copy jobs that were at the "verifying vmdk" phase.
So are you saying that the backup copy is recoverable if all vms process successfully? (In cases like this, it would be nice to run a surebackup against the backup copy files...)
Yes, Backup Copy is designed to auto-recover incomplete backup file chains caused by server crashes. So, just let it run and the job should fix everything automatically. Unless there is some very special crash scenario that we cannot handle (but in that case, you will get an error).
SureBackup is not required because there is periodic Health Check process that ensures that Backup Copies are bit-identical to source backups contents. Thus, if your source backup have been tested for recoverability, there is no need to test them again. Just make sure you have Health Check enabled in the advanced Backup Copy job settings.