]>
Commit | Line | Data |
---|---|---|
1 | .\" Copyright (c) 1980, 1991, 1993 | |
2 | .\" Regents of the University of California. | |
3 | .\" All rights reserved. | |
4 | .\" | |
5 | .\" Redistribution and use in source and binary forms, with or without | |
6 | .\" modification, are permitted provided that the following conditions | |
7 | .\" are met: | |
8 | .\" 1. Redistributions of source code must retain the above copyright | |
9 | .\" notice, this list of conditions and the following disclaimer. | |
10 | .\" 2. Redistributions in binary form must reproduce the above copyright | |
11 | .\" notice, this list of conditions and the following disclaimer in the | |
12 | .\" documentation and/or other materials provided with the distribution. | |
13 | .\" 3. All advertising materials mentioning features or use of this software | |
14 | .\" must display the following acknowledgement: | |
15 | .\" This product includes software developed by the University of | |
16 | .\" California, Berkeley and its contributors. | |
17 | .\" 4. Neither the name of the University nor the names of its contributors | |
18 | .\" may be used to endorse or promote products derived from this software | |
19 | .\" without specific prior written permission. | |
20 | .\" | |
21 | .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND | |
22 | .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE | |
23 | .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE | |
24 | .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE | |
25 | .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL | |
26 | .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS | |
27 | .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) | |
28 | .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT | |
29 | .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY | |
30 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | |
31 | .\" SUCH DAMAGE. | |
32 | .\" | |
33 | .\" $Id: dump.8.in,v 1.44 2002/07/24 14:12:00 stelian Exp $ | |
34 | .\" | |
35 | .TH DUMP 8 "version __VERSION__ of __DATE__" BSD "System management commands" | |
36 | .SH NAME | |
37 | dump \- ext2/3 filesystem backup | |
38 | .SH SYNOPSIS | |
39 | .B dump | |
40 | [\fB\-0123456789ackMnqSuv\fR] | |
41 | [\fB\-A \fIfile\fR] | |
42 | [\fB\-B \fIrecords\fR] | |
43 | [\fB\-b \fIblocksize\fR] | |
44 | [\fB\-d \fIdensity\fR] | |
45 | [\fB\-e \fIinode numbers\fR] | |
46 | [\fB\-E \fIfile\fR] | |
47 | [\fB\-f \fIfile\fR] | |
48 | [\fB\-F \fIscript\fR] | |
49 | [\fB\-h \fIlevel\fR] | |
50 | [\fB\-I \fInr errors\fR] | |
51 | [\fB\-j\fIcompression level\fR] | |
52 | [\fB\-L \fIlabel\fR] | |
53 | [\fB\-Q \fIfile\fR] | |
54 | [\fB\-s \fIfeet\fR] | |
55 | [\fB\-T \fIdate\fR] | |
56 | [\fB\-z\fIcompression level\fR] | |
57 | .I files-to-dump | |
58 | .PP | |
59 | .B dump | |
60 | [\fB\-W \fR| \fB\-w\fR] | |
61 | .PP | |
62 | (The 4.3BSD option syntax is implemented for backward compatibility but is not | |
63 | documented here.) | |
64 | .SH DESCRIPTION | |
65 | .B Dump | |
66 | examines files on an ext2/3 filesystem and determines which files need to be | |
67 | backed up. These files are copied to the given disk, tape or other storage | |
68 | medium for safe keeping (see the | |
69 | .B \-f | |
70 | option below for doing remote backups). A dump that is larger than the output | |
71 | medium is broken into multiple volumes. On most media the size is determined by | |
72 | writing until an end-of-media indication is returned. | |
73 | .PP | |
74 | On media that cannot reliably return an end-of-media indication (such as some | |
75 | cartridge tape drives), each volume is of a fixed size; the actual size is | |
76 | determined by specifying cartridge media, or via the tape size, density and/or | |
77 | block count options below. By default, the same output file name is used for | |
78 | each volume after prompting the operator to change media. | |
79 | .PP | |
80 | .I files-to-dump | |
81 | is either a mountpoint of a filesystem or a list of files and directories to be | |
82 | backed up as a subset of a filesystem. In the former case, either the path to a | |
83 | mounted filesystem or the device of an unmounted filesystem can be used. In the | |
84 | latter case, certain restrictions are placed on the backup: | |
85 | .B \-u | |
86 | is not allowed, the only dump level that is supported is | |
87 | .B 0 | |
88 | and all the files and directories must reside on the same filesystem. | |
89 | .SH OPTIONS | |
90 | The following options are supported by | |
91 | .B dump: | |
92 | .TP | |
93 | .BI \-0\-9 | |
94 | Dump levels. A level 0, full backup, guarantees the entire file system is | |
95 | copied (but see also the | |
96 | .B \-h | |
97 | option below). A level number above 0, incremental backup, tells | |
98 | .B dump | |
99 | to | |
100 | copy all files new or modified since the last dump of a lower level. The | |
101 | default level is 9. | |
102 | .TP | |
103 | .BI \-a | |
104 | \*(lqauto-size\*(rq. Bypass all tape length calculations, and write until an | |
105 | end-of-media indication is returned. This works best for most modern tape | |
106 | drives, and is the default. Use of this option is particularly recommended when | |
107 | appending to an existing tape, or using a tape drive with hardware compression | |
108 | (where you can never be sure about the compression ratio). | |
109 | .TP | |
110 | .BI \-A " archive_file" | |
111 | Archive a dump table-of-contents in the specified | |
112 | .I archive_file | |
113 | to be used by | |
114 | .BR restore (8) | |
115 | to determine whether a file is in the dump file that is being restored. | |
116 | .TP | |
117 | .BI \-b " blocksize" | |
118 | The number of kilobytes per dump record. Since the IO system slices all | |
119 | requests into chunks of | |
120 | .B MAXBSIZE | |
121 | (typically 64kB), it is not possible to use a larger blocksize without having | |
122 | problems later with | |
123 | .BR restore (8). | |
124 | Therefore | |
125 | .B dump | |
126 | will constrain writes to | |
127 | .B MAXBSIZE. | |
128 | The default blocksize is 10. | |
129 | .TP | |
130 | .BI \-B " records" | |
131 | The number of 1 kB blocks per volume. Not normally required, as | |
132 | .B dump | |
133 | can detect end-of-media. When the specified size is reached, | |
134 | .B dump | |
135 | waits for you to change the volume. This option overrides the calculation of | |
136 | tape size based on length and density. If compression is on this limits the | |
137 | size of the compressed output per volume. | |
138 | .TP | |
139 | .BI \-c | |
140 | Change the defaults for use with a cartridge tape drive, with a density of 8000 | |
141 | bpi, and a length of 1700 feet. Specifying a cartridge drive overrides the | |
142 | end-of-media detection. | |
143 | .TP | |
144 | .BI \-d " density" | |
145 | Set tape density to | |
146 | .IR density . | |
147 | The default is 1600BPI. Specifying a tape density overrides the end-of-media | |
148 | detection. | |
149 | .TP | |
150 | .BI \-e " inodes" | |
151 | Exclude | |
152 | .I inodes | |
153 | from the dump. The | |
154 | .I inodes | |
155 | parameter is a comma separated list of inode numbers (you can use | |
156 | .BR stat (1) | |
157 | to find the inode number for a file or directory). | |
158 | .TP | |
159 | .BI \-E " file" | |
160 | Read list of inodes to be excluded from the dump from the text file | |
161 | .IR file . | |
162 | The file | |
163 | .I file | |
164 | should be an ordinary file containing inode numbers separated by newlines. | |
165 | .TP | |
166 | .BI \-f " file" | |
167 | Write the backup to | |
168 | .IR file ; | |
169 | .I file | |
170 | may be a special device file like | |
171 | .I /dev/st0 | |
172 | (a tape drive), | |
173 | .I /dev/rsd1c | |
174 | (a floppy disk drive), an ordinary file, or | |
175 | .I \- | |
176 | (the standard output). Multiple file names may be given as a single argument | |
177 | separated by commas. Each file will be used for one dump volume in the order | |
178 | listed; if the dump requires more volumes than the number of names given, | |
179 | the last file name will used for all remaining volumes after prompting for | |
180 | media changes. If the name of the file is of the form | |
181 | .I host:file | |
182 | or | |
183 | .I user@host:file | |
184 | .B dump | |
185 | writes to the named file on the remote host using | |
186 | .BR rmt (8). | |
187 | The default path name of the remote | |
188 | .BR rmt (8) | |
189 | program is | |
190 | .IR /etc/rmt ; | |
191 | this can be overridden by the environment variable | |
192 | .BR RMT . | |
193 | .TP | |
194 | .BI \-F " script" | |
195 | Run script at the end of each tape. The device name and the current volume | |
196 | number are passed on the command line. The script must return 0 if | |
197 | .B dump | |
198 | should continue without asking the user to change the tape, 1 if | |
199 | .B dump | |
200 | should continue but ask the user to change the tape. Any other exit code will | |
201 | cause | |
202 | .B dump | |
203 | to abort. For security reasons, | |
204 | .B dump | |
205 | reverts back to the real user ID and the real group ID before running the | |
206 | script. | |
207 | .TP | |
208 | .BI \-h " level" | |
209 | Honor the user | |
210 | .B nodump | |
211 | flag | |
212 | .B UF_NODUMP | |
213 | only for dumps at or above the given | |
214 | .IR level . | |
215 | The default honor level is 1, so that incremental backups omit such files but | |
216 | full backups retain them. | |
217 | .TP | |
218 | .BI \-I " nr errors" | |
219 | By default, | |
220 | .B dump | |
221 | will ignore the first 32 read errors on the file system before asking for | |
222 | operator intervention. You can change this using this flag to any value. This | |
223 | is useful when running | |
224 | .B dump | |
225 | on an active filesystem where read errors simply indicate an inconsistency | |
226 | between the mapping and dumping passes. | |
227 | .TP | |
228 | .BI \-j "compression level" | |
229 | Compress every block to be written on the tape using bzlib library. This option | |
230 | will work only when dumping to a file or pipe or, when dumping to a tape drive, | |
231 | if the tape drive is capable of writing variable length blocks. You will need | |
232 | at least the 0.4b24 version of | |
233 | .B restore | |
234 | in order to extract compressed tapes. Tapes written using compression will not | |
235 | be compatible with the BSD tape format. The (optional) parameter specifies the | |
236 | compression level bzlib will use. The default compression level is 2. If the | |
237 | optional parameter is specified, there should be no white space between the | |
238 | option letter and the parameter. | |
239 | .TP | |
240 | .BI \-k | |
241 | Use Kerberos authentication to talk to remote tape servers. (Only available if | |
242 | this option was enabled when | |
243 | .B dump | |
244 | was compiled.) | |
245 | .TP | |
246 | .BI \-L " label" | |
247 | The user-supplied text string | |
248 | .I label | |
249 | is placed into the dump header, where tools like | |
250 | .BR restore (8) | |
251 | and | |
252 | .BR file (8) | |
253 | can access it. Note that this label is limited to be at most | |
254 | .B LBLSIZE | |
255 | (currently 16) characters, which must include the terminating \e0. | |
256 | .TP | |
257 | .BI \-m | |
258 | If this flag is specified, | |
259 | .B dump | |
260 | will optimise the output for inodes having been changed but not modified since | |
261 | the last dump ('changed' and 'modified' have the meaning defined in | |
262 | .BR stat (2) | |
263 | ). For those inodes, | |
264 | .B dump | |
265 | will save only the metadata, instead of saving the entire inode contents. | |
266 | Inodes which are either directories or have been modified since the last dump | |
267 | are saved in a regular way. Uses of this flag must be consistent, meaning that | |
268 | either every dump in an incremental dump set have the flag, or no one has it. | |
269 | .IP | |
270 | Tapes written using such 'metadata only' inodes will not be compatible with the | |
271 | BSD tape format or older versions of | |
272 | .B restore. | |
273 | .TP | |
274 | .BI \-M | |
275 | Enable the multi-volume feature. The name specified with | |
276 | .B f | |
277 | is treated as a prefix and | |
278 | .B dump | |
279 | writes in sequence to | |
280 | .I <prefix>001, <prefix>002 | |
281 | etc. This can be useful when dumping to files on an ext2 partition, in order to | |
282 | bypass the 2GB file size limitation. | |
283 | .TP | |
284 | .BI \-n | |
285 | Whenever | |
286 | .B dump | |
287 | requires operator attention, notify all operators in the group | |
288 | .B operator | |
289 | by means similar to a | |
290 | .BR wall (1). | |
291 | .TP | |
292 | .BI \-q | |
293 | Make | |
294 | .B dump | |
295 | abort immediately whenever operator attention is required, without prompting in | |
296 | case of write errors, tape changes etc. | |
297 | .TP | |
298 | .BI \-Q " file" | |
299 | Enable the Quick File Access support. Tape positions for each inode are stored | |
300 | into the file | |
301 | .I file | |
302 | which is used by | |
303 | .B restore | |
304 | (if called with parameter | |
305 | .B \-Q | |
306 | and the filename) to directly position the tape at the file | |
307 | .B restore | |
308 | is currently working on. This saves hours when restoring single files from | |
309 | large backups, saves the tapes and the drive's head. | |
310 | .IP | |
311 | It is recommended to set up the st driver to return logical tape positions | |
312 | rather than physical before calling | |
313 | .B dump/restore | |
314 | with parameter | |
315 | .BR \-Q . | |
316 | Since not all tape devices support physical tape positions those tape devices | |
317 | return an error during | |
318 | .B dump/restore | |
319 | when the st driver is set to the default physical setting. Please see the | |
320 | .BR st (4) | |
321 | man page, option | |
322 | .B MTSETDRVBUFFER | |
323 | , or the | |
324 | .BR mt (1) | |
325 | man page, on how to set the driver to return logical tape positions. | |
326 | .IP | |
327 | Before calling | |
328 | .B restore | |
329 | with parameter | |
330 | .BR \-Q , | |
331 | always make sure the st driver is set to return the same type of tape position | |
332 | used during the call to | |
333 | .BR dump . | |
334 | Otherwise | |
335 | .B restore | |
336 | may be confused. | |
337 | .IP | |
338 | This option can be used when dumping to local tapes (see above) or to local | |
339 | files. | |
340 | .TP | |
341 | .BI \-s " feet" | |
342 | Attempt to calculate the amount of tape needed at a particular density. If this | |
343 | amount is exceeded, | |
344 | .B dump | |
345 | prompts for a new tape. It is recommended to be a bit conservative on this | |
346 | option. The default tape length is 2300 feet. Specifying the tape size | |
347 | overrides end-of-media detection. | |
348 | .TP | |
349 | .BI \-S | |
350 | Size estimate. Determine the amount of space that is needed to perform the dump | |
351 | without actually doing it, and display the estimated number of bytes it will | |
352 | take. This is useful with incremental dumps to determine how many volumes of | |
353 | media will be needed. | |
354 | .TP | |
355 | .BI \-T " date" | |
356 | Use the specified date as the starting time for the dump instead of the time | |
357 | determined from looking in | |
358 | .I __DUMPDATES__ . | |
359 | The format of | |
360 | .I date | |
361 | is the same as that of | |
362 | .BR ctime (3). | |
363 | This option is useful for automated dump scripts that wish to dump over a | |
364 | specific period of time. The | |
365 | .B \-T | |
366 | option is mutually exclusive from the | |
367 | .B \-u | |
368 | option. | |
369 | .TP | |
370 | .BI \-u | |
371 | Update the file | |
372 | .I __DUMPDATES__ | |
373 | after a successful dump. The format of | |
374 | .I __DUMPDATES__ | |
375 | is readable by people, consisting of one free format record per line: | |
376 | filesystem name, increment level and | |
377 | .BR ctime (3) | |
378 | format dump date. There may be only one entry per filesystem at each level. The | |
379 | file | |
380 | .I __DUMPDATES__ | |
381 | may be edited to change any of the fields, if necessary. | |
382 | .TP | |
383 | .BI \-v | |
384 | The | |
385 | .B \-v | |
386 | (verbose) makes | |
387 | .B dump | |
388 | to print extra information which could be helpful in debug sessions. | |
389 | .TP | |
390 | .BI \-W | |
391 | .B Dump | |
392 | tells the operator what file systems need to be dumped. This information is | |
393 | gleaned from the files | |
394 | .I __DUMPDATES__ | |
395 | and | |
396 | .IR /etc/fstab . | |
397 | The | |
398 | .B \-W | |
399 | option causes | |
400 | .B dump | |
401 | to print out, for all file systems in | |
402 | .I __DUMPDATES__ , | |
403 | and regognized file systems in | |
404 | .IR /etc/fstab . | |
405 | the most recent dump date and level, and highlights those that should be | |
406 | dumped. If the | |
407 | .B \-W | |
408 | option is set, all other options are ignored, and | |
409 | .B dump | |
410 | exits immediately. | |
411 | .TP | |
412 | .BI \-w | |
413 | Is like | |
414 | .BR \-W , | |
415 | but prints only recognized filesystems in | |
416 | .I /etc/fstab | |
417 | which need to be dumped. | |
418 | .TP | |
419 | .BI \-z "compression level" | |
420 | Compress every block to be written on the tape using zlib library. This option | |
421 | will work only when dumping to a file or pipe or, when dumping to a tape drive, | |
422 | if the tape drive is capable of writing variable length blocks. You will need | |
423 | at least the 0.4b22 version of | |
424 | .B restore | |
425 | in order to extract compressed tapes. Tapes written using compression will not | |
426 | be compatible with the BSD tape format. The (optional) parameter specifies the | |
427 | compression level zlib will use. The default compression level is 2. If the | |
428 | optional parameter is specified, there should be no white space between the | |
429 | option letter and the parameter. | |
430 | .PP | |
431 | .B Dump | |
432 | requires operator intervention on these conditions: end of tape, end of dump, | |
433 | tape write error, tape open error or disk read error (if there is more than a | |
434 | threshold of nr errors). In addition to alerting all operators implied by the | |
435 | .B \-n | |
436 | key, | |
437 | .B dump | |
438 | interacts with the operator on dump's control terminal at times when | |
439 | .B dump | |
440 | can no longer proceed, or if something is grossly wrong. All questions | |
441 | .B dump | |
442 | poses | |
443 | .I must | |
444 | be answered by typing \*(lqyes\*(rq or \*(lqno\*(rq, appropriately. | |
445 | .PP | |
446 | Since making a dump involves a lot of time and effort for full dumps, | |
447 | .B dump | |
448 | checkpoints itself at the start of each tape volume. If writing that volume | |
449 | fails for some reason, | |
450 | .B dump | |
451 | will, with operator permission, restart itself from the checkpoint after the | |
452 | old tape has been rewound and removed, and a new tape has been mounted. | |
453 | .PP | |
454 | .B Dump | |
455 | tells the operator what is going on at periodic intervals, including usually | |
456 | low estimates of the number of blocks to write, the number of tapes it will | |
457 | take, the time to completion, and the time to the tape change. The output is | |
458 | verbose, so that others know that the terminal controlling | |
459 | .B dump | |
460 | is busy, and will be for some time. | |
461 | .PP | |
462 | In the event of a catastrophic disk event, the time required to restore all the | |
463 | necessary backup tapes or files to disk can be kept to a minimum by staggering | |
464 | the incremental dumps. An efficient method of staggering incremental dumps to | |
465 | minimize the number of tapes follows: | |
466 | .IP \(em | |
467 | Always start with a level 0 backup, for example: | |
468 | .RS 14 | |
469 | .B /sbin/dump -0u -f /dev/st0 /usr/src | |
470 | .RE | |
471 | .IP | |
472 | This should be done at set intervals, say once a month or once every two months, | |
473 | and on a set of fresh tapes that is saved forever. | |
474 | .IP \(em | |
475 | After a level 0, dumps of active file systems are taken on a daily basis, using | |
476 | a modified Tower of Hanoi algorithm, with this sequence of dump levels: | |
477 | .RS 14 | |
478 | .B 3 2 5 4 7 6 9 8 9 9 ... | |
479 | .RE | |
480 | .IP | |
481 | For the daily dumps, it should be possible to use a fixed number of tapes for | |
482 | each day, used on a weekly basis. Each week, a level 1 dump is taken, and the | |
483 | daily Hanoi sequence repeats beginning with 3. For weekly dumps, another fixed | |
484 | set of tapes per dumped file system is used, also on a cyclical basis. | |
485 | .PP | |
486 | After several months or so, the daily and weekly tapes should get rotated out | |
487 | of the dump cycle and fresh tapes brought in. | |
488 | .SH ENVIRONMENT | |
489 | .TP | |
490 | .B TAPE | |
491 | If no | |
492 | .B \-f | |
493 | option was specified, | |
494 | .B dump | |
495 | will use the device specified via | |
496 | .B TAPE | |
497 | as the dump device. | |
498 | .B TAPE | |
499 | may be of the form | |
500 | .IR tapename , | |
501 | .IR host:tapename , | |
502 | or | |
503 | .IR user@host:tapename . | |
504 | .TP | |
505 | .B RMT | |
506 | The environment variable | |
507 | .B RMT | |
508 | will be used to determine the pathname of the remote | |
509 | .BR rmt (8) | |
510 | program. | |
511 | .TP | |
512 | .B RSH | |
513 | .B Dump | |
514 | uses the contents of this variable to determine the name of the remote shell | |
515 | command to use when doing remote backups (rsh, ssh etc.). If this variable is | |
516 | not set, | |
517 | .BR rcmd (3) | |
518 | will be used, but only root will be able to do remote backups. | |
519 | .SH FILES | |
520 | .TP | |
521 | .I /dev/st0 | |
522 | default tape unit to dump to | |
523 | .TP | |
524 | .I __DUMPDATES__ | |
525 | dump date records | |
526 | .TP | |
527 | .I /etc/fstab | |
528 | dump table: file systems and frequency | |
529 | .TP | |
530 | .I /etc/group | |
531 | to find group | |
532 | .I operator | |
533 | .SH SEE ALSO | |
534 | .BR fstab (5), | |
535 | .BR restore (8), | |
536 | .BR rmt (8) | |
537 | .SH DIAGNOSTICS | |
538 | Many, and verbose. | |
539 | .SH EXIT STATUS | |
540 | .B Dump | |
541 | exits with zero status on success. Startup errors are indicated with an exit | |
542 | code of 1; abnormal termination is indicated with an exit code of 3. | |
543 | .SH BUGS | |
544 | It might be considered a bug that this version of dump can only handle ext2/3 | |
545 | filesystems. Specifically, it does not work with FAT filesystems. | |
546 | .PP | |
547 | Fewer than 32 read errors (change this with | |
548 | .BR \-I ) | |
549 | on the filesystem are ignored. If noticing read errors is important, the output | |
550 | from dump can be parsed to look for lines that contain the text 'read error'. | |
551 | .PP | |
552 | When a read error occurs, | |
553 | .B dump | |
554 | prints out the corresponding physical disk block and sector number and the | |
555 | ext2/3 logical block number. It doesn't print out the corresponing file name or | |
556 | even the inode number. The user has to use | |
557 | .BR debugfs (8), | |
558 | commands | |
559 | .B ncheck | |
560 | and | |
561 | .B icheck | |
562 | to translate the | |
563 | .B ext2blk | |
564 | number printed out by | |
565 | .B dump | |
566 | into an inode number, then into a file name. | |
567 | .PP | |
568 | Each reel requires a new process, so parent processes for reels already written | |
569 | just hang around until the entire tape is written. | |
570 | .PP | |
571 | The estimated number of tapes is not correct if compression is on. | |
572 | .PP | |
573 | It would be nice if | |
574 | .B dump | |
575 | knew about the dump sequence, kept track of the tapes scribbled on, told the | |
576 | operator which tape to mount when, and provided more assistance for the | |
577 | operator running | |
578 | .BR restore . | |
579 | .PP | |
580 | .B Dump | |
581 | cannot do remote backups without being run as root, due to its security history. | |
582 | Presently, it works if you set it setuid (like it used to be), but this might | |
583 | constitute a security risk. Note that you can set | |
584 | .B RSH | |
585 | to use a remote shell program instead. | |
586 | .SH AUTHOR | |
587 | The | |
588 | .B dump/restore | |
589 | backup suite was ported to Linux's Second Extended File System by Remy Card | |
590 | <card@Linux.EU.Org>. He maintained the initial versions of | |
591 | .B dump | |
592 | (up and including 0.4b4, released in january 1997). | |
593 | .PP | |
594 | Starting with 0.4b5, the new maintainer is Stelian Pop <stelian@popies.net>. | |
595 | .SH AVAILABILITY | |
596 | The | |
597 | .B dump/restore | |
598 | backup suite is available from <http://dump.sourceforge.net> | |
599 | .SH HISTORY | |
600 | A | |
601 | .B dump | |
602 | command appeared in | |
603 | .B Version 6 AT&T UNIX. |