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