3 backup listdumps - Displays the dump hierarchy from the Backup Database
7 backup listdumps [B<-localauth>] [B<-cell> I<cell name>] [B<-help>]
9 backup listd [B<-l>] [B<-c> I<cell name>] [B<-h>]
13 The C<backup listdumps> command displays the dump hierarchy from the
22 Constructs a server ticket using a key from the local
23 B</usr/afs/etc/KeyFile> file. The C<backup> command interpreter
24 presents it to the Backup Server, Volume Server and VL Server
25 during mutual authentication. Do not combine this flag with the
26 B<-cell> argument. For more details, see the introductory L<backup(1)>
29 =item B<-cell> I<cell name>
31 Names the cell in which to run the command. Do not combine this
32 argument with the B<-localauth> flag. For more details, see the
33 introductory L<backup(1)> reference page.
37 Prints the online help for this command. All other valid
44 The output displays the complete dump hierarchy and indicates the
45 relationship between full and incremental dump levels. Full dump
46 levels appear at the left margin. The hierarchy can include more than
47 one full dump level; each one defines a subhierarchy of dump levels
48 that can be used for dumping different volume sets.
50 Incremental dump levels appear below and indented to the right of
51 their parent dump levels, which can be either full or incremental.
52 Since multiple incremental dump levels can share the same parent, an
53 incremental dump level is not always directly below its parent; the
54 amount of indentation indicates the parent/child relationship.
56 If a dump level has an associated expiration date, it appears along
57 with the level name. Absolute expiration dates appear in the format
59 I<dump_level> expires at I<day> I<month> I<date> I<time> I<year>
61 and relative expiration dates in the format
63 I<dump_level> expires in {I<years>y | I<months>m | I<days>d}
65 to indicate the number of years, months, days, or combination of the
66 three after creation a dump expires when created at this level.
70 The following example depicts six dump hierarchies. The expiration
71 date for all incremental dump levels is 13 days so that the
72 corresponding tapes can be recycled two weeks after their creation.
73 The expiration dates for all full dump levels is 27 days so that the
74 corresponding tapes can be recycled four weeks after their creation.
78 /tuesday expires in 13d
79 /thursday expires in 13d
80 /sunday expires in 13d
81 /tuesday expires in 13d
82 /thursday expires in 13d
84 /tuesday expires in 13d
85 /thursday expires in 13d
86 /sunday expires in 13d
87 /tuesday expires in 13d
88 /thursday expires in 13d
89 /sunday1 expires in 27d
90 /monday1 expires in 13d
91 /tuesday1 expires in 13d
92 /wednesday1 expires in 13d
93 /thursday1 expires in 13d
94 /friday1 expires in 13d
95 /sunday2 expires in 27d
96 /monday2 expires in 13d
97 /tuesday2 expires in 13d
98 /wednesday2 expires in 13d
99 /thursday2 expires in 13d
100 /friday2 expires in 13d
101 /sunday3 expires in 27d
102 /monday1 expires in 13d
103 /tuesday1 expires in 13d
104 /wednesday1 expires in 13d
105 /thursday1 expires in 13d
106 /friday1 expires in 13d
107 /sunday4 expires in 27d
108 /monday2 expires in 13d
109 /tuesday2 expires in 13d
110 /wednesday2 expires in 13d
111 /thursday2 expires in 13d
112 /friday2 expires in 13d
114 =head1 PRIVILEGE REQUIRED
116 The issuer must be listed in the B</usr/afs/etc/UserList> file on every
117 machine where the Backup Server is running, or must be logged onto a
118 server machine as the local superuser B<root> if the B<-localauth> flag is
123 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
125 Converted from html to pod by Alf Wachsmann <alfw@slac.stanford.edu>, 2003,
126 and Elizabeth Cassell <e_a_c@mailsnare.net>, 2004,
127 Stanford Linear Accelerator Center, a department of Stanford University.
132 L<backup_adddump(1)>,