Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod8 / backup_dumpinfo.pod
CommitLineData
805e021f
CE
1=head1 NAME
2
3backup_dumpinfo - Displays a dump record from the Backup Database
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10B<backup dumpinfo> S<<< [B<-ndumps> <I<number of dumps>>] >>>
11 S<<< [B<-id> <I<dump id>>] >>> [B<-verbose>] [B<-localauth>]
12 S<<< [B<-cell> <I<cell name>>] >>> [B<-help>]
13
14B<backup dumpi> S<<< [B<-n> <I<no. of dumps>>] >>> [-i <I<dump id>>] [B<-v>]
15 [B<-l>] S<<< [B<-c> <I<cell name>>] >>> [B<-h>]
16
17=for html
18</div>
19
20=head1 DESCRIPTION
21
22The B<backup dumpinfo> command formats and displays the Backup Database
23record for the specified dumps. To specify how many of the most recent
24dumps to display, starting with the newest one and going back in time, use
25the B<-ndumps> argument. To display more detailed information about a
26single dump, use the B<-id> argument. To display the records for the 10
27most recent dumps, omit both the B<-ndumps> and B<-id> arguments.
28
29The B<-verbose> flag produces very detailed information that is useful
30mostly for debugging purposes. It can be combined only with the B<-id>
31argument.
32
33=head1 OPTIONS
34
35=over 4
36
37=item B<-ndumps> <I<number of dumps>>
38
39Displays the Backup Database record for each of the specified number of
40dumps that were most recently performed. If the database contains fewer
41dumps than are requested, the output includes the records for all existing
42dumps. Do not combine this argument with the B<-id> or B<-verbose>
43options; omit all options to display the records for the last 10 dumps.
44
45=item B<-id> <I<dump id>>
46
47Specifies the dump ID number of a single dump for which to display the
48Backup Database record. Precede the I<dump id> value with the B<-id>
49switch; otherwise, the command interpreter interprets it as the value of
50the B<-ndumps> argument. Combine this argument with the B<-verbose> flag,
51but not with the B<-ndumps> argument; omit all options to display the
52records for the last 10 dumps.
53
54=item B<-verbose>
55
56Provides more detailed information about the dump specified with the
57B<-id> argument, which must be provided along with it. Do not combine this
58flag with the B<-ndumps> argument.
59
60=item B<-localauth>
61
62Constructs a server ticket using a key from the local
63F</usr/afs/etc/KeyFile> file. The B<backup> command interpreter presents
64it to the Backup Server, Volume Server and VL Server during mutual
65authentication. Do not combine this flag with the B<-cell> argument. For
66more details, see L<backup(8)>.
67
68=item B<-cell> <I<cell name>>
69
70Names the cell in which to run the command. Do not combine this argument
71with the B<-localauth> flag. For more details, see L<backup(8)>.
72
73=item B<-help>
74
75Prints the online help for this command. All other valid options are
76ignored.
77
78=back
79
80=head1 OUTPUT
81
82If the B<-ndumps> argument is provided, the output presents the following
83information in table form, with a separate line for each dump:
84
85=over 4
86
87=item dumpid
88
89The dump ID number.
90
91=item parentid
92
93The dump ID number of the dump's parent dump. A value of C<0> (zero)
94identifies a full dump.
95
96=item lv
97
98The depth in the dump hierarchy of the dump level used to create the
99dump. A value of C<0> (zero) identifies a full dump, in which case the
100value in the C<parentid> field is also C<0>. A value of C<1> or greater
101indicates an incremental dump made at the corresponding level in the dump
102hierarchy.
103
104=item created
105
106The date and time at which the Backup System started the dump operation
107that created the dump.
108
109=item nt
110
111The number of tapes that contain the data in the dump. A value of C<0>
112(zero) indicates that the dump operation was terminated or failed. Use the
113B<backup deletedump> command to remove such entries.
114
115=item nvols
116
117The number of volumes from which the dump includes data. If a volume spans
118tapes, it is counted twice. A value of C<0> (zero) indicates that the dump
119operation was terminated or failed; the value in the C<nt> field is also
120C<0> in this case.
121
122=item dump name
123
124The dump name in the form
125
126 <volume_set_name>.<dump_level_name> (<initial_dump_ID>)
127
128where <volume_set_name> is the name of the volume set, and
129<dump_level_name> is the last element in the dump level pathname at which
130the volume set was dumped.
131
132The <initial_dump_ID>, if displayed, is the dump ID of the initial dump in
133the dump set to which this dump belongs. If there is no value in
134parentheses, the dump is the initial dump in a dump set that has no
135appended dumps.
136
137=back
138
139If the B<-id> argument is provided alone, the first line of output begins
140with the string C<Dump> and reports information for the entire dump in the
141following fields:
142
143=over 4
144
145=item id
146
147The dump ID number.
148
149=item level
150
151The depth in the dump hierarchy of the dump level used to create the
152dump. A value of C<0> (zero) identifies a full dump. A value of C<1> (one)
153or greater indicates an incremental dump made at the specified level in
154the dump hierarchy.
155
156=item volumes
157
158The number of volumes for which the dump includes data.
159
160=item created
161
162The date and time at which the dump operation began.
163
164=back
165
166If an XBSA server was the backup medium for the dump (rather than a tape
167device or backup data file), the following line appears next:
168
169 Backup Service: <XBSA_program>: Server: <hostname>
170
171where <XBSA_program> is the name of the XBSA-compliant program and
172<hostname> is the name of the machine on which the program runs.
173
174Next the output includes an entry for each tape that houses volume data
175from the dump. Following the string C<Tape>, the first two lines of each
176entry report information about that tape in the following fields:
177
178=over 4
179
180=item name
181
182The tape's permanent name if it has one, or its AFS tape name otherwise,
183and its tape ID number in parentheses.
184
185=item nVolumes
186
187The number of volumes for which this tape includes dump data.
188
189=item created
190
191The date and time at which the Tape Coordinator began writing data to this
192tape.
193
194=back
195
196Following another blank line, the tape-specific information concludes with
197a table that includes a line for each volume dump on the tape. The
198information appears in columns with the following headings:
199
200=over 4
201
202=item Pos
203
204The relative position of each volume in this tape or file. On a tape, the
205counter begins at position 2 (the tape label occupies position 1), and
206increments by one for each volume. For volumes in a backup data file, the
207position numbers start with 1 and do not usually increment only by one,
208because each is the ordinal of the 16 KB offset in the file at which the
209volume's data begins. The difference between the position numbers
210therefore indicates how many 16 KB blocks each volume's data occupies. For
211example, if the second volume is at position 5 and the third volume in the
212list is at position 9, that means that the dump of the second volume
213occupies 64 KB (four 16-KB blocks) of space in the file.
214
215=item Clone time
216
217For a backup or read-only volume, the time at which it was cloned from its
218read/write source. For a Read/Write volume, it is the same as the dump
219creation date reported on the first line of the output.
220
221=item Nbytes
222
223The number of bytes of data in the dump of the volume.
224
225=item Volume
226
227The volume name, complete with C<.backup> or C<.readonly> extension if
228appropriate.
229
230=back
231
232If both the B<-id> and B<-verbose> options are provided, the output is
233divided into several sections:
234
235=over 4
236
237=item *
238
239The first section, headed by the underlined string C<Dump>, includes
240information about the entire dump. The fields labeled C<id>, C<level>,
241C<created>, and C<nVolumes> report the same values (though in a different
242order) as appear on the first line of output when the B<-id> argument is
243provided by itself. Other fields of potential interest to the backup
244operator are:
245
246=over 4
247
248=item Group id
249
250The dump's I<group ID number>, which is recorded in the dump's Backup
251Database record if the C<GROUPID> instruction appears in the Tape
252Coordinator's F</usr/afs/backup/CFG_I<tcid>> file when the dump is
253created.
254
255=item maxTapes
256
257The number of tapes that contain the dump set to which this dump belongs.
258
259=item Start Tape Seq
260
261The ordinal of the tape on which this dump begins in the set of tapes that
262contain the dump set.
263
264=back
265
266=item *
267
268For each tape that contains data from this dump, there follows a section
269headed by the underlined string C<Tape>. The fields labeled C<name>,
270C<written>, and C<nVolumes> report the same values (though in a different
271order) as appear on the second and third lines of output when the B<-id>
272argument is provided by itself. Other fields of potential interest to the
273backup operator are:
274
275=over 4
276
277=item expires
278
279The date and time when this tape can be recycled, because all dumps it
280contains have expired.
281
282=item nMBytes Data and nBytes Data
283
284Summed together, these fields represent the total amount of dumped data
285actually from volumes (as opposed to labels, filemarks, and other
286markers).
287
288=item KBytes Tape Used
289
290The number of kilobytes of tape (or disk space, for a backup data file)
291used to store the dump data. It is generally larger than the sum of the
292values in the C<nMBytes Data> and C<nBytes Data> fields, because it
293includes the space required for the label, file marks and other markers,
294and because the Backup System writes data at 16 KB offsets, even if the
295data in a given block doesn't fill the entire 16 KB.
296
297=back
298
299=item *
300
301For each volume on a given tape, there follows a section headed by the
302underlined string C<Volume>. The fields labeled C<name>, C<position>,
303C<clone>, and C<nBytes> report the same values (though in a different
304order) as appear in the table that lists the volumes in each tape when the
305B<-id> argument is provided by itself. Other fields of potential interest
306to the backup operator are:
307
308=over 4
309
310=item id
311
312The volume ID.
313
314=item tape
315
316The name of the tape containing this volume data.
317
318=back
319
320=back
321
322=head1 EXAMPLES
323
324The following example displays information about the last five dumps:
325
326 % backup dumpinfo -ndumps 5
327 dumpid parentid lv created nt nvols dump name
328 924424000 0 0 04/18/1999 04:26 1 22 usr.sun (924424000)
329 924685000 924424000 1 04/21/1999 04:56 1 62 usr.wed (924424000)
330 924773000 924424000 1 04/22/1999 05:23 1 46 usr.thu (924424000)
331 924860000 924424000 1 04/23/1999 05:33 1 58 usr.fri (924424000)
332 925033000 0 0 04/25/1999 05:36 2 73 sys.week
333
334The following example displays a more detailed record for a single dump.
335
336 % backup dumpinfo -id 922097346
337 Dump: id 922097346, level 0, volumes 1, created Mon Mar 22 05:09:06 1999
338 Tape: name monday.user.backup (922097346)
339 nVolumes 1, created 03/22/1999 05:09
340 Pos Clone time Nbytes Volume
341 1 03/22/1999 04:43 27787914 user.pat.backup
342
343The following example displays even more detailed information about the
344dump displayed in the previous example (dump ID 922097346). This example
345includes only one exemplar of each type of section (C<Dump>, C<Tape>, and
346C<Volume>):
347
348 % backup dumpinfo -id 922097346 -verbose
349 Dump
350 ----
351 id = 922097346
352 Initial id = 0
353 Appended id = 922099568
354 parent = 0
355 level = 0
356 flags = 0x0
357 volumeSet = user
358 dump path = /monday1
359 name = user.monday1
360 created = Mon Mar 22 05:09:06 1999
361 nVolumes = 1
362 id = 0
363 tapeServer =
364 format= user.monday1.%d
365 maxTapes = 1
366 Start Tape Seq = 1
367 name = pat
368 instance =
369 cell =
370 Tape
371 ----
372 tape name = monday.user.backup
373 AFS tape name = user.monday1.1
374 flags = 0x20
375 written = Mon Mar 22 05:09:06 1999
376 expires = NEVER
377 kBytes Tape Used = 121
378 nMBytes Data = 0
379 nBytes Data = 19092
380 nFiles = 0
381 nVolumes = 1
382 seq = 1
383 tapeid = 0
384 useCount = 1
385 dump = 922097346
386 Volume
387 ------
388 name = user.pat.backup
389 flags = 0x18
390 id = 536871640
391 server =
392 partition = 0
393 nFrags = 1
394 position = 2
395 clone = Mon Mar 22 04:43:06 1999
396 startByte = 0
397 nBytes = 19092
398 seq = 0
399 dump = 922097346
400 tape = user.monday1.1
401
402=head1 PRIVILEGE REQUIRED
403
404The issuer must be listed in the F</usr/afs/etc/UserList> file on every
405machine where the Backup Server is running, or must be logged onto a
406server machine as the local superuser C<root> if the B<-localauth> flag is
407included.
408
409=head1 SEE ALSO
410
411L<butc(5)>,
412L<backup(8)>,
413L<backup_deletedump(8)>
414
415=head1 COPYRIGHT
416
417IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
418
419This documentation is covered by the IBM Public License Version 1.0. It was
420converted from HTML to POD by software written by Chas Williams and Russ
421Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.