This error can be caused by a hardware, file system, or operating system failure that causes Disk Safe file corruption. Drive viability, in particular, depends on the stability of the underlying hardware and operating system of the host storage device.
The safest solution is to create a new Disk Safe as soon as Server Backup reports that the database disk image is corrupt. In some situations, Disk Safe can still be used to restore recovery points that were created before Disk Safe reported corruption. However, we cannot determine the degree of corruption, or if the workaround mentioned below can restore Disk Safe. In addition, we do not expect damaged Disk Safe to be successful in recovering pure metal.
You can try to restore Disk Safe by running the Disk Safe Verification (DSV) task (introduced in Server Backup v5.2.0) against Disk Safe with a distorted image. DSV will check the latest recovery point to ensure that all blocks are accounted for. If the secure drive is not checked, during the next replication task, a recovery attempt will be made that will attempt to reconcile any missing blocks from the recovery point.
Ataboy josef
source share