perform operations on a replica repository


accurev replica sync
accurev replica -t <transaction-range> [ -i ] [ -fx ] [ -p <depot-name>


replica sync

The replica sync command brings your local replica repository up to date with respect to the master repository.

During the course of development, your local replica repository typically becomes out-of-date with respect to the master repository. This occurs when other users send commands to other replica servers or directly to the master server. In both such cases, new transactions are entered in the master repository, but are not entered in the your local replica repository.

At any time, you can enter a replica sync command to bring your local replica repository up to date. This transfers data from the master repository site slice to the replica repository site slice. It also transfers database transactions from the master repository to the replica repository — but only for the depots that are included in the local replica. The replica sync command does not transfer the corresponding storage files for keep transactions.

A replica sync command is performed automatically on the local replica after each operation that is initiated by a client of the local replica, and that makes a change to the repository.

Note: You never need to synchronize directly with other replicas; synchronizing with the master is sufficient to bring your replica up to date.

replica archive

The replica archive command is used to remove unused container files from a depot’s storage directory on a replica server. This command activates the server_preop_trig trigger on the replica with a replica_archive command.

The command output lists each element for which the storage container was removed, for example:

Removing storage for element /file1.txt (2/5)
Removing storage for element /file1.txt (2/6)


These options apply to the replica archive command only.

-t <transaction-range>

Specifies a transaction range to the replica archive command. The command looks for archive transactions in the range and physically removes the container files of all the versions on the replica associated with those transactions. Transactions can be specified in the following ways:

  • Time in <YYYY/MM/DD HH:MM:SS> format: e.g. 2007/08/07 20:27:15.
    Note that you might need to use quotes in composing the argument following -t; the entire argument must be interpreted by the command shell as a single token.
  • Time keyword: now
  • Transaction number as a positive integer: e.g. 146 or 23965
  • Transaction number keyword: highest


Lists the versions that would be archived (in XML format), but does not actually archive them.


Display the results in XML format.

-p <depot-name>

Specifies the depot to use; defaulting to the depot of the current workspace. If this option is not specified, you must be in a workspace.

See Also

archive, mkreplica, rmreplica

Replication of the AccuRev Repository in the AccuRev Admin Guide