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