]> git.wh0rd.org - dump.git/blame_incremental - restore/restore.8.in
Made dump report the total number of MB written to tape.
[dump.git] / restore / restore.8.in
... / ...
CommitLineData
1.\" Copyright (c) 1985, 1991, 1993
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
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.
19.\"
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
30.\" SUCH DAMAGE.
31.\"
32.\" $Id: restore.8.in,v 1.7 2000/01/21 10:23:30 stelian Exp $
33.\"
34.Dd __DATE__
35.Dt RESTORE 8
36.Os "restore __VERSION__"
37.Sh NAME
38.Nm restore
39.Nd "restore files or file systems from backups made with dump"
40.Sh SYNOPSIS
41.Nm restore
42.Fl C
43.Op Fl ckMvy
44.Op Fl b Ar blocksize
45.Op Fl D Ar filesystem
46.Op Fl f Ar file
47.Op Fl s Ar fileno
48.Op Fl T Ar directory
49.Nm restore
50.Fl i
51.Op Fl chkmMNuvy
52.Op Fl b Ar blocksize
53.Op Fl f Ar file
54.Op Fl s Ar fileno
55.Op Fl T Ar directory
56.Nm restore
57.Fl R
58.Op Fl ckMNuvy
59.Op Fl b Ar blocksize
60.Op Fl f Ar file
61.Op Fl s Ar fileno
62.Op Fl T Ar directory
63.Nm restore
64.Fl r
65.Op Fl ckMNuvy
66.Op Fl b Ar blocksize
67.Op Fl f Ar file
68.Op Fl s Ar fileno
69.Op Fl T Ar directory
70.Nm restore
71.Fl t
72.Op Fl chkMNuvy
73.Op Fl b Ar blocksize
74.Op Fl f Ar file
75.Op Fl s Ar fileno
76.Op Fl T Ar directory
77.Op file ...
78.Nm restore
79.Fl x
80.Op Fl chkmMNuvy
81.Op Fl b Ar blocksize
82.Op Fl f Ar file
83.Op Fl s Ar fileno
84.Op Fl T Ar directory
85.Op file ...
86.Pp
87.in
88(The
89.Bx 4.3
90option syntax is implemented for backward compatibility but
91is not documented here.)
92.Sh DESCRIPTION
93The
94.Nm restore
95command performs the inverse function of
96.Xr dump 8 .
97A full backup of a file system may be restored and
98subsequent incremental backups layered on top of it.
99Single files and
100directory subtrees may be restored from full or partial
101backups.
102.Nm Restore
103works across a network;
104to do this see the
105.Fl f
106flag described below.
107Other arguments to the command are file or directory
108names specifying the files that are to be restored.
109Unless the
110.Fl h
111flag is specified (see below),
112the appearance of a directory name refers to
113the files and (recursively) subdirectories of that directory.
114.Pp
115Exactly one of the following flags is required:
116.Bl -tag -width Ds
117.It Fl C
118This mode allows comparison of files from a dump.
119.Nm Restore
120reads the backup and compares its contents with files present on the
121disk.
122It first changes its working directory to the root of the filesystem
123that was dumped and compares the tape with the files in its new
124current directory.
125.It Fl i
126This mode allows interactive restoration of files from a dump.
127After reading in the directory information from the dump,
128.Nm restore
129provides a shell like interface that allows the user to move
130around the directory tree selecting files to be extracted.
131The available commands are given below;
132for those commands that require an argument,
133the default is the current directory.
134.Bl -tag -width Fl
135.It Ic add Op Ar arg
136The current directory or specified argument is added to the list of
137files to be extracted.
138If a directory is specified, then it and all its descendents are
139added to the extraction list
140(unless the
141.Fl h
142flag is specified on the command line).
143Files that are on the extraction list are prepended with a
144.Dq \&*
145when they are listed by
146.Ic ls .
147.It Ic \&cd Ar arg
148Change the current working directory to the specified argument.
149.It Ic delete Op Ar arg
150The current directory or specified argument is deleted from the list of
151files to be extracted.
152If a directory is specified, then it and all its descendents are
153deleted from the extraction list
154(unless the
155.Fl h
156flag is specified on the command line).
157The most expedient way to extract most of the files from a directory
158is to add the directory to the extraction list and then delete
159those files that are not needed.
160.It Ic extract
161All files on the extraction list are extracted
162from the dump.
163.Nm Restore
164will ask which volume the user wishes to mount.
165The fastest way to extract a few files is to
166start with the last volume and work towards the first volume.
167.It Ic help
168List a summary of the available commands.
169.It Ic \&ls Op Ar arg
170List the current or specified directory.
171Entries that are directories are appended with a
172.Dq \&* .
173Entries that have been marked for extraction are prepended with a ``*''.
174If the verbose
175flag is set, the inode number of each entry is also listed.
176.It Ic pwd
177Print the full pathname of the current working directory.
178.It Ic quit
179Restore immediately exits,
180even if the extraction list is not empty.
181.It Ic setmodes
182All directories that have been added to the extraction list
183have their owner, modes, and times set;
184nothing is extracted from the dump.
185This is useful for cleaning up after a restore has been prematurely aborted.
186.It Ic verbose
187The sense of the
188.Fl v
189flag is toggled.
190When set, the verbose flag causes the
191.Ic ls
192command to list the inode numbers of all entries.
193It also causes
194.Nm restore
195to print out information about each file as it is extracted.
196.El
197.It Fl R
198.Nm Restore
199requests a particular tape of a multi-volume set on which to restart
200a full restore
201(see the
202.Fl r
203flag below).
204This is useful if the restore has been interrupted.
205.It Fl r
206Restore (rebuild) a file system.
207The target file system should be made pristine with
208.Xr mke2fs 8 ,
209mounted, and the user
210.Xr cd Ns 'd
211into the pristine file system
212before starting the restoration of the initial level 0 backup. If the
213level 0 restores successfully, the
214.Fl r
215flag may be used to restore
216any necessary incremental backups on top of the level 0.
217The
218.Fl r
219flag precludes an interactive file extraction and can be
220detrimental to one's health (not to mention the disk) if not used carefully.
221An example:
222.Bd -literal -offset indent
223mke2fs /dev/sda1
224mount /dev/sda1 /mnt
225cd /mnt
226
227restore rf /dev/st0
228.Ed
229.Pp
230Note that
231.Nm restore
232leaves a file
233.Pa restoresymtable
234in the root directory to pass information between incremental
235restore passes.
236This file should be removed when the last incremental has been
237restored.
238.Pp
239.Nm Restore ,
240in conjunction with
241.Xr mke2fs 8
242and
243.Xr dump 8 ,
244may be used to modify file system parameters
245such as size or block size.
246.It Fl t
247The names of the specified files are listed if they occur
248on the backup.
249If no file argument is given,
250the root directory is listed,
251which results in the entire content of the
252backup being listed,
253unless the
254.Fl h
255flag has been specified.
256Note that the
257.Fl t
258flag replaces the function of the old
259.Xr dumpdir 8
260program.
261.ne 1i
262.It Fl x
263The named files are read from the given media.
264If a named file matches a directory whose contents
265are on the backup
266and the
267.Fl h
268flag is not specified,
269the directory is recursively extracted.
270The owner, modification time,
271and mode are restored (if possible).
272If no file argument is given,
273the root directory is extracted,
274which results in the entire content of the
275backup being extracted,
276unless the
277.Fl h
278flag has been specified.
279.El
280.Pp
281The following additional options may be specified:
282.Bl -tag -width Ds
283.It Fl b Ar blocksize
284The number of kilobytes per dump record.
285If the
286.Fl b
287option is not specified,
288.Nm restore
289tries to determine the media block size dynamically.
290.It Fl c
291Normally,
292.Nm restore
293will try to determine dynamically whether the dump was made from an
294old (pre-4.4) or new format file system. The
295.Fl c
296flag disables this check, and only allows reading a dump in the old
297format.
298.It Fl D Ar filesystem
299The
300.Fl D
301flag allows the user to specify the filesystem name when using
302.Nm restore
303with the
304.Fl C
305option to check the backup.
306.It Fl f Ar file
307Read the backup from
308.Ar file ;
309.Ar file
310may be a special device file
311like
312.Pa /dev/st0
313(a tape drive),
314.Pa /dev/sda1
315(a disk drive),
316an ordinary file,
317or
318.Ql Fl
319(the standard input).
320If the name of the file is of the form
321.Dq host:file
322or
323.Dq user@host:file ,
324.Nm restore
325reads from the named file on the remote host using
326.Xr rmt 8 .
327.Pp
328.It Fl k
329Use Kerberos authentication when contacting the remote tape server.
330(Only available if this options was enabled when
331.Nm restore
332was compiled.)
333.Pp
334.It Fl h
335Extract the actual directory,
336rather than the files that it references.
337This prevents hierarchical restoration of complete subtrees
338from the dump.
339.It Fl m
340Extract by inode numbers rather than by file name.
341This is useful if only a few files are being extracted,
342and one wants to avoid regenerating the complete pathname
343to the file.
344.It Fl M
345Enables the multi-volume feature (for reading dumps made using
346the
347.Fl M
348option of dump). The name specified with
349.Fl f
350is treated as a prefix and
351.Nm
352tries to read in sequence from <prefix>001, <prefix>002 etc.
353.It Fl N
354The
355.Fl N
356flag causes
357.Nm
358to only print file names. Files are not extracted.
359.It Fl s Ar fileno
360Read from the specified
361.Ar fileno
362on a multi-file tape.
363File numbering starts at 1.
364.It Fl T Ar directory
365The
366.Fl T
367flag allows the user to specify a directory to use for the storage of
368temporary files. The default value is /tmp. This flag is most useful
369when restoring files after having booted from a floppy. There might be little
370or no space on the floppy filesystem, but another source of space might exist.
371.It Fl u
372When creating certain types of files, restore may generate a warning
373diagnostic if they already exist in the target directory.
374To prevent this, the
375.Fl u
376(unlink) flag causes restore to remove old entries before attempting
377to create new ones.
378.It Fl v
379Normally
380.Nm restore
381does its work silently.
382The
383.Fl v
384(verbose)
385flag causes it to type the name of each file it treats
386preceded by its file type.
387.It Fl y
388Do not ask the user whether to abort the restore in the event of an error.
389Always try to skip over the bad block(s) and continue.
390.El
391.Sh DIAGNOSTICS
392Complains if it gets a read error.
393If
394.Fl y
395has been specified, or the user responds
396.Ql y ,
397.Nm restore
398will attempt to continue the restore.
399.Pp
400If a backup was made using more than one tape volume,
401.Nm restore
402will notify the user when it is time to mount the next volume.
403If the
404.Fl x
405or
406.Fl i
407flag has been specified,
408.Nm restore
409will also ask which volume the user wishes to mount.
410The fastest way to extract a few files is to
411start with the last volume, and work towards the first volume.
412.Pp
413There are numerous consistency checks that can be listed by
414.Nm restore .
415Most checks are self-explanatory or can
416.Dq never happen .
417Common errors are given below.
418.Pp
419.Bl -tag -width Ds -compact
420.It Converting to new file system format
421A dump tape created from the old file system has been loaded.
422It is automatically converted to the new file system format.
423.Pp
424.It <filename>: not found on tape
425The specified file name was listed in the tape directory,
426but was not found on the tape.
427This is caused by tape read errors while looking for the file,
428and from using a dump tape created on an active file system.
429.Pp
430.It expected next file <inumber>, got <inumber>
431A file that was not listed in the directory showed up.
432This can occur when using a dump created on an active file system.
433.Pp
434.It Incremental dump too low
435When doing an incremental restore,
436a dump that was written before the previous incremental dump,
437or that has too low an incremental level has been loaded.
438.Pp
439.It Incremental dump too high
440When doing an incremental restore,
441a dump that does not begin its coverage where the previous incremental
442dump left off,
443or that has too high an incremental level has been loaded.
444.Pp
445.It Tape read error while restoring <filename>
446.It Tape read error while skipping over inode <inumber>
447.It Tape read error while trying to resynchronize
448A tape (or other media) read error has occurred.
449If a file name is specified,
450its contents are probably partially wrong.
451If an inode is being skipped or the tape is trying to resynchronize,
452no extracted files have been corrupted,
453though files may not be found on the tape.
454.Pp
455.It resync restore, skipped <num> blocks
456After a dump read error,
457.Nm restore
458may have to resynchronize itself.
459This message lists the number of blocks that were skipped over.
460.El
461.Sh ENVIRONMENT
462If the following environment variable exists it will be utilized by
463.Nm restore :
464.Pp
465.Bl -tag -width "TMPDIR" -compact
466.It Ev TAPE
467If no -f option was specified,
468.Nm
469will use the device specified via
470.Ev TAPE
471as the dump device.
472.Ev TAPE
473may be of the form
474.Qq tapename ,
475.Qq host:tapename
476or
477.Qq user@host:tapename .
478.It Ev TMPDIR
479The directory given in
480.Ev TMPDIR
481will be used
482instead of
483.Pa /tmp
484to store temporary files.
485.It Ev RMT
486The environment variable
487.Ev RMT
488will be used to determine the pathname of the remote
489.Xr rmt 8
490program.
491.It Ev RSH
492.Nm Restore
493uses the contents of this variable to determine the name of the
494remote shell command to use when doing a network restore (rsh, ssh etc.).
495If this variable is not set,
496.Xr rcmd 3
497will be used, but only root will be able to do a network restore.
498.Sh FILES
499.Bl -tag -width "./restoresymtable" -compact
500.It Pa /dev/st0
501the default tape drive
502.It Pa /tmp/rstdir*
503file containing directories on the tape
504.It Pa /tmp/rstmode*
505owner, mode, and time stamps for directories
506.It Pa \&./restoresymtable
507information passed between incremental restores
508.El
509.Sh SEE ALSO
510.Xr dump 8 ,
511.Xr mount 8 ,
512.Xr mke2fs 8 ,
513.Xr rmt 8
514.Sh BUGS
515.Nm Restore
516can get confused when doing incremental restores from
517dumps that were made on active file systems.
518.Pp
519A level 0 dump must be done after a full restore.
520Because
521.Nm restore
522runs in user code,
523it has no control over inode allocation;
524thus a full dump must be done to get a new set of directories
525reflecting the new inode numbering,
526even though the content of the files is unchanged.
527.Pp
528The temporary files
529.Pa /tmp/rstdir*
530and
531.Pa /tmp/rstmode*
532are generated with a unique name based on the date of the dump
533and the process ID (see
534.Xr mktemp 3 ),
535except when
536.Fl r
537or
538.Fl R
539is used.
540Because
541.Fl R
542allows you to restart a
543.Fl r
544operation that may have been interrupted, the temporary files should
545be the same across different processes.
546In all other cases, the files are unique because it is possible to
547have two different dumps started at the same time, and separate
548operations shouldn't conflict with each other.
549.Pp
550To do a network restore, you have to run restore as root or use
551a remote shell replacement (see RSH variable). This is due
552to the previous security history of dump and restore. (restore is
553written to be setuid root, but we are not certain all bugs are gone
554from the restore code - run setuid at your own risk.)
555.Sh AUTHOR
556The
557.Nm dump/restore
558backup suit was ported to Linux's Second Extended File System
559by Remy Card <card@Linux.EU.Org>. He maintained the initial versions
560of dump (up and including 0.4b4, released in january 1997).
561.Pp
562Starting with 0.4b5, the new maintainer is Stelian Pop
563.br
564<pop@cybercable.fr>.
565.Sh AVAILABILITY
566The
567.Nm dump/restore
568backup suit is available from
569.br
570http://dump.sourceforge.net
571.Sh HISTORY
572The
573.Nm restore
574command appeared in
575.Bx 4.2 .