Saving views from the replaced replica

When you replace a replica, you can still save the views that were used in that replica.

About this task

Procedure

  1. Move all view-private files into the view's lost+found directory (replica-uuid is boston_hub's UUID): 
    cleartool recoverview –vob replica-uuid –tag view-tag
  2. List view-private files in each of the views: 
    cleartool lsprivate –tag view-tag –invob vob-selector
  3. Use the uncheckout command to cancel all checkouts in the replica to be replaced; use the –keep option to save copies of the files.
  4. Copy the .keep files to temporary directories outside the view. You can refer to these files when the new replica is available and you have checked out the elements again.
  5. Use the rmdo command to remove all derived objects associated with the VOB to be replaced.
  6. Remove all .cmake.state files.
  7. Decide whether any valuable information is in any of the other view-private files associated with the VOB to be replaced.
  8. After the replacement replica is back online, complete these additional steps:
    1. Rebuild all derived objects.
    2. Reconcile view-private files.

      Because view-private files are associated with a particular replica, restoration from backup makes them inaccessible. To continue work on checkouts, you must identify all checkouts, capture the related files, and place them in the correct location.

      You can do this by implementing a view backup procedure for files that cannot be re-created easily. For example, write a script that uses the lsprivate command to find all view-private objects (except for derived objects) and back them up to a backup tree. If the structure of this tree mirrors the VOB structure, it is easier to put the files back in their correct locations.

    3. Run the recoverview command to free space associated with view-private files for the replica you removed.

      An alternative method is based on recoverview. After letting recoverview move private files to the view's lost+found directory, the moved files are captured and placed into a location appropriate for the new replica. The main problem with this method is that the file names recoverview generates are leaf names; any directory structure is lost.

    4. Redo changes to pool assignments.

      Pool assignments are local to a replica, so re-creating the original replica may undo changes made to them. Major changes to pool structure must be duplicated manually at the backup replica.