mirror of
https://git.openafs.org/openafs.git
synced 2025-01-22 00:41:08 +00:00
291 lines
17 KiB
HTML
291 lines
17 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="auarf090.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="auarf092.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_VOLRESTORE" HREF="auarf002.htm#ToC_105">backup volrestore</A></H2>
|
||
|
|
<A NAME="IDX4422"></A>
|
||
|
|
<A NAME="IDX4423"></A>
|
||
|
|
<A NAME="IDX4424"></A>
|
||
|
|
<A NAME="IDX4425"></A>
|
||
|
|
<A NAME="IDX4426"></A>
|
||
|
|
<A NAME="IDX4427"></A>
|
||
|
|
<P><STRONG>Purpose</STRONG>
|
||
|
|
<P>Restores one or more volumes
|
||
|
|
<P><STRONG>Synopsis</STRONG>
|
||
|
|
<PRE><B>backup volrestore -server</B> <<VAR>destination machine</VAR>>
|
||
|
|
<B>-partition</B> <<VAR>destination partition</VAR>>
|
||
|
|
<B>-volume</B> <<VAR>volume(s) to restore</VAR>><SUP>+</SUP>
|
||
|
|
[<B>-extension</B> <<VAR>new volume name extension</VAR>>]
|
||
|
|
[<B>-date</B> <<VAR>date from which to restore</VAR>><SUP>+</SUP>]
|
||
|
|
[<B>-portoffset</B> <<VAR>TC port offsets</VAR>><SUP>+</SUP>] [<B>-n</B>]
|
||
|
|
[<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
|
||
|
|
|
||
|
|
<B>backup volr -s</B> <<VAR>destination machine</VAR>> <B>-pa</B> <<VAR>destination partition</VAR>>
|
||
|
|
<B>-v</B> <<VAR>volume(s) to restore</VAR>><SUP>+</SUP> [<B>-e</B> <<VAR>new volume name extension</VAR>>]
|
||
|
|
[<B>-d</B> <<VAR>date from which to restore</VAR>><SUP>+</SUP>] [-<B>po</B> <<VAR>TC port offsets</VAR>><SUP>+</SUP>]
|
||
|
|
[<B>-n</B>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
|
||
|
|
</PRE>
|
||
|
|
<P><STRONG>Description</STRONG>
|
||
|
|
<P>The <B>backup volrestore</B> command restores the contents of one or
|
||
|
|
more volumes to the site indicated by the <B>-server</B> and
|
||
|
|
<B>-partition</B> arguments. Use the command either to overwrite
|
||
|
|
the contents of existing volumes with the restored data or to create new
|
||
|
|
volumes while retaining the existing ones. The specified site does not
|
||
|
|
have to be the current site for the volumes.
|
||
|
|
<P>(If the <B>FILE YES</B> instruction appears in the
|
||
|
|
<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file associated with the
|
||
|
|
specified port offset, then the <B>backup volrestore</B> command restores
|
||
|
|
data from the backup data file listed for that port offset in the Tape
|
||
|
|
Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, rather than
|
||
|
|
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.)
|
||
|
|
<P>The command's arguments can be combined as indicated:
|
||
|
|
<UL>
|
||
|
|
<P><LI>To preserve a volume's current contents and also create a new volume
|
||
|
|
to house the restored version, use the <B>-extension</B> argument.
|
||
|
|
The Backup System creates the new volume on the server and partition named by
|
||
|
|
the <B>-server</B> and <B>-partition</B> arguments, assigns it the
|
||
|
|
same name as the current volume with the addition of the specified extension,
|
||
|
|
and creates a new Volume Location Database (VLDB) entry for it.
|
||
|
|
Creating a new volume enables the administrator to compare the two
|
||
|
|
versions.
|
||
|
|
<P><LI>To overwrite a volume's existing contents with the restored version,
|
||
|
|
omit the <B>-extension</B> argument, and specify the site as
|
||
|
|
indicated:
|
||
|
|
<UL>
|
||
|
|
<P><LI>To retain the current site, specify it with the <B>-server</B> and
|
||
|
|
<B>-partition</B> arguments.
|
||
|
|
<P><LI>To move the volume to a different site while overwriting it, specify the
|
||
|
|
new site with the <B>-server</B> argument, <B>-partition</B> argument,
|
||
|
|
or both. The Backup System creates a new volume at that site, removes
|
||
|
|
the existing volume, and updates the site information in the volume's
|
||
|
|
VLDB entry. The backup version of the volume is not removed
|
||
|
|
automatically from the original site, if it exists. Use the <B>vos
|
||
|
|
remove</B> command to remove it and the <B>vos backup</B> command to
|
||
|
|
create a backup version at the new site.
|
||
|
|
</UL>
|
||
|
|
<P><LI>To restore a volume that no longer exists in the file system, specify its
|
||
|
|
name with the <B>-volume</B> argument and use the <B>-server</B> and
|
||
|
|
<B>-partition</B> arguments to place it at the desired site. The
|
||
|
|
Backup System creates a new volume and new VLDB entry.
|
||
|
|
</UL>
|
||
|
|
<P>In each case, the command sets each volume's creation date to the date
|
||
|
|
and time at which it restores it. The creation date appears in the
|
||
|
|
<TT>Creation</TT> field in the output from the <B>vos examine</B> and
|
||
|
|
<B>vos listvol</B> commands.
|
||
|
|
<P>If restoring all of the volumes that resided on a single partition, it is
|
||
|
|
usually more efficient to use the <B>backup diskrestore</B>
|
||
|
|
command. If restoring multiple volumes to many different sites, it can
|
||
|
|
be more efficient to use the <B>backup volsetrestore</B> command.
|
||
|
|
<P>By default, the <B>backup volrestore</B> command restores the most
|
||
|
|
recent full dump and all subsequent incremental dumps for each volume,
|
||
|
|
bringing the restored volumes to the most current possible state. To
|
||
|
|
restore the volumes to their state at some time in the past, use the
|
||
|
|
<B>-date</B> argument. The Backup System restores the most recent
|
||
|
|
full dump and each subsequent incremental dump for which the <VAR>clone
|
||
|
|
date</VAR> of the volume included in the dump is before the indicated date and
|
||
|
|
time (the clone date timestamp appears in the <TT>clone date</TT> field of
|
||
|
|
the output from the <B>backup volinfo</B> command). For backup and
|
||
|
|
read-only volumes, the clone date represents the time at which the volume was
|
||
|
|
copied from its read/write source; for read/write volumes, it represents
|
||
|
|
the time at which the volume was locked for inclusion in the dump. The
|
||
|
|
resemblance of a restored volume to its actual state at the indicated time
|
||
|
|
depends on the amount of time that elapsed between the volume's clone
|
||
|
|
date in the last eligible dump and the specified time.
|
||
|
|
<P>If the <B>-volume</B> argument specifies the base (read/write) form of
|
||
|
|
the volume name, 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 volume
|
||
|
|
name explicitly includes the <B>.backup</B> or
|
||
|
|
<B>.readonly</B> extension, the Backup System restores dumps of the
|
||
|
|
corresponding volume version only.
|
||
|
|
<P>To generate a list of the tapes the Backup System needs to perform the
|
||
|
|
restore operation, without actually performing it, combine the <B>-n</B>
|
||
|
|
flag with the options to be used on the actual command.
|
||
|
|
<P>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
|
||
|
|
<B>-portoffset</B> 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). If restoring multiple volumes, the same ordered list of port
|
||
|
|
offsets must apply to all of them. If not, either issue this command
|
||
|
|
separately for each volume, or use the <B>vos volsetrestore</B> command
|
||
|
|
after defining groups of volumes that were dumped to compatible tape
|
||
|
|
types. For further discussion, see the <I>IBM AFS Administration
|
||
|
|
Guide</I>.
|
||
|
|
<P>The Tape Coordinator's default response to this command is to access
|
||
|
|
the first tape it needs by invoking the <B>MOUNT</B> instruction in the
|
||
|
|
local <B>/usr/afs/backup/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, or is the wrong tape, 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 restore operation; the backup operator must
|
||
|
|
arrange to provide them.
|
||
|
|
<P><STRONG>Options</STRONG>
|
||
|
|
<DL>
|
||
|
|
<P><DT><B>-server
|
||
|
|
</B><DD>Names the file server machine on which to restore each volume. If
|
||
|
|
this argument and the <B>-partition</B> argument indicate a site other
|
||
|
|
than the current site for each volume, and the <B>-extension</B> argument
|
||
|
|
is not also provided, the Backup System removes the existing volumes from
|
||
|
|
their current sites, places the restored contents at the specified site, and
|
||
|
|
changes the site information in the volume's VLDB entry.
|
||
|
|
<P><DT><B>-partition
|
||
|
|
</B><DD>Names the partition to which to restore each volume. If this
|
||
|
|
argument and the <B>-server</B> argument indicate a site other than the
|
||
|
|
current site for each volume, and the <B>-extension</B> argument is not
|
||
|
|
also provided, the Backup System removes the existing volumes from their
|
||
|
|
current sites, places the restored contents at the specified site, and changes
|
||
|
|
the site information in the volume's VLDB entry.
|
||
|
|
<P><DT><B>-volume
|
||
|
|
</B><DD>Names one or more volumes to restore, using the volume name as listed in
|
||
|
|
the Backup Database. Provide the base (read/write) name of each volume
|
||
|
|
to have the Backup System search 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, a volume name
|
||
|
|
explicitly includes the <B>.backup</B> or
|
||
|
|
<B>.readonly</B> extension, the Backup System restores dumps of the
|
||
|
|
corresponding volume version only.
|
||
|
|
<P><DT><B>-extension
|
||
|
|
</B><DD>Creates a new volume to house the restored data, with a name derived by
|
||
|
|
appending the specified string to each volume named by the <B>-volume</B>
|
||
|
|
argument. The Backup System creates a new VLDB entry for the
|
||
|
|
volume. Any string other than <B>.readonly</B> or
|
||
|
|
<B>.backup</B> is acceptable, but the combination of the existing
|
||
|
|
volume 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 <B>.rst</B>, for example).
|
||
|
|
<P><DT><B>-date
|
||
|
|
</B><DD>Specifies a date and optionally time; the restored volume includes
|
||
|
|
data from dumps performed before the date only. Provide a value in the
|
||
|
|
format <VAR>mm</VAR>/<VAR>dd</VAR>/<VAR>yyyy</VAR> [<VAR>hh</VAR>:<VAR>MM</VAR>],
|
||
|
|
where the required <VAR>mm/dd/yyyy</VAR> portion indicates the month
|
||
|
|
(<VAR>mm</VAR>), day (<VAR>dd</VAR>), and year (<VAR>yyyy</VAR>), and the optional
|
||
|
|
<VAR>hh:MM</VAR> portion indicates the hour and minutes in 24-hour format
|
||
|
|
(for example, the value <B>14:36</B> represents 2:36
|
||
|
|
p.m.). If omitted, the time defaults to 59 seconds after
|
||
|
|
midnight (00:00:59 hours).
|
||
|
|
<P>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
|
||
|
|
command interpreter automatically reduces any later date to the maximum
|
||
|
|
value.
|
||
|
|
<P>If this argument is omitted, the Backup System restores all possible dumps
|
||
|
|
including the most recently created.
|
||
|
|
<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>-portoffset
|
||
|
|
</B><DD>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.
|
||
|
|
<P>Provide this argument unless the default value of 0 (zero) is appropriate
|
||
|
|
for all dumps. If <B>0</B> is just one of the values in the list,
|
||
|
|
provide it explicitly in the appropriate order.
|
||
|
|
<P><DT><B>-n
|
||
|
|
</B><DD>Displays the list of tapes that contain the dumps required by the restore
|
||
|
|
operation, without actually performing the operation.
|
||
|
|
<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>If the issuer includes the <B>-n</B> flag with the command, the
|
||
|
|
following string appears at the head of the list of the tapes necessary to
|
||
|
|
complete the restore operation.
|
||
|
|
<PRE> Tapes needed:
|
||
|
|
|
||
|
|
</PRE>
|
||
|
|
<P><STRONG>Examples</STRONG>
|
||
|
|
<P>The following command restores the volume <B>user.pat</B> to
|
||
|
|
partition <B>/vicepa</B> on machine
|
||
|
|
<B>fs5.abc.com</B>:
|
||
|
|
<PRE> % <B>backup volrestore -server fs5.abc.com -partition a -volume user.pat</B>
|
||
|
|
|
||
|
|
</PRE>
|
||
|
|
<P>The following command restores the volumes <B>user.smith</B> and
|
||
|
|
<B>user.terry</B> to partition <B>/vicepb</B> on machine
|
||
|
|
<B>fs4.abc.com</B>, adding a <B>.rst</B>
|
||
|
|
extension to each volume name and preserving the existing
|
||
|
|
<B>user.smith</B> and <B>user.terry</B> volumes.
|
||
|
|
Only dumps created before 5:00 p.m. on 31 January 1998 are
|
||
|
|
restored. (The command is shown here on multiple lines only for
|
||
|
|
legibility reasons.)
|
||
|
|
<PRE> % <B>backup volrestore -server fs4.abc.com -partition b</B> \
|
||
|
|
<B>-volume user.smith user.terry</B> \
|
||
|
|
<B>-extension .rst -date 1/31/1998 17:00</B>
|
||
|
|
|
||
|
|
</PRE>
|
||
|
|
<P>The following command restores the volume <B>user.pat</B> to
|
||
|
|
partition <B>/vicepb</B> on machine
|
||
|
|
<B>fs4.abc.com</B>. The Tape Coordinator with port
|
||
|
|
offset 1 handles the tape containing the full dump; the Tape Coordinator
|
||
|
|
with port offset 0 handles all tapes containing incremental dumps. (The
|
||
|
|
command is shown here on two lines only for legibility reasons.)
|
||
|
|
<PRE> % <B>backup volrestore -server fs5.abc.com -partition a</B> \
|
||
|
|
<B>-volume user.pat -portoffset 1 0</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="auarf073.htm#HDRBK_DUMP">backup dump</A>
|
||
|
|
<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
|
||
|
|
<P><A HREF="auarf092.htm#HDRBK_VOLSETRESTORE">backup volsetrestore</A>
|
||
|
|
<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
|
||
|
|
<P><A HREF="auarf255.htm#HDRVOS_BACKUP">vos backup</A>
|
||
|
|
<P><A HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</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="auarf090.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="auarf092.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>
|