rsoper(1M) — ADMINISTRATOR COMMANDS

NAME

rsoper − service pending restore requests and service media insertion prompts

SYNOPSIS

rsoper −d ddev [−j jobids] [−u user] [−m method] [−n] [−s|v] [−t]
[−o oname[:odevice] ]

rsoper −r jobid

rsoper −c jobid

DESCRIPTION

rsoper −d identifies media containing backup archives of file systems and data slices, and allows an operator to complete pending restore(1M) and urestore(1M) requests. rsoper takes information about the archive entered on the command line and matches it against pending restore or urestore requests in the restore status table. rsoper then invokes the proper archiving method to read the archive and extract requested files, directories, and data slices. As subsequent archive volumes are needed, the operator is requested to insert or mount the appropriate archive volumes. See getvol(1M).

Depending on the information available in bkhist.tab and the volume labeling technique (internal or external), all options and arguments listed below may not be required. If required fields are omitted, rsoper issues an error message indicating the information that is needed. The command can then be reissued with the appropriate fields specified.

rsoper may be executed only by a user with superuser privileges.

rsoper −r removes a pending restore job from the restore status table (see rsstatus(1M) and ursstatus(1M)) and notifies the requesting user that the job has been marked complete.

rsoper −c removes a pending restore job from the restore status table (see rsstatus(1M) and ursstatus(1M)) and notifies the requesting user that the job has been canceled.

Options

−c jobid Cancels a pending restore request and notifies the originating user that the request has been canceled.

−d ddev Describes the device that will be used to read the archive containing the required file system or data slice. ddev is of the form:

ddevice[:[dchar][:[dmnames]]]

ddevice is the device name for the device; see device.tab(4). dchar describes characteristics associated with the device. dchar is of the form:

[density=density] [blk_fac=blockingfactor] [mntpt=dir]

If mntpt=dir is specified, ddevice is assumed to be a file system slice and dir is the place in the UNIX system directory structure where ddevice will be mounted. This is valid only for fimage(1M) archives. dmnames is a list of volume labels, separated by either commas or blanks. If the list is blank separated, the entire ddev argument must be surrounded by quotes.

−j jobids Limits the scope of the request to the jobs specified. jobids is a list of restore job IDs (either comma separated or blank separated and surrounded by quotes).

−m method
Assumes the archive on the first volume in the destination device was created by the method archiving operation. Valid methods are: incfile, ffile, fimage, fdp, fdisk, and any customized methods in the /etc/bkup/method directory. This option is required if the backup history log is not available, if the log does not include information about the specified archive or if rsoper cannot determine the format of the archive.

−n Displays attributes of the specified destination device but does not attempt to service pending restore requests.

−o oname[:odevice]
Specifies the originating file system slice or data slice to be restored. oname is the name of the the originating file system. It may be null. odevice is the device name of the originating file system or data slice. This option is required if the backup history log is not available or does not include information about the specified archive.

−r jobid Removes the restore request for the specified job.

−s While a restore operation is occurring, this option displays a period ( . ) for each 100 (512-byte) blocks transferred from the destination device.

−t Assumes that the volume inserted in the destination device contains a table of contents for an archive. This option is required if the backup history log is not available, if the log does not include information about the specified archive, or if rsoper cannot determine the format of the volume.

−u user Restricts restores to those requested by the user specified.

−v Displays the name of each object as it is restored. Only those archiving methods that restore named directories and files (incfile and ffile) support this option.

DIAGNOSTICS

The exit codes for rsoper are the following:

0 = the task completed successfully
1 = one or more parameters to rsoper are invalid
2 = an error has occurred, causing rsoper to fail to
complete all portions of its task

If a method reports that no part of a restore request was completed, rsoper reports this fact to the user.

EXAMPLES

Example 1:

rsoper −d /dev/rmt/ctape1

asks the restore service to read the archive volume that has been inserted into the device /dev/rmt/ctape1. The service will attempt to resolve any restore requests that can be satisfied by the archive volume.

Example 2:

The following example assumes that the backup history table contains a record of backups performed and that the restore status table contains a record of the restore requests. The command line

rsoper −d /dev/rmt/ctape1:density=1600:USRLBL1 −v −u clerk1

instructs the restore service to perform only pending restore requests from the rsstatus.tab table issued by clerk1. The restore procedures are to be done from the cartridge tape labeled USRLBL1, with a density of 1600 bps. The restore service will display on the operator terminal the names of the files and directories as they are successfully restored.

Example 3:

rsoper −c rest-737b

cancels the restore request with the job ID rest-737b.

FILES

/etc/bkup/bkhist.tab lists the labels of all volumes that have been used for backup operations

/etc/bkup/rsstatus.tab
lists the status of all restore requests from users

/etc/bkup/rsnotify.tab lists the electronic mail address of the operator to be notified whenever restore requests require operator intervention

/etc/bkup/method a directory that contains the programs used for various backup methods

Museum

Related Articles