How the system handles damaged objects during a save operation

 

How the system handles damaged objects during a save operation explains how the system handles damaged objects. This information also provides you with important information on error messages that you may see during a save operation.

When the system encounters a damaged object during a save operation, it does one of several things based on when it detected the damage.

 

Object that the system marked as damaged before the save operation

The system does not save an object that it marked as damaged, but the save operation continues with the next object. The operation completes with an indication of how many objects the system saved and how many it did not save. Diagnostic messages describe the reason that the system did not save each object.

 

Object that the save operation detects as damaged

The system marks the object as damaged, and the save operation ends. The save operation ends because the save media may contain part of the damaged object. If the media contains a damaged object, the save media cannot be used for restore operations. The system sends diagnostic messages.

 

Object that the system does not detect as damaged

In some unusual cases, a save operation does not detect a damaged object. The save operation may detect physical damage on the disk, but it may not detect all damage. For example, the system does not attempt to determine if all bytes within an object are valid and consistent (logical damage). For some cases, you will not be able to determine a damage condition unless you attempt to use the object (such as calling a program object). If this type of damage exists, the system restores the object normally.

 

Parent topic:

Before you save anything...