Cleaning Up After Accidental Deletion of a Replica


This situation is a more catastrophic variation of the problem described in Restoring a Replica from Backup: a replica’s storage directory is lost, and there is no backup to be restored. The procedure for handling this situation is similar to that in Deleting a Replica.

Perform this procedure in the replica that masters the deleted replica. (If the replica was its own master, perform this procedure in the replica that will master the deleted replica’s objects.) It is also important that the replica know about all the objects that were mastered by the deleted replica.

  1. Transfer mastership of all the objects mastered by the deleted replica. For example, if the tokyo replica is deleted, enter this command at the sanfran_hub replica:
  2. multitool chmaster –all –obsolete_replica tokyo@/vobs/dev –long sanfran_hub 

    Caution: Incorrect use of –all –obsolete_replica can lead to irreparable inconsistencies among the replicas in a family.

  3. Remove the VOB-replica object for the deleted replica.
  4. multitool rmreplica tokyo@/vobs/dev 
  5. Send an update packet to all other replicas in the family, to inform them of the mastership changes and the replica deletion.
  6. multitool syncreplica –export ...