- Service Provider
- Posts: 39
- Liked: 5 times
- Joined: Feb 09, 2019 5:06 pm
Current behaviour I am seeing - After BCJ starts, it silently starts health check, but it looks like only on the target repository/SP side, after that check is complete, it proceeds to copy data and finish the job, after finishing the job, there is no health check done, which is a little weird considering that data could be damaged as they landed on the repo.
Also, why is there no visual representation of running health check?
- Product Manager
- Posts: 7603
- Liked: 1978 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
Yes, Health Check for Backup Copy Jobs works differently from Backup Jobs.
When you do a backup, first we want to have the backup as scheduled. Waiting for a copy job to be finished would make the backup schedule unreliable. So the backup job starts immediately. With copy job we have more time. We first check if the latest restore point is not corrupt. If corruption is detected, we can use the copy job to copy the new backup and to replace the corrupted blocks in the copy location.
Backup Job --> User Guide
Backup Copy Job --> Backup Copy Job
In V10/V11 you can configure your copy jobs todo a daily health check. This would allow to check for file corruption once per day before the new restore point gets copied.
In our upcoming release V12, Health Checks have their own schedule and are not done within the backup/backup copy job session. You can schedule them after your copy jobs are normally finished. Health Checks will be shown as their own session in your Veeam console (Last 24 hours / History).
Users browsing this forum: Bing [Bot] and 71 guests