mirror of
https://git.openafs.org/openafs.git
synced 2025-01-19 15:30:14 +00:00
478 lines
26 KiB
XML
478 lines
26 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<refentry id="backup_volsetrestore8">
|
|
<refmeta>
|
|
<refentrytitle>backup volsetrestore</refentrytitle>
|
|
<manvolnum>8</manvolnum>
|
|
</refmeta>
|
|
<refnamediv>
|
|
<refname>backup volsetrestore</refname>
|
|
<refpurpose>Restores all volumes in a volume set</refpurpose>
|
|
</refnamediv>
|
|
<refsect1>
|
|
<title>Synopsis</title>
|
|
<para><emphasis role="bold">backup volsetrestore</emphasis> [<emphasis role="bold">-name</emphasis> <<emphasis>volume set name</emphasis>>]
|
|
[<emphasis role="bold">-file</emphasis> <<emphasis>file name</emphasis>>] [<emphasis role="bold">-portoffset</emphasis> <<emphasis>TC port offset</emphasis>>+]
|
|
[<emphasis role="bold">-extension</emphasis> <<emphasis>new volume name extension</emphasis>>] [<emphasis role="bold">-n</emphasis>]
|
|
[<emphasis role="bold">-localauth</emphasis>] [<emphasis role="bold">-cell</emphasis> <<emphasis>cell name</emphasis>>] [<emphasis role="bold">-help</emphasis>]</para>
|
|
|
|
<para><emphasis role="bold">backup vols</emphasis> [<emphasis role="bold">-na</emphasis> <<emphasis>volume set name</emphasis>>] [<emphasis role="bold">-f</emphasis> <<emphasis>file name</emphasis>>]
|
|
[<emphasis role="bold">-p</emphasis> <<emphasis>TC port offset</emphasis>>+] [<emphasis role="bold">-e</emphasis> <<emphasis>new volume name extension</emphasis>>]
|
|
[<emphasis role="bold">-n</emphasis>] [<emphasis role="bold">-l</emphasis>] [<emphasis role="bold">-c</emphasis> <<emphasis>cell name</emphasis>>] [<emphasis role="bold">-h</emphasis>]</para>
|
|
|
|
</refsect1>
|
|
<refsect1>
|
|
<title>Description</title>
|
|
<para>The <emphasis role="bold">backup volsetrestore</emphasis> command restores the complete contents of a
|
|
group of read/write volumes to the file system, by restoring data from the
|
|
last full dump and all subsequent incremental dumps of each volume. It is
|
|
most useful for recovering from loss of data on multiple partitions, since
|
|
it can restore each of a defined set of volumes to a different site.</para>
|
|
|
|
<para>(If the <computeroutput>FILE YES</computeroutput> instruction appears in the
|
|
<replaceable>/usr/afs/backup/CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file associated with the specified
|
|
port offset, then the <emphasis role="bold">backup volsetrestore</emphasis> command restores data from
|
|
the backup data file listed for that port offset in the Tape Coordinator's
|
|
<replaceable>/usr/afs/backup/tapeconfig</replaceable> file, instead of from tape. For the sake of
|
|
clarity, the following text refers to tapes only, but the Backup System
|
|
handles backup data files in much the same way.)</para>
|
|
|
|
<para>If restoring one or more volumes to a single site only, it is usually more
|
|
efficient to use the <emphasis role="bold">backup volrestore</emphasis> command. If restoring all
|
|
volumes that resided on a single partition, it is usually more efficient
|
|
to use the <emphasis role="bold">backup diskrestore</emphasis> command.</para>
|
|
|
|
<para>Indicate the volumes to restore by providing either the <emphasis role="bold">-name</emphasis> argument
|
|
or the <emphasis role="bold">-file</emphasis> argument:</para>
|
|
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>The <emphasis role="bold">-name</emphasis> argument names a volume set. The Backup System restores all
|
|
volumes listed in the Volume Location Database (VLDB) that match the
|
|
server, partition, and volume name criteria defined in the volume set's
|
|
volume entries, and for which dumps are available. It restores the volumes
|
|
to their current site (machine and partition), and by default overwrites
|
|
the existing volume contents.</para>
|
|
|
|
<para>It is not required that the volume set was previously used to back up
|
|
volumes (was used as the <emphasis role="bold">-volumeset</emphasis> option to the <emphasis role="bold">backup dump</emphasis>
|
|
command). It can be defined especially to match the volumes that need to
|
|
be restored with this command, and that is usually the better
|
|
choice. Indeed, a <emphasis>temporary</emphasis> volume set, created by including the
|
|
<emphasis role="bold">-temporary</emphasis> flag to the <emphasis role="bold">backup addvolset</emphasis> command, can be especially
|
|
useful in this context. A temporary volume set is not added to the Backup
|
|
Database and exists only during the current interactive backup session,
|
|
which is suitable if the volume set is needed only to complete the single
|
|
restore operation initialized by this command.</para>
|
|
|
|
<para>The reason that a specially defined volume set is probably better is that
|
|
volume sets previously defined for use in dump operations usually match
|
|
the backup version of volumes, whereas for a restore operation it is best
|
|
to define volume entries that match the base (read/write) name. In that
|
|
case, the Backup System searches the Backup Database for the newest dump
|
|
set that includes either the read/write or the backup version of the
|
|
volume. If, in contrast, a volume entry explicitly matches the volume's
|
|
backup or read-only version, the Backup System restores dumps of that
|
|
volume version only.</para>
|
|
|
|
</listitem>
|
|
<listitem>
|
|
<para>The <emphasis role="bold">-file</emphasis> argument names a file that lists specific volumes and the
|
|
site to which to restore each. The volume name must match the name used in
|
|
Backup Database dump records rather than in the VLDB, if they differ,
|
|
because the Backup System does not look up volumes in the VLDB. The
|
|
specified site can be different than the volume's current one; in that
|
|
case, the Backup System removes the current version of the volume and
|
|
updates the volume's location information in the VLDB.</para>
|
|
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para>If all of the full and incremental dumps of all relevant volumes were not
|
|
written to a type of tape that a single Tape Coordinator can read, use the
|
|
<emphasis role="bold">-portoffset</emphasis> argument to list multiple port offset numbers in the order
|
|
in which the tapes are needed (first list the port offset for the full
|
|
dump, second the port offset for the level 1 incremental dump, and so
|
|
on). This implies that the full dumps of all relevant volumes must have
|
|
been written to a type of tape that the first Tape Coordinator can read,
|
|
the level 1 incremental dumps to a type of tape the second Tape
|
|
Coordinator can read, and so on. If dumps are on multiple incompatible
|
|
tape types, use the <emphasis role="bold">backup volrestore</emphasis> command to restore individual
|
|
volumes, or use this command after defining new volume sets that group
|
|
together volumes that were dumped to compatible tape types. For further
|
|
discussion, see the <emphasis>IBM AFS Administration Guide</emphasis>.</para>
|
|
|
|
<para>By default, the Backup System overwrites the contents of an existing
|
|
volume with the restored data. To create a new volume to house the
|
|
restored version instead, use the <emphasis role="bold">-extension</emphasis> argument. The Backup
|
|
System derives the new volume's name by adding the specified extension to
|
|
the read/write base name, and creates a new VLDB entry. The command does
|
|
not affect the existing volume in any way. However, if a volume with the
|
|
specified extension also already exists, the command overwrites it.</para>
|
|
|
|
<para>The <emphasis role="bold">-n</emphasis> flag produces a list of the volumes to be restored if the <emphasis role="bold">-n</emphasis>
|
|
flag were not included, without actually restoring any volumes. See
|
|
<link linkend="OUTPUT">OUTPUT</link> for a detailed description of the output, and suggestions on how
|
|
to combine it most effectively with the <emphasis role="bold">-file</emphasis> and <emphasis role="bold">-name</emphasis> arguments.</para>
|
|
|
|
<para>The execution time for a <emphasis role="bold">backup volsetrestore</emphasis> command depends on the
|
|
number of volumes to be restored and the amount of data in them, but it
|
|
can take hours to restore a large number of volumes. One way to reduce the
|
|
time is to run multiple instances of the command simultaneously, either
|
|
using the <emphasis role="bold">-name</emphasis> argument to specify disjoint volume sets for each
|
|
command, or the <emphasis role="bold">-file</emphasis> argument to name files that list different
|
|
volumes. This is possible if there are multiple available Tape
|
|
Coordinators that can read the required tapes. Depending on how the
|
|
volumes to be restored were dumped to tape, specifying disjoint volume
|
|
sets can also reduce the number of tape changes required.</para>
|
|
|
|
<para>The Tape Coordinator's default response to this command is to access the
|
|
first tape it needs by invoking the <computeroutput>MOUNT</computeroutput> instruction in the local
|
|
<replaceable>/usr/afs/backup/CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file, or by prompting the backup
|
|
operator to insert the tape if there is no <computeroutput>MOUNT</computeroutput> instruction. However,
|
|
if the <computeroutput>AUTOQUERY NO</computeroutput> instruction appears in the <replaceable>CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable>
|
|
file, or if the issuer of the <emphasis role="bold">butc</emphasis> command included the <emphasis role="bold">-noautoquery</emphasis>
|
|
flag, the Tape Coordinator instead expects the tape to be in the device
|
|
already. If it is not, or is the wrong tape, the Tape Coordinator invokes
|
|
the <computeroutput>MOUNT</computeroutput> instruction or prompts the operator. It also invokes the
|
|
<computeroutput>MOUNT</computeroutput> instruction or prompts for any additional tapes needed to
|
|
complete the restore operation; the backup operator must arrange to
|
|
provide them.</para>
|
|
|
|
</refsect1>
|
|
<refsect1>
|
|
<title>Options</title>
|
|
<variablelist>
|
|
<varlistentry>
|
|
<term><emphasis role="bold">-name</emphasis> <<emphasis>volume set name</emphasis>></term>
|
|
<listitem>
|
|
<para>Names a volume set to restore. The Backup System restores all of the
|
|
volumes listed in the VLDB that match the volume set's volume
|
|
entries. Provide this argument or the <emphasis role="bold">-file</emphasis> argument, but not both.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><emphasis role="bold">-file</emphasis> <<emphasis>file name</emphasis>></term>
|
|
<listitem>
|
|
<para>Specifies the full pathname of a file that lists one or more volumes and
|
|
the site (file server machine and partition) to which to restore each.
|
|
Use either this argument or the <emphasis role="bold">-name</emphasis> argument, but not both.</para>
|
|
|
|
<para>Each volume's entry must appear on its own (unbroken) line in the file,
|
|
and have the following format:</para>
|
|
|
|
<programlisting>
|
|
&lt;machine&gt; &lt;partition&gt; &lt;volume&gt; [&lt;comments&gt; ...]
|
|
|
|
</programlisting>
|
|
<para>where</para>
|
|
|
|
<variablelist>
|
|
<varlistentry>
|
|
<term><machine></term>
|
|
<listitem>
|
|
<para>Names the file server machine to which to restore the volume.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><partition></term>
|
|
<listitem>
|
|
<para>Names the partition to which to restore the volume.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><volume></term>
|
|
<listitem>
|
|
<para>Names the volume to restore. It is generally best to specify the base
|
|
(read/write) name of each volume. In this case, the Backup System searches
|
|
the Backup Database for the newest dump set that includes a dump of either
|
|
the read/write or the backup version of the volume. It restores the dumps
|
|
of that version of the volume, starting with the most recent full
|
|
dump. If, in contrast, the name explicitly includes the <computeroutput>.backup</computeroutput> or
|
|
<computeroutput>.readonly</computeroutput> extension, the Backup System restores dumps of that volume
|
|
version only.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><comments> ...</term>
|
|
<listitem>
|
|
<para>Is any other text. The Backup System ignores any text on each line that
|
|
appears after the volume name, so this field can be used for notes helpful
|
|
to the backup operator or other administrator.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
</variablelist>
|
|
<para>Do not use wildcards (for example, <computeroutput>.*</computeroutput>) in the <machine>, <partition>,
|
|
or <volume> fields. It is acceptable for multiple lines in the file to
|
|
name the same volume, but the Backup System processes only the first of
|
|
them.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><emphasis role="bold">-extension</emphasis> <<emphasis>new volume name extension</emphasis>></term>
|
|
<listitem>
|
|
<para>Creates a new volume for each volume specified by the <emphasis role="bold">-name</emphasis> or <emphasis role="bold">-file</emphasis>
|
|
argument, to house the restored data from that volume. The Backup System
|
|
derives the new volume's name by appending the specified string to the
|
|
read/write base name, and creates a new VLDB volume entry. It preserves
|
|
the contents of each existing volume. Any string other than <computeroutput>.readonly</computeroutput>
|
|
or <computeroutput>.backup</computeroutput> is acceptable, but the combination of the base name and
|
|
extension cannot exceed 22 characters in length. To use a period to
|
|
separate the extension from the name, specify it as the first character of
|
|
the string (as in <computeroutput>.rst</computeroutput>, for example).</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><emphasis role="bold">-portoffset</emphasis> <<emphasis>TC port offset</emphasis>>+</term>
|
|
<listitem>
|
|
<para>Specifies one or more port offset numbers (up to a maximum of 128), each
|
|
corresponding to a Tape Coordinator to use in the operation. If there is
|
|
more than one value, the Backup System uses the first one when restoring
|
|
the full dump of each volume, the second one when restoring the level 1
|
|
incremental dump of each volume, and so on. It uses the final value in the
|
|
list when restoring dumps at the corresponding depth in the dump hierarchy
|
|
and all dumps at lower levels.</para>
|
|
|
|
<para>Provide this argument unless the default value of 0 (zero) is appropriate
|
|
for all dumps. If <computeroutput>0</computeroutput> is just one of the values in the list, provide it
|
|
explicitly in the appropriate order.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><emphasis role="bold">-n</emphasis></term>
|
|
<listitem>
|
|
<para>Displays a list of the volumes to be restored if the flag were not
|
|
included, without actually restoring them. <link linkend="OUTPUT">OUTPUT</link> details the format of
|
|
the output. When combined with the <emphasis role="bold">-name</emphasis> argument, its output is easily
|
|
edited for use as input to the <emphasis role="bold">-file</emphasis> argument on a subsequent <emphasis role="bold">backup
|
|
volsetrestore</emphasis> command.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><emphasis role="bold">-localauth</emphasis></term>
|
|
<listitem>
|
|
<para>Constructs a server ticket using a key from the local
|
|
<replaceable>/usr/afs/etc/KeyFile</replaceable> file. The <emphasis role="bold">backup</emphasis> command interpreter presents
|
|
it to the Backup Server, Volume Server and VL Server during mutual
|
|
authentication. Do not combine this flag with the <emphasis role="bold">-cell</emphasis> argument. For
|
|
more details, see <link linkend="backup8">backup(8)</link>.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><emphasis role="bold">-cell</emphasis> <<emphasis>cell name</emphasis>></term>
|
|
<listitem>
|
|
<para>Names the cell in which to run the command. Do not combine this argument
|
|
with the <emphasis role="bold">-localauth</emphasis> flag. For more details, see <link linkend="backup8">backup(8)</link>.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><emphasis role="bold">-help</emphasis></term>
|
|
<listitem>
|
|
<para>Prints the online help for this command. All other valid options are
|
|
ignored.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
</variablelist>
|
|
</refsect1>
|
|
<refsect1>
|
|
<title>Output</title>
|
|
<para>If the <emphasis role="bold">-n</emphasis> flag is not provided, the command displays a unique task ID
|
|
number for the operation, in two places:</para>
|
|
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>In the shell window, directly following the command line.</para>
|
|
|
|
</listitem>
|
|
<listitem>
|
|
<para>In the Tape Coordinator window, if the butc process was started at debug
|
|
level 1.</para>
|
|
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para>The task ID number is not the same as the job ID number displayed by the
|
|
<emphasis role="bold">backup jobs</emphasis> command when the <emphasis role="bold">backup volsetrestore</emphasis> command is issued
|
|
in interactive mode. The Backup System does not assign either type of ID
|
|
number until the restoration process actually begins.</para>
|
|
|
|
<para>When the <emphasis role="bold">-n</emphasis> flag is included, no task ID or job ID numbers are reported
|
|
because none are assigned. Instead, the output begins with a count of the
|
|
number of volumes to be restored, followed by a line for each dump of a
|
|
volume. For each volume, the line representing the most recent full dump
|
|
appears first, and lines for any subsequent incremental dumps follow,
|
|
ordered by dump level. The lines for a given volume do not necessarily
|
|
appear all together, however.</para>
|
|
|
|
<para>The format of each line is as follows (the output is shown here on two
|
|
lines only for legibility reasons):</para>
|
|
|
|
<programlisting>
|
|
&lt;machine&gt; &lt;partition&gt; &lt;volume_dumped&gt; # as &lt;volume_restored&gt;; \
|
|
&lt;tape_name&gt; (&lt;tape_ID&gt;); pos &lt;position_number&gt;; &lt;date&gt;
|
|
|
|
</programlisting>
|
|
<para>where</para>
|
|
|
|
<variablelist>
|
|
<varlistentry>
|
|
<term><machine></term>
|
|
<listitem>
|
|
<para>Names the file server machine that currently houses the volume, as listed
|
|
in the VLDB.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><partition></term>
|
|
<listitem>
|
|
<para>Names the partition that currently houses the volume, as listed in the
|
|
VLDB.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><volume_dumped></term>
|
|
<listitem>
|
|
<para>Specifies the version (read/write or backup) of the volume that was
|
|
dumped, as listed in the Backup Database.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><volume_restored></term>
|
|
<listitem>
|
|
<para>Specifies the name under which to restore the volume. The Backup System
|
|
only restores data to read/write volumes. If the <emphasis role="bold">-extension</emphasis> argument is
|
|
included, then the specified extension appears on the name in this field
|
|
(for example, <computeroutput>user.pat.rst</computeroutput>).</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><tape_name></term>
|
|
<listitem>
|
|
<para>Names the tape containing the dump of the volume, from the Backup
|
|
Database. If the tape has a permanent name, it appears here; otherwise, it
|
|
is the AFS tape name.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><tape_ID></term>
|
|
<listitem>
|
|
<para>The tape ID of the tape containing the dump of the volume, from the Backup
|
|
Database.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><position_number></term>
|
|
<listitem>
|
|
<para>Specifies the dump's position on the tape (for example, <computeroutput>31</computeroutput> indicates
|
|
that 30 volume dumps precede the current one on the tape). If the dump was
|
|
written to a backup data file, this number is the ordinal of the 16
|
|
KB-offset at which the volume's data begins.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
<varlistentry>
|
|
<term><date></term>
|
|
<listitem>
|
|
<para>The date and time when the volume was dumped.</para>
|
|
|
|
</listitem>
|
|
</varlistentry>
|
|
</variablelist>
|
|
<para>One way to generate a file for use as input to the <emphasis role="bold">-file</emphasis> argument is to
|
|
combine the <emphasis role="bold">-name</emphasis> and <emphasis role="bold">-n</emphasis> options, directing the output to a
|
|
file. The <emphasis>IBM AFS Administration Guide</emphasis> section on using the Backup
|
|
System to restore data explains how to edit the file as necessary before
|
|
using it as input to the <emphasis role="bold">-file</emphasis> argument.</para>
|
|
|
|
<para>The output of this command includes only volumes for which the Backup
|
|
Database includes at least one dump record. The command interpreter
|
|
generates a message on the standard error stream about volumes that do not
|
|
have dump records but either are listed in the file named by the <emphasis role="bold">-file</emphasis>
|
|
argument, or appear in the VLDB as a match to a volume entry in the volume
|
|
set named by the <emphasis role="bold">-name</emphasis> argument.</para>
|
|
|
|
</refsect1>
|
|
<refsect1>
|
|
<title>Examples</title>
|
|
<para>The following command restores all volumes included in entries in the
|
|
volume set named <computeroutput>data.restore</computeroutput>, which was created expressly to restore
|
|
data to a pair of file server machines on which all data was corrupted due
|
|
to a software error. All volumes are restored to the sites recorded in
|
|
their entries in the VLDB.</para>
|
|
|
|
<programlisting>
|
|
% backup volsetrestore -name data.restore
|
|
Starting restore
|
|
backup: task ID of restore operation: 112
|
|
backup: Finished doing restore
|
|
|
|
</programlisting>
|
|
<para>The following command restores all volumes that have entries in the file
|
|
named <replaceable>/tmp/restore</replaceable>:</para>
|
|
|
|
<programlisting>
|
|
% backup volsetrestore -file /tmp/restore
|
|
Starting restore
|
|
backup: task ID of restore operation: 113
|
|
backup: Finished doing restore
|
|
|
|
</programlisting>
|
|
<para>The <replaceable>/tmp/restore</replaceable> file has the following contents:</para>
|
|
|
|
<programlisting>
|
|
fs1.abc.com b user.pat
|
|
fs1.abc.com b user.terry
|
|
fs1.abc.com b user.smith
|
|
fs2.abc.com c user.jones
|
|
. . .
|
|
. . .
|
|
|
|
</programlisting>
|
|
</refsect1>
|
|
<refsect1>
|
|
<title>Privilege Required</title>
|
|
<para>The issuer must be listed in the <replaceable>/usr/afs/etc/UserList</replaceable> file on every
|
|
machine where the Backup Server or Volume Location (VL) Server is running,
|
|
and on every file server machine that houses an affected volume. If the
|
|
<emphasis role="bold">-localauth</emphasis> flag is included, the issuer must instead be logged on to a
|
|
server machine as the local superuser <computeroutput>root</computeroutput>.</para>
|
|
|
|
</refsect1>
|
|
<refsect1>
|
|
<title>See Also</title>
|
|
<para><link linkend="butc5">butc(5)</link>,
|
|
<link linkend="backup8">backup(8)</link>,
|
|
<link linkend="backup_addvolentry8">backup_addvolentry(8)</link>,
|
|
<link linkend="backup_addvolset8">backup_addvolset(8)</link>,
|
|
<link linkend="backup_diskrestore8">backup_diskrestore(8)</link>,
|
|
<link linkend="backup_dump8">backup_dump(8)</link>,
|
|
<link linkend="backup_volrestore8">backup_volrestore(8)</link>,
|
|
<link linkend="butc8">butc(8)</link></para>
|
|
|
|
</refsect1>
|
|
<refsect1>
|
|
<title>Copyright</title>
|
|
<para>IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.</para>
|
|
|
|
<para>This documentation is covered by the IBM Public License Version 1.0. It was
|
|
converted from HTML to POD by software written by Chas Williams and Russ
|
|
Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.</para>
|
|
|
|
</refsect1>
|
|
</refentry>
|