May 3, 2023

Veeam agent backups check if bad blocks are listed in the $BadClus metadata file on the NTFS file system. The One or more bad blocks were detected and skipped and skipped in the source disk error message means that there were bad blocks found. You can try to scan for and fix these bad blocks by running the following command. Replace C: with the affected drive letter. If during the above command you see errors about open files, you can run the following command. Keep in mind that this may disconnect any drives in use so ensure that there are no active tasks using the drives before running. If you continue to see these issues it may be time to replace your drives. You may want to backup and restore the drives to new disks. In that scenario, the $BadClus metadata may also be restored which can cause these error messages to continue, even though the drives have been replaced. You may need to run chkdsk again using the /B flag for all of the partitions. That will clear the $BadClus file and rescan all of the clusters. Example: Then also to run it on the recovery partition:

The restore point is corrupted error can be caused if the replication is set to use a backup as it’s source. If the source backup is running it marks the backup files as incomplete which can cause the replication job to see the files as corrupted. Once the job is completed the restore point is changed to a “valid” state. There are typically a few different ways to fix these errors: *In both of these scenarios it may also be beneficial to set the backups window of the source backup job to disable it from running during the time the replication job is scheduled.