Manual Pages

Table of Contents


na_restore - file system restore


restore options [ arguments ... ] [ files ... ]


The restore command restores files from backup tapes created with the Data ONTAP dump (see na_dump(1)) command. A full backup of a file system may be restored and subsequent incremental backups layered on top of it. The actions of restore are controlled by the given options, which are a string of characters containing at most one function letter and possibly one or more function modifiers.

Depending on the function letter, files may have to be specified following the arguments.


The restore command's behavior is controlled by a command key entered in the options field. This key is mandatory, but may be located anywhere in the options field. The function keys (and their associated restore behavior) is as follows:

Restores (rebuilds a file system or subtree). The target subtree should be made pristine by removing it from a client of the server or, if the entire file system or all subtrees of the file system are to be restored, by booting from floppy disk and selecting the "Install new file system." option, before starting the restoration of the initial level 0 backup. If the level 0 restores successfully, the r key can be used to restore any necessary incremental backups on top of the level 0.

Note that restore r will restore all files from the dump tape(s).

An example:

  restore rf rst0a

Note that restore leaves a file restore_symboltable in the directory that was dumped to pass information between incremental restore passes. This file should be removed when the last incremental has been restored.

The restore command requests a particular tape of a multi-volume set on which to restart a full restore (see the r key above). This is useful if the restore has been interrupted.

Lists the names of the specified files if they occur on the backup. If no files argument is given, then the root directory is listed, which results in the entire content of the backup being listed.

Lists the names of specified files if they are in the backup and happen to be the roots of qtrees. Also lists qtree properties (security style and oplock status) for each qtree root. If no file argument is given, then the root directory is listed, which results in all qtree roots on the dump file being listed.

Note: Older dump files do not contain qtree information, so these will not show qtree data (nor will qtrees be restored using the other flags).

Extracts the named files. If a named file matches a directory whose contents were backed up, the directory is recursively extracted. The owner, modification time, and mode are restored. If no files argument is specified, the backup root directory is extracted. This results in the entire backup being restored.


If characters in the options string take an arguments, the arguments (which follow the options string) are specified in the order of the letters which apply to them. For example:

  restore rfD rst0a /vol/users/backup

Here, restore has two options that take arguments, `f' and `D'. The ``rst0a'' argument applies to `f', and the ``/vol/users/backup'' argument applies to `D'.

The following characters can be used in the options string, in addition to the letter that selects the function desired.

Ignore any ACLs on tape. Even if Access Control Lists are present on tape, do not restore them to the file system. By default, restore recovers as much metadata as is available to it; if the dumped file system had ACLs attached to files, restore will attach them to the restored versions of those files.

D target
By default, files will be restored into the directory from which they were dumped. If the D option is specified, the next argument to restore is the full absolute pathname of a directory into which the files should be restored.

Force restore to continue, regardless of inode limitations. If restore finds out that there are fewer free inodes than the number of files it needs to create, it aborts. This might not be necessary; in some cases, the new files that restore creates can overwrite older versions of those files, thereby not taking up any ``new'' inodes. The F flag forces restore to proceed on the assumption that this case is common enough that the file system will not run out of free inodes during the restore. If this flag is specified, and there are indeed not enough inodes for the restore to complete, it will abort in the middle of its run.

Don't write data to disk. This is used for dump verification only.

Ignore qtree information. Normally, restore will restore qtree information that is dumped. If this flag is specified, any qtree information on the dump file will not be restored.

b blksize
The next argument to restore is used as the block size of the media (in kilobytes). If the b option is not specified, restore tries to determine the media block size dynamically.

f file The next argument to restore is used as the name of the archive instead of the standard input. If the name of the file is -, restore reads from standard input.

s fileno
The next argument to restore is a number which selects the file on a multi-file dump tape. File numbering starts at 1, and is based on the current tape position.

Normally restore does its work silently. The v (verbose) key causes it to type the name of each file it treats preceded by its file type.

Will automatically answer "yes" should restore prompt for user confirmation.


Complains about bad key characters.

Complains if it gets a read error. If y has been specified, or the user responds y, restore will attempt to continue the restore.

If a backup was made using more than one tape volume, restore will notify the user when it is time to mount the next tape volume.

There are numerous consistency checks that can be listed by restore. Most checks are self-explanatory or can ``never happen''. Common errors are given below.

filename: not found on tape
The specified file name was listed in the tape directory, but was 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.

expected next file inumber, got inumber A file that was not listed in the directory showed up. This can occur when using a dump created on an active file system.

Incremental dump too low
When doing incremental restore, a dump that was written before the previous incremental dump, or that has too low an incremental level has been loaded.

Incremental dump too high
When doing incremental restore, a dump that does not begin its coverage where the previous incremental dump left off, or that has too high an incremental level has been loaded.

Tape read error while restoring filename

Tape read error while skipping over inode inumber

Tape read error while trying to resynchronize A tape (or other media) read error has occurred. If a file name is specified, then its contents are probably partially wrong. If an inode is being skipped or the tape is trying to resynchronize, then no extracted files have been corrupted, though files may not be found on the tape.

resync restore, skipped num blocks
After a dump read error, restore may have to resynchronize itself. This message lists the number of blocks that were skipped over.


Older versions of dump did not dump qtree information. If an old dump file is given to restore, it will not restore any qtrees that were present on that dumped volume.

If there is qtree information present on the dump file, restore will attempt to recover it and (re-)create the qtree root with the appropriate information. If no directory exists in the target path of the qtree, and it is possible to create a qtree root, restore will do so, and set the attributes (security style, oplock status) to those of the dumped qtree. Note that the root of a volume acts as an implicit qtree; so if the root is restored to a non-existent, first-level pathname, the new directory created there will be the root of a qtree with the same attributes as those of the dumped volume.

You can use the T function letter to list qtree information on the dump file. You can use the Q option to ignore qtree information on the dump.


In takeover mode, the failed node cannot access its tape devices. The restore command can only restore from the tape devices on the live node.


/tmp/rstdir* file containing directories on the tape.

owner, mode, and time stamps for directories.

information passed between incremental restores.




A level zero dump must be done after a full restore. restore has no control over inode allocation; thus a full restore must be done to get a new set of directories reflecting the new inode numbering, even though the contents of the files is unchanged.

restore does not support the -i option for interactive restoring of files. Alternatively, provided your file access is limited to NFS, you could use restore -i from a UNIX client. (That alternative won't work correctly for a file system with CIFS clients, because the UNIX restore utility doesn't support the multi-protocol directory structures used by the node.) If your tape drive is local to the node, you can use the rmt facility (see na_rmt(8)) on the node to access the local tape drive from the client doing the interactive restore.



Table of Contents