restorereplica

Locking the replica

restorereplica locks the current replica's VOB object. Locking it ensures that while restoration proceeds through execution of syncreplica–exportand syncreplica –import commands, no other changes are made to the current replica.

When syncreplica applies the final required update, it displays a message indicating that the restoration process is complete. At this point, use the cleartool unlock vob: command to unlock the restored VOB replica, enabling normal development to proceed.

Optimizing the restoration process

By default, restorereplica requires that the replica receive restoration updates from all other replicas in its family (either directly or indirectly). Only after all the updates are imported does the syncreplica command display the message indicating that restoration is complete.

In some cases, you can relax this requirement without compromising the correctness of the restoration process. The replica will be brought up to date if it receives a restoration update from only one replica, the last one to which the replica sent an update before it was restored from the backup version. You can specify the name of that last-updated replica (or a list of replicas, one of which must be the last-updated one) to restorereplica. The syncreplica command displays the restoration-completed message after receiving restoration updates from all the specified replicas.

Event records and comments

Default

Creates one or more event records, with commenting controlled by the standard ClearCase user profile (default: –cq). See Event records and comments in the multitool reference page. To edit a comment, use cleartool chevent.

–c/omment comment-string | –cfi/le comment-file-pname | –cq/uery | –cqe/ach | –nc/omment

Overrides the default with the specified comment option.

Suppressing interactive prompts

Default

restorereplica prompts you for confirmation.

–f/orce

Suppresses the confirmation step.

Specifying the VOB family

Default

Processes the replica that contains the current working directory.

–invob vob-selector

Processes the current replica in the specified family. Specify vob-selector in the form [vob:]pname-in-vob

pname-in-vob

Pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted)

Reducing the number of required updates

Default

The syncreplica command declares the replica to be restored completely only after updates are received from all other members of the VOB family and imported.

Warning: Incorrect use of these options allows new changes to be made to the replica before all missing changes are received from other replicas. This may place the entire family in an irreparably inconsistent state.

replica-selector ...

Specifies a subset of replicas from which updates are required before syncreplica declares the replica to be restored completely. Specify replica-selector in the form [replica:]replica-name[@vob-selector]

replica-name

Name of the replica (displayed with lsreplica)

vob-selector

VOB family of the replica; can be omitted if the current working directory is within the VOB.

Specify vob-selector in the form [vob:]pname-in-vob

pname-in-vob

Pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted)

–rep/lace replica-selector ...

Changes the subset of replicas from which restoration updates are required.

–override

Overrides normal restoration processing and declares the VOB to be restored completely. The lsreplica –long command no longer annotates any replicas as needing to provide updates, and you can use cleartool unlock vob: to place the replica back in normal service.

When you specify this option, the command displays a list of replicas from which updates have not been received and prompts you to cancel the operation or continue.