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 acknowledgment:
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.\" @(#)dump.8 8.3 (Berkeley) 5/1/95
| 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 acknowledgment:
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.\" @(#)dump.8 8.3 (Berkeley) 5/1/95
|
34.\" $FreeBSD: head/sbin/dump/dump.8 90492 2002-02-10 22:14:09Z dd $
| 34.\" $FreeBSD: head/sbin/dump/dump.8 90742 2002-02-16 20:22:26Z iedowse $
|
35.\"
36.Dd July 9, 2001
37.Dt DUMP 8
38.Os
39.Sh NAME
40.Nm dump ,
41.Nm rdump
42.Nd filesystem backup
43.Sh SYNOPSIS
44.Nm
45.Op Fl 0123456789acknu
46.Op Fl B Ar records
47.Op Fl b Ar blocksize
48.Op Fl D Ar dumpdates
49.Op Fl d Ar density
50.Op Fl f Ar file
51.Op Fl h Ar level
52.Op Fl s Ar feet
53.Op Fl T Ar date
54.Ar filesystem
55.Nm
56.Op Fl W Li \&| Fl w
57.Pp
58.in \" XXX
59(The
60.Bx 4.3
61option syntax is implemented for backward compatibility, but
62is not documented here.)
63.Sh DESCRIPTION
64.Nm Dump
65examines files
66on a filesystem
67and determines which files
68need to be backed up.
69These files
70are copied to the given disk, tape or other
71storage medium for safe keeping (see the
72.Fl f
73option below for doing remote backups).
74A dump that is larger than the output medium is broken into
75multiple volumes.
76On most media the size is determined by writing until an
77end-of-media indication is returned. This can be enforced
78by using the
79.Fl a
80option.
81.Pp
82On media that cannot reliably return an end-of-media indication
83(such as some cartridge tape drives)
84each volume is of a fixed size;
85the actual size is determined by the tape size and density and/or
86block count options below.
87By default, the same output file name is used for each volume
88after prompting the operator to change media.
89.Pp
90The following options are supported by
91.Nm :
92.Bl -tag -width Ds
93.It Fl 0\-9
94Dump levels.
95A level 0, full backup,
96guarantees the entire file system is copied
97(but see also the
98.Fl h
99option below).
100A level number above 0,
101incremental backup,
102tells dump to
103copy all files new or modified since the
104last dump of any lower level.
105The default level is 0.
106.It Fl a
107.Dq auto-size .
108Bypass all tape length considerations, and enforce writing
109until an end-of-media indication is returned. This fits best
110for most modern tape drives. Use of this option is particularly
111recommended when appending to an existing tape, or using a tape
112drive with hardware compression (where you can never be sure about
113the compression ratio).
114.It Fl B Ar records
115The number of 1 KB blocks per volume.
116This option overrides the calculation of tape size
117based on length and density.
118.It Fl b Ar blocksize
119The number of kilobytes per dump record.
120.It Fl c
121Change the defaults for use with a cartridge tape drive, with a density
122of 8000 bpi, and a length of 1700 feet.
123.It Fl D Ar dumpdates
124Specify an alternate path to the
125.Pa dumpdates
126file.
127The default is
128.Pa /etc/dumpdates .
129.It Fl d Ar density
130Set tape density to
131.Ar density .
132The default is 1600BPI.
133.It Fl f Ar file
134Write the backup to
135.Ar file ;
136.Ar file
137may be a special device file
138like
139.Pa /dev/sa0
140(a tape drive),
141.Pa /dev/fd1
142(a floppy disk drive),
143an ordinary file,
144or
145.Ql Fl
146(the standard output).
147Multiple file names may be given as a single argument separated by commas.
148Each file will be used for one dump volume in the order listed;
149if the dump requires more volumes than the number of names given,
150the last file name will used for all remaining volumes after prompting
151for media changes.
152If the name of the file is of the form
153.Dq host:file ,
154or
155.Dq user@host:file ,
156.Nm
157writes to the named file on the remote host using
158.Xr rmt 8 .
159The default path name of the remote
160.Xr rmt 8
161program is
162.\" rmt path, is the path on the remote host
163.Pa /etc/rmt ;
164this can be overridden by the environment variable
165.Ev RMT .
166.It Fl h Ar level
167Honor the user
168.Dq nodump
169flag
170.Pq Dv UF_NODUMP
171only for dumps at or above the given
172.Ar level .
173The default honor level is 1,
174so that incremental backups omit such files
175but full backups retain them.
176.It Fl k
177Use Kerberos authentication to talk to remote tape servers. (Only
178available if this option was enabled when
179.Nm
180was compiled.)
181.It Fl n
182Whenever
183.Nm
184requires operator attention,
185notify all operators in the group
186.Dq operator
187by means similar to a
188.Xr wall 1 .
189.It Fl s Ar feet
190Attempt to calculate the amount of tape needed
191at a particular density.
192If this amount is exceeded,
193.Nm
194prompts for a new tape.
195It is recommended to be a bit conservative on this option.
196The default tape length is 2300 feet.
197.It Fl T Ar date
198Use the specified date as the starting time for the dump
199instead of the time determined from looking in
200the
201.Pa dumpdates
202file.
203The format of date is the same as that of
204.Xr ctime 3 .
205This option is useful for automated dump scripts that wish to
206dump over a specific period of time.
207The
208.Fl T
209option is mutually exclusive from the
210.Fl u
211option.
212.It Fl u
213Update the
214.Pa dumpdates
215file
216after a successful dump.
217The format of
218the
219.Pa dumpdates
220file
221is readable by people, consisting of one
222free format record per line:
223filesystem name,
224increment level
225and
226.Xr ctime 3
227format dump date.
228There may be only one entry per filesystem at each level.
229The
230.Pa dumpdates
231file
232may be edited to change any of the fields,
233if necessary.
234The default path for the
235.Pa dumpdates
236file is
237.Pa /etc/dumpdates ,
238but the
239.Fl D
240option may be used to change it.
241.It Fl W
242.Nm Dump
243tells the operator what file systems need to be dumped.
244This information is gleaned from the files
245.Pa dumpdates
246and
247.Pa /etc/fstab .
248The
249.Fl W
250option causes
251.Nm
252to print out, for each file system in
253the
254.Pa dumpdates
255file
256the most recent dump date and level,
257and highlights those file systems that should be dumped.
258If the
259.Fl W
260option is set, all other options are ignored, and
261.Nm
262exits immediately.
263.It Fl w
264Is like W, but prints only those filesystems which need to be dumped.
265.El
266.Pp
267Directories and regular files which have their
268.Dq nodump
269flag
270.Pq Dv UF_NODUMP
271set will be omitted along with everything under such directories,
272subject to the
273.Fl h
274option.
275.Pp
276.Nm Dump
277requires operator intervention on these conditions:
278end of tape,
279end of dump,
280tape write error,
281tape open error or
282disk read error (if there are more than a threshold of 32).
283In addition to alerting all operators implied by the
284.Fl n
285key,
286.Nm
287interacts with the operator on
288.Em dump's
289control terminal at times when
290.Nm
291can no longer proceed,
292or if something is grossly wrong.
293All questions
294.Nm
295poses
296.Em must
297be answered by typing
298.Dq yes
299or
300.Dq no ,
301appropriately.
302.Pp
303Since making a dump involves a lot of time and effort for full dumps,
304.Nm
305checkpoints itself at the start of each tape volume.
306If writing that volume fails for some reason,
307.Nm
308will,
309with operator permission,
310restart itself from the checkpoint
311after the old tape has been rewound and removed,
312and a new tape has been mounted.
313.Pp
314.Nm Dump
| 35.\"
36.Dd July 9, 2001
37.Dt DUMP 8
38.Os
39.Sh NAME
40.Nm dump ,
41.Nm rdump
42.Nd filesystem backup
43.Sh SYNOPSIS
44.Nm
45.Op Fl 0123456789acknu
46.Op Fl B Ar records
47.Op Fl b Ar blocksize
48.Op Fl D Ar dumpdates
49.Op Fl d Ar density
50.Op Fl f Ar file
51.Op Fl h Ar level
52.Op Fl s Ar feet
53.Op Fl T Ar date
54.Ar filesystem
55.Nm
56.Op Fl W Li \&| Fl w
57.Pp
58.in \" XXX
59(The
60.Bx 4.3
61option syntax is implemented for backward compatibility, but
62is not documented here.)
63.Sh DESCRIPTION
64.Nm Dump
65examines files
66on a filesystem
67and determines which files
68need to be backed up.
69These files
70are copied to the given disk, tape or other
71storage medium for safe keeping (see the
72.Fl f
73option below for doing remote backups).
74A dump that is larger than the output medium is broken into
75multiple volumes.
76On most media the size is determined by writing until an
77end-of-media indication is returned. This can be enforced
78by using the
79.Fl a
80option.
81.Pp
82On media that cannot reliably return an end-of-media indication
83(such as some cartridge tape drives)
84each volume is of a fixed size;
85the actual size is determined by the tape size and density and/or
86block count options below.
87By default, the same output file name is used for each volume
88after prompting the operator to change media.
89.Pp
90The following options are supported by
91.Nm :
92.Bl -tag -width Ds
93.It Fl 0\-9
94Dump levels.
95A level 0, full backup,
96guarantees the entire file system is copied
97(but see also the
98.Fl h
99option below).
100A level number above 0,
101incremental backup,
102tells dump to
103copy all files new or modified since the
104last dump of any lower level.
105The default level is 0.
106.It Fl a
107.Dq auto-size .
108Bypass all tape length considerations, and enforce writing
109until an end-of-media indication is returned. This fits best
110for most modern tape drives. Use of this option is particularly
111recommended when appending to an existing tape, or using a tape
112drive with hardware compression (where you can never be sure about
113the compression ratio).
114.It Fl B Ar records
115The number of 1 KB blocks per volume.
116This option overrides the calculation of tape size
117based on length and density.
118.It Fl b Ar blocksize
119The number of kilobytes per dump record.
120.It Fl c
121Change the defaults for use with a cartridge tape drive, with a density
122of 8000 bpi, and a length of 1700 feet.
123.It Fl D Ar dumpdates
124Specify an alternate path to the
125.Pa dumpdates
126file.
127The default is
128.Pa /etc/dumpdates .
129.It Fl d Ar density
130Set tape density to
131.Ar density .
132The default is 1600BPI.
133.It Fl f Ar file
134Write the backup to
135.Ar file ;
136.Ar file
137may be a special device file
138like
139.Pa /dev/sa0
140(a tape drive),
141.Pa /dev/fd1
142(a floppy disk drive),
143an ordinary file,
144or
145.Ql Fl
146(the standard output).
147Multiple file names may be given as a single argument separated by commas.
148Each file will be used for one dump volume in the order listed;
149if the dump requires more volumes than the number of names given,
150the last file name will used for all remaining volumes after prompting
151for media changes.
152If the name of the file is of the form
153.Dq host:file ,
154or
155.Dq user@host:file ,
156.Nm
157writes to the named file on the remote host using
158.Xr rmt 8 .
159The default path name of the remote
160.Xr rmt 8
161program is
162.\" rmt path, is the path on the remote host
163.Pa /etc/rmt ;
164this can be overridden by the environment variable
165.Ev RMT .
166.It Fl h Ar level
167Honor the user
168.Dq nodump
169flag
170.Pq Dv UF_NODUMP
171only for dumps at or above the given
172.Ar level .
173The default honor level is 1,
174so that incremental backups omit such files
175but full backups retain them.
176.It Fl k
177Use Kerberos authentication to talk to remote tape servers. (Only
178available if this option was enabled when
179.Nm
180was compiled.)
181.It Fl n
182Whenever
183.Nm
184requires operator attention,
185notify all operators in the group
186.Dq operator
187by means similar to a
188.Xr wall 1 .
189.It Fl s Ar feet
190Attempt to calculate the amount of tape needed
191at a particular density.
192If this amount is exceeded,
193.Nm
194prompts for a new tape.
195It is recommended to be a bit conservative on this option.
196The default tape length is 2300 feet.
197.It Fl T Ar date
198Use the specified date as the starting time for the dump
199instead of the time determined from looking in
200the
201.Pa dumpdates
202file.
203The format of date is the same as that of
204.Xr ctime 3 .
205This option is useful for automated dump scripts that wish to
206dump over a specific period of time.
207The
208.Fl T
209option is mutually exclusive from the
210.Fl u
211option.
212.It Fl u
213Update the
214.Pa dumpdates
215file
216after a successful dump.
217The format of
218the
219.Pa dumpdates
220file
221is readable by people, consisting of one
222free format record per line:
223filesystem name,
224increment level
225and
226.Xr ctime 3
227format dump date.
228There may be only one entry per filesystem at each level.
229The
230.Pa dumpdates
231file
232may be edited to change any of the fields,
233if necessary.
234The default path for the
235.Pa dumpdates
236file is
237.Pa /etc/dumpdates ,
238but the
239.Fl D
240option may be used to change it.
241.It Fl W
242.Nm Dump
243tells the operator what file systems need to be dumped.
244This information is gleaned from the files
245.Pa dumpdates
246and
247.Pa /etc/fstab .
248The
249.Fl W
250option causes
251.Nm
252to print out, for each file system in
253the
254.Pa dumpdates
255file
256the most recent dump date and level,
257and highlights those file systems that should be dumped.
258If the
259.Fl W
260option is set, all other options are ignored, and
261.Nm
262exits immediately.
263.It Fl w
264Is like W, but prints only those filesystems which need to be dumped.
265.El
266.Pp
267Directories and regular files which have their
268.Dq nodump
269flag
270.Pq Dv UF_NODUMP
271set will be omitted along with everything under such directories,
272subject to the
273.Fl h
274option.
275.Pp
276.Nm Dump
277requires operator intervention on these conditions:
278end of tape,
279end of dump,
280tape write error,
281tape open error or
282disk read error (if there are more than a threshold of 32).
283In addition to alerting all operators implied by the
284.Fl n
285key,
286.Nm
287interacts with the operator on
288.Em dump's
289control terminal at times when
290.Nm
291can no longer proceed,
292or if something is grossly wrong.
293All questions
294.Nm
295poses
296.Em must
297be answered by typing
298.Dq yes
299or
300.Dq no ,
301appropriately.
302.Pp
303Since making a dump involves a lot of time and effort for full dumps,
304.Nm
305checkpoints itself at the start of each tape volume.
306If writing that volume fails for some reason,
307.Nm
308will,
309with operator permission,
310restart itself from the checkpoint
311after the old tape has been rewound and removed,
312and a new tape has been mounted.
313.Pp
314.Nm Dump
|
315tells the operator what is going on at periodic intervals,
| 315tells the operator what is going on at periodic intervals --
316every 5 minutes, or promptly after receiving SIGINFO --
|
316including usually low estimates of the number of blocks to write,
317the number of tapes it will take, the time to completion, and
318the time to the tape change.
319The output is verbose,
320so that others know that the terminal
321controlling
322.Nm
323is busy,
324and will be for some time.
325.Pp
326In the event of a catastrophic disk event, the time required
327to restore all the necessary backup tapes or files to disk
328can be kept to a minimum by staggering the incremental dumps.
329An efficient method of staggering incremental dumps
330to minimize the number of tapes follows:
331.Bl -bullet -offset indent
332.It
333Always start with a level 0 backup, for example:
334.Bd -literal -offset indent
335/sbin/dump -0u -f /dev/nsa0 /usr/src
336.Ed
337.Pp
338This should be done at set intervals, say once a month or once every two months,
339and on a set of fresh tapes that is saved forever.
340.It
341After a level 0, dumps of active file
342systems are taken on a daily basis,
343using a modified Tower of Hanoi algorithm,
344with this sequence of dump levels:
345.Bd -literal -offset indent
3463 2 5 4 7 6 9 8 9 9 ...
347.Ed
348.Pp
349For the daily dumps, it should be possible to use a fixed number of tapes
350for each day, used on a weekly basis.
351Each week, a level 1 dump is taken, and
352the daily Hanoi sequence repeats beginning with 3.
353For weekly dumps, another fixed set of tapes per dumped file system is
354used, also on a cyclical basis.
355.El
356.Pp
357After several months or so, the daily and weekly tapes should get
358rotated out of the dump cycle and fresh tapes brought in.
359.Sh ENVIRONMENT
360The environment variable
361.Ev RMT
362will be used to determine the pathname of the remote
363.Xr rmt 8
364program.
365.Sh FILES
366.Bl -tag -width /etc/dumpdates -compact
367.It Pa /dev/sa0
368default tape unit to dump to
369.It Pa /etc/dumpdates
370dump date records
371(this can be changed;
372see the
373.Fl D
374option)
375.It Pa /etc/fstab
376dump table: file systems and frequency
377.It Pa /etc/group
378to find group
379.Em operator
380.El
381.Sh SEE ALSO
382.Xr chflags 1 ,
383.Xr fstab 5 ,
384.Xr restore 8 ,
385.Xr rmt 8
386.Sh DIAGNOSTICS
387Many, and verbose.
388.Pp
389Dump exits with zero status on success.
390Startup errors are indicated with an exit code of 1;
391abnormal termination is indicated with an exit code of 3.
392.Sh BUGS
393Fewer than 32 read errors on the filesystem are ignored.
394.Pp
395Each reel requires a new process, so parent processes for
396reels already written just hang around until the entire tape
397is written.
398.Pp
399Currently,
400.Xr physio 9
401slices all requests into chunks of 64 KB. Therefore, it is
402impossible to use a larger tape blocksize, so
403.Nm
404will prevent this from happening.
405.Pp
406.Nm Dump
407with the
408.Fl W
409or
410.Fl w
411options does not report filesystems that have never been recorded
412in the
413.Pa dumpdates
414file,
415even if listed in
416.Pa /etc/fstab .
417.Pp
418It would be nice if
419.Nm
420knew about the dump sequence,
421kept track of the tapes scribbled on,
422told the operator which tape to mount when,
423and provided more assistance
424for the operator running
425.Xr restore .
426.Pp
427.Nm Dump
428cannot do remote backups without being run as root, due to its
429security history. This will be fixed in a later version of
430.Fx .
431Presently, it works if you set it setuid (like it used to be), but this
432might constitute a security risk.
433.Sh HISTORY
434A
435.Nm
436command appeared in
437.At v6 .
| 317including usually low estimates of the number of blocks to write,
318the number of tapes it will take, the time to completion, and
319the time to the tape change.
320The output is verbose,
321so that others know that the terminal
322controlling
323.Nm
324is busy,
325and will be for some time.
326.Pp
327In the event of a catastrophic disk event, the time required
328to restore all the necessary backup tapes or files to disk
329can be kept to a minimum by staggering the incremental dumps.
330An efficient method of staggering incremental dumps
331to minimize the number of tapes follows:
332.Bl -bullet -offset indent
333.It
334Always start with a level 0 backup, for example:
335.Bd -literal -offset indent
336/sbin/dump -0u -f /dev/nsa0 /usr/src
337.Ed
338.Pp
339This should be done at set intervals, say once a month or once every two months,
340and on a set of fresh tapes that is saved forever.
341.It
342After a level 0, dumps of active file
343systems are taken on a daily basis,
344using a modified Tower of Hanoi algorithm,
345with this sequence of dump levels:
346.Bd -literal -offset indent
3473 2 5 4 7 6 9 8 9 9 ...
348.Ed
349.Pp
350For the daily dumps, it should be possible to use a fixed number of tapes
351for each day, used on a weekly basis.
352Each week, a level 1 dump is taken, and
353the daily Hanoi sequence repeats beginning with 3.
354For weekly dumps, another fixed set of tapes per dumped file system is
355used, also on a cyclical basis.
356.El
357.Pp
358After several months or so, the daily and weekly tapes should get
359rotated out of the dump cycle and fresh tapes brought in.
360.Sh ENVIRONMENT
361The environment variable
362.Ev RMT
363will be used to determine the pathname of the remote
364.Xr rmt 8
365program.
366.Sh FILES
367.Bl -tag -width /etc/dumpdates -compact
368.It Pa /dev/sa0
369default tape unit to dump to
370.It Pa /etc/dumpdates
371dump date records
372(this can be changed;
373see the
374.Fl D
375option)
376.It Pa /etc/fstab
377dump table: file systems and frequency
378.It Pa /etc/group
379to find group
380.Em operator
381.El
382.Sh SEE ALSO
383.Xr chflags 1 ,
384.Xr fstab 5 ,
385.Xr restore 8 ,
386.Xr rmt 8
387.Sh DIAGNOSTICS
388Many, and verbose.
389.Pp
390Dump exits with zero status on success.
391Startup errors are indicated with an exit code of 1;
392abnormal termination is indicated with an exit code of 3.
393.Sh BUGS
394Fewer than 32 read errors on the filesystem are ignored.
395.Pp
396Each reel requires a new process, so parent processes for
397reels already written just hang around until the entire tape
398is written.
399.Pp
400Currently,
401.Xr physio 9
402slices all requests into chunks of 64 KB. Therefore, it is
403impossible to use a larger tape blocksize, so
404.Nm
405will prevent this from happening.
406.Pp
407.Nm Dump
408with the
409.Fl W
410or
411.Fl w
412options does not report filesystems that have never been recorded
413in the
414.Pa dumpdates
415file,
416even if listed in
417.Pa /etc/fstab .
418.Pp
419It would be nice if
420.Nm
421knew about the dump sequence,
422kept track of the tapes scribbled on,
423told the operator which tape to mount when,
424and provided more assistance
425for the operator running
426.Xr restore .
427.Pp
428.Nm Dump
429cannot do remote backups without being run as root, due to its
430security history. This will be fixed in a later version of
431.Fx .
432Presently, it works if you set it setuid (like it used to be), but this
433might constitute a security risk.
434.Sh HISTORY
435A
436.Nm
437command appeared in
438.At v6 .
|