Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod8 / backup_jobs.pod
CommitLineData
805e021f
CE
1=head1 NAME
2
3backup_jobs - Lists pending and running operations in interactive mode
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10B<jobs> [B<-help>]
11
12B<j> [B<-h>]
13
14=for html
15</div>
16
17=head1 DESCRIPTION
18
19The B<backup jobs> command lists the job ID number and status of each
20B<backup> operation running or pending in the current interactive session.
21
22This command can be issued in interactive mode only. If the issuer of the
23B<backup interactive> command included the B<-localauth> flag, the
24B<-cell> argument, or both, those settings apply to this command also.
25
26To terminate operations that appear in the output, issue the B<backup
27kill> command and identify the operation to cancel with the job ID number
28from this command's output.
29
30To check the status of a Tape Coordinator, rather than of a certain
31operation, use the B<backup status> command.
32
33=head1 OPTIONS
34
35=over 4
36
37=item B<-help>
38
39Prints the online help for this command. All other valid options are
40ignored.
41
42=back
43
44=head1 OUTPUT
45
46The output always includes the expiration date and time of the tokens that
47the B<backup> command interpreter is using during the current interactive
48session, in the following format:
49
50 <date> <time>: TOKEN EXPIRATION
51
52If the execution date and time specified for a scheduled dump operation is
53later than <date time>, then its individual line (as described in the
54following paragraphs) appears below this line to indicate that the current
55tokens will not be available to it.
56
57If the issuer of the backup command included the B<-localauth> flag when
58entering interactive mode, the line instead reads as follows:
59
60 : TOKEN NEVER EXPIRES
61
62The entry for a scheduled dump operation has the following format:
63
64 Job <job_ID>: <timestamp>: dump <volume_set> <dump_level>
65
66where
67
68=over 4
69
70=item <job_ID>
71
72Is a job identification number assigned by the Backup System.
73
74=item <timestamp>
75
76Indicates the date and time the dump operation is to begin, in the format
77I<month>/I<date>/I<year> I<hours>:I<minutes> (in 24-hour format)
78
79=item <volume_set>
80
81Indicates the volume set to dump.
82
83=item <dump_level>
84
85Indicates the dump level at which to perform the dump operation.
86
87=back
88
89The line for a pending or running operation of any other type has the
90following format:
91
92 Job <job_ID>: <operation> <status>
93
94where
95
96=over 4
97
98=item <job_ID>
99
100Is a job identification number assigned by the Backup System.
101
102=item <operation>
103
104Identifies the operation the Tape Coordinator is performing, which is
105initiated by the indicated command:
106
107=over 4
108
109=item Dump (I<dump name>)
110
111Initiated by the backup dump command. The I<dump name> has the following
112format:
113
114 <volume_set_name>.<dump_level_name>
115
116=item Restore
117
118Initiated by the B<backup diskrestore>, B<backup volrestore>, or B<backup
119volsetrestore> command.
120
121=item Labeltape (I<tape_label>)
122
123Initiated by the B<backup labeltape>n command. The I<tape_label> is the
124name specified by the B<backup labeltape> command's B<-name> or B<-pname>
125argument.
126
127=item Scantape
128
129Initiated by the B<backup scantape> command.
130
131=item SaveDb
132
133Initiated by the B<backup savedb> command.
134
135=item RestoreDb
136
137Initiated by the B<backup restoredb> command.
138
139=back
140
141=item <status>
142
143Indicates the job's current status in one of the following messages. If no
144message appears, the job is either still pending or has finished.
145
146=over 4
147
148=item I<number> Kbytes, volume I<volume_name>
149
150For a running dump operation, indicates the number of kilobytes copied to
151tape or a backup data file so far, and the volume currently being dumped.
152
153=item I<number> Kbytes, restore.volume
154
155For a running restore operation, indicates the number of kilobytes copied
156into AFS from a tape or a backup data file so far.
157
158=item [abort requested]
159
160The B<backup kill> command was issued, but the termination signal has yet
161to reach the Tape Coordinator.
162
163=item [abort sent]
164
165The operation is canceled by the B<backup kill> command. Once the Backup
166System removes an operation from the queue or stops it from running, it no
167longer appears at all in the output from the command.
168
169=item [butc contact lost]
170
171The backup command interpreter cannot reach the Tape Coordinator. The
172message can mean either that the Tape Coordinator handling the operation
173was terminated or failed while the operation was running, or that the
174connection to the Tape Coordinator timed out.
175
176=item [done]
177
178The Tape Coordinator has finished the operation.
179
180=item [drive wait]
181
182The operation is waiting for the specified tape drive to become free.
183
184=item [operator wait]
185
186The Tape Coordinator is waiting for the backup operator to insert a tape
187in the drive.
188
189=back
190
191=back
192
193=head1 EXAMPLES
194
195The following example shows that two restore operations and one dump
196operation are running (presumably on different Tape Coordinators) and that
197the B<backup> command interpreter's tokens expire on 22 April 1999 at
19810:45 am:
199
200 backup> jobs
201 Job 1: Restore, 1306 Kbytes, restore.volume
202 Job 2: Dump (user.sunday1), 34 Kbytes, volume user.pat.backup
203 Job 3: Restore, 2498 Kbytes, restore.volume
204 04/22/1999 10:45: TOKEN EXPIRATION
205
206=head1 PRIVILEGE REQUIRED
207
208None. However, queuing any operation requires privilege, and it is
209possible to issue this command only within the interactive session in
210which the jobs are queued.
211
212=head1 SEE ALSO
213
214L<backup(8)>,
215L<backup_interactive(8)>,
216L<backup_kill(8)>,
217L<backup_quit(8)>
218
219=head1 COPYRIGHT
220
221IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
222
223This documentation is covered by the IBM Public License Version 1.0. It was
224converted from HTML to POD by software written by Chas Williams and Russ
225Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.