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