

A hardware or O/S fault causing incorrect data to be written to Disk Safe files.



If Disk Safe is corrupted by any one of the events below, it can not be repaired: If your Disk Safe becomes corrupted, you may lose all or some of your archived data. If any of the following events occur, you may corrupt your Disk Safe. Even with industrial grade protection, there are still ways for your data to become lost or damaged beyond repair. The Disk Safe is highly reliable and robust. Please make sure your hardware and Operating System follow the recommendations in our Disk Safe Best PracticesĪdditional Information - Corruption of Data Archived in the Disk Safe.In this case, we recommend that you create a new Disk Safe and also check the disks that host the Disk Safe and also review the operating system logs for failures related to I/O, disk space or file system. If DSV does not find any errors with the recovery point, the problem may have originated outside of the disk safe.DSV does not verify recovery points with a locked or incomplete status. Please note that DSV verifies only those recovery points with an available status. If the disk safe fails to verify, a repair attempt will be made during the next replication task which will attempt to reconcile any missing blocks from the recovery point.įor more information on DSV, please review our documentation: Wiki Article The DSV will check the most recent recovery point to ensure all blocks are accounted for. You may attempt to repair the Disk Safe by running a Disk Safe Verification (DSV) task (introduced in Server Backup v5.2.0) against the Disk Safe with the malformed image. In addition, we do not expect that a corrupt Disk Safe will be successful in a bare metal restore. However, we have no way to determine the extent of the corruption or if the workaround mentioned below will be able to repair the Disk Safe. In some situations, the Disk Safe may still be usable for restoring recovery points that were created before the Disk Safe reported a corruption. The safest solution is to create a new Disk Safe as soon as Server Backup reports that the database disk image is malformed. Disk Safe viability, in part, relies on the stability of the underlying hardware and Operating System of the host storage device. This error may be caused by a hardware, file system or Operating System fault causing corruption to the Disk Safe file. "Error Server reset(): database disk image is malformed(11)"
