3 backup dumpinfo - Displays a dump record from the Backup Database
7 backup dumpinfo [B<-ndumps> I<no. of dumps>] [B<-id> I<dump id>]
8 [B<-verbose>] [B<-localauth>] [B<-cell> I<cell name>] [B<-help> ]
10 backup dumpi [B<-n> I<no. of dumps>] [B<-i> I<dump id>]
11 [B<-v>] [B<-l>] [B<-c> I<cell name>] [B<-h>]
15 The C<backup dumpinfo> command formats and displays the Backup Database
16 record for the specified dumps. To specify how many of the most recent
17 dumps to display, starting with the newest one and going back in time,
18 use the B<-ndumps> argument. To display more detailed information about a
19 single dump, use the B<-id> argument. To display the records for the 10
20 most recent dumps, omit both the B<-ndumps> and B<-id> arguments.
22 The B<-verbose> flag produces very detailed information that is useful
23 mostly for debugging purposes. It can be combined only with the B<-id>
30 =item B<-ndumps> I<no. of dumps>
32 Displays the Backup Database record for each of the specified
33 number of dumps that were most recently performed. If the
34 database contains fewer dumps than are requested, the output
35 includes the records for all existing dumps. Do not combine
36 this argument with the B<-id> or B<-verbose> options; omit all
37 options to display the records for the last 10 dumps.
39 =item B<-id> I<dump id>
41 Specifies the dump ID number of a single dump for which to
42 display the Backup Database record. Precede the I<dump id> value
43 with the B<-id> switch; otherwise, the command interpreter
44 interprets it as the value of the B<-ndumps> argument. Combine
45 this argument with the B<-verbose> flag, but not with the B<-ndumps>
46 argument; omit all options to display the records for the last
51 Provides more detailed information about the dump specified
52 with the B<-id> argument, which must be provided along with it. Do
53 not combine this flag with the B<-ndumps> argument.
57 Constructs a server ticket using a key from the local
58 B</usr/afs/etc/KeyFile> file. The C<backup> command interpreter
59 presents it to the Backup Server, Volume Server and VL Server
60 during mutual authentication. Do not combine this flag with the
61 B<-cell> argument. For more details, see the introductory L<backup(1)> reference page.
63 =item B<-cell> I<cell name>
65 Names the cell in which to run the command. Do not combine this
66 argument with the B<-localauth> flag. For more details, see the
67 introductory L<backup(1)> reference page.
72 Prints the online help for this command. All other valid
79 If the B<-ndumps> argument is provided, the output presents the following
80 information in table form, with a separate line for each dump:
90 The dump ID number of the dump's parent dump. A value of 0
91 (zero) identifies a full dump.
95 The depth in the dump hierarchy of the dump level used to
96 create the dump. A value of 0 (zero) identifies a full dump, in
97 which case the value in the C<parentid> field is also 0. A value
98 of 1 or greater indicates an incremental dump made at the
99 corresponding level in the dump hierarchy.
103 The date and time at which the Backup System started the dump
104 operation that created the dump.
108 The number of tapes that contain the data in the dump. A value
109 of 0 (zero) indicates that the dump operation was terminated or
110 failed. Use the C<backup deletedump> command to remove such
115 The number of volumes from which the dump includes data. If a
116 volume spans tapes, it is counted twice. A value of 0 (zero)
117 indicates that the dump operation was terminated or failed; the
118 value in the nt field is also 0 in this case.
122 The dump name in the form
124 I<volume_set_name>.I<dump_level_name> (I<initial_dump_ID>)
126 where I<volume_set_name> is the name of the volume set, and
127 I<dump_level_name> is the last element in the dump level pathname
128 at which the volume set was dumped.
130 The I<initial_dump_ID>, if displayed, is the dump ID of the
131 initial dump in the dump set to which this dump belongs. If
132 there is no value in parentheses, the dump is the initial dump
133 in a dump set that has no appended dumps.
137 If the B<-id> argument is provided alone, the first line of output begins
138 with the string C<Dump> and reports information for the entire dump in
139 the following fields:
149 The depth in the dump hierarchy of the dump level used to
150 create the dump. A value of 0 (zero) identifies a full dump. A
151 value of 1 (one) or greater indicates an incremental dump made
152 at the specified level in the dump hierarchy.
156 The number of volumes for which the dump includes data.
160 The date and time at which the dump operation began.
164 If an XBSA server was the backup medium for the dump (rather than a
165 tape device or backup data file), the following line appears next:
167 Backup Service: I<XBSA_program>: Server: I<hostname>
169 where I<XBSA_program> is the name of the XBSA-compliant program and
170 I<hostname> is the name of the machine on which the program runs.
172 Next the output includes an entry for each tape that houses volume
173 data from the dump. Following the string C<Tape>, the first two lines of
174 each entry report information about that tape in the following fields:
180 The tape's permanent name if it has one, or its AFS tape name
181 otherwise, and its tape ID number in parentheses.
185 The number of volumes for which this tape includes dump data.
189 The date and time at which the Tape Coordinator began writing
194 Following another blank line, the tape-specific information concludes
195 with a table that includes a line for each volume dump on the tape.
196 The information appears in columns with the following headings:
202 The relative position of each volume in this tape or file. On a
203 tape, the counter begins at position 2 (the tape label occupies
204 position 1), and increments by one for each volume. For volumes
205 in a backup data file, the position numbers start with 1 and do
206 not usually increment only by one, because each is the ordinal
207 of the 16 KB offset in the file at which the volume's data
208 begins. The difference between the position numbers therefore
209 indicates how many 16 KB blocks each volume's data occupies.
210 For example, if the second volume is at position 5 and the
211 third volume in the list is at position 9, that means that the
212 dump of the second volume occupies 64 KB (four 16-KB blocks) of
217 For a backup or read-only volume, the time at which it was
218 cloned from its read/write source. For a Read/Write volume, it
219 is the same as the dump creation date reported on the first
224 The number of bytes of data in the dump of the volume.
228 The volume name, complete with C<.backup> or C<.readonly> extension
233 If both the B<-id> and B<-verbose> options are provided, the output is
234 divided into several sections:
240 The first section, headed by the underlined string C<Dump>, includes
241 information about the entire dump. The fields labeled C<id>, C<level>,
242 C<created>, and C<nVolumes> report the same values (though in a
243 different order) as appear on the first line of output when the
244 B<-id> argument is provided by itself. Other fields of potential
245 interest to the backup operator are:
251 The dump's I<group ID number>, which is recorded in the
252 dump's Backup Database record if the B<GROUPID> instruction
253 appears in the Tape Coordinator's
254 B</usr/afs/backup/CFG_>I<tcid> file when the dump is created.
258 The number of tapes that contain the dump set to which
261 =item B<Start Tape Seq>
263 The ordinal of the tape on which this dump begins in the
264 set of tapes that contain the dump set.
270 For each tape that contains data from this dump, there follows a
271 section headed by the underlined string C<Tape>. The fields labeled
272 C<name>, C<written>, and C<nVolumes> report the same values (though in a
273 different order) as appear on the second and third lines of output
274 when the B<-id> argument is provided by itself. Other fields of
275 potential interest to the backup operator are:
281 The date and time when this tape can be recycled, because
282 all dumps it contains have expired.
284 =item B<nMBytes Data and nBytes Data>
286 Summed together, these fields represent the total amount
287 of dumped data actually from volumes (as opposed to
288 labels, filemarks, and other markers).
290 =item B<KBytes Tape Used>
292 The number of kilobytes of tape (or disk space, for a
293 backup data file) used to store the dump data. It is
294 generally larger than the sum of the values in the
295 C<nMBytes> Data and C<nBytes> Data fields, because it includes
296 the space required for the label, file marks and other
297 markers, and because the Backup System writes data at 16
298 KB offsets, even if the data in a given block doesn't
299 fill the entire 16 KB.
305 For each volume on a given tape, there follows a section headed by
306 the underlined string C<Volume>. The fields labeled C<name>, C<position>,
307 C<clone>, and C<nBytes> report the same values (though in a different
308 order) as appear in the table that lists the volumes in each tape
309 when the B<-id> argument is provided by itself. Other fields of
310 potential interest to the backup operator are:
320 The name of the tape containing this volume data.
328 The following example displays information about the last five dumps:
330 backup dumpinfo -ndumps 5
331 dumpid parentid lv created nt nvols dump name
332 924424000 0 0 04/18/1999 04:26 1 22 usr.sun (924424000)
333 924685000 924424000 1 04/21/1999 04:56 1 62 usr.wed (924424000)
334 924773000 924424000 1 04/22/1999 05:23 1 46 usr.thu (924424000)
335 924860000 924424000 1 04/23/1999 05:33 1 58 usr.fri (924424000)
336 925033000 0 0 04/25/1999 05:36 2 73 sys.week
338 The following example displays a more detailed record for a single
341 backup dumpinfo -id 922097346
342 Dump: id 922097346, level 0, volumes 1, created Mon Mar 22 05:09:06 1999
343 Tape: name monday.user.backup (922097346)
344 nVolumes 1, created 03/22/1999 05:09
345 Pos Clone time Nbytes Volume
346 1 03/22/1999 04:43 27787914 user.pat.backup
348 The following example displays even more detailed information about
349 the dump displayed in the previous example (dump ID 922097346). This
350 example includes only one exemplar of each type of section (C<Dump>,
351 C<Tape>, and C<Volume>):
353 backup dumpinfo -id 922097346 -verbose
358 Appended id = 922099568
365 created = Mon Mar 22 05:09:06 1999
369 format= user.monday1.%d
377 tape name = monday.user.backup
378 AFS tape name = user.monday1.1
380 written = Mon Mar 22 05:09:06 1999
382 kBytes Tape Used = 121
393 name = user.pat.backup
400 clone = Mon Mar 22 04:43:06 1999
405 tape = user.monday1.1
407 =head1 PRIVILEGE REQUIRED
409 The issuer must be listed in the B</usr/afs/etc/UserList> file on every
410 machine where the Backup Server is running, or must be logged onto a
411 server machine as the local superuser B<root> if the B<-localauth> flag is
416 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
418 Converted from html to pod by Alf Wachsmann <alfw@slac.stanford.edu>, 2003,
419 and Elizabeth Cassell <e_a_c@mailsnare.net>, 2004,
420 Stanford Linear Accelerator Center, a department of Stanford University.
425 L<backup_deletedump(1)>