1 <?xml version="1.0" encoding="UTF-8"?>
2 <refentry id="backup_dump8">
4 <refentrytitle>backup dump</refentrytitle>
5 <manvolnum>8</manvolnum>
8 <refname>backup dump</refname>
9 <refpurpose>Creates a dump (dumps a volume set at a particular dump level)</refpurpose>
12 <title>Synopsis</title>
13 <para><emphasis role="bold">backup dump</emphasis> [<emphasis role="bold">-volumeset</emphasis> <<emphasis>volume set name</emphasis>>]
14 [<emphasis role="bold">-dump</emphasis> <<emphasis>dump level name</emphasis>>] [<emphasis role="bold">-portoffset</emphasis> <<emphasis>TC port offset</emphasis>>]
15 [<emphasis role="bold">-at</emphasis> <<emphasis>date/time to start dump</emphasis>>+] [<emphasis role="bold">-append</emphasis>] [<emphasis role="bold">-n</emphasis>]
16 [<emphasis role="bold">-file</emphasis> <<emphasis>load file</emphasis>>] [<emphasis role="bold">-localauth</emphasis>] [-<emphasis role="bold">cell</emphasis> <<emphasis>cell name</emphasis>>]
17 [<emphasis role="bold">-help</emphasis>]</para>
19 <para><emphasis role="bold">backup dump</emphasis> [<emphasis role="bold">-v</emphasis> <<emphasis>volume set name</emphasis>>] [<emphasis role="bold">-d</emphasis> <<emphasis>dump level name</emphasis>>]
20 [<emphasis role="bold">-p</emphasis> <<emphasis>TC port offset</emphasis>>] [<emphasis role="bold">-at</emphasis> <<emphasis>Date/time to start dump</emphasis>>+]
21 [<emphasis role="bold">-ap</emphasis>] [<emphasis role="bold">-n</emphasis>] [<emphasis role="bold">-f</emphasis> <<emphasis>load file</emphasis>>] [<emphasis role="bold">-l</emphasis>] [<emphasis role="bold">-c</emphasis> <<emphasis>cell name</emphasis>>]
22 [<emphasis role="bold">-h</emphasis>]</para>
26 <title>Description</title>
27 <para>The <emphasis role="bold">backup dump</emphasis> command either dumps the volume set specified by the
28 <emphasis role="bold">-volumeset</emphasis> argument at the dump level specified by the <emphasis role="bold">-dump</emphasis>
29 argument and creates a Backup Database dump record about it, or executes
30 the dump instructions listed in the file named by the <emphasis role="bold">-file</emphasis>
31 argument. The Tape Coordinator indicated by the <emphasis role="bold">-portoffset</emphasis> argument
32 (or on each command in the file) executes the operation.</para>
34 <para>(If the <computeroutput>FILE YES</computeroutput> instruction appears in the
35 <replaceable>/usr/afs/backup/CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file on the Tape Coordinator machine
36 associated with the specified port offset, then the Backup System dumps
37 data to the backup data file listed for that port offset in the Tape
38 Coordinator's <replaceable>/usr/afs/backup/tapeconfig</replaceable> file, rather than to tape. For
39 the sake of clarity, the following text refers to tapes only, but the
40 Backup System handles backup data files in much the same way.)</para>
42 <para>The term <emphasis>dumping</emphasis> refers to copying a collection of data to tape or a
43 backup data file, and the resulting collection is termed a <emphasis>dump</emphasis>. The
44 set of tapes that contain one or more dumps is called a <emphasis>dump set</emphasis>. The
45 first dump in a dump set is its <emphasis>initial dump</emphasis>, and any dumps
46 subsequently added to the dump set (by use of the <emphasis role="bold">-append</emphasis> argument) are
47 <emphasis>appended dumps</emphasis>. Creating appended dumps is optional, and appended
48 dumps can be of different volume sets, and at different dump levels, than
49 the initial dump.</para>
51 <para>A <emphasis>full dump</emphasis>, created at a full dump level in the dump hierarchy,
52 contains all of the data that existed at the time of the dump in the
53 volumes belonging to the volume set. An <emphasis>incremental dump</emphasis>, created at an
54 incremental dump level, contains only data that has changed since the
55 volume set was dumped at the incremental level's <emphasis>parent dump level</emphasis> (the
56 dump level immediately above the incremental level in the hierarchy),
57 which can be a full or incremental level. More specifically, an
58 incremental dump includes only the files and directories that have
59 modification timestamps later than the <emphasis>clone date</emphasis> of the volume
60 included at the parent dump level. For backup and read-only volumes, the
61 clone date is the time at which the volume was cloned from its read/write
62 source before being included in the parent dump; for read/write volumes,
63 it represents the time at which the volume was locked for inclusion in the
64 parent dump. The clone date appears in the <emphasis>clone date</emphasis> field of the
65 output from the <emphasis role="bold">backup volinfo</emphasis> command. As an example, an incremental
66 dump at the <computeroutput>/full/week1/thursday</computeroutput> level includes only files and
67 directories that have changed since the volume set was dumped at the
68 <computeroutput>/full/week1</computeroutput> level.</para>
71 <title>Initiating different types of dump operations</title>
72 <para>To initiate a dump operation that is to start as soon as the relevant Tape
73 Coordinator is available, provide only the <emphasis role="bold">-volumeset</emphasis>, <emphasis role="bold">-dump</emphasis>,
74 <emphasis role="bold">-portoffset</emphasis>, and optionally <emphasis role="bold">-append</emphasis> options. To schedule a single
75 <emphasis role="bold">backup dump</emphasis> command to execute in the future, also include the <emphasis role="bold">-at</emphasis>
76 argument to specify the start time.</para>
78 <para>To append a dump to an existing dump set, include the <emphasis role="bold">-append</emphasis> flag. The
79 Backup System imposes the following conditions on appended dumps:</para>
83 <para>If writing to tape, the Tape Coordinator checks that it is the final one
84 in a dump set for which there are complete and valid tape and dump records
85 in the Backup Database. If not, it rejects the tape and requests an
86 acceptable one. The operator can use the <emphasis role="bold">-dbadd</emphasis> argument to the
87 <emphasis role="bold">backup scantape</emphasis> command to insert the necessary records into the
92 <para>The most recent dump on the tape or in the backup data file must have
93 completed successfully.</para>
97 <para>The dump set must begin with an initial dump that is recorded in the
98 Backup Database. If there are no dumps on the tape, then the Backup System
99 treats the dump operation as an initial dump and imposes the relevant
100 requirements (for example, checks the AFS tape name if appropriate).</para>
104 <para>To schedule multiple dump operations, list the operations in the file
105 named by the <emphasis role="bold">-file</emphasis> argument. Optionally include the <emphasis role="bold">-at</emphasis> argument to
106 specify when the <emphasis role="bold">backup</emphasis> command interpreter reads the file; otherwise
107 it reads it immediately. Do not combine the <emphasis role="bold">-file</emphasis> argument with the
108 command's first three arguments or the <emphasis role="bold">-append</emphasis> or <emphasis role="bold">-n</emphasis> flags. The
109 commands in the file can include any of the <emphasis role="bold">backup dump</emphasis> command's
110 arguments, including the <emphasis role="bold">-at</emphasis> argument to schedule them to run even
111 later in the future.</para>
113 <para>To generate a list of the volumes included in a dump, without actually
114 dumping them, combine the <emphasis role="bold">-n</emphasis> flag with the options to be used on the
115 actual command.</para>
119 <title>How the Backup System executes a dump operation</title>
120 <para>Before beginning a dump operation, the Backup System verifies that there
121 is a Backup Database entry for the volume set, dump level, and port
122 offset. If the command is correctly formed and issued in interactive mode,
123 it is assigned a job number and added to the jobs list. List jobs in
124 interactive mode by using the <emphasis role="bold">backup jobs</emphasis> command; terminate them with
125 the <emphasis role="bold">backup kill</emphasis> command.</para>
127 <para>After obtaining the list of volumes to dump from the Volume Location (VL)
128 Server, the Backup System sorts the list by site (server and
129 partition). It groups volumes from the same site together in the dump to
130 minimize the number of times the operator must change tapes during restore
133 <para>The dependence of an incremental dump on its parent means that a valid
134 parent dump must already exist for the Backup System to create its child
135 incremental dump. If the Backup System does not find a record of a dump
136 created at the immediate parent dump level, it looks in the Backup
137 Database for a dump created at one level higher in the hierarchy, and so
138 on, up to the full dump level if necessary. It creates an incremental dump
139 at the level one below the lowest valid parent dump set that it finds. If
140 it fails to find even a full dump, it dumps the volume set at the full
143 <para>If the Backup System is unable to access a volume during a dump operation,
144 it skips the volume and dumps the remaining volumes from the volume
145 set. Possible reasons a volume is inaccessible include server machine or
146 process outages, or that the volume was moved between the time the Volume
147 Location (VL) Server generated the list of sites for the volume in the
148 volume set and the time the Backup System actually attempts to dump the
149 data in it. After the first dumping pass, the Backup System attempts to
150 dump each volume it skipped. If it still cannot dump a volume and the
151 <computeroutput>ASK NO</computeroutput> instruction does not appear in the <replaceable>CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file,
152 it queries the operator as to whether it needs to attempt to dump the
153 volume again, omit the volume from the dump, or halt the dump operation
154 altogether. When prompted, the operator can attempt to solve whatever
155 problem prevented the Backup System from accessing the volumes. If the
156 <computeroutput>ASK NO</computeroutput> instruction appears in the <replaceable>CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file, the
157 Backup System omits the volume from the dump.</para>
159 <para>Before scheduling a dump operation, the Backup System verifies that the
160 date specified by the <emphasis role="bold">-at</emphasis> argument is in the future, and checks the
161 validity of the volume set, dump level and port offset as for a regular
162 dump operation. It checks the validity of the parameters again just before
163 actually running the scheduled operation.</para>
165 <para>Before writing an initial dump to a tape that does not have a permanent
166 name on the label, the Backup System checks that the AFS tape name on the
167 label is acceptable. If desired, disable name checking by including the
168 <computeroutput>NAME_CHECK NO</computeroutput> instruction in the <replaceable>CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file.</para>
170 <para>If AFS tape name checking is enabled, the Backup System accepts the
171 following three types of values for the AFS tape name. If the name on the
172 label does not conform, the Backup System obtains a tape with an
173 acceptable label by invoking the <computeroutput>MOUNT</computeroutput> instruction in the
174 <replaceable>CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file or prompting the operator.</para>
178 <para>A name of the form <emphasis>volume_set_name.dump_level_name.tape_index</emphasis>, where
179 <emphasis>volume_set_name</emphasis> matches the value of the <emphasis role="bold">-volumeset</emphasis> argument,
180 <emphasis>dump_level_name</emphasis> matches the last element in the pathname value of the
181 <emphasis role="bold">-dump</emphasis> argument, and <emphasis>tape_index</emphasis> reflects the tape's place in a
182 multitape dump set. As an example, the first tape in a dump set for which
183 the initial dump is of volume set <computeroutput>user</computeroutput> at the dump level
184 <computeroutput>/sunday2/monday</computeroutput> has AFS tape name <computeroutput>user.monday.1</computeroutput>. If the label
185 records this type of AFS tape name, the Backup System retains the AFS tape
186 name and writes the dump to the tape.</para>
190 <para>The string <computeroutput><NULL></computeroutput>, which usually indicates that a backup operator
191 has used the <emphasis role="bold">backup labeltape</emphasis> command to write a label on the tape, but
192 did not include the <emphasis role="bold">-name</emphasis> argument to assign an AFS tape
193 name. Presumably, the operator did include the <emphasis role="bold">-pname</emphasis> argument to
194 assign a permanent name. If the label records a <computeroutput><NULL></computeroutput> value, the
195 Backup System constructs and records on the label the appropriate AFS tape
196 name, and writes the dump on the tape.</para>
200 <para>No value at all, because the tape has never been labeled or used in the
201 Backup System. As when the AFS tape name is <computeroutput><NULL></computeroutput>, the Backup
202 System constructs and records on the label the appropriate AFS tape name,
203 and writes the dump on the tape.</para>
207 <para>To determine how much data it can write to a tape, the Tape Coordinator
208 reads the capacity recorded on the tape's label (placed there by including
209 the <emphasis role="bold">-size</emphasis> argument to the <emphasis role="bold">backup labeltape</emphasis> command). If the label's
210 capacity field is empty, the Tape Coordinator uses the capacity recorded
211 for the specified port offset in the local <replaceable>tapeconfig</replaceable> file. If the
212 capacity field in the <replaceable>tapeconfig</replaceable> file is also empty, the Tape
213 Coordinator uses the maximum capacity of 2 TB.</para>
215 <para>During a dump operation, the Tape Coordinator tracks how much data it has
216 written and stops shortly before it reaches what it believes is the tape's
217 capacity. If it is in the middle of writing the data for a volume when it
218 reaches that point, it writes a special marker that indicates an
219 interrupted volume and continues writing the volume on the next tape. It
220 can split a volume this way during both an initial and an appended dump,
221 and the fact that the volume resides on multiple tapes is automatically
222 recorded in the Backup Database.</para>
224 <para>If the tape is actually larger than the expected capacity, then the Tape
225 Coordinator simply does not use the excess tape. If the tape is smaller
226 than the expected capacity, the Tape Coordinator can reach the end-of-tape
227 (EOT) unexpectedly while it is writing data. If the Tape Coordinator is in
228 the middle of the writing data from a volume, it obtains a new tape and
229 rewrites the entire contents of the interrupted volume to it. The data
230 from the volume that was written to the previous tape remains there, but
231 is never used.</para>
233 <para>The Backup System allows recycling of tapes (writing a new dump set over
234 an old dump set that is no longer needed), but imposes the following
239 <para>All dumps in the old dump set must be expired. The Backup System always
240 checks expiration dates, even when name checking is disabled.</para>
244 <para>If the tape to be recycled does not have a permanent name and name
245 checking is enabled, then the AFS tape name derived from the new initial
246 dump's volume set name and dump level name must match the AFS tape name
247 already recorded on the label.</para>
251 <para>The tape cannot already have data on it that belongs to the dump currently
252 being performed, because that implies that the operator or automated tape
253 device has not removed the previous tape from the drive, or has mistakenly
254 reinserted it. The Tape Coordinator generates the following message and
255 attempts to obtain another tape:</para>
258 Can't overwrite tape containing the dump in progress
263 <para>The tape cannot contain data from a parent dump of the current
264 (incremental) dump, because overwriting a parent dump makes it impossible
265 to restore data from the current dump. The Tape Coordinator generates the
266 following message and attempts to obtain another tape:</para>
269 Can't overwrite the parent dump I&lt;parent_name&gt; (I&lt;parent_dump_ID&gt;)
274 <para>To recycle a tape before all dumps on it have expired or if the AFS tape
275 name is wrong, use the <emphasis role="bold">backup labeltape</emphasis> command to overwrite the tape's
276 label and remove all associated tape and dump records from the Backup
279 <para>The Tape Coordinator's default response to this command is to access the
280 first tape by invoking the <computeroutput>MOUNT</computeroutput> instruction in the
281 <replaceable>CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file, or by prompting the backup operator to insert
282 the tape if there is no <computeroutput>MOUNT</computeroutput> instruction. However, if the <computeroutput>AUTOQUERY
283 NO</computeroutput> instruction appears in the <replaceable>CFG_</replaceable><emphasis>device_name</emphasis><replaceable></replaceable> file, or if the
284 issuer of the <emphasis role="bold">butc</emphasis> command included the <emphasis role="bold">-noautoquery</emphasis> flag, the Tape
285 Coordinator instead expects the tape to be in the device already. If it is
286 not, the Tape Coordinator invokes the <computeroutput>MOUNT</computeroutput> instruction or prompts the
287 operator. It also invokes the <computeroutput>MOUNT</computeroutput> instruction or prompts for any
288 additional tapes needed to complete the dump operation; the issuer must
289 arrange to provide them.</para>
294 <title>Cautions</title>
295 <para>If a dump operation is interrupted or fails for any reason, data from all
296 volumes written to tape before the interrupt are valid can be used in a
297 restore operation. The Backup Database includes an entry for the failed
298 dump and for each volume that was successfully dumped. See the <emphasis>IBM AFS
299 Administration Guide</emphasis> for information on dealing with interrupted dumps.</para>
301 <para>If dumping to tape rather than a backup data file, it is best to use only
302 compatible tape devices (ones that can read the same type of tape). Using
303 compatible devices greatly simplifies restore operations. The
304 <emphasis role="bold">-portoffset</emphasis> argument to the <emphasis role="bold">backup diskrestore</emphasis> and <emphasis role="bold">backup
305 volsetrestore</emphasis> commands accepts multiple port offset numbers, but the
306 Backup System uses the first listed port offset when restoring all full
307 dumps, the second port offset when restoring all level 1 dumps, and so
308 on. At the very least, use compatible tape devices to perform dumps at
309 each level. If compatible tape devices are not used, the <emphasis role="bold">backup
310 volrestore</emphasis> command must be used to restore one volume at a time.</para>
312 <para>Valid (unexpired) administrative tokens must be available to the <emphasis role="bold">backup</emphasis>
313 command interpreter both when it reads the file named by the <emphasis role="bold">-file</emphasis>
314 argument and when it runs each operation listed in the file. Presumably,
315 the issuer is scheduling dumps for times when no human operator is
316 present, and so must arrange for valid tokens to be available on the local
317 machine. One option is to issue all commands (or run all scripts) on file
318 server machines and use the <emphasis role="bold">-localauth</emphasis> flag on the <emphasis role="bold">backup</emphasis> and <emphasis role="bold">vos</emphasis>
319 commands. To protect against improper access to the machine or the tokens,
320 the machine must be physically secure (perhaps even more protected than a
321 Tape Coordinator machine monitored by a human operator during
322 operation). Also, if an unattended dump requires multiple tapes, the
323 operator must properly configure a tape stacker or jukebox and the device
324 configuration file.</para>
326 <para>When the command is issued in regular (non-interactive) mode, the command
327 shell prompt does not return until the dump operation completes. To avoid
328 having to open additional connections, issue the command in interactive
329 mode, especially when including the <emphasis role="bold">-at</emphasis> argument to schedule dump
334 <title>Options</title>
337 <term><emphasis role="bold">-volumeset</emphasis> <<emphasis>volume set name</emphasis>></term>
339 <para>Names the volume set to dump. The <emphasis role="bold">-dump</emphasis> argument must be provided along
340 with this one; do not combine them with the <emphasis role="bold">-file</emphasis> argument. If using a
341 temporary volume set, the <emphasis role="bold">vos dump</emphasis> command must be issued within the
342 interactive session in which the <emphasis role="bold">backup addvolset</emphasis> command was issued
343 with the <emphasis role="bold">-temporary</emphasis> flag.</para>
348 <term><emphasis role="bold">-dump</emphasis> <<emphasis>dump level name</emphasis>></term>
350 <para>Specifies the complete pathname of the dump level at which to dump the
351 volume set. The <emphasis role="bold">-volumeset</emphasis> argument must be provided along with this
352 one; do not combine them with the <emphasis role="bold">-file</emphasis> argument.</para>
357 <term><emphasis role="bold">-portoffset</emphasis> <<emphasis>TC port offset</emphasis>></term>
359 <para>Specifies the port offset number of the Tape Coordinator handling the
360 tapes for this operation. It must be provided unless the default value of
361 0 (zero) is appropriate; do not combine it with the <emphasis role="bold">-file</emphasis> argument.</para>
366 <term><emphasis role="bold">-at</emphasis> <<emphasis>date/time to start dump</emphasis>></term>
368 <para>Specifies the date and time in the future at which to run the command, or
369 to read the file named by the <emphasis role="bold">-file</emphasis> argument. Provide a value in the
370 format <emphasis>mm/dd/yyyy</emphasis> [<emphasis>hh:MM</emphasis>], where the month (<emphasis>mm</emphasis>), day (<emphasis>dd</emphasis>), and
371 year (<emphasis>yyyy</emphasis>) are required. Valid values for the year range from <computeroutput>1970</computeroutput>
372 to <computeroutput>2037</computeroutput>; higher values are not valid because the latest possible date
373 in the standard UNIX representation is in February 2038. The Backup System
374 automatically reduces any later date to the maximum value.</para>
376 <para>The hour and minutes (<emphasis>hh:MM</emphasis>) are optional, but if provided must be in
377 24-hour format (for example, the value <computeroutput>14:36</computeroutput> represents 2:36 p.m.). If
378 omitted, the time defaults to midnight (00:00 hours).</para>
380 <para>As an example, the value 04/23/1999 20:20 schedules the command for 8:20
381 p.m. on 23 April 1999.</para>
386 <term><emphasis role="bold">-append</emphasis></term>
388 <para>Appends the dump onto the end of a tape that already contains data from
389 another dump. However, if the tape is not in fact part of an existing dump
390 set, the Backup System creates a new dump set using the parameters of this
391 dump. If the tape is not the last tape in the dump set, the Tape
392 Coordinator prompts for insertion of the appropriate tape. Do not combine
393 this argument with the <emphasis role="bold">-file</emphasis> argument.</para>
398 <term><emphasis role="bold">-n</emphasis></term>
400 <para>Displays the names of volumes to be included in the indicated dump,
401 without actually performing the dump operation. Do not combine this
402 argument with the <emphasis role="bold">-file</emphasis> argument.</para>
407 <term><emphasis role="bold">-file</emphasis> <<emphasis>load file</emphasis>></term>
409 <para>Specifies the local disk or AFS pathname of a file containing <emphasis role="bold">backup</emphasis>
410 commands. The Backup System reads the file immediately, or at the time
411 specified by the <emphasis role="bold">-at</emphasis> argument if it is provided. A partial pathname is
412 interpreted relative to the current working directory.</para>
414 <para>Place each <emphasis role="bold">backup dump</emphasis> command on its own line in the indicated file,
415 using the same syntax as for the command line, but without the word
416 <emphasis role="bold">backup</emphasis> at the start of the line. Each command must include a value for
417 the <emphasis role="bold">-volumeset</emphasis> and <emphasis role="bold">-dump</emphasis> arguments, and for the <emphasis role="bold">-portoffset</emphasis>
418 argument unless the default value of 0 is appropriate. Commands in the
419 file can also include any of the <emphasis role="bold">backup dump</emphasis> command's optional
420 options. In the following example file, the first command runs as soon as
421 the Backup System reads the file, whereas the other commands are
422 themselves scheduled; the specified date and time must be later than the
423 date and time at which the Backup System reads the file.</para>
426 dump user /sunday1/wednesday -port 1
427 dump sun4x_56 /sunday1/friday -port 2 -at 04/08/1999
428 dump sun4x_55 /sunday1/friday -port 2 -at 04/08/1999 02:00 -append
431 <para>Do not combine this argument with the <emphasis role="bold">-volumeset</emphasis>, <emphasis role="bold">-dump</emphasis>,
432 <emphasis role="bold">-portoffset</emphasis>, <emphasis role="bold">-append</emphasis>, or <emphasis role="bold">-n</emphasis> options.</para>
437 <term><emphasis role="bold">-localauth</emphasis></term>
439 <para>Constructs a server ticket using a key from the local
440 <replaceable>/usr/afs/etc/KeyFile</replaceable> file. The <emphasis role="bold">backup</emphasis> command interpreter presents
441 it to the Backup Server, Volume Server and VL Server during mutual
442 authentication. Do not combine this flag with the <emphasis role="bold">-cell</emphasis> argument. For
443 more details, see <link linkend="backup8">backup(8)</link>.</para>
448 <term><emphasis role="bold">-cell</emphasis> <<emphasis>cell name</emphasis>></term>
450 <para>Names the cell in which to run the command. Do not combine this argument
451 with the <emphasis role="bold">-localauth</emphasis> flag. For more details, see <link linkend="backup8">backup(8)</link>.</para>
456 <term><emphasis role="bold">-help</emphasis></term>
458 <para>Prints the online help for this command. All other valid options are
466 <title>Output</title>
467 <para>The command interpreter first generates a list of the volumes to be
468 included in the dump by matching the entries in the volume set against the
469 volumes listed in the Volume Location Database (VLDB). It prints the list
470 following the header:</para>
473 Preparing to dump the following volumes:
476 <para>The following message then indicates that the command interpreter has
477 passed the dump request to the appropriate Tape Coordinator for
484 <para>If the issuer includes the <emphasis role="bold">-n</emphasis> flag, the output is of the following
488 Starting dump of volume set '&lt;volume set&gt;' (dump set '&lt;dump level&gt;')
489 Total number of volumes : &lt;number dumped&gt;
490 Would have dumped the following volumes:
491 &lt;list_of_volumes&gt;
494 <para>where <emphasis>list_of_volumes</emphasis> identifies each volume by name and volume ID
497 <para>If the Tape Coordinator is unable to access a volume, it prints an error
498 message in its window and records the error in its log and error files.</para>
502 <title>Examples</title>
503 <para>The following command dumps the volumes in the volume set called <computeroutput>user</computeroutput>
504 at the dump level <computeroutput>/full/sunday2/monday</computeroutput>. The issuer places the necessary
505 tapes in the device with port offset 5.</para>
508 % backup dump -volumeset user -dump /full/sunday2/monday -portoffset 5
509 Preparing to dump the following volumes:
510 user.jones.backup 387623900
511 user.pat.backup 486219245
512 user.smith.backup 597315841
518 <para>The following command displays the list of volumes to be dumped when the
519 user dumps the <computeroutput>sys_sun</computeroutput> volume set at the <computeroutput>/full</computeroutput> dump level.</para>
522 % backup dump -volumeset sys_sun -dump /full -n
523 Starting dump of volume set 'sys_sun' (dump set '/full')
524 Total number of volumes: 24
525 Would have dumped the following volumes:
527 sun4x_56.bin 124857241
535 <para>The following command schedules a dump of the volumes in the volume set
536 <computeroutput>user</computeroutput> at the dump level <computeroutput>/sunday2/monday1</computeroutput> for 11:00 p.m. on 14 June
537 1999. The appropriate Tape Coordinator has port offset 0 (zero), so that
538 argument is omitted.</para>
541 % backup dump -volumeset user -dump /sunday2/monday1 -at 06/14/1999 23:00
546 <title>Privilege Required</title>
547 <para>The issuer must be listed in the <replaceable>/usr/afs/etc/UserList</replaceable> file on every
548 machine where the Backup Server or Volume Location (VL) Server is running,
549 and on every file server machine that houses an affected volume. If the
550 <emphasis role="bold">-localauth</emphasis> flag is included, the issuer must instead be logged on to a
551 server machine as the local superuser <computeroutput>root</computeroutput>.</para>
555 <title>See Also</title>
556 <para><link linkend="butc5">butc(5)</link>,
557 <link linkend="backup8">backup(8)</link>,
558 <link linkend="backup_adddump8">backup_adddump(8)</link>,
559 <link linkend="backup_addvolentry8">backup_addvolentry(8)</link>,
560 <link linkend="backup_addvolset8">backup_addvolset(8)</link>,
561 <link linkend="backup_diskrestore8">backup_diskrestore(8)</link>,
562 <link linkend="backup_labeltape8">backup_labeltape(8)</link>,
563 <link linkend="backup_volrestore8">backup_volrestore(8)</link>,
564 <link linkend="butc8">butc(8)</link></para>
568 <title>Copyright</title>
569 <para>IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.</para>
571 <para>This documentation is covered by the IBM Public License Version 1.0. It was
572 converted from HTML to POD by software written by Chas Williams and Russ
573 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.</para>