Sun Microsystems Sun Workstation 100U System Manager's Manual page 181

DUMP(8)
MAINTENANCE COMMANDS
DUMP(8)
FILES
Dump
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. The output is verbose, so that others know that the terminal controlling
dump
is busy, and will be for some time.
Now a short suggestion on how to perform dumps. Start with a full level
0
dump
dump Oun
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:
3254769899 ...
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.
/dev/rrplg
/dev/rmtS
letc/dumpdates
letc/fstab
letclgroup
default filesystem
to
dump from
default tape unit to dump to
new format dump date record
dump table: file systems and frequency
to find group op erator
SEE ALSO
restore(8), dump(5), fstab(5)
DIAGNOSTICS
BUGS
26
Many, and verbose.
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 is
written.
It would be nice if
dump
knew about the dump sequence, kept track of the tapes scribbled on,
told the operator which tape to mount when, and provided more assistance for the operator run-
ning restor.
Last change: 28 October 1983
Sun Release 1.1