1 <?xml version="1.0" encoding="UTF-8"?>
2 <refentry id="backup_jobs8">
4 <refentrytitle>backup jobs</refentrytitle>
5 <manvolnum>8</manvolnum>
8 <refname>backup jobs</refname>
9 <refpurpose>Lists pending and running operations in interactive mode</refpurpose>
12 <title>Synopsis</title>
13 <para><emphasis role="bold">jobs</emphasis> [<emphasis role="bold">-help</emphasis>]</para>
15 <para><emphasis role="bold">j</emphasis> [<emphasis role="bold">-h</emphasis>]</para>
19 <title>Description</title>
20 <para>The <emphasis role="bold">backup jobs</emphasis> command lists the job ID number and status of each
21 <emphasis role="bold">backup</emphasis> operation running or pending in the current interactive session.</para>
23 <para>This command can be issued in interactive mode only. If the issuer of the
24 <emphasis role="bold">backup interactive</emphasis> command included the <emphasis role="bold">-localauth</emphasis> flag, the
25 <emphasis role="bold">-cell</emphasis> argument, or both, those settings apply to this command also.</para>
27 <para>To terminate operations that appear in the output, issue the <emphasis role="bold">backup
28 kill</emphasis> command and identify the operation to cancel with the job ID number
29 from this command's output.</para>
31 <para>To check the status of a Tape Coordinator, rather than of a certain
32 operation, use the <emphasis role="bold">backup status</emphasis> command.</para>
36 <title>Options</title>
39 <term><emphasis role="bold">-help</emphasis></term>
41 <para>Prints the online help for this command. All other valid options are
50 <para>The output always includes the expiration date and time of the tokens that
51 the <emphasis role="bold">backup</emphasis> command interpreter is using during the current interactive
52 session, in the following format:</para>
55 &lt;date&gt; &lt;time&gt;: TOKEN EXPIRATION
58 <para>If the execution date and time specified for a scheduled dump operation is
59 later than <date time>, then its individual line (as described in the
60 following paragraphs) appears below this line to indicate that the current
61 tokens will not be available to it.</para>
63 <para>If the issuer of the backup command included the <emphasis role="bold">-localauth</emphasis> flag when
64 entering interactive mode, the line instead reads as follows:</para>
70 <para>The entry for a scheduled dump operation has the following format:</para>
73 Job &lt;job_ID&gt;: &lt;timestamp&gt;: dump &lt;volume_set&gt; &lt;dump_level&gt;
80 <term><job_ID></term>
82 <para>Is a job identification number assigned by the Backup System.</para>
87 <term><timestamp></term>
89 <para>Indicates the date and time the dump operation is to begin, in the format
90 <emphasis>month</emphasis>/<emphasis>date</emphasis>/<emphasis>year</emphasis> <emphasis>hours</emphasis>:<emphasis>minutes</emphasis> (in 24-hour format)</para>
95 <term><volume_set></term>
97 <para>Indicates the volume set to dump.</para>
102 <term><dump_level></term>
104 <para>Indicates the dump level at which to perform the dump operation.</para>
109 <para>The line for a pending or running operation of any other type has the
110 following format:</para>
113 Job &lt;job_ID&gt;: &lt;operation&gt; &lt;status&gt;
120 <term><job_ID></term>
122 <para>Is a job identification number assigned by the Backup System.</para>
127 <term><operation></term>
129 <para>Identifies the operation the Tape Coordinator is performing, which is
130 initiated by the indicated command:</para>
134 <term>Dump (<emphasis>dump name</emphasis>)</term>
136 <para>Initiated by the backup dump command. The <emphasis>dump name</emphasis> has the following
140 &lt;volume_set_name&gt;.&lt;dump_level_name&gt;
148 <para>Initiated by the <emphasis role="bold">backup diskrestore</emphasis>, <emphasis role="bold">backup volrestore</emphasis>, or <emphasis role="bold">backup
149 volsetrestore</emphasis> command.</para>
154 <term>Labeltape (<emphasis>tape_label</emphasis>)</term>
156 <para>Initiated by the <emphasis role="bold">backup labeltape</emphasis>n command. The <emphasis>tape_label</emphasis> is the
157 name specified by the <emphasis role="bold">backup labeltape</emphasis> command's <emphasis role="bold">-name</emphasis> or <emphasis role="bold">-pname</emphasis>
163 <term>Scantape</term>
165 <para>Initiated by the <emphasis role="bold">backup scantape</emphasis> command.</para>
172 <para>Initiated by the <emphasis role="bold">backup savedb</emphasis> command.</para>
177 <term>RestoreDb</term>
179 <para>Initiated by the <emphasis role="bold">backup restoredb</emphasis> command.</para>
187 <term><status></term>
189 <para>Indicates the job's current status in one of the following messages. If no
190 message appears, the job is either still pending or has finished.</para>
194 <term><emphasis>number</emphasis> Kbytes, volume <emphasis>volume_name</emphasis></term>
196 <para>For a running dump operation, indicates the number of kilobytes copied to
197 tape or a backup data file so far, and the volume currently being dumped.</para>
202 <term><emphasis>number</emphasis> Kbytes, restore.volume</term>
204 <para>For a running restore operation, indicates the number of kilobytes copied
205 into AFS from a tape or a backup data file so far.</para>
210 <term>[abort requested]</term>
212 <para>The <emphasis role="bold">backup kill</emphasis> command was issued, but the termination signal has yet
213 to reach the Tape Coordinator.</para>
218 <term>[abort sent]</term>
220 <para>The operation is canceled by the <emphasis role="bold">backup kill</emphasis> command. Once the Backup
221 System removes an operation from the queue or stops it from running, it no
222 longer appears at all in the output from the command.</para>
227 <term>[butc contact lost]</term>
229 <para>The backup command interpreter cannot reach the Tape Coordinator. The
230 message can mean either that the Tape Coordinator handling the operation
231 was terminated or failed while the operation was running, or that the
232 connection to the Tape Coordinator timed out.</para>
239 <para>The Tape Coordinator has finished the operation.</para>
244 <term>[drive wait]</term>
246 <para>The operation is waiting for the specified tape drive to become free.</para>
251 <term>[operator wait]</term>
253 <para>The Tape Coordinator is waiting for the backup operator to insert a tape
264 <title>Examples</title>
265 <para>The following example shows that two restore operations and one dump
266 operation are running (presumably on different Tape Coordinators) and that
267 the <emphasis role="bold">backup</emphasis> command interpreter's tokens expire on 22 April 1999 at
272 Job 1: Restore, 1306 Kbytes, restore.volume
273 Job 2: Dump (user.sunday1), 34 Kbytes, volume user.pat.backup
274 Job 3: Restore, 2498 Kbytes, restore.volume
275 04/22/1999 10:45: TOKEN EXPIRATION
280 <title>Privilege Required</title>
281 <para>None. However, queuing any operation requires privilege, and it is
282 possible to issue this command only within the interactive session in
283 which the jobs are queued.</para>
287 <title>See Also</title>
288 <para><link linkend="backup8">backup(8)</link>,
289 <link linkend="backup_interactive8">backup_interactive(8)</link>,
290 <link linkend="backup_kill8">backup_kill(8)</link>,
291 <link linkend="backup_quit8">backup_quit(8)</link></para>
295 <title>Copyright</title>
296 <para>IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.</para>
298 <para>This documentation is covered by the IBM Public License Version 1.0. It was
299 converted from HTML to POD by software written by Chas Williams and Russ
300 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.</para>