+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 3//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3190/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 5 Nov 1999 at 13:58:29 -->
-<META HTTP-EQUIV="updated" CONTENT="Fri, 05 Nov 1999 13:58:29">
-<META HTTP-EQUIV="review" CONTENT="Sun, 05 Nov 2000 13:58:29">
-<META HTTP-EQUIV="expires" CONTENT="Mon, 05 Nov 2001 13:58:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf077.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf079.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_KILL" HREF="auarf002.htm#ToC_92">backup kill</A></H2>
-<A NAME="IDX4339"></A>
-<A NAME="IDX4340"></A>
-<A NAME="IDX4341"></A>
-<A NAME="IDX4342"></A>
-<A NAME="IDX4343"></A>
-<A NAME="IDX4344"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Terminates a pending or running operation
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kill -id</B> <<VAR>job ID or dump set name</VAR>> [<B>-help</B>]
-
-<B>k -i</B> <<VAR>job ID or dump set name</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>(backup) kill</B> command dequeues a Backup System operation
-that is pending, or terminates an operation that is running, in the current
-interactive session. It is available only in interactive mode.
-If the issuer of the <B>backup (interactive)</B> command included the
-<B>-localauth</B> flag, the <B>-cell</B> argument, or both, then those
-settings apply to this command also.
-<P>To terminate a dump operation, specify either the dump name
-(<VAR>volume_set_name</VAR>.<VAR>dump_level_name</VAR>) or its job ID
-number, which appears in the output from the <B>(backup) jobs</B>
-command. To terminate any other type of operation, provide the job ID
-number.
-<P>The effect of terminating an operation depends on the type and current
-state of the operation:
-<UL>
-<P><LI>If an operation is still pending, the Tape Coordinator removes it from the
-queue with no other lasting effects.
-<P><LI>If the Tape Coordinator is unable to process the termination signal before
-an operation completes, it simply confirms the operation's
-completion. The operator must take the action necessary to undo the
-effects of the incorrect operation.
-<P><LI>If a tape labeling operation is running, the effect depends on when the
-Tape Coordinator receives the termination signal. The labeling
-operation is atomic, so it either completes or does not begin at all.
-Use the <B>backup readlabel</B> command to determine if the labeling
-operation completed, and reissue the <B>backup labeltape</B> command to
-overwrite the incorrect label if necessary.
-<P><LI>If a tape scanning operation is running, it terminates with no other
-effects unless the <B>-dbadd</B> flag was included on the
-<B>backup</B> command. In that case, the Backup System possibly has
-already written new Backup Database records to represent dumps on the scanned
-tape. If planning to restart the scanning operation, first locate and
-remove the records created during the terminated operation: a repeated
-<B>backup scantape</B> operation exits automatically when it finds that a
-record that it needs to create already exists.
-<P><LI>If a dump operation is running, all of the volumes written to the tape or
-backup data file before the termination signal is received are complete and
-usable. If the operation is restarted, the Backup System performs all
-the dumps again from scratch, and assigns a new dump ID number. If
-writing the new dumps to the same tape or file, the operator must relabel it
-first if the interrupted dump is not expired. If writing the new dump
-to a different tape or file, the operator can remove the dump record
-associated with the interrupted dump to free up space in the database.
-<P><LI>If a restore operation is running, completely restored volumes are online
-and usable. However, it is unlikely that many volumes are completely
-restored, given that complete restoration usually requires data from multiple
-tapes. If the termination signal comes before the Backup System has
-accessed all of the necessary tapes, each volume is only partially written and
-is never brought online. It is best to restart the restore operation
-from scratch to avoid possible inconsistencies. See also the
-<B>Cautions</B> section.
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>It is best not to issue the <B>(backup) kill</B> command against
-restore operations. If the termination signal interrupts a restore
-operation as the Backup System is overwriting an existing volume, it is
-possible to lose the volume entirely (that is, to lose both the contents of
-the volume as it was before the restore and any data that was restored before
-the termination signal arrived). The data being restored still exists
-on the tape, but some data can be lost permanently.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Identifies the backup operation to terminate. Provide one of two
-types of values:
-<UL>
-<P><LI>The operation's job ID number, as displayed in the output of the
-<B>(backup) jobs</B> command.
-<P><LI>For a dump operation, either the job ID number or a dump name of the form
-<VAR>volume_set_name</VAR>.<VAR>dump_level_name</VAR>, where
-<VAR>volume_set_name</VAR> is the name of the volume set being dumped and
-<VAR>dump_level_name</VAR> is the last element in the dump level pathname at
-which the volume set is being dumped. The dump name appears in the
-output of the <B>(backup) jobs</B> command along with the job ID
-number.
-</UL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command terminates the operation with job ID 5:
-<PRE> backup> <B>kill 5</B>
-
-</PRE>
-<P>The following command terminates the dump operation called
-<B>user.sunday1</B>:
-<PRE> backup> <B>kill user.sunday1</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the privilege required to initiate the operation being
-cancelled. Because this command can be issued only within the
-interactive session during which the operation was initiated, the required
-privilege is essentially guaranteed.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf076.htm#HDRBK_INTERACTIVE">backup interactive</A>
-<P><A HREF="auarf077.htm#HDRBK_JOBS">backup jobs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf077.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf079.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
git://git.openafs.org / openafs.git / blobdiff