Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

restor(1m) [v7 man page]

RESTOR(1M)																RESTOR(1M)

NAME
restor - incremental file system restore SYNOPSIS
restor key [ argument ... ] DESCRIPTION
Restor is used to read magtapes dumped with the dump command. The key specifies what is to be done. Key is one of the characters rRxt optionally combined with f. f Use the first argument as the name of the tape instead of the default. r or R The tape is read and loaded into the file system specified in argument. This should not be done lightly (see below). If the key is R restor asks which tape of a multi volume set to start on. This allows restor to be interrupted and then restarted (an icheck -s must be done before restart). x Each file on the tape named by an argument is extracted. The file name has all `mount' prefixes removed; for example, /usr/bin/lpr is named /bin/lpr on the tape. The file extracted is placed in a file with a numeric name supplied by restor (actually the inode number). In order to keep the amount of tape read to a minimum, the following procedure is recommended: Mount volume 1 of the set of dump tapes. Type the restor command. Restor will announce whether or not it found the files, give the number it will name the file, and rewind the tape. It then asks you to `mount the desired tape volume'. Type the number of the volume you choose. On a multivolume dump the recom- mended procedure is to mount the last through the first volume in that order. Restor checks to see if any of the files requested are on the mounted tape (or a later tape, thus the reverse order) and doesn't read through the tape if no files are. If you are working with a single volume dump or the number of files being restored is large, respond to the query with `1' and restor will read the tapes in sequential order. If you have a hierarchy to restore you can use dumpdir(1) to produce the list of names and a shell script to move the resulting files to their homes. t Print the date the tape was written and the date the filesystem was dumped from. The r option should only be used to restore a complete dump tape onto a clear file system or to restore an incremental dump tape onto this. Thus /etc/mkfs /dev/rp0 40600 restor r /dev/rp0 is a typical sequence to restore a complete dump. Another restor can be done to get an incremental dump in on top of this. A dump followed by a mkfs and a restor is used to change the size of a file system. FILES
default tape unit varies with installation rst* SEE ALSO
dump(1), mkfs(1), dumpdir(1) DIAGNOSTICS
There are various diagnostics involved with reading the tape and writing the disk. There are also diagnostics if the i-list or the free list of the file system is not large enough to hold the dump. If the dump extends over more than one tape, it may ask you to change tapes. Reply with a new-line when the next tape has been mounted. BUGS
There is redundant information on the tape that could be used in case of tape reading problems. Unfortunately, restor doesn't use it. RESTOR(1M)

Check Out this Related Man Page

restore(1M)															       restore(1M)

NAME
restore, rrestore - restore file system incrementally, local or across network SYNOPSIS
key [name ...] key [name ...] DESCRIPTION
The and commands read tapes previously dumped by the or command (see dump(1M) and rdump(1M)). Actions taken are controlled by the key argument where key is a string of characters containing not more than one function letter and pos- sibly one or more function modifiers. One or more name arguments, if present, are file or directory names specifying the files that are to be restored. Unless the modifier is specified (see below), the appearance of a directory name refers to the files and (recursively) subdi- rectories of that directory. Function Portion of key The function portion of the key is specified by one of the following letters: Read the tape and load into the current directory. should be used only after careful consideration, and only to restore a complete dump tape onto a clear file system, or to restore an incremental dump tape after a full level zero restore. Thus, is a typical sequence to restore a complete dump. Another or can then be performed to restore an incremental dump on top of this. Note that and leave a file in the root directory of the file system to pass information between incremental restore passes. This file should be removed when the last incremental tape has been restored. A or followed by a and a or is used to change the size of a file system (see newfs(1M)). and request a particular tape of a multivolume set on which to restart a full restore (see above). This provides a means for interrupting and restarting and Extract the named files from the tape. If the named file matches a directory whose contents had been written onto the tape, and the modifier is not specified, the directory is recursively extracted. The owner, modification time, and mode are restored (if possible). If no file argument is given, the root directory is extracted, which results in the entire contents of the tape being extracted, unless has been specified. Names of the specified files are listed if they occur on the tape. If no file argument is given, the root directory is listed, which results in the entire content of the tape being listed, unless has been specified. The next argument to is used as the dump file number to recover. This is useful if there is more than one dump file on a tape. This mode allows interactive restoration of files from a dump tape. After reading in the directory information from the tape, and provide a shell-like interface that allows the user to move around the directory tree selecting files to be extracted. The available commands are given below; for those commands that require an argument, the default is the current directory. The current directory or specified argument is added to the list of files to be extracted. If a directory is specified, it and all its descendents are added to the extraction list (unless the key is specified on the command line). File names on the extraction list are displayed with a leading when listed by Change the current working directory to the specified argument. The current directory or specified argument is deleted from the list of files to be extracted. If a directory is specified, it and all its descendents are deleted from the extraction list (unless is specified on the command line). The most expedient way to extract files from a directory is to add the directory to the extraction list, then delete unnecessary files. All files named on the extraction list are extracted from the dump tape. and ask which volume the user wants to mount. The fastest way to extract a few files is to start with the last volume, then work toward the first volume. List a summary of the available commands. List the current or specified directory. Entries that are directories are displayed with a trailing Entries marked for extraction are displayed with a leading If the verbose key is set, the inode number of each entry is also listed. Print the full path name of the current working directory. and immediately exit, even if the extraction list is not empty. Set the owner, modes, and times of all directories that are added to the extraction list. Nothing is extracted from the tape. This setting is useful for clean- ing up after a restore aborts prematurely. The sense of the modifier is toggled. When set, the verbose key causes the command to list the inode numbers of all entries. It also causes and to print out information about each file as it is extracted. Function Modifiers The following function modifier characters can be used in addition to the letter that selects the function desired: Specify the block size of the tape in kilobytes. If the option is not specified, and try to determine the tape block size dynamically. Specify the name of the archive instead of If the name of the file is reads from standard input. Thus, and can be used in a pipeline to dump and restore a file system with the command When using this key should be specified, and the next argument supplied should be of the form Extract the actual directory, rather than the files to which it refers. This prevents hierarchical restoration of complete subtrees from the tape, rather than the files to which it refers. Extract by inode numbers rather than by file name. This is useful if only a few files are being extracted and one wants to avoid regenerating the complete path name to the file. Type the name of each file and treat, preceded by its file type. Normally and do their work silently; the modifier specifies verbose output. Do not ask whether to abort the operation if and encounters a tape error. and attempt to skip over the bad tape block(s) and continue. creates a server, either or on the remote machine to access the tape device. DIAGNOSTICS
and complain about bad key characters. and complain if a read error is encountered. If the modifier has been specified, or the user responds and attempt to continue the restore. If the dump extends over more than one tape, and ask the user to change tapes. If the or function has been specified, and also ask which volume the user wants to mount. The fastest way to extract a few files is to start with the last volume and work towards the first volume. There are numerous consistency checks that can be listed by and Most checks are self-explanatory or can ``never happen''. Here are some common errors: The specified file name was listed in the tape directory but not found on the tape. This is caused by tape read errors while looking for the file, and from using a dump tape created on an active file system. A file not listed in the directory showed up. This can occur when using a dump tape created on an active file system. When doing an incremental restore, a tape that was written before the previous incremental tape, or that has too low an incremental level has been loaded. When doing an incremental restore, a tape that does not begin its coverage where the previous incremental tape left off, or that has too high an incremental level has been loaded. A tape read error has occurred. If a file name is specified, the contents of the restored files are probably partially wrong. If restore is skipping an inode or is trying to resynchronize the tape, no extracted files are corrupted, although files may not be found on the tape. After a tape read error, and may have to resynchronize themselves. This message indicates the number of blocks skipped over. WARNINGS
and can get confused when doing incremental restores from dump tapes that were made on active file systems. A level zero dump (see dump(1M)) must be done after a full restore. Since restore runs in user code, it has no control over inode alloca- tion; thus a full dump must be done to get a new set of directories reflecting the new inode numbering, even though the contents of the files are unchanged. AUTHOR
and were developed by the University of California, Berkeley. FILES
Default tape drive. File containing directories on the tape. Owner, mode, and time stamps for directories. Information passed between incremental restores. SEE ALSO
dump(1M), mkfs(1M), mount(1M), newfs(1M), rmt(1M), mt(7). restore(1M)
Man Page