]> git.wh0rd.org - dump.git/blame_incremental - restore/restore.8.in
Fixed a markup bug in dump man page.
[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.27 2002/06/08 07:10:37 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 cdklMvVy
44.Op Fl b Ar blocksize
45.Op Fl D Ar filesystem
46.Op Fl f Ar file
47.Op Fl F Ar script
48.Op Fl L Ar limit
49.Op Fl s Ar fileno
50.Op Fl T Ar directory
51.Nm restore
52.Fl i
53.Op Fl acdhklmMNouvVy
54.Op Fl A Ar file
55.Op Fl b Ar blocksize
56.Op Fl f Ar file
57.Op Fl F Ar script
58.Op Fl Q Ar file
59.Op Fl s Ar fileno
60.Op Fl T Ar directory
61.Nm restore
62.Fl P Ar file
63.Op Fl acdhklmMNuvVy
64.Op Fl A Ar file
65.Op Fl b Ar blocksize
66.Op Fl f Ar file
67.Op Fl F Ar script
68.Op Fl s Ar fileno
69.Op Fl T Ar directory
70.Op Fl X Ar filelist
71.Op file ...
72.Nm restore
73.Fl R
74.Op Fl cdklMNuvVy
75.Op Fl b Ar blocksize
76.Op Fl f Ar file
77.Op Fl F Ar script
78.Op Fl s Ar fileno
79.Op Fl T Ar directory
80.Nm restore
81.Fl r
82.Op Fl cdklMNuvVy
83.Op Fl b Ar blocksize
84.Op Fl f Ar file
85.Op Fl F Ar script
86.Op Fl s Ar fileno
87.Op Fl T Ar directory
88.Nm restore
89.Fl t
90.Op Fl cdhklMNuvVy
91.Op Fl A Ar file
92.Op Fl b Ar blocksize
93.Op Fl f Ar file
94.Op Fl F Ar script
95.Op Fl Q Ar file
96.Op Fl s Ar fileno
97.Op Fl T Ar directory
98.Op Fl X Ar filelist
99.Op file ...
100.Nm restore
101.Fl x
102.Op Fl adchklmMNouvVy
103.Op Fl A Ar file
104.Op Fl b Ar blocksize
105.Op Fl f Ar file
106.Op Fl F Ar script
107.Op Fl Q Ar file
108.Op Fl s Ar fileno
109.Op Fl T Ar directory
110.Op Fl X Ar filelist
111.Op file ...
112.Pp
113.in
114(The
115.Bx 4.3
116option syntax is implemented for backward compatibility but
117is not documented here.)
118.Sh DESCRIPTION
119The
120.Nm restore
121command performs the inverse function of
122.Xr dump 8 .
123A full backup of a file system may be restored and
124subsequent incremental backups layered on top of it.
125Single files and
126directory subtrees may be restored from full or partial
127backups.
128.Nm Restore
129works across a network;
130to do this see the
131.Fl f
132flag described below.
133Other arguments to the command are file or directory
134names specifying the files that are to be restored.
135Unless the
136.Fl h
137flag is specified (see below),
138the appearance of a directory name refers to
139the files and (recursively) subdirectories of that directory.
140.Pp
141Exactly one of the following flags is required:
142.Bl -tag -width Ds
143.It Fl C
144This mode allows comparison of files from a dump.
145.Nm Restore
146reads the backup and compares its contents with files present on the
147disk.
148It first changes its working directory to the root of the filesystem
149that was dumped and compares the tape with the files in its new
150current directory.
151See also the
152.Fl L
153flag described below.
154.It Fl i
155This mode allows interactive restoration of files from a dump.
156After reading in the directory information from the dump,
157.Nm restore
158provides a shell like interface that allows the user to move
159around the directory tree selecting files to be extracted.
160The available commands are given below;
161for those commands that require an argument,
162the default is the current directory.
163.Bl -tag -width Fl
164.It Ic add Op Ar arg
165The current directory or specified argument is added to the list of
166files to be extracted.
167If a directory is specified, then it and all its descendents are
168added to the extraction list
169(unless the
170.Fl h
171flag is specified on the command line).
172Files that are on the extraction list are prepended with a
173.Dq \&*
174when they are listed by
175.Ic ls .
176.It Ic \&cd Ar arg
177Change the current working directory to the specified argument.
178.It Ic delete Op Ar arg
179The current directory or specified argument is deleted from the list of
180files to be extracted.
181If a directory is specified, then it and all its descendents are
182deleted from the extraction list
183(unless the
184.Fl h
185flag is specified on the command line).
186The most expedient way to extract most of the files from a directory
187is to add the directory to the extraction list and then delete
188those files that are not needed.
189.It Ic extract
190All files on the extraction list are extracted
191from the dump.
192.Nm Restore
193will ask which volume the user wishes to mount.
194The fastest way to extract a few files is to
195start with the last volume and work towards the first volume.
196.It Ic help
197List a summary of the available commands.
198.It Ic \&ls Op Ar arg
199List the current or specified directory.
200Entries that are directories are appended with a
201.Dq \&* .
202Entries that have been marked for extraction are prepended with a ``*''.
203If the verbose
204flag is set, the inode number of each entry is also listed.
205.It Ic pwd
206Print the full pathname of the current working directory.
207.It Ic quit
208Restore immediately exits,
209even if the extraction list is not empty.
210.It Ic setmodes
211All directories that have been added to the extraction list
212have their owner, modes, and times set;
213nothing is extracted from the dump.
214This is useful for cleaning up after a restore has been prematurely aborted.
215.It Ic verbose
216The sense of the
217.Fl v
218flag is toggled.
219When set, the verbose flag causes the
220.Ic ls
221command to list the inode numbers of all entries.
222It also causes
223.Nm restore
224to print out information about each file as it is extracted.
225.El
226.It Fl P Ar file
227.Nm Restore
228creates a new Quick File Access file
229.Ar file
230from an existing dump file without restoring its contents.
231.It Fl R
232.Nm Restore
233requests a particular tape of a multi-volume set on which to restart
234a full restore
235(see the
236.Fl r
237flag below).
238This is useful if the restore has been interrupted.
239.It Fl r
240Restore (rebuild) a file system.
241The target file system should be made pristine with
242.Xr mke2fs 8 ,
243mounted, and the user
244.Xr cd Ns 'd
245into the pristine file system
246before starting the restoration of the initial level 0 backup. If the
247level 0 restores successfully, the
248.Fl r
249flag may be used to restore
250any necessary incremental backups on top of the level 0.
251The
252.Fl r
253flag precludes an interactive file extraction and can be
254detrimental to one's health (not to mention the disk) if not used carefully.
255An example:
256.Bd -literal -offset indent
257mke2fs /dev/sda1
258mount /dev/sda1 /mnt
259cd /mnt
260
261restore rf /dev/st0
262.Ed
263.Pp
264Note that
265.Nm restore
266leaves a file
267.Pa restoresymtable
268in the root directory to pass information between incremental
269restore passes.
270This file should be removed when the last incremental has been
271restored.
272.Pp
273.Nm Restore ,
274in conjunction with
275.Xr mke2fs 8
276and
277.Xr dump 8 ,
278may be used to modify file system parameters
279such as size or block size.
280.It Fl t
281The names of the specified files are listed if they occur
282on the backup.
283If no file argument is given,
284the root directory is listed,
285which results in the entire content of the
286backup being listed,
287unless the
288.Fl h
289flag has been specified.
290Note that the
291.Fl t
292flag replaces the function of the old
293.Xr dumpdir 8
294program.
295See also the
296.Fl X
297option below.
298.ne 1i
299.It Fl x
300The named files are read from the given media.
301If a named file matches a directory whose contents
302are on the backup
303and the
304.Fl h
305flag is not specified,
306the directory is recursively extracted.
307The owner, modification time,
308and mode are restored (if possible).
309If no file argument is given,
310the root directory is extracted,
311which results in the entire content of the
312backup being extracted,
313unless the
314.Fl h
315flag has been specified.
316See also the
317.Fl X
318option below.
319.El
320.Pp
321The following additional options may be specified:
322.Bl -tag -width Ds
323.It Fl a
324In
325.Fl i
326or
327.Fl x
328mode,
329.Nm restore
330does ask the user for the volume number on which the files to
331be extracted are supposed to be (in order to minimise the time
332be reading only the interesting volumes). The
333.Fl a
334option disables this behaviour and reads all the volumes starting
335with 1. This option is useful when the operator does not know on which
336volume the files to be extracted are and/or when he prefers the
337longer unattended mode rather than the shorter interactive mode.
338.It Fl A Ar archive_file
339Read the table of contents from
340.Ar archive_file
341instead of the media. This option can be used in combination with the
342.Fl t,
343.Fl i,
344or
345.Fl x
346options, making it possible to check whether files are on the media
347without having to mount the media.
348.It Fl b Ar blocksize
349The number of kilobytes per dump record.
350If the
351.Fl b
352option is not specified,
353.Nm restore
354tries to determine the media block size dynamically.
355.It Fl c
356Normally,
357.Nm restore
358will try to determine dynamically whether the dump was made from an
359old (pre-4.4) or new format file system. The
360.Fl c
361flag disables this check, and only allows reading a dump in the old
362format.
363.It Fl d
364The
365.Fl d
366(debug)
367flag causes
368.Nm restore
369to print debug information.
370.It Fl D Ar filesystem
371The
372.Fl D
373flag allows the user to specify the filesystem name when using
374.Nm restore
375with the
376.Fl C
377option to check the backup.
378.It Fl f Ar file
379Read the backup from
380.Ar file ;
381.Ar file
382may be a special device file
383like
384.Pa /dev/st0
385(a tape drive),
386.Pa /dev/sda1
387(a disk drive),
388an ordinary file,
389or
390.Ql Fl
391(the standard input).
392If the name of the file is of the form
393.Dq host:file
394or
395.Dq user@host:file ,
396.Nm restore
397reads from the named file on the remote host using
398.Xr rmt 8 .
399.Pp
400.It Fl F Ar script
401Run script at the beginning of each tape. The device name and the
402current volume number are passed on the command line.
403The script must return 0 if
404.Nm
405should continue without asking the user to change the tape, 1 if
406.Nm
407should continue but ask the user to change the tape.
408Any other exit code will cause
409.Nm
410to abort.
411For security reasons,
412.Nm
413reverts back to the real user ID and the real group ID before
414running the script.
415.It Fl h
416Extract the actual directory,
417rather than the files that it references.
418This prevents hierarchical restoration of complete subtrees
419from the dump.
420.It Fl k
421Use Kerberos authentication when contacting the remote tape server.
422(Only available if this options was enabled when
423.Nm restore
424was compiled.)
425.It Fl l
426When doing remote restores, assume the remote file is a
427regular file (instead of a tape device). If you're restoring
428a remote compressed file, you will need to specify this
429option or
430.Nm restore
431will fail to access it correctly.
432.It Fl L Ar limit
433The
434.Fl L
435flag allows the user to specify a maximal number of miscompares
436when using
437.Nm restore
438with the
439.Fl C
440option to check the backup. If this limit is reached,
441.Nm restore
442will abort with an error message. A value of 0 (the default value)
443disables the check.
444.It Fl m
445Extract by inode numbers rather than by file name.
446This is useful if only a few files are being extracted,
447and one wants to avoid regenerating the complete pathname
448to the file.
449.It Fl M
450Enables the multi-volume feature (for reading dumps made using
451the
452.Fl M
453option of dump). The name specified with
454.Fl f
455is treated as a prefix and
456.Nm
457tries to read in sequence from <prefix>001, <prefix>002 etc.
458.It Fl N
459The
460.Fl N
461flag causes
462.Nm
463to perform a full execution as requested by one of
464.Fl i,
465.Fl R,
466.Fl r,
467.Fl t
468or
469.Fl x
470command without actually writing any file on disk.
471.It Fl o
472The
473.Fl o
474flag causes
475.Nm
476to automatically restore the current directory permissions
477without asking the operator whether to do so in one of
478.Fl i
479or
480.Fl x
481modes.
482.It Fl Q Ar file
483Use the file
484.Ar file
485in order to read tape position as stored using the dump Quick File
486Access mode, in one of
487.Fl i,
488.Fl x
489or
490.Fl t
491mode.
492.Pp
493It is recommended to set up the st driver to return logical tape
494positions rather than physical before calling dump/restore with
495parameter Q. Since not all tape devices support physical tape
496positions those tape devices return an error during dump/restore when
497the st driver is set to the default physical setting.
498Please see the st man page, option MTSETDRVBUFFER, or the mt man
499page, on how to set the driver to return logical tape positions.
500.Pp
501Before calling restore with parameter Q, always make sure the st
502driver is set to return the same type of tape position used during the
503call to dump. Otherwise restore may be confused.
504.Pp
505This option can be used when restoring from local or remote tapes
506(see above) or from local or remote files.
507.It Fl s Ar fileno
508Read from the specified
509.Ar fileno
510on a multi-file tape.
511File numbering starts at 1.
512.It Fl T Ar directory
513The
514.Fl T
515flag allows the user to specify a directory to use for the storage of
516temporary files. The default value is /tmp. This flag is most useful
517when restoring files after having booted from a floppy. There might be little
518or no space on the floppy filesystem, but another source of space might exist.
519.It Fl u
520When creating certain types of files, restore may generate a warning
521diagnostic if they already exist in the target directory.
522To prevent this, the
523.Fl u
524(unlink) flag causes restore to remove old entries before attempting
525to create new ones.
526.It Fl v
527Normally
528.Nm restore
529does its work silently.
530The
531.Fl v
532(verbose)
533flag causes it to type the name of each file it treats
534preceded by its file type.
535.It Fl V
536Enables reading multi-volume non-tape mediums like CDROMs.
537.It Fl X Ar filelist
538Read list of files to be listed or extracted from the text file
539.Ar filelist
540in addition to those specified on the command line. This can be used in
541conjunction with the
542.Fl t
543or
544.Fl x
545commands. The file
546.Ar filelist
547should contain file names separated by newlines.
548.Ar filelist
549may be an ordinary file or
550.Ql Fl
551(the standard input).
552.It Fl y
553Do not ask the user whether to abort the restore in the event of an error.
554Always try to skip over the bad block(s) and continue.
555.El
556.Sh DIAGNOSTICS
557Complains if it gets a read error.
558If
559.Fl y
560has been specified, or the user responds
561.Ql y ,
562.Nm restore
563will attempt to continue the restore.
564.Pp
565If a backup was made using more than one tape volume,
566.Nm restore
567will notify the user when it is time to mount the next volume.
568If the
569.Fl x
570or
571.Fl i
572flag has been specified,
573.Nm restore
574will also ask which volume the user wishes to mount.
575The fastest way to extract a few files is to
576start with the last volume, and work towards the first volume.
577.Pp
578There are numerous consistency checks that can be listed by
579.Nm restore .
580Most checks are self-explanatory or can
581.Dq never happen .
582Common errors are given below.
583.Pp
584.Bl -tag -width Ds -compact
585.It Converting to new file system format
586A dump tape created from the old file system has been loaded.
587It is automatically converted to the new file system format.
588.Pp
589.It <filename>: not found on tape
590The specified file name was listed in the tape directory,
591but was not found on the tape.
592This is caused by tape read errors while looking for the file,
593and from using a dump tape created on an active file system.
594.Pp
595.It expected next file <inumber>, got <inumber>
596A file that was not listed in the directory showed up.
597This can occur when using a dump created on an active file system.
598.Pp
599.It Incremental dump too low
600When doing an incremental restore,
601a dump that was written before the previous incremental dump,
602or that has too low an incremental level has been loaded.
603.Pp
604.It Incremental dump too high
605When doing an incremental restore,
606a dump that does not begin its coverage where the previous incremental
607dump left off,
608or that has too high an incremental level has been loaded.
609.Pp
610.It Tape read error while restoring <filename>
611.It Tape read error while skipping over inode <inumber>
612.It Tape read error while trying to resynchronize
613A tape (or other media) read error has occurred.
614If a file name is specified,
615its contents are probably partially wrong.
616If an inode is being skipped or the tape is trying to resynchronize,
617no extracted files have been corrupted,
618though files may not be found on the tape.
619.Pp
620.It resync restore, skipped <num> blocks
621After a dump read error,
622.Nm restore
623may have to resynchronize itself.
624This message lists the number of blocks that were skipped over.
625.El
626.Pp
627.Nm Restore
628exits with zero status on success.
629Tape errors are indicated with an exit code of 1.
630.Pp
631When doing a comparison of files from a dump, an exit code
632of 2 indicates that some files were modified or deleted since
633the dump was made.
634.Sh ENVIRONMENT
635If the following environment variable exists it will be utilized by
636.Nm restore :
637.Pp
638.Bl -tag -width "TMPDIR" -compact
639.It Ev TAPE
640If no -f option was specified,
641.Nm
642will use the device specified via
643.Ev TAPE
644as the dump device.
645.Ev TAPE
646may be of the form
647.Qq tapename ,
648.Qq host:tapename
649or
650.Qq user@host:tapename .
651.It Ev TMPDIR
652The directory given in
653.Ev TMPDIR
654will be used
655instead of
656.Pa /tmp
657to store temporary files.
658.It Ev RMT
659The environment variable
660.Ev RMT
661will be used to determine the pathname of the remote
662.Xr rmt 8
663program.
664.It Ev RSH
665.Nm Restore
666uses the contents of this variable to determine the name of the
667remote shell command to use when doing a network restore (rsh, ssh etc.).
668If this variable is not set,
669.Xr rcmd 3
670will be used, but only root will be able to do a network restore.
671.El
672.Sh FILES
673.Bl -tag -width "./restoresymtable" -compact
674.It Pa /dev/st0
675the default tape drive
676.It Pa /tmp/rstdir*
677file containing directories on the tape
678.It Pa /tmp/rstmode*
679owner, mode, and time stamps for directories
680.It Pa \&./restoresymtable
681information passed between incremental restores
682.El
683.Sh SEE ALSO
684.Xr dump 8 ,
685.Xr mount 8 ,
686.Xr mke2fs 8 ,
687.Xr rmt 8
688.Sh BUGS
689.Nm Restore
690can get confused when doing incremental restores from
691dumps that were made on active file systems.
692.Pp
693A level 0 dump must be done after a full restore.
694Because
695.Nm restore
696runs in user code,
697it has no control over inode allocation;
698thus a full dump must be done to get a new set of directories
699reflecting the new inode numbering,
700even though the content of the files is unchanged.
701.Pp
702The temporary files
703.Pa /tmp/rstdir*
704and
705.Pa /tmp/rstmode*
706are generated with a unique name based on the date of the dump
707and the process ID (see
708.Xr mktemp 3 ),
709except when
710.Fl r
711or
712.Fl R
713is used.
714Because
715.Fl R
716allows you to restart a
717.Fl r
718operation that may have been interrupted, the temporary files should
719be the same across different processes.
720In all other cases, the files are unique because it is possible to
721have two different dumps started at the same time, and separate
722operations shouldn't conflict with each other.
723.Pp
724To do a network restore, you have to run restore as root or use
725a remote shell replacement (see RSH variable). This is due
726to the previous security history of dump and restore. (restore is
727written to be setuid root, but we are not certain all bugs are gone
728from the restore code - run setuid at your own risk.)
729.Sh AUTHOR
730The
731.Nm dump/restore
732backup suite was ported to Linux's Second Extended File System
733by Remy Card <card@Linux.EU.Org>. He maintained the initial versions
734of dump (up and including 0.4b4, released in january 1997).
735.Pp
736Starting with 0.4b5, the new maintainer is Stelian Pop
737.br
738<stelian@popies.net>.
739.Sh AVAILABILITY
740The
741.Nm dump/restore
742backup suite is available from
743.br
744http://dump.sourceforge.net
745.Sh HISTORY
746The
747.Nm restore
748command appeared in
749.Bx 4.2 .