Synchronizing VOBs and views after you restore

When a VOB is restored from backup, it might be out of sync with any view that holds a reference to it (a checked-out or loaded version from the VOB, for example). When a view is restored from backup, it mightbe similarly out of sync with any of the VOBs to which it holds a reference. This skew can cause a variety of problems, primarily in views, but also in VOBs.

• Problems in the view. Whenever a view is restored or a VOB referenced by a view is restored, any of the following problems can occur in the view:
  • View-private files and directories can become stranded because the VOB directory element that they were cataloged in no longer exists in the VOB.
  • Elements can become checked out but removed when the VOB has recorded that the view has the element checked out, but the view does not have a view-private file for the element.
  • Elements can become eclipsed by a view-private file when the checkout that was once valid in the view is no longer recognized in the VOB.
  • DO promotions can fail because the VOB records information about unshared DOs that do not exist.
  • Winked-in DOs become inaccessible when the VOB no longer contains the shared DOs. This can occur if the VOB loses its DO pools and the shared DOs are removed by checkvob fix processing.
• Problems in the VOB. Whenever a dynamic view is restored, DOs in VOBs referenced by the view might not be scrubbed because they have out-of-date reference counts (the restored view no longer holds the references to the DO that are recorded in the VOB).