mirror of
https://git.openafs.org/openafs.git
synced 2025-01-22 00:41:08 +00:00
481 lines
27 KiB
HTML
481 lines
27 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
|
|
<HTML><HEAD>
|
|
<TITLE>Administration Reference</TITLE>
|
|
<!-- Begin Header Records ========================================== -->
|
|
<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
|
|
<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
|
|
<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
|
|
<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
|
|
<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
|
|
</HEAD><BODY>
|
|
<!-- (C) IBM Corporation 2000. All Rights Reserved -->
|
|
<BODY bgcolor="ffffff">
|
|
<!-- End Header Records ============================================ -->
|
|
<A NAME="Top_Of_Page"></A>
|
|
<H1>Administration Reference</H1>
|
|
<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf072.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf074.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
|
|
<P>
|
|
<H2><A NAME="HDRBK_DUMP" HREF="auarf002.htm#ToC_87">backup dump</A></H2>
|
|
<A NAME="IDX4302"></A>
|
|
<A NAME="IDX4303"></A>
|
|
<A NAME="IDX4304"></A>
|
|
<A NAME="IDX4305"></A>
|
|
<A NAME="IDX4306"></A>
|
|
<A NAME="IDX4307"></A>
|
|
<A NAME="IDX4308"></A>
|
|
<A NAME="IDX4309"></A>
|
|
<A NAME="IDX4310"></A>
|
|
<A NAME="IDX4311"></A>
|
|
<A NAME="IDX4312"></A>
|
|
<A NAME="IDX4313"></A>
|
|
<A NAME="IDX4314"></A>
|
|
<A NAME="IDX4315"></A>
|
|
<P><STRONG>Purpose</STRONG>
|
|
<P>Creates a dump (dumps a volume set at a particular dump level)
|
|
<P><STRONG>Synopsis</STRONG>
|
|
<PRE><B>backup dump</B> [<B>-volumeset</B> <<VAR>volume set name</VAR>>] [<B>-dump</B> <<VAR>dump level name</VAR>>]
|
|
[<B>-portoffset</B> <<VAR>TC port offset</VAR>>] [<B>-at</B> <<VAR>Date/time to start dump</VAR>><SUP>+</SUP>]
|
|
[<B>-append</B>] [<B>-n</B>] [<B>-file</B> <<VAR>load file</VAR>>]
|
|
[<B>-localauth</B>] [-<B>cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
|
|
|
|
<B>backup dump</B> [<B>-v</B> <<VAR>volume set name</VAR>>] [<B>-d</B> <<VAR>dump level name</VAR>>]
|
|
[<B>-p</B> <<VAR>TC port offset</VAR>>] [<B>-at</B> <<VAR>Date/time to start dump</VAR>><SUP>+</SUP>]
|
|
[<B>-ap</B>] [<B>-n</B>] [<B>-f</B> <<VAR>load file</VAR>>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
|
|
</PRE>
|
|
<P><STRONG>Description</STRONG>
|
|
<P>The <B>backup dump</B> command either dumps the volume set specified by
|
|
the <B>-volumeset</B> argument at the dump level specified by the
|
|
<B>-dump</B> argument and creates a Backup Database dump record about it,
|
|
or executes the dump instructions listed in the file named by the
|
|
<B>-file</B> argument. The Tape Coordinator indicated by the
|
|
<B>-portoffset</B> argument (or on each command in the file) executes the
|
|
operation.
|
|
<P>(If the <B>FILE YES</B> instruction appears in the
|
|
<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file on the Tape
|
|
Coordinator machine associated with the specified port offset, then the Backup
|
|
System dumps data to the backup data file listed for that port offset in the
|
|
Tape Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, rather
|
|
than to 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.)
|
|
<P>The term <I>dumping</I> refers to copying a collection of data to tape
|
|
or a backup data file, and the resulting collection is termed a
|
|
<I>dump</I>. The set of tapes that contain one or more dumps is
|
|
called a <I>dump set</I>. The first dump in a dump set is its
|
|
<I>initial dump</I>, and any dumps subsequently added to the dump set (by
|
|
use of the <B>-append</B> argument) are <I>appended dumps</I>.
|
|
Creating appended dumps is optional, and appended dumps can be of different
|
|
volume sets, and at different dump levels, than the initial dump.
|
|
<P>A <I>full dump</I>, created at a full dump level in the dump hierarchy,
|
|
contains all of the data that existed at the time of the dump in the volumes
|
|
belonging to the volume set. An <I>incremental dump</I>, created at
|
|
an incremental dump level, contains only data that has changed since the
|
|
volume set was dumped at the incremental level's <I>parent dump
|
|
level</I> (the dump level immediately above the incremental level in the
|
|
hierarchy), which can be a full or incremental level. More
|
|
specifically, an incremental dump includes only the files and directories that
|
|
have modification timestamps later than the <I>clone date</I> of the
|
|
volume included at the parent dump level. For backup and read-only
|
|
volumes, the clone date is the time at which the volume was cloned from its
|
|
read/write source before being included in the parent dump; for
|
|
read/write volumes, it represents the time at which the volume was locked for
|
|
inclusion in the parent dump. The clone date appears in the <VAR>clone
|
|
date</VAR> field of the output from the <B>backup volinfo</B>
|
|
command. As an example, an incremental dump at the
|
|
<B>/full/week1/thursday</B> level includes only files and directories that
|
|
have changed since the volume set was dumped at the <B>/full/week1</B>
|
|
level.
|
|
<P><B>Initiating different types of dump operations</B>
|
|
<P>To initiate a dump operation that is to start as soon as the relevant Tape
|
|
Coordinator is available, provide only the <B>-volumeset</B>,
|
|
<B>-dump</B>, <B>-portoffset</B>, and optionally <B>-append</B>
|
|
options. To schedule a single <B>backup dump</B> command to execute
|
|
in the future, also include the <B>-at</B> argument to specify the start
|
|
time.
|
|
<P>To append a dump to an existing dump set, include the <B>-append</B>
|
|
flag. The Backup System imposes the following conditions on appended
|
|
dumps:
|
|
<UL>
|
|
<P><LI>If writing to tape, the Tape Coordinator checks that it is the final one
|
|
in a dump set for which there are complete and valid tape and dump records in
|
|
the Backup Database. If not, it rejects the tape and requests an
|
|
acceptable one. The operator can use the <B>-dbadd</B> argument to
|
|
the <B>backup scantape</B> command to insert the necessary records into
|
|
the database.
|
|
<P><LI>The most recent dump on the tape or in the backup data file must have
|
|
completed successfully.
|
|
<P><LI>The dump set must begin with an initial dump that is recorded in the
|
|
Backup Database. If there are no dumps on the tape, then the Backup
|
|
System treats the dump operation as an initial dump and imposes the relevant
|
|
requirements (for example, checks the AFS tape name if appropriate).
|
|
</UL>
|
|
<P>To schedule multiple dump operations, list the operations in the file named
|
|
by the <B>-file</B> argument. Optionally include the <B>-at</B>
|
|
argument to specify when the <B>backup</B> command interpreter reads the
|
|
file; otherwise it reads it immediately. Do not combine the
|
|
<B>-file</B> argument with the command's first three arguments or the
|
|
<B>-append</B> or <B>-n</B> flags. The commands in the file can
|
|
include any of the <B>backup dump</B> command's arguments, including
|
|
the <B>-at</B> argument to schedule them to run even later in the
|
|
future.
|
|
<P>To generate a list of the volumes included in a dump, without actually
|
|
dumping them, combine the <B>-n</B> flag with the options to be used on
|
|
the actual command.
|
|
<P><B>How the Backup System executes a dump operation</B>
|
|
<P>Before beginning a dump operation, the Backup System verifies that there is
|
|
a Backup Database entry for the volume set, dump level, and port
|
|
offset. If the command is correctly formed and issued in interactive
|
|
mode, it is assigned a job number and added to the jobs list. List jobs
|
|
in interactive mode by using the <B>(backup) jobs</B> command;
|
|
terminate them with the <B>(backup) kill</B> command.
|
|
<P>After obtaining the list of volumes to dump from the Volume Location (VL)
|
|
Server, the Backup System sorts the list by site (server and
|
|
partition). It groups volumes from the same site together in the dump
|
|
to minimize the number of times the operator must change tapes during restore
|
|
operations.
|
|
<P>The dependence of an incremental dump on its parent means that a valid
|
|
parent dump must already exist for the Backup System to create its child
|
|
incremental dump. If the Backup System does not find a record of a dump
|
|
created at the immediate parent dump level, it looks in the Backup Database
|
|
for a dump created at one level higher in the hierarchy, and so on, up to the
|
|
full dump level if necessary. It creates an incremental dump at the
|
|
level one below the lowest valid parent dump set that it finds. If it
|
|
fails to find even a full dump, it dumps the volume set at the full dump
|
|
level.
|
|
<P>If the Backup System is unable to access a volume during a dump operation,
|
|
it skips the volume and dumps the remaining volumes from the volume
|
|
set. Possible reasons a volume is inaccessible include server machine
|
|
or process outages, or that the volume was moved between the time the Volume
|
|
Location (VL) Server generated the list of sites for the volume in the volume
|
|
set and the time the Backup System actually attempts to dump the data in
|
|
it. After the first dumping pass, the Backup System attempts to dump
|
|
each volume it skipped. If it still cannot dump a volume and the
|
|
<B>ASK NO</B> instruction does not appear in the
|
|
<B>CFG_</B><VAR>device_name</VAR> file, it queries the operator as to
|
|
whether it needs to attempt to dump the volume again, omit the volume from the
|
|
dump, or halt the dump operation altogether. When prompted, the
|
|
operator can attempt to solve whatever problem prevented the Backup System
|
|
from accessing the volumes. If the <B>ASK NO</B> instruction
|
|
appears in the <B>CFG_</B><VAR>device_name</VAR> file, the Backup System
|
|
omits the volume from the dump.
|
|
<P>Before scheduling a dump operation, the Backup System verifies that the
|
|
date specified by the <B>-at</B> argument is in the future, and checks the
|
|
validity of the volume set, dump level and port offset as for a regular dump
|
|
operation. It checks the validity of the parameters again just before
|
|
actually running the scheduled operation.
|
|
<P>Before writing an initial dump to a tape that does not have a permanent
|
|
name on the label, the Backup System checks that the AFS tape name on the
|
|
label is acceptable. If desired, disable name checking by including the
|
|
<B>NAME_CHECK NO</B> instruction in the
|
|
<B>CFG_</B><VAR>device_name</VAR> file.
|
|
<P>If AFS tape name checking is enabled, the Backup System accepts the
|
|
following three types of values for the AFS tape name. If the name on
|
|
the label does not conform, the Backup System obtains a tape with an
|
|
acceptable label by invoking the <B>MOUNT</B> instruction in the
|
|
<B>CFG_</B><VAR>device_name</VAR> file or prompting the operator.
|
|
<OL TYPE=1>
|
|
<P><LI>A name of the form
|
|
<VAR>volume_set_name.dump_level_name.tape_index</VAR>, where
|
|
<VAR>volume_set_name</VAR> matches the value of the <B>-volumeset</B>
|
|
argument, <VAR>dump_level_name</VAR> matches the last element in the pathname
|
|
value of the <B>-dump</B> argument, and <VAR>tape_index</VAR> reflects the
|
|
tape's place in a multitape dump set. As an example, the first
|
|
tape in a dump set for which the initial dump is of volume set <B>user</B>
|
|
at the dump level <B>/sunday2/monday</B> has AFS tape name
|
|
<B>user.monday.1</B>. If the label records this type
|
|
of AFS tape name, the Backup System retains the AFS tape name and writes the
|
|
dump to the tape.
|
|
<P><LI>The string <TT><NULL></TT>, which usually indicates that a backup
|
|
operator has used the <B>backup labeltape</B> command to write a label on
|
|
the tape, but did not include the <B>-name</B> argument to assign an AFS
|
|
tape name. Presumably, the operator did include the <B>-pname</B>
|
|
argument to assign a permanent name. If the label records a
|
|
<TT><NULL></TT> value, the Backup System constructs and records on the
|
|
label the appropriate AFS tape name, and writes the dump on the tape.
|
|
<P><LI>No value at all, because the tape has never been labeled or used in the
|
|
Backup System. As when the AFS tape name is <TT><NULL></TT>, the
|
|
Backup System constructs and records on the label the appropriate AFS tape
|
|
name, and writes the dump on the tape.
|
|
</OL>
|
|
<P>To determine how much data it can write to a tape, the Tape Coordinator
|
|
reads the capacity recorded on the tape's label (placed there by
|
|
including the <B>-size</B> argument to the <B>backup labeltape</B>
|
|
command). If the label's capacity field is empty, the Tape
|
|
Coordinator uses the capacity recorded for the specified port offset in the
|
|
local <B>tapeconfig</B> file. If the capacity field in the
|
|
<B>tapeconfig</B> file is also empty, the Tape Coordinator uses the
|
|
maximum capacity of 2 TB.
|
|
<P>During a dump operation, the Tape Coordinator tracks how much data it has
|
|
written and stops shortly before it reaches what it believes is the
|
|
tape's capacity. If it is in the middle of writing the data for a
|
|
volume when it reaches that point, it writes a special marker that indicates
|
|
an interrupted volume and continues writing the volume on the next
|
|
tape. It can split a volume this way during both an initial and an
|
|
appended dump, and the fact that the volume resides on multiple tapes is
|
|
automatically recorded in the Backup Database.
|
|
<P>If the tape is actually larger than the expected capacity, then the Tape
|
|
Coordinator simply does not use the excess tape. If the tape is smaller
|
|
than the expected capacity, the Tape Coordinator can reach the end-of-tape
|
|
(EOT) unexpectedly while it is writing data. If the Tape Coordinator is
|
|
in the middle of the writing data from a volume, it obtains a new tape and
|
|
rewrites the entire contents of the interrupted volume to it. The data
|
|
from the volume that was written to the previous tape remains there, but is
|
|
never used.
|
|
<P>The Backup System allows recycling of tapes (writing a new dump set over an
|
|
old dump set that is no longer needed), but imposes the following
|
|
conditions:
|
|
<UL>
|
|
<P><LI>All dumps in the old dump set must be expired. The Backup System
|
|
always checks expiration dates, even when name checking is disabled.
|
|
<P><LI>If the tape to be recycled does not have a permanent name and name
|
|
checking is enabled, then the AFS tape name derived from the new initial
|
|
dump's volume set name and dump level name must match the AFS tape name
|
|
already recorded on the label.
|
|
<P><LI>The tape cannot already have data on it that belongs to the dump currently
|
|
being performed, because that implies that the operator or automated tape
|
|
device has not removed the previous tape from the drive, or has mistakenly
|
|
reinserted it. The Tape Coordinator generates the following message and
|
|
attempts to obtain another tape:
|
|
<PRE> Can't overwrite tape containing the dump in progress
|
|
|
|
</PRE>
|
|
<P><LI>The tape cannot contain data from a parent dump of the current
|
|
(incremental) dump, because overwriting a parent dump makes it impossible to
|
|
restore data from the current dump. The Tape Coordinator generates the
|
|
following message and attempts to obtain another tape:
|
|
<PRE> Can't overwrite the parent dump <VAR>parent_name</VAR> (<VAR>parent_dump_ID</VAR>)
|
|
|
|
</PRE>
|
|
</UL>
|
|
<P>To recycle a tape before all dumps on it have expired or if the AFS tape
|
|
name is wrong, use the <B>backup labeltape</B> command to overwrite the
|
|
tape's label and remove all associated tape and dump records from the
|
|
Backup Database.
|
|
<P>The Tape Coordinator's default response to this command is to access
|
|
the first tape by invoking the <B>MOUNT</B> instruction in the
|
|
<B>CFG_</B><VAR>device_name</VAR> file, or by prompting the backup operator
|
|
to insert the tape if there is no <B>MOUNT</B> instruction.
|
|
However, if the <B>AUTOQUERY NO</B> instruction appears in the
|
|
<B>CFG_</B><VAR>device_name</VAR> file, or if the issuer of the
|
|
<B>butc</B> command included the <B>-noautoquery</B> flag, the Tape
|
|
Coordinator instead expects the tape to be in the device already. If it
|
|
is not, the Tape Coordinator invokes the <B>MOUNT</B> instruction or
|
|
prompts the operator. It also invokes the <B>MOUNT</B> instruction
|
|
or prompts for any additional tapes needed to complete the dump
|
|
operation; the issuer must arrange to provide them.
|
|
<P><STRONG>Cautions</STRONG>
|
|
<P>If a dump operation is interrupted or fails for any reason, data from all
|
|
volumes written to tape before the interrupt are valid can be used in a
|
|
restore operation. The Backup Database includes an entry for the failed
|
|
dump and for each volume that was successfully dumped. See the <I>IBM
|
|
AFS Administration Guide</I> for information on dealing with interrupted
|
|
dumps.
|
|
<P>If dumping to tape rather than a backup data file, it is best to use only
|
|
compatible tape devices (ones that can read the same type of tape).
|
|
Using compatible devices greatly simplifies restore operations. The
|
|
<B>-portoffset</B> argument to the <B>backup diskrestore</B> and
|
|
<B>backup volsetrestore</B> commands accepts multiple port offset numbers,
|
|
but the Backup System uses the first listed port offset when restoring all
|
|
full dumps, the second port offset when restoring all level 1 dumps, and so
|
|
on. At the very least, use compatible tape devices to perform dumps at
|
|
each level. If compatible tape devices are not used, the <B>backup
|
|
volrestore</B> command must be used to restore one volume at a time.
|
|
<P>Valid (unexpired) administrative tokens must be available to the
|
|
<B>backup</B> command interpreter both when it reads the file named by the
|
|
<B>-file</B> argument and when it runs each operation listed in the
|
|
file. Presumably, the issuer is scheduling dumps for times when no
|
|
human operator is present, and so must arrange for valid tokens to be
|
|
available on the local machine. One option is to issue all commands (or
|
|
run all scripts) on file server machines and use the <B>-localauth</B>
|
|
flag on the <B>backup</B> and <B>vos</B> commands. To protect
|
|
against improper access to the machine or the tokens, the machine must be
|
|
physically secure (perhaps even more protected than a Tape Coordinator machine
|
|
monitored by a human operator during operation). Also, if an unattended
|
|
dump requires multiple tapes, the operator must properly configure a tape
|
|
stacker or jukebox and the device configuration file.
|
|
<P>When the command is issued in regular (non-interactive) mode, the command
|
|
shell prompt does not return until the dump operation completes. To
|
|
avoid having to open additional connections, issue the command in interactive
|
|
mode, especially when including the <B>-at</B> argument to schedule dump
|
|
operations.
|
|
<P><STRONG>Options</STRONG>
|
|
<DL>
|
|
<P><DT><B>-volumeset
|
|
</B><DD>Names the volume set to dump. The <B>-dump</B> argument must be
|
|
provided along with this one; do not combine them with the
|
|
<B>-file</B> argument. If using a temporary volume set, the
|
|
<B>vos dump</B> command must be issued within the interactive session in
|
|
which the <B>backup addvolset</B> command was issued with the
|
|
<B>-temporary</B> flag.
|
|
<P><DT><B>-dump
|
|
</B><DD>Specifies the complete pathname of the dump level at which to dump the
|
|
volume set. The <B>-volumeset</B> argument must be provided along
|
|
with this one; do not combine them with the <B>-file</B>
|
|
argument.
|
|
<P><DT><B>-portoffset
|
|
</B><DD>Specifies the port offset number of the Tape Coordinator handling the
|
|
tapes for this operation. It must be provided unless the default value
|
|
of 0 (zero) is appropriate; do not combine it with the <B>-file</B>
|
|
argument.
|
|
<P><DT><B><B>-at</B>
|
|
</B><DD>Specifies the date and time in the future at which to run the command, or
|
|
to read the file named by the <B>-file</B> argument. Provide a
|
|
value in the format <VAR>mm/dd/yyyy</VAR> [<VAR>hh:MM</VAR>], where the
|
|
month (<VAR>mm</VAR>), day (<VAR>dd</VAR>), and year (<VAR>yyyy</VAR>) are
|
|
required. Valid values for the year range from <B>1970</B> to
|
|
<B>2037</B>; higher values are not valid because the latest possible
|
|
date in the standard UNIX representation is in February 2038. The
|
|
Backup System automatically reduces any later date to the maximum
|
|
value.
|
|
<P>The hour and minutes (<VAR>hh:MM</VAR>) are optional, but if provided
|
|
must be in 24-hour format (for example, the value <B>14:36</B>
|
|
represents 2:36 p.m.). If omitted, the time
|
|
defaults to midnight (00:00 hours).
|
|
<P>As an example, the value <B>04/23/1999 20:20</B> schedules the
|
|
command for 8:20 p.m. on 23 April 1999.
|
|
<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A plus sign follows this argument in the command's syntax statement
|
|
because it accepts a multiword value which does not need to be enclosed in
|
|
double quotes or other delimiters, not because it accepts multiple
|
|
dates. Provide only one date (and optionally, time) definition.
|
|
</TD></TR></TABLE>
|
|
<P><DT><B>-append
|
|
</B><DD>Appends the dump onto the end of a tape that already contains data from
|
|
another dump. However, if the tape is not in fact part of an existing
|
|
dump set, the Backup System creates a new dump set using the parameters of
|
|
this dump. If the tape is not the last tape in the dump set, the Tape
|
|
Coordinator prompts for insertion of the appropriate tape. Do not
|
|
combine this argument with the <B>-file</B> argument.
|
|
<P><DT><B>-n
|
|
</B><DD>Displays the names of volumes to be included in the indicated dump,
|
|
without actually performing the dump operation. Do not combine this
|
|
argument with the <B>-file</B> argument.
|
|
<P><DT><B>-file
|
|
</B><DD>Specifies the local disk or AFS pathname of a file containing
|
|
<B>backup</B> commands. The Backup System reads the file
|
|
immediately, or at the time specified by the <B>-at</B> argument if it is
|
|
provided. A partial pathname is interpreted relative to the current
|
|
working directory.
|
|
<P>Place each <B>backup dump</B> command on its own line in the indicated
|
|
file, using the same syntax as for the command line, but without the word
|
|
<B>backup</B> at the start of the line. Each command must include a
|
|
value for the <B>-volumeset</B> and <B>-dump</B> arguments, and for
|
|
the <B>-portoffset</B> argument unless the default value of 0 is
|
|
appropriate. Commands in the file can also include any of the
|
|
<B>backup dump</B> command's optional options. In the
|
|
following example file, the first command runs as soon as the Backup System
|
|
reads the file, whereas the other commands are themselves scheduled; the
|
|
specified date and time must be later than the date and time at which the
|
|
Backup System reads the file.
|
|
<PRE> dump user /sunday1/wednesday -port 1
|
|
dump sun4x_56 /sunday1/friday -port 2 -at 04/08/1999
|
|
dump sun4x_55 /sunday1/friday -port 2 -at 04/08/1999 02:00 -append
|
|
|
|
</PRE>
|
|
<P>
|
|
<P>Do not combine this argument with the <B>-volumeset</B>,
|
|
<B>-dump</B>, <B>-portoffset</B>, <B>-append</B>, or <B>-n</B>
|
|
options.
|
|
<P><DT><B>-localauth
|
|
</B><DD>Constructs a server ticket using a key from the local
|
|
<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
|
|
interpreter presents it to the Backup Server, Volume Server and VL Server
|
|
during mutual authentication. Do not combine this flag with the
|
|
<B>-cell</B> argument. For more details, see the introductory
|
|
<B>backup</B> reference page.
|
|
<P><DT><B>-cell
|
|
</B><DD>Names the cell in which to run the command. Do not combine this
|
|
argument with the <B>-localauth</B> flag. For more details, see the
|
|
introductory <B>backup</B> reference page.
|
|
<P><DT><B>-help
|
|
</B><DD>Prints the online help for this command. All other valid options
|
|
are ignored.
|
|
</DL>
|
|
<P><STRONG>Output</STRONG>
|
|
<P>The command interpreter first generates a list of the volumes to be
|
|
included in the dump by matching the entries in the volume set against the
|
|
volumes listed in the Volume Location Database (VLDB). It prints the
|
|
list following the header:
|
|
<PRE> Preparing to dump the following volumes:
|
|
|
|
</PRE>
|
|
<P>The following message then indicates that the command interpreter has
|
|
passed the dump request to the appropriate Tape Coordinator for
|
|
processing:
|
|
<PRE> Starting dump.
|
|
|
|
</PRE>
|
|
<P>If the issuer includes the <B>-n</B> flag, the output is of the
|
|
following form:
|
|
<PRE> Starting dump of volume set '<VAR>volume set</VAR>' (dump set '<VAR>dump level</VAR>')
|
|
Total number of volumes : <VAR>number dumped</VAR>
|
|
Would have dumped the following volumes:
|
|
<VAR>list_of_volumes</VAR>
|
|
|
|
</PRE>
|
|
<P>where <VAR>list_of_volumes</VAR> identifies each volume by name and volume ID
|
|
number.
|
|
<P>If the Tape Coordinator is unable to access a volume, it prints an error
|
|
message in its window and records the error in its log and error files.
|
|
<P><STRONG>Examples</STRONG>
|
|
<P>The following command dumps the volumes in the volume set called
|
|
<B>user</B> at the dump level <B>/full/sunday2/monday</B>. The
|
|
issuer places the necessary tapes in the device with port offset 5.
|
|
<PRE> % <B>backup dump -volumeset user -dump /full/sunday2/monday -portoffset 5</B>
|
|
Preparing to dump the following volumes:
|
|
user.jones.backup 387623900
|
|
user.pat.backup 486219245
|
|
user.smith.backup 597315841
|
|
. .
|
|
. .
|
|
Starting dump.
|
|
|
|
</PRE>
|
|
<P>The following command displays the list of volumes to be dumped when the
|
|
user dumps the <B>sys_sun</B> volume set at the <B>/full</B> dump
|
|
level.
|
|
<PRE> % <B>backup dump -volumeset sys_sun -dump /full -n</B>
|
|
Starting dump of volume set 'sys_sun' (dump set '/full')
|
|
Total number of volumes: 24
|
|
Would have dumped the following volumes:
|
|
sun4x_56 124857238
|
|
sun4x_56.bin 124857241
|
|
. .
|
|
. .
|
|
sun4x_55 124857997
|
|
. .
|
|
. .
|
|
|
|
</PRE>
|
|
<P>The following command schedules a dump of the volumes in the volume set
|
|
<B>user</B> at the dump level <B>/sunday2/monday1</B> for 11:00
|
|
p.m. on 14 June 1999. The appropriate Tape Coordinator
|
|
has port offset 0 (zero), so that argument is omitted.
|
|
<PRE> % <B>backup dump -volumeset user -dump /sunday2/monday1 -at 06/14/1999 23:00</B>
|
|
|
|
</PRE>
|
|
<P><STRONG>Privilege Required</STRONG>
|
|
<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> 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 <B>-localauth</B> flag is included, the issuer must
|
|
instead be logged on to a server machine as the local superuser
|
|
<B>root</B>.
|
|
<P><STRONG>Related Information</STRONG>
|
|
<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
|
|
<P><A HREF="auarf061.htm#HDRBK_ADDDUMP">backup adddump</A>
|
|
<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
|
|
<P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
|
|
<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
|
|
<P><A HREF="auarf079.htm#HDRBK_LABELTAPE">backup labeltape</A>
|
|
<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
|
|
<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
|
|
<P>
|
|
<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf072.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf074.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
|
|
<!-- Begin Footer Records ========================================== -->
|
|
<P><HR><B>
|
|
<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
|
|
</B>
|
|
<!-- End Footer Records ============================================ -->
|
|
<A NAME="Bot_Of_Page"></A>
|
|
</BODY></HTML>
|