Version 3 by Derek Wood
on Jul 10, 2013 09:37.

compared with
Version 4 by Randy Bowie
on Jun 25, 2018 09:53.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (7)

View Page History
h3. Resolution

The safest solution is to create a new Disk Safe as soon as Server Backup reports that the database disk image is malformed. In some situations, the Disk Safe may still be usable for restoring recovery points that were created before the Disk Safe reported a corruption. 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 addition, we do not expect that a corrupt Disk Safe will be successful in a bare metal restore.

h5. Workaround
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. The DSV will check the most recent recovery point to ensure all blocks are accounted for. 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.

{info:title=Note}For more information on DSV, please review our documentation: [http://wiki.r1soft.com/display/ServerBackup/Scheduling+Disk+Safe+Verification]
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. The DSV will check the most recent recovery point to ensure all blocks are accounted for. 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.

{info:title=Note}For more information on DSV, please review our documentation: [Wiki Article|http://wiki.r1soft.com/display/ServerBackup/Schedule+Disk+Safe+verification]

Please note that DSV verifies only those recovery points with an available status. DSV does not verify recovery points with a locked or incomplete status.
{info}

h5. Additional Suggestions

* If DSV does not find any errors with the recovery point, the problem may have originated outside of 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.


h5. Additional Information - Corruption of Data Archived in the Disk Safe

The Disk Safe is highly reliable and robust. Even with industrial grade protection, there are still ways for your data to become lost or damaged beyond repair. If any of the following events occur, you may corrupt your Disk Safe. If your Disk Safe becomes corrupted, you may lose all or some of your archived data. If Disk Safe is corrupted by any one of the events below, it can not be repaired: