[unix-history] / usr / man / man1 / dump.1m

.TH DUMP 1M 
.SH NAME
dump \- incremental file system dump
.SH SYNOPSIS
.B dump
[ key [ argument ... ] filesystem ]
.SH DESCRIPTION
.I Dump
copies to magnetic tape all files
changed after a certain date
in the
.I filesystem.
The
.I key
specifies the date and other options about the dump.
.I Key
consists of characters from
the set
.B 0123456789fusd.
.TP 5
.B  f
Place the dump on the next 
.I argument 
file
instead of the tape.
.TP 5
.B  u
If the dump completes successfully,
write the date of the beginning of the dump on
file `/etc/ddate'.
This file records a separate date for
each filesystem and each dump level.
.TP 5
.B  0\-9
This number is the `dump level'.
All files modified since the last date stored
in the file `/etc/ddate' for
the same filesystem at lesser levels
will be dumped.
If no date is determined by the level,
the beginning of time is assumed;
thus the option
.B 0
causes the entire filesystem to be dumped.
.TP 5
.B  s
The size of the dump tape is specified in feet.
The number of feet is taken from the next
.I argument.
When the specified size is reached,
the dump will wait for reels to be changed.
The default size is 2300 feet.
.TP 5
.B d
The density of the tape, expressed in BPI,
is taken from the next
.I argument.
This is used in calculating the amount of tape
used per write. The default is 1600.
.PP
.DT
If no arguments are given,
the
.I key
is assumed to be
.B 9u
and a default file system is dumped
to the default tape.
.PP
Now a short suggestion on how
perform dumps.
Start with a full level 0 dump
.PP
	dump 0u
.PP
Next,
periodic level 9 dumps should be made on an
exponential progression of tapes.
(Sometimes called Tower of Hanoi \- 1 2 1 3 1 2 1 4 ...
tape 1 used every other time,
tape 2 used every fourth,
tape 3 used every eighth, etc.)
.PP
	dump 9u
.PP
When the level 9 incremental approaches a full
tape (about 78000 blocks at 1600 BPI blocked 20),
a level 1 dump should be made.
.PP
	dump 1u
.PP
After this,
the exponential series should progress as uninterrupted.
These level 9 dumps are based on the level 1 dump which
is based on the level 0 full dump.
This progression of levels of dump can be carried
as far as desired.
.SH FILES
default filesystem and tape vary with installation.
.br
/etc/ddate	record dump dates of filesystem/level.
.SH "SEE ALSO"
restor(1), dump(5), dumpdir(1)
.SH DIAGNOSTICS
If the dump requires more than one tape,
it will ask you to change tapes.
Reply with a new-line when this has been done.
.SH BUGS
Sizes are based on 1600 BPI blocked tape.
The raw magtape device has to be used to
approach these densities.
Read errors on the filesystem are ignored.
Write errors on the magtape are usually fatal.
Commit	Line	Data
e6817382 BJ	1	.TH DUMP 1M
	2	.SH NAME
	3	dump \- incremental file system dump
	4	.SH SYNOPSIS
	5	.B dump
	6	[ key [ argument ... ] filesystem ]
	7	.SH DESCRIPTION
	8	.I Dump
	9	copies to magnetic tape all files
	10	changed after a certain date
	11	in the
	12	.I filesystem.
	13	The
	14	.I key
	15	specifies the date and other options about the dump.
	16	.I Key
	17	consists of characters from
	18	the set
	19	.B 0123456789fusd.
	20	.TP 5
	21	.B f
	22	Place the dump on the next
	23	.I argument
	24	file
	25	instead of the tape.
	26	.TP 5
	27	.B u
	28	If the dump completes successfully,
	29	write the date of the beginning of the dump on
	30	file `/etc/ddate'.
	31	This file records a separate date for
	32	each filesystem and each dump level.
	33	.TP 5
	34	.B 0\-9
	35	This number is the `dump level'.
	36	All files modified since the last date stored
	37	in the file `/etc/ddate' for
	38	the same filesystem at lesser levels
	39	will be dumped.
	40	If no date is determined by the level,
	41	the beginning of time is assumed;
	42	thus the option
	43	.B 0
	44	causes the entire filesystem to be dumped.
	45	.TP 5
	46	.B s
	47	The size of the dump tape is specified in feet.
	48	The number of feet is taken from the next
	49	.I argument.
	50	When the specified size is reached,
	51	the dump will wait for reels to be changed.
	52	The default size is 2300 feet.
	53	.TP 5
	54	.B d
	55	The density of the tape, expressed in BPI,
	56	is taken from the next
	57	.I argument.
	58	This is used in calculating the amount of tape
	59	used per write. The default is 1600.
	60	.PP
	61	.DT
	62	If no arguments are given,
	63	the
	64	.I key
65	is assumed to be
66	.B 9u
67	and a default file system is dumped
68	to the default tape.
69	.PP
70	Now a short suggestion on how
71	perform dumps.
72	Start with a full level 0 dump
73	.PP
74	dump 0u
75	.PP
76	Next,
77	periodic level 9 dumps should be made on an
78	exponential progression of tapes.
79	(Sometimes called Tower of Hanoi \- 1 2 1 3 1 2 1 4 ...
80	tape 1 used every other time,
81	tape 2 used every fourth,
82	tape 3 used every eighth, etc.)
83	.PP
84	dump 9u
85	.PP
86	When the level 9 incremental approaches a full
87	tape (about 78000 blocks at 1600 BPI blocked 20),
88	a level 1 dump should be made.
89	.PP
90	dump 1u
91	.PP
92	After this,
93	the exponential series should progress as uninterrupted.
94	These level 9 dumps are based on the level 1 dump which
95	is based on the level 0 full dump.
96	This progression of levels of dump can be carried
97	as far as desired.
98	.SH FILES
99	default filesystem and tape vary with installation.
100	.br
101	/etc/ddate record dump dates of filesystem/level.
102	.SH "SEE ALSO"
103	restor(1), dump(5), dumpdir(1)
104	.SH DIAGNOSTICS
105	If the dump requires more than one tape,
106	it will ask you to change tapes.
107	Reply with a new-line when this has been done.
108	.SH BUGS
109	Sizes are based on 1600 BPI blocked tape.
110	The raw magtape device has to be used to
111	approach these densities.
112	Read errors on the filesystem are ignored.
113	Write errors on the magtape are usually fatal.