1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
3 <TITLE>Administration Reference</TITLE>
4 <!-- Begin Header Records ========================================== -->
5 <!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
6 <!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
7 <META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
8 <META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
9 <META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
11 <!-- (C) IBM Corporation 2000. All Rights Reserved -->
12 <BODY bgcolor="ffffff">
13 <!-- End Header Records ============================================ -->
14 <A NAME="Top_Of_Page"></A>
15 <H1>Administration Reference</H1>
16 <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>
18 <H2><A NAME="HDRBK_DUMP" HREF="auarf002.htm#ToC_87">backup dump</A></H2>
19 <A NAME="IDX4302"></A>
20 <A NAME="IDX4303"></A>
21 <A NAME="IDX4304"></A>
22 <A NAME="IDX4305"></A>
23 <A NAME="IDX4306"></A>
24 <A NAME="IDX4307"></A>
25 <A NAME="IDX4308"></A>
26 <A NAME="IDX4309"></A>
27 <A NAME="IDX4310"></A>
28 <A NAME="IDX4311"></A>
29 <A NAME="IDX4312"></A>
30 <A NAME="IDX4313"></A>
31 <A NAME="IDX4314"></A>
32 <A NAME="IDX4315"></A>
33 <P><STRONG>Purpose</STRONG>
34 <P>Creates a dump (dumps a volume set at a particular dump level)
35 <P><STRONG>Synopsis</STRONG>
36 <PRE><B>backup dump</B> [<B>-volumeset</B> <<VAR>volume set name</VAR>>] [<B>-dump</B> <<VAR>dump level name</VAR>>]
37 [<B>-portoffset</B> <<VAR>TC port offset</VAR>>] [<B>-at</B> <<VAR>Date/time to start dump</VAR>><SUP>+</SUP>]
38 [<B>-append</B>] [<B>-n</B>] [<B>-file</B> <<VAR>load file</VAR>>]
39 [<B>-localauth</B>] [-<B>cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
41 <B>backup dump</B> [<B>-v</B> <<VAR>volume set name</VAR>>] [<B>-d</B> <<VAR>dump level name</VAR>>]
42 [<B>-p</B> <<VAR>TC port offset</VAR>>] [<B>-at</B> <<VAR>Date/time to start dump</VAR>><SUP>+</SUP>]
43 [<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>]
45 <P><STRONG>Description</STRONG>
46 <P>The <B>backup dump</B> command either dumps the volume set specified by
47 the <B>-volumeset</B> argument at the dump level specified by the
48 <B>-dump</B> argument and creates a Backup Database dump record about it,
49 or executes the dump instructions listed in the file named by the
50 <B>-file</B> argument. The Tape Coordinator indicated by the
51 <B>-portoffset</B> argument (or on each command in the file) executes the
53 <P>(If the <B>FILE YES</B> instruction appears in the
54 <B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file on the Tape
55 Coordinator machine associated with the specified port offset, then the Backup
56 System dumps data to the backup data file listed for that port offset in the
57 Tape Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, rather
58 than to tape. For the sake of clarity, the following text refers to
59 tapes only, but the Backup System handles backup data files in much the same
61 <P>The term <I>dumping</I> refers to copying a collection of data to tape
62 or a backup data file, and the resulting collection is termed a
63 <I>dump</I>. The set of tapes that contain one or more dumps is
64 called a <I>dump set</I>. The first dump in a dump set is its
65 <I>initial dump</I>, and any dumps subsequently added to the dump set (by
66 use of the <B>-append</B> argument) are <I>appended dumps</I>.
67 Creating appended dumps is optional, and appended dumps can be of different
68 volume sets, and at different dump levels, than the initial dump.
69 <P>A <I>full dump</I>, created at a full dump level in the dump hierarchy,
70 contains all of the data that existed at the time of the dump in the volumes
71 belonging to the volume set. An <I>incremental dump</I>, created at
72 an incremental dump level, contains only data that has changed since the
73 volume set was dumped at the incremental level's <I>parent dump
74 level</I> (the dump level immediately above the incremental level in the
75 hierarchy), which can be a full or incremental level. More
76 specifically, an incremental dump includes only the files and directories that
77 have modification timestamps later than the <I>clone date</I> of the
78 volume included at the parent dump level. For backup and read-only
79 volumes, the clone date is the time at which the volume was cloned from its
80 read/write source before being included in the parent dump; for
81 read/write volumes, it represents the time at which the volume was locked for
82 inclusion in the parent dump. The clone date appears in the <VAR>clone
83 date</VAR> field of the output from the <B>backup volinfo</B>
84 command. As an example, an incremental dump at the
85 <B>/full/week1/thursday</B> level includes only files and directories that
86 have changed since the volume set was dumped at the <B>/full/week1</B>
88 <P><B>Initiating different types of dump operations</B>
89 <P>To initiate a dump operation that is to start as soon as the relevant Tape
90 Coordinator is available, provide only the <B>-volumeset</B>,
91 <B>-dump</B>, <B>-portoffset</B>, and optionally <B>-append</B>
92 options. To schedule a single <B>backup dump</B> command to execute
93 in the future, also include the <B>-at</B> argument to specify the start
95 <P>To append a dump to an existing dump set, include the <B>-append</B>
96 flag. The Backup System imposes the following conditions on appended
99 <P><LI>If writing to tape, the Tape Coordinator checks that it is the final one
100 in a dump set for which there are complete and valid tape and dump records in
101 the Backup Database. If not, it rejects the tape and requests an
102 acceptable one. The operator can use the <B>-dbadd</B> argument to
103 the <B>backup scantape</B> command to insert the necessary records into
105 <P><LI>The most recent dump on the tape or in the backup data file must have
106 completed successfully.
107 <P><LI>The dump set must begin with an initial dump that is recorded in the
108 Backup Database. If there are no dumps on the tape, then the Backup
109 System treats the dump operation as an initial dump and imposes the relevant
110 requirements (for example, checks the AFS tape name if appropriate).
112 <P>To schedule multiple dump operations, list the operations in the file named
113 by the <B>-file</B> argument. Optionally include the <B>-at</B>
114 argument to specify when the <B>backup</B> command interpreter reads the
115 file; otherwise it reads it immediately. Do not combine the
116 <B>-file</B> argument with the command's first three arguments or the
117 <B>-append</B> or <B>-n</B> flags. The commands in the file can
118 include any of the <B>backup dump</B> command's arguments, including
119 the <B>-at</B> argument to schedule them to run even later in the
121 <P>To generate a list of the volumes included in a dump, without actually
122 dumping them, combine the <B>-n</B> flag with the options to be used on
124 <P><B>How the Backup System executes a dump operation</B>
125 <P>Before beginning a dump operation, the Backup System verifies that there is
126 a Backup Database entry for the volume set, dump level, and port
127 offset. If the command is correctly formed and issued in interactive
128 mode, it is assigned a job number and added to the jobs list. List jobs
129 in interactive mode by using the <B>(backup) jobs</B> command;
130 terminate them with the <B>(backup) kill</B> command.
131 <P>After obtaining the list of volumes to dump from the Volume Location (VL)
132 Server, the Backup System sorts the list by site (server and
133 partition). It groups volumes from the same site together in the dump
134 to minimize the number of times the operator must change tapes during restore
136 <P>The dependence of an incremental dump on its parent means that a valid
137 parent dump must already exist for the Backup System to create its child
138 incremental dump. If the Backup System does not find a record of a dump
139 created at the immediate parent dump level, it looks in the Backup Database
140 for a dump created at one level higher in the hierarchy, and so on, up to the
141 full dump level if necessary. It creates an incremental dump at the
142 level one below the lowest valid parent dump set that it finds. If it
143 fails to find even a full dump, it dumps the volume set at the full dump
145 <P>If the Backup System is unable to access a volume during a dump operation,
146 it skips the volume and dumps the remaining volumes from the volume
147 set. Possible reasons a volume is inaccessible include server machine
148 or process outages, or that the volume was moved between the time the Volume
149 Location (VL) Server generated the list of sites for the volume in the volume
150 set and the time the Backup System actually attempts to dump the data in
151 it. After the first dumping pass, the Backup System attempts to dump
152 each volume it skipped. If it still cannot dump a volume and the
153 <B>ASK NO</B> instruction does not appear in the
154 <B>CFG_</B><VAR>device_name</VAR> file, it queries the operator as to
155 whether it needs to attempt to dump the volume again, omit the volume from the
156 dump, or halt the dump operation altogether. When prompted, the
157 operator can attempt to solve whatever problem prevented the Backup System
158 from accessing the volumes. If the <B>ASK NO</B> instruction
159 appears in the <B>CFG_</B><VAR>device_name</VAR> file, the Backup System
160 omits the volume from the dump.
161 <P>Before scheduling a dump operation, the Backup System verifies that the
162 date specified by the <B>-at</B> argument is in the future, and checks the
163 validity of the volume set, dump level and port offset as for a regular dump
164 operation. It checks the validity of the parameters again just before
165 actually running the scheduled operation.
166 <P>Before writing an initial dump to a tape that does not have a permanent
167 name on the label, the Backup System checks that the AFS tape name on the
168 label is acceptable. If desired, disable name checking by including the
169 <B>NAME_CHECK NO</B> instruction in the
170 <B>CFG_</B><VAR>device_name</VAR> file.
171 <P>If AFS tape name checking is enabled, the Backup System accepts the
172 following three types of values for the AFS tape name. If the name on
173 the label does not conform, the Backup System obtains a tape with an
174 acceptable label by invoking the <B>MOUNT</B> instruction in the
175 <B>CFG_</B><VAR>device_name</VAR> file or prompting the operator.
177 <P><LI>A name of the form
178 <VAR>volume_set_name.dump_level_name.tape_index</VAR>, where
179 <VAR>volume_set_name</VAR> matches the value of the <B>-volumeset</B>
180 argument, <VAR>dump_level_name</VAR> matches the last element in the pathname
181 value of the <B>-dump</B> argument, and <VAR>tape_index</VAR> reflects the
182 tape's place in a multitape dump set. As an example, the first
183 tape in a dump set for which the initial dump is of volume set <B>user</B>
184 at the dump level <B>/sunday2/monday</B> has AFS tape name
185 <B>user.monday.1</B>. If the label records this type
186 of AFS tape name, the Backup System retains the AFS tape name and writes the
188 <P><LI>The string <TT><NULL></TT>, which usually indicates that a backup
189 operator has used the <B>backup labeltape</B> command to write a label on
190 the tape, but did not include the <B>-name</B> argument to assign an AFS
191 tape name. Presumably, the operator did include the <B>-pname</B>
192 argument to assign a permanent name. If the label records a
193 <TT><NULL></TT> value, the Backup System constructs and records on the
194 label the appropriate AFS tape name, and writes the dump on the tape.
195 <P><LI>No value at all, because the tape has never been labeled or used in the
196 Backup System. As when the AFS tape name is <TT><NULL></TT>, the
197 Backup System constructs and records on the label the appropriate AFS tape
198 name, and writes the dump on the tape.
200 <P>To determine how much data it can write to a tape, the Tape Coordinator
201 reads the capacity recorded on the tape's label (placed there by
202 including the <B>-size</B> argument to the <B>backup labeltape</B>
203 command). If the label's capacity field is empty, the Tape
204 Coordinator uses the capacity recorded for the specified port offset in the
205 local <B>tapeconfig</B> file. If the capacity field in the
206 <B>tapeconfig</B> file is also empty, the Tape Coordinator uses the
207 maximum capacity of 2 TB.
208 <P>During a dump operation, the Tape Coordinator tracks how much data it has
209 written and stops shortly before it reaches what it believes is the
210 tape's capacity. If it is in the middle of writing the data for a
211 volume when it reaches that point, it writes a special marker that indicates
212 an interrupted volume and continues writing the volume on the next
213 tape. It can split a volume this way during both an initial and an
214 appended dump, and the fact that the volume resides on multiple tapes is
215 automatically recorded in the Backup Database.
216 <P>If the tape is actually larger than the expected capacity, then the Tape
217 Coordinator simply does not use the excess tape. If the tape is smaller
218 than the expected capacity, the Tape Coordinator can reach the end-of-tape
219 (EOT) unexpectedly while it is writing data. If the Tape Coordinator is
220 in the middle of the writing data from a volume, it obtains a new tape and
221 rewrites the entire contents of the interrupted volume to it. The data
222 from the volume that was written to the previous tape remains there, but is
224 <P>The Backup System allows recycling of tapes (writing a new dump set over an
225 old dump set that is no longer needed), but imposes the following
228 <P><LI>All dumps in the old dump set must be expired. The Backup System
229 always checks expiration dates, even when name checking is disabled.
230 <P><LI>If the tape to be recycled does not have a permanent name and name
231 checking is enabled, then the AFS tape name derived from the new initial
232 dump's volume set name and dump level name must match the AFS tape name
233 already recorded on the label.
234 <P><LI>The tape cannot already have data on it that belongs to the dump currently
235 being performed, because that implies that the operator or automated tape
236 device has not removed the previous tape from the drive, or has mistakenly
237 reinserted it. The Tape Coordinator generates the following message and
238 attempts to obtain another tape:
239 <PRE> Can't overwrite tape containing the dump in progress
242 <P><LI>The tape cannot contain data from a parent dump of the current
243 (incremental) dump, because overwriting a parent dump makes it impossible to
244 restore data from the current dump. The Tape Coordinator generates the
245 following message and attempts to obtain another tape:
246 <PRE> Can't overwrite the parent dump <VAR>parent_name</VAR> (<VAR>parent_dump_ID</VAR>)
250 <P>To recycle a tape before all dumps on it have expired or if the AFS tape
251 name is wrong, use the <B>backup labeltape</B> command to overwrite the
252 tape's label and remove all associated tape and dump records from the
254 <P>The Tape Coordinator's default response to this command is to access
255 the first tape by invoking the <B>MOUNT</B> instruction in the
256 <B>CFG_</B><VAR>device_name</VAR> file, or by prompting the backup operator
257 to insert the tape if there is no <B>MOUNT</B> instruction.
258 However, if the <B>AUTOQUERY NO</B> instruction appears in the
259 <B>CFG_</B><VAR>device_name</VAR> file, or if the issuer of the
260 <B>butc</B> command included the <B>-noautoquery</B> flag, the Tape
261 Coordinator instead expects the tape to be in the device already. If it
262 is not, the Tape Coordinator invokes the <B>MOUNT</B> instruction or
263 prompts the operator. It also invokes the <B>MOUNT</B> instruction
264 or prompts for any additional tapes needed to complete the dump
265 operation; the issuer must arrange to provide them.
266 <P><STRONG>Cautions</STRONG>
267 <P>If a dump operation is interrupted or fails for any reason, data from all
268 volumes written to tape before the interrupt are valid can be used in a
269 restore operation. The Backup Database includes an entry for the failed
270 dump and for each volume that was successfully dumped. See the <I>IBM
271 AFS Administration Guide</I> for information on dealing with interrupted
273 <P>If dumping to tape rather than a backup data file, it is best to use only
274 compatible tape devices (ones that can read the same type of tape).
275 Using compatible devices greatly simplifies restore operations. The
276 <B>-portoffset</B> argument to the <B>backup diskrestore</B> and
277 <B>backup volsetrestore</B> commands accepts multiple port offset numbers,
278 but the Backup System uses the first listed port offset when restoring all
279 full dumps, the second port offset when restoring all level 1 dumps, and so
280 on. At the very least, use compatible tape devices to perform dumps at
281 each level. If compatible tape devices are not used, the <B>backup
282 volrestore</B> command must be used to restore one volume at a time.
283 <P>Valid (unexpired) administrative tokens must be available to the
284 <B>backup</B> command interpreter both when it reads the file named by the
285 <B>-file</B> argument and when it runs each operation listed in the
286 file. Presumably, the issuer is scheduling dumps for times when no
287 human operator is present, and so must arrange for valid tokens to be
288 available on the local machine. One option is to issue all commands (or
289 run all scripts) on file server machines and use the <B>-localauth</B>
290 flag on the <B>backup</B> and <B>vos</B> commands. To protect
291 against improper access to the machine or the tokens, the machine must be
292 physically secure (perhaps even more protected than a Tape Coordinator machine
293 monitored by a human operator during operation). Also, if an unattended
294 dump requires multiple tapes, the operator must properly configure a tape
295 stacker or jukebox and the device configuration file.
296 <P>When the command is issued in regular (non-interactive) mode, the command
297 shell prompt does not return until the dump operation completes. To
298 avoid having to open additional connections, issue the command in interactive
299 mode, especially when including the <B>-at</B> argument to schedule dump
301 <P><STRONG>Options</STRONG>
304 </B><DD>Names the volume set to dump. The <B>-dump</B> argument must be
305 provided along with this one; do not combine them with the
306 <B>-file</B> argument. If using a temporary volume set, the
307 <B>vos dump</B> command must be issued within the interactive session in
308 which the <B>backup addvolset</B> command was issued with the
309 <B>-temporary</B> flag.
311 </B><DD>Specifies the complete pathname of the dump level at which to dump the
312 volume set. The <B>-volumeset</B> argument must be provided along
313 with this one; do not combine them with the <B>-file</B>
315 <P><DT><B>-portoffset
316 </B><DD>Specifies the port offset number of the Tape Coordinator handling the
317 tapes for this operation. It must be provided unless the default value
318 of 0 (zero) is appropriate; do not combine it with the <B>-file</B>
321 </B><DD>Specifies the date and time in the future at which to run the command, or
322 to read the file named by the <B>-file</B> argument. Provide a
323 value in the format <VAR>mm/dd/yyyy</VAR> [<VAR>hh:MM</VAR>], where the
324 month (<VAR>mm</VAR>), day (<VAR>dd</VAR>), and year (<VAR>yyyy</VAR>) are
325 required. Valid values for the year range from <B>1970</B> to
326 <B>2037</B>; higher values are not valid because the latest possible
327 date in the standard UNIX representation is in February 2038. The
328 Backup System automatically reduces any later date to the maximum
330 <P>The hour and minutes (<VAR>hh:MM</VAR>) are optional, but if provided
331 must be in 24-hour format (for example, the value <B>14:36</B>
332 represents 2:36 p.m.). If omitted, the time
333 defaults to midnight (00:00 hours).
334 <P>As an example, the value <B>04/23/1999 20:20</B> schedules the
335 command for 8:20 p.m. on 23 April 1999.
336 <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
337 because it accepts a multiword value which does not need to be enclosed in
338 double quotes or other delimiters, not because it accepts multiple
339 dates. Provide only one date (and optionally, time) definition.
342 </B><DD>Appends the dump onto the end of a tape that already contains data from
343 another dump. However, if the tape is not in fact part of an existing
344 dump set, the Backup System creates a new dump set using the parameters of
345 this dump. If the tape is not the last tape in the dump set, the Tape
346 Coordinator prompts for insertion of the appropriate tape. Do not
347 combine this argument with the <B>-file</B> argument.
349 </B><DD>Displays the names of volumes to be included in the indicated dump,
350 without actually performing the dump operation. Do not combine this
351 argument with the <B>-file</B> argument.
353 </B><DD>Specifies the local disk or AFS pathname of a file containing
354 <B>backup</B> commands. The Backup System reads the file
355 immediately, or at the time specified by the <B>-at</B> argument if it is
356 provided. A partial pathname is interpreted relative to the current
358 <P>Place each <B>backup dump</B> command on its own line in the indicated
359 file, using the same syntax as for the command line, but without the word
360 <B>backup</B> at the start of the line. Each command must include a
361 value for the <B>-volumeset</B> and <B>-dump</B> arguments, and for
362 the <B>-portoffset</B> argument unless the default value of 0 is
363 appropriate. Commands in the file can also include any of the
364 <B>backup dump</B> command's optional options. In the
365 following example file, the first command runs as soon as the Backup System
366 reads the file, whereas the other commands are themselves scheduled; the
367 specified date and time must be later than the date and time at which the
368 Backup System reads the file.
369 <PRE> dump user /sunday1/wednesday -port 1
370 dump sun4x_56 /sunday1/friday -port 2 -at 04/08/1999
371 dump sun4x_55 /sunday1/friday -port 2 -at 04/08/1999 02:00 -append
375 <P>Do not combine this argument with the <B>-volumeset</B>,
376 <B>-dump</B>, <B>-portoffset</B>, <B>-append</B>, or <B>-n</B>
379 </B><DD>Constructs a server ticket using a key from the local
380 <B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
381 interpreter presents it to the Backup Server, Volume Server and VL Server
382 during mutual authentication. Do not combine this flag with the
383 <B>-cell</B> argument. For more details, see the introductory
384 <B>backup</B> reference page.
386 </B><DD>Names the cell in which to run the command. Do not combine this
387 argument with the <B>-localauth</B> flag. For more details, see the
388 introductory <B>backup</B> reference page.
390 </B><DD>Prints the online help for this command. All other valid options
393 <P><STRONG>Output</STRONG>
394 <P>The command interpreter first generates a list of the volumes to be
395 included in the dump by matching the entries in the volume set against the
396 volumes listed in the Volume Location Database (VLDB). It prints the
397 list following the header:
398 <PRE> Preparing to dump the following volumes:
401 <P>The following message then indicates that the command interpreter has
402 passed the dump request to the appropriate Tape Coordinator for
407 <P>If the issuer includes the <B>-n</B> flag, the output is of the
409 <PRE> Starting dump of volume set '<VAR>volume set</VAR>' (dump set '<VAR>dump level</VAR>')
410 Total number of volumes : <VAR>number dumped</VAR>
411 Would have dumped the following volumes:
412 <VAR>list_of_volumes</VAR>
415 <P>where <VAR>list_of_volumes</VAR> identifies each volume by name and volume ID
417 <P>If the Tape Coordinator is unable to access a volume, it prints an error
418 message in its window and records the error in its log and error files.
419 <P><STRONG>Examples</STRONG>
420 <P>The following command dumps the volumes in the volume set called
421 <B>user</B> at the dump level <B>/full/sunday2/monday</B>. The
422 issuer places the necessary tapes in the device with port offset 5.
423 <PRE> % <B>backup dump -volumeset user -dump /full/sunday2/monday -portoffset 5</B>
424 Preparing to dump the following volumes:
425 user.jones.backup 387623900
426 user.pat.backup 486219245
427 user.smith.backup 597315841
433 <P>The following command displays the list of volumes to be dumped when the
434 user dumps the <B>sys_sun</B> volume set at the <B>/full</B> dump
436 <PRE> % <B>backup dump -volumeset sys_sun -dump /full -n</B>
437 Starting dump of volume set 'sys_sun' (dump set '/full')
438 Total number of volumes: 24
439 Would have dumped the following volumes:
441 sun4x_56.bin 124857241
449 <P>The following command schedules a dump of the volumes in the volume set
450 <B>user</B> at the dump level <B>/sunday2/monday1</B> for 11:00
451 p.m. on 14 June 1999. The appropriate Tape Coordinator
452 has port offset 0 (zero), so that argument is omitted.
453 <PRE> % <B>backup dump -volumeset user -dump /sunday2/monday1 -at 06/14/1999 23:00</B>
456 <P><STRONG>Privilege Required</STRONG>
457 <P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
458 every machine where the Backup Server or Volume Location (VL) Server is
459 running, and on every file server machine that houses an affected
460 volume. If the <B>-localauth</B> flag is included, the issuer must
461 instead be logged on to a server machine as the local superuser
463 <P><STRONG>Related Information</STRONG>
464 <P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
465 <P><A HREF="auarf061.htm#HDRBK_ADDDUMP">backup adddump</A>
466 <P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
467 <P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
468 <P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
469 <P><A HREF="auarf079.htm#HDRBK_LABELTAPE">backup labeltape</A>
470 <P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
471 <P><A HREF="auarf126.htm#HDRBUTC">butc</A>
473 <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>
474 <!-- Begin Footer Records ========================================== -->
476 <br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
478 <!-- End Footer Records ============================================ -->
479 <A NAME="Bot_Of_Page"></A>
git://git.openafs.org / openafs.git / blob