1 .\" Copyright (c) 1985, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)restore.8 8.4 (Berkeley) 5/1/95
33 .\" $Id: restore.8,v 1.14 1998/09/22 10:05:27 roberto Exp $
40 .Nd "restore files or file systems from backups made with dump"
78 option syntax is implemented for backward compatibility, but
79 is not documented here.)
83 command performs the inverse function of
85 A full backup of a file system may be restored and
86 subsequent incremental backups layered on top of it.
88 directory subtrees may be restored from full or partial
91 works across a network;
95 Other arguments to the command are file or directory
96 names specifying the files that are to be restored.
99 flag is specified (see below),
100 the appearance of a directory name refers to
101 the files and (recursively) subdirectories of that directory.
103 Exactly one of the following flags is required:
106 This mode allows interactive restoration of files from a dump.
107 After reading in the directory information from the dump,
109 provides a shell like interface that allows the user to move
110 around the directory tree selecting files to be extracted.
111 The available commands are given below;
112 for those commands that require an argument,
113 the default is the current directory.
116 The current directory or specified argument is added to the list of
117 files to be extracted.
118 If a directory is specified, then it and all its descendents are
119 added to the extraction list
122 flag is specified on the command line).
123 Files that are on the extraction list are prepended with a ``*''
124 when they are listed by
127 Change the current working directory to the specified argument.
128 .It Ic delete Op Ar arg
129 The current directory or specified argument is deleted from the list of
130 files to be extracted.
131 If a directory is specified, then it and all its descendents are
132 deleted from the extraction list
135 flag is specified on the command line).
136 The most expedient way to extract most of the files from a directory
137 is to add the directory to the extraction list and then delete
138 those files that are not needed.
140 All the files that are on the extraction list are extracted
143 will ask which volume the user wishes to mount.
144 The fastest way to extract a few files is to
145 start with the last volume, and work towards the first volume.
147 List a summary of the available commands.
148 .It Ic \&ls Op Ar arg
149 List the current or specified directory.
150 Entries that are directories are appended with a ``/''.
151 Entries that have been marked for extraction are prepended with a ``*''.
153 flag is set the inode number of each entry is also listed.
155 Print the full pathname of the current working directory.
157 Restore immediately exits,
158 even if the extraction list is not empty.
160 All the directories that have been added to the extraction list
161 have their owner, modes, and times set;
162 nothing is extracted from the dump.
163 This is useful for cleaning up after a restore has been prematurely aborted.
168 When set, the verbose flag causes the
170 command to list the inode numbers of all entries.
173 to print out information about each file as it is extracted.
177 requests a particular tape of a multi volume set on which to restart
182 This is useful if the restore has been interrupted.
184 Restore (rebuild a file system).
185 The target file system should be made pristine with
189 into the pristine file system
190 before starting the restoration of the initial level 0 backup. If the
191 level 0 restores successfully, the
193 flag may be used to restore
194 any necessary incremental backups on top of the level 0.
197 flag precludes an interactive file extraction and can be
198 detrimental to one's health if not used carefully (not to mention
199 the disk). An example:
200 .Bd -literal -offset indent
201 newfs /dev/rrp0g eagle
212 in the root directory to pass information between incremental
214 This file should be removed when the last incremental has been
222 may be used to modify file system parameters
223 such as size or block size.
225 The names of the specified files are listed if they occur
227 If no file argument is given,
228 then the root directory is listed,
229 which results in the entire content of the
233 flag has been specified.
236 flag replaces the function of the old
241 The named files are read from the given media.
242 If a named file matches a directory whose contents
246 flag is not specified,
247 the directory is recursively extracted.
248 The owner, modification time,
249 and mode are restored (if possible).
250 If no file argument is given,
251 then the root directory is extracted,
252 which results in the entire content of the
253 backup being extracted,
256 flag has been specified.
259 The following additional options may be specified:
261 .It Fl b Ar blocksize
262 The number of kilobytes per dump record.
265 option is not specified,
267 tries to determine the media block size dynamically.
271 will try to determine dynamically whether the dump was made from an
272 old (pre-4.4) or new format file system. The
274 flag disables this check, and only allows reading a dump in the old
280 may be a special device file
289 (the standard input).
290 If the name of the file is of the form
295 reads from the named file on the remote host using
299 Use Kerberos authentication when contacting the remote tape server.
300 (Only available if this options was enabled when
305 Extract the actual directory,
306 rather than the files that it references.
307 This prevents hierarchical restoration of complete subtrees
310 Extract by inode numbers rather than by file name.
311 This is useful if only a few files are being extracted,
312 and one wants to avoid regenerating the complete pathname
315 Read from the specified
317 on a multi-file tape.
318 File numbering starts at 1.
320 When creating certain types of files, restore may generate a warning
321 diagnostic if they already exist in the target directory.
324 (unlink) flag causes restore to remove old entries before attempting
329 does its work silently.
333 flag causes it to type the name of each file it treats
334 preceded by its file type.
336 Do not ask the user whether to abort the restore in the event of an error.
337 Always try to skip over the bad block(s) and continue.
340 Complaints if it gets a read error.
343 has been specified, or the user responds
346 will attempt to continue the restore.
348 If a backup was made using more than one tape volume,
350 will notify the user when it is time to mount the next volume.
355 flag has been specified,
357 will also ask which volume the user wishes to mount.
358 The fastest way to extract a few files is to
359 start with the last volume, and work towards the first volume.
361 There are numerous consistency checks that can be listed by
363 Most checks are self-explanatory or can ``never happen''.
364 Common errors are given below.
366 .Bl -tag -width Ds -compact
367 .It Converting to new file system format.
368 A dump tape created from the old file system has been loaded.
369 It is automatically converted to the new file system format.
371 .It <filename>: not found on tape
372 The specified file name was listed in the tape directory,
373 but was not found on the tape.
374 This is caused by tape read errors while looking for the file,
375 and from using a dump tape created on an active file system.
377 .It expected next file <inumber>, got <inumber>
378 A file that was not listed in the directory showed up.
379 This can occur when using a dump created on an active file system.
381 .It Incremental dump too low
382 When doing incremental restore,
383 a dump that was written before the previous incremental dump,
384 or that has too low an incremental level has been loaded.
386 .It Incremental dump too high
387 When doing incremental restore,
388 a dump that does not begin its coverage where the previous incremental
390 or that has too high an incremental level has been loaded.
392 .It Tape read error while restoring <filename>
393 .It Tape read error while skipping over inode <inumber>
394 .It Tape read error while trying to resynchronize
395 A tape (or other media) read error has occurred.
396 If a file name is specified,
397 then its contents are probably partially wrong.
398 If an inode is being skipped or the tape is trying to resynchronize,
399 then no extracted files have been corrupted,
400 though files may not be found on the tape.
402 .It resync restore, skipped <num> blocks
403 After a dump read error,
405 may have to resynchronize itself.
406 This message lists the number of blocks that were skipped over.
409 .Bl -tag -width "./restoresymtable" -compact
411 the default tape drive
413 file containing directories on the tape.
415 owner, mode, and time stamps for directories.
416 .It Pa \&./restoresymtable
417 information passed between incremental restores.
427 can get confused when doing incremental restores from
428 dumps that were made on active file systems.
430 A level zero dump must be done after a full restore.
431 Because restore runs in user code,
432 it has no control over inode allocation;
433 thus a full dump must be done to get a new set of directories
434 reflecting the new inode numbering,
435 even though the contents of the files is unchanged.
437 To do a network restore, you have to run restore as root. This is due
438 to the previous security history of dump and restore. (restore is
439 written to be setuid root, but we are not certain all bugs are gone
440 from the restore code - run setuid at your own risk.)