unarchive

restore version container files that were previously archived

Usage

accurev unarchive [ -E <element-type(s)> ] [ -i ]
[ -s <stream> ] [ -t <transaction-range> ]
[ -R ] { [ -Fx ] -l <list-file> | <element-list> }
accurev unarchive -a { [ -Fx ] -l <list-file> | <element-list> }

Description

The unarchive command restores to a depot’s file storage area one or more version container files that were previously archived. The container files shift from archived status to normal status. The container files are moved from the depot’s gateway area back to their original locations in the depot’s file storage area.

You can use this command in either of these ways:;

  • To restore the versions that were archived by one particular invocation of archive, use command-line options that match the options specified in the original archive command. (But don’t include any comment specified in the original command with -c.) For example:

    • command to archive versions:
    • accurev archive -R -t 34591 -c "all deliverable files" binaries
    • command to restore archived versions:
    • accurev unarchive -R -t 34591 binaries
  • To restore all archived versions of a particular set of elements, use the -a option. For example:
  • accurev unarchive -a -l archived_elements.2007_03_14

Options

-i

List the versions that would be unarchived (in XML format), but do not actually unarchive them.

-E <element-type(s)>

Restrict the unarchive operation to elements of one or more element-types: text, binary, and/or ptext. To specify multiple types, use a comma-separated list (default: all specifies all element types). Examples:

 -E ptext,binary
-E "text, ptext"

-s <stream>

Restrict the unarchive operation to versions in the specified stream (or snapshot, or workspace). Default: unarchive versions in the current workspace stream.

If you use this option, you must identify the elements to be processed using depot-relative pathnames.

-t <transaction>[ .<count> ]

The first form specifies one transaction, or a specified number of transactions up to (i.e. preceding) and including a particular transaction, for example: 23695 or now.5.

The second form specifies a range of transactions; the optional suffix truncates the listing after the

most recent <count> transactions. You may need to use quotes in composing the argument following -t; the entire argument must be interpreted by the command shell as a single token. You cannot use the now or highest keyword in the interval specification.

For the unarchive command, a transaction can be represented in the following ways:

• Time keyword: now

• Transaction number as a positive integer: e.g. 146 or 23965

• Transaction number keyword: highest

-t <transaction> - <transaction>[ .<count> ]

The first form specifies one transaction, or a specified number of transactions up to (i.e. preceding) and including a particular transaction, for example: 23695 or now.5.

The second form specifies a range of transactions; the optional suffix truncates the listing after the most recent <count> transactions. You may need to use quotes in composing the argument following -t; the entire argument must be interpreted by the command shell as a single token. You cannot use the now or highest keyword in the interval specification.

For the unarchive command, a transaction can be represented in the following ways:

  • Time keyword: now
  • Transaction number as a positive integer: e.g. 146 or 23965
  • Transaction number keyword: highest

-R

Recurse into each directory specified in <element-list> or <list-file>.

-Fx

Signals that <list-file> (see the -l option) is an XML-format file, not a flat text file. Example:

 <elements>
    <element location="\.\dir07\sub01\file01.txt"/>
    <element location="\.\dir07\sub01\file02.txt"/>
    <element location="\.\dir07\sub01\file14.txt"/>
</elements>

The -Fx option must precede the -l option on the command line.

-l <list-file>

Process the elements listed in <list-file>. This must be a text file, with one element name per line. Extra whitespace is not allowed; make sure there are no empty lines and no leading or trailing white space around the filenames. Wildcards are not expanded. There is no provision for comment lines in the file.

If you use this option, any <element-list> specified is silently ignored.

<element-list>

One or more element names, separated by whitespace. If you also specify a <list-file> using the –l option, this <element-list> is silently ignored.

See Also

archive, reclaim

Techniques for Selecting Elements

Archiving of Version Container Files in the AccuRev Admin Guide.