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.
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.
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: