.\" Copyright (c) 1980 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)dump.8 6.1 (Berkeley) %G%
dump \- incremental file system dump
copies to magnetic tape all files
changed after a certain date
specifies the date and other options about the dump.
consists of characters from
This number is the `dump level'.
All files modified since the last date stored
for the same filesystem at lesser levels
If no date is determined by the level,
the beginning of time is assumed;
causes the entire filesystem to be dumped.
Place the dump on the next
If the name of the file is ``\-'',
writes to standard output.
If the dump completes successfully,
write the date of the beginning of the dump on
This file records a separate date for
each filesystem and each dump level.
is readable by people, consisting of one
free format record per line:
filesystem name, increment level
may be edited to change any of the fields,
The size of the dump tape is specified in feet.
The number of feet is taken from the next
When the specified size is reached,
will wait for reels to be changed.
The default tape size is 2300 feet.
The density of the tape, expressed in BPI,
This is used in calculating the amount of tape
used per reel. The default is 1600.
tells the operator what file systems need to be dumped.
This information is gleaned from the files
to print out, for each file system in
the most recent dump date and level,
and highlights those file systems that should be dumped.
option is set, all other options are ignored, and
Is like W, but prints only those filesystems which need to be dumped.
requires operator attention,
notify by means similar to a
all of the operators in the group \*(lqoperator\*(rq.
If no arguments are given,
and a default file system is dumped
requires operator intervention on these conditions:
disk read error (if there are more than a threshold of 32).
In addition to alerting all operators implied by the
interacts with the operator on
control terminal at times when
or if something is grossly wrong.
be answered by typing \*(lqyes\*(rq or \*(lqno\*(rq,
Since making a dump involves a lot of time and effort for full dumps,
checkpoints itself at the start of each tape volume.
If writing that volume fails for some reason,
with operator permission,
restart itself from the checkpoint
after the old tape has been rewound and removed,
and a new tape has been mounted.
tells the operator what is going on at periodic intervals,
including usually low estimates of the number of blocks to write,
the number of tapes it will take, the time to completion, and
the time to the tape change.
so that others know that the terminal
and will be for some time.
Now a short suggestion on how to
Start with a full level 0 dump
Next, dumps of active file
systems are taken on a daily basis,
using a modified Tower of Hanoi algorithm,
with this sequence of dump levels:
For the daily dumps, a set of 10 tapes per dumped file system
is used on a cyclical basis.
Each week, a level 1 dump is taken, and
the daily Hanoi sequence repeats with 3.
For weekly dumps, a set of 5 tapes per dumped file system is
used, also on a cyclical basis.
Each month, a level 0 dump is taken
on a set of fresh tapes that is saved forever.
.ta \w'/etc/dumpdates\ \ 'u
/dev/rrp1g default filesystem to dump from
/dev/rmt8 default tape unit to dump to
/etc/ddate old format dump date record (obsolete after \fB\-J\fR option)
/etc/dumpdates new format dump date record
/etc/fstab dump table: file systems and frequency
/etc/group to find group \fIoperator\fP
Sizes are based on 1600 BPI blocked tape;
the raw magtape device has to be used to approach these densities.
Fewer than 32 read errors on the filesystem are ignored.
Each reel requires a new process, so parent processes for
reels already written just hang around until the entire tape
knew about the dump sequence,
kept track of the tapes scribbled on,
told the operator which tape to mount when,
and provided more assistance