The command accurev archive processes one or more versions of file elements, shifting the versions’ container files from
normal status to
archived status. The command has this format:
archive determines the set of versions to archive as follows:
If you don’t use the –a or
–I option,
archive refuses to archive any version that is currently visible in any stream or snapshot. Specified versions that are already archived are silently ignored.
Using the –i option (in addition to the other options described above) generates an XML-format listing of the desired versions, but does not perform any actual archiving work. It is highly recommended that you do this “dry run” before actually archiving any versions, to avoid any surprises.
After determining which versions to process, the archive command moves a version’s container file from a “normal” location under the
data directory:
archive also marks the version as “archived” in the database.
Subsequent attempts by AccuRev commands to retrieve the contents of the archived version will fail.
The changes made by this command are recorded in the database as a transaction of type archive. You can use the
–c option to specify a comment string to be stored in this transaction. You can search for particular comment strings when using the
hist command to locate previous
archive transactions. See
Using ‘hist’ to Research Previous ‘archive’ Commands on page 42.