RESTORE | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
NAME | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
SYNOPSIS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
restore -i [-acdhHklmMNouvVy] [-A file] [-b blocksize] [-f file] [-F script] [-Q file] [-s fileno] [-T directory]
restore -P file [-acdhHklmMNuvVy] [-A file] [-b blocksize] [-f file] [-F script] [-s fileno] [-T directory] [-X filelist] [ file ... ]
restore -R [-cdHklMNuvVy] [-b blocksize] [-f file] [-F script] [-s fileno] [-T directory]
restore -r [-cdHklMNuvVy] [-b blocksize] [-f file] [-F script] [-s fileno] [-T directory]
restore -t [-cdhHklMNuvVy] [-A file] [-b blocksize] [-f file] [-F script] [-Q file] [-s fileno] [-T directory] [-X filelist] [ file ... ]
restore -x [-adchHklmMNouvVy] [-A file] [-b blocksize] [-f file] [-F script] [-Q file] [-s fileno] [-T directory] [-X filelist] [ file ... ]
DESCRIPTION | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
Exactly one of the following flags is required:
OPTIONS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
(The 4.3BSD option syntax is implemented for backward compatibility but is not documented here.)
DIAGNOSTICS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
If a backup was made using more than one tape volume, restore will notify the user when it is time to mount the next volume. If the -x or -i flag has been specified, restore will also ask which volume the user wishes 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 restore. Most checks are self-explanatory or can ``never happen''. Common errors are given below:
EXIT STATUS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
When doing a comparison of files from a dump, an exit code of 2 indicates that some files were modified or deleted since the dump was made.
ENVIRONMENT | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
FILES | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
SEE ALSO | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
BUGS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
A level 0 dump must be done after a full restore. Because restore runs in user code, it has no control over inode allocation; thus a full dump must be done to get a new set of directories reflecting the new inode numbering, even though the content of the files is unchanged.
The temporary files /tmp/rstdir* and /tmp/rstmode* are generated with a unique name based on the date of the dump and the process ID (see mktemp(3)), except when -r or -R is used. Because -R allows you to restart a -r operation that may have been interrupted, the temporary files should be the same across different processes. In all other cases, the files are unique because it is possible to have two different dumps started at the same time, and separate operations shouldn't conflict with each other.
To do a network restore, you have to run restore as root or use a remote shell replacement (see RSH variable). This is due to the previous security history of dump and restore. ( restore is written to be setuid root, but we are not certain all bugs are gone from the code - run setuid at your own risk.)
At the end of restores in -i or -x modes (unless -o option is in use), restore will ask the operator whether to set the permissions on the current directory. If the operator confirms this action, the permissions on the directory from where restore was launched will be replaced by the permissions on the dumped root inode. Although this behaviour is not really a bug, it has proven itself to be confusing for many users, so it is recommended to answer 'no', unless you're performing a full restore and you do want to restore the permissions on '/'.
It should be underlined that because it runs in user code, restore , when run with the -C option, sees the files as the kernel presents them, whereas dump sees all the files on a given filesystem. In particular, this can cause some confusion when comparing a dumped filesystem a part of which is hidden by a filesystem mounted on top of it.
AUTHOR | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
Starting with 0.4b5, the new maintainer is Stelian Pop <stelian@popies.net>.
AVAILABILITY | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
HISTORY | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
Sommaire | Début | Suivant | Sommaire | Préc.page.lue | Accueil |
Table des mots clés | Début | Suivant | Sommaire | Préc.page.lue | Accueil |
-a | OPTIONS |
-A archive_file | OPTIONS |
-b blocksize | OPTIONS |
-c | OPTIONS |
-d | OPTIONS |
-D filesystem | OPTIONS |
-f file | OPTIONS |
-F script | OPTIONS |
-h | OPTIONS |
-H hash_size | OPTIONS |
-i | DESCRIPTION |
-k | OPTIONS |
-l | OPTIONS |
-L limit | OPTIONS |
-M | OPTIONS |
-N | OPTIONS |
-o | OPTIONS |
-P file | DESCRIPTION |
-Q file | OPTIONS |
-R | DESCRIPTION |
-s fileno | OPTIONS |
-t | DESCRIPTION |
-T directory | OPTIONS |
-u | OPTIONS |
-v | OPTIONS |
-x | DESCRIPTION |
-X filelist | OPTIONS |
-y | OPTIONS |
RMT | ENVIRONMENT |
RSH | ENVIRONMENT |
TAPE | ENVIRONMENT |
TMPDIR | ENVIRONMENT |