Skip to main content
  • EN

I have been going through Google the last few days trying to find an answer to my issue, but so far I have not found the answer that works.  I am getting this error message when I try to run a backup on my one and only community edition that we do not pay for support for. 

 Failed to perform backup file verification Error: Data error (cyclic redundancy check).
Asynchronous request operation has failed. dreadsize = 524288] 8offset = 4763648]
Agent failed to process method {Signature.FullRecheckBackup}.

This is backing up a Cantos SMB server and Every post I have seen says to check for bad sectors, but the checks come back as “OK”.  How else can I check for corrupt data?  what other options do I have to try to remedy this?  Any tips on where to look next are greatly appreciated.
  
 

Hi @jestepp welcome to the Community Forums.

Have you tried the Veeam Backup Validator? - https://helpcenter.veeam.com/docs/backup/vsphere/backup_validator_validate.html?ver=120

Additionally, have you tried to run a full Active Backup?

Finally, have a look at the logs under %ProgramData%\Veeam\Backup and look for the job name. 

 

Also check the disk offset as mentioned in the error.  There is another post on here (I cannot find it at the moment) that talks about this and how to increase this to ensure it aligns.  I think this is part of the issue you are having to rectify this.

Hi Mr. Jestepp

As the error says, you have a corrupted backup in your backup chain on the performance tier. It has nothing to do with the server you are backing up. 

On your performance tier look for the folder where the backup are located. Rename the folder to something similar  e.g bkj_cantos_smb to bkj_cantos_smb_save.

Create the folder for bkj_cantos_smb again and copy the file bkj_cantos_smb.vbm form the folder bkj_cantos_smb_save to the folder  bkj_canos_smb. Then you should run a full backup as Mr Dips explains above. 

Also the capacity tier should be fine after this operation. Later on you may remove the save folder. 

This is an issue only seen in Veeam 12. 

 

Regards.

 

 

 

Comment


Terms & Conditions