bkoper(1M) bkoper(1M)
NAME
bkoper - interact with backup operations to service media
insertion prompts
SYNOPSIS
bkoper [-u users]
DESCRIPTION
Backup operations may require an operator to insert media and
to confirm proper volume labels. The bkoper command provides
a mailx-like interface for these operator interactions. It
begins by printing a list of headers. Each header describes a
backup operation requiring interaction, the device requiring
attention including the media type and label of the volume to
be inserted (see EXAMPLE). The system displays prompts and
the operator issues commands to resolve the backup operation.
Typing a carriage return invokes the current header. If no
headers have been serviced, the current header is the first
header on the list. If a header has been selected and
serviced, the current header is the next one following.
bkoper may be executed only by a privileged user. By default,
the operator may interact only with backup operations that
were started by the same user ID .
If the -u users option is given, the operator interacts only
with backup operations started by the specified user(s).
Commands
!shell-command
Escapes to the shell. The remainder of the line
after the ! is sent to the UNIX system shell (sh) to
be interpreted as a command.
= Prints the current backup operation number.
? Prints this summary of commands.
[p|t] [n] Both the p and t options operate in the same way.
Either option will interact with the backup
operation described by the n'th header. n defaults
to the current header number.
h Prints the list of backup operations.
Copyright 1994 Novell, Inc. Page 1
bkoper(1M) bkoper(1M)
q Quits from bkoper.
DIAGNOSTICS
The exit codes for bkoper are the following:
0 The task completed successfully.
1 One or more parameters to bkoper are invalid.
2 An error has occurred which caused bkoper to fail to
complete all portions of its task.
EXAMPLES
A sample header is shown below. Items appearing in the header
are listed in the following order: header number, job-ID, tag,
originating device, destination group, destination device,
destination volume labels. [See bkreg(1M) for descriptions of
items.] Not every header contains values for all these
fields; if a destination group is not specified in
/etc/bkup/bkreg.tab, then no value for ``destination group''
appears in the header.
1 back-111 usrsun /dev/dsk/c1d0s1 disk /dev/dsk/c2d1s9 usrsave
2 back-112 fs2daily /dev/dsk/c1d0s8 ctape /dev/ctape/c4d0s2 -
Backup headers are numbered on the basis of arrival; the
oldest header has the lowest number. If the destination
device does not have a volume label, a dash is displayed in
the header.
REFERENCES
bkreg(1M), bkstatus(1M), getvol(1M), mailx(1)
Copyright 1994 Novell, Inc. Page 2