"Full backup file merge failed Error: CRC Error code: 23 Failed to read data from the file [\\server\share$\folder\Backup Job mlabbe\Backup Job mlabbe2015-12-29T003418.vib]."
I can't say I'd sleep well if I had important data to backup on a daily basis and it was my only backup solution.
the merge thing ended up corrupting a backup file that was perfectly fine before
While it wasn't a big issue to me (I renamed the backup folder and started over, it's been running fine since)
We got several cases in QA department when check disk did not properly report disk corruption. Try any third party tool to be sure.
We have pretty decent blog post - How to follow the 3-2-1 backup rule with Veeam Backup & Replication.
Strange because there is a built-in health check – which basically confirms that existing chain is restorable before creating a new incremental backup or performing merge.
A bit sad that you did not open a support case since then we could analyze the VEB logs and get better understanding on what actually has happened.
health check did find the existing chain was restorable before performing merge, but it didn't check after the merge completed
Do you have any third party to recommend?
the blog doesn't make it clear that keeping an offline backup is also important
the message returned by the website is confusing
Dima P. wrote:We can’t find the logs you are referring to in the case.
Dima P. wrote:QA team wanted to check if you could start a File Level Recovery from the restore point in the backup chain that seems to be corrupted?
Dima P. wrote:We’ve identified the issue you faced [...] We will add additional logic to handle such issues in the upcoming update – so thanks again for all your help in investigation!
Users browsing this forum: No registered users and 14 guests