NAME

urestore − request restore of files and directories

SYNOPSIS

urestore [−mn] [−s|v] [−o target] [−d date] −F file . . . 

urestore [−mn] [−s|v] [−o target] [−d date] −D dir . . . 

urestore −c jobid

DESCRIPTION

urestore posts requests for files or directories to be restored from system-maintained archives.  If the appropriate archive containing the requested files or directories is on-line, the files or directories are restored immediately.  If not, a request to restore the specified files or directories is posted to a restore status table, /etc/bkup/rsstatus.tab.  A restore request that has been posted must later be resolved by an operator (see rsoper(1M)).  Each file or directory to be restored is assigned a restore job ID that can be used to monitor the progress of the restore (see ursstatus(1M)) or to cancel it. 

The user must have write permission for the current directory and any subdirectories to be traversed in storing the restored files or directories.  Requests for restores may be made only by the user who owned the files or directories at the time the archive containing the files or directories was made, or by a user with superuser privileges. 

Options

-c jobid Cancels a previously issued restore request. 

−d date Restores the filesystem or directory as of date. (This may or may not be the latest archive.) See getdate(3C) for valid date formats. 

−m If the restore cannot be carried out immediately, this option notifies the invoking user (via mail) when the request has been completed. 

−n Displays a list of all archived versions of the filesystem or directory contained in the backup history log but does not attempt to restore the filesystem or directory. 

−o target Instead of restoring directly to the specified file or directory, this option replaces the file or directory target with the archive of the specified file or directory. 

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

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

−D Initiates a restore operation for directories. 

−F Initiates a restore operation for files. 

DIAGNOSTICS

The exit codes for urestore are the following:

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

EXAMPLES

Example 1:

urestore −m −F bigfile

posts a request to restore the most current archived version of the file bigfile.  If the restore operation cannot be carried out immediately, it notifies the invoking user when the request has been completed. 

Example 2:

urestore −c rest-256a,rest-256b

cancels restore requests with job ID numbers rest-256a and rest-256b. 

Example 3:

urestore −o /testfiles/myfile.b −F /testfiles/myfile.a

posts a request for the archived file /testfiles/myfile.a to be restored as /testfiles/myfile.b

Example 4:

urestore −d "december 1, 1987" −D /user1 -v

posts a request for the archived directory structure /user1, with all its files and subdirectories, to be restored as of December 1, 1987.  If the restore is done immediately from an on-line archive, the name of each file will be displayed on standard output while the restore is underway. 

Example 5:

urestore −n −D /pr3/reports

requests the system to display the backup dates and an ls -l listing from the backup history log of all archived versions of the directory /pr3/reports.  The directory is not restored. 

FILES

SEE ALSO

restore(1M), ursstatus(1M), mail(1), getdate(3C). 

  —  System Administration Utilities