|
|
1.1 root 1: .TH DUMP 8 "4 February 1983"
2: .UC 4
3: .SH NAME
4: dump \- incremental file system dump
5: .SH SYNOPSIS
6: .B /etc/dump
7: [ key [
8: .I argument
9: \&... ] filesystem ]
10: .SH DESCRIPTION
11: .I Dump
12: copies to magnetic tape all files
13: changed after a certain date
14: in the
15: .I filesystem.
16: The
17: .I key
18: specifies the date and other options about the dump.
19: .I Key
20: consists of characters from
21: the set
22: .B 0123456789fusdWn.
23: .TP 5
24: .B 0\-9
25: This number is the `dump level'.
26: All files modified since the last date stored
27: in the file
28: .I /etc/dumpdates
29: for the same filesystem at lesser levels
30: will be dumped.
31: If no date is determined by the level,
32: the beginning of time is assumed;
33: thus the option
34: .B 0
35: causes the entire filesystem to be dumped.
36: .TP 5
37: .B f
38: Place the dump on the next
39: .I argument
40: file
41: instead of the tape.
42: If the name of the file is ``\-'',
43: .I dump
44: writes to standard output.
45: .TP 5
46: .B u
47: If the dump completes successfully,
48: write the date of the beginning of the dump on
49: file
50: .I /etc/dumpdates.
51: This file records a separate date for
52: each filesystem and each dump level.
53: The format of
54: .I /etc/dumpdates
55: is readable by people, consisting of one
56: free format record per line:
57: filesystem name, increment level
58: and
59: .I ctime(3)
60: format dump date.
61: .I /etc/dumpdates
62: may be edited to change any of the fields,
63: if necessary.
64: .TP 5
65: .B s
66: The size of the dump tape is specified in feet.
67: The number of feet is taken from the next
68: .I argument.
69: When the specified size is reached,
70: .I dump
71: will wait for reels to be changed.
72: The default tape size is 2300 feet.
73: .TP 5
74: .B d
75: The density of the tape, expressed in BPI,
76: is taken from the next
77: .I argument.
78: This is used in calculating the amount of tape
79: used per reel. The default is 1600.
80: .TP 5
81: .B W
82: .I Dump
83: tells the operator what file systems need to be dumped.
84: This information is gleaned from the files
85: .I /etc/dumpdates
86: and
87: .I /etc/fstab.
88: The
89: .B W
90: option causes
91: .I dump
92: to print out, for each file system in
93: .I /etc/dumpdates
94: the most recent dump date and level,
95: and highlights those file systems that should be dumped.
96: If the
97: .B W
98: option is set, all other options are ignored, and
99: .I dump
100: exits immediately.
101: .TP 5
102: .B w
103: Is like W, but prints only those filesystems which need to be dumped.
104: .TP 5
105: .B n
106: Whenever
107: .I dump
108: requires operator attention,
109: notify by means similar to a
110: .IR wall (1)
111: all of the operators in the group \*(lqoperator\*(rq.
112: .PP
113: If no arguments are given,
114: the
115: .I key
116: is assumed to be
117: .B 9u
118: and a default file system is dumped
119: to the default tape.
120: .PP
121: .I Dump
122: requires operator intervention on these conditions:
123: end of tape,
124: end of dump,
125: tape write error,
126: tape open error or
127: disk read error (if there are more than a threshold of 32).
128: In addition to alerting all operators implied by the
129: .B n
130: key,
131: .I dump
132: interacts with the operator on
133: .I dump's
134: control terminal at times when
135: .I dump
136: can no longer proceed,
137: or if something is grossly wrong.
138: All questions
139: .I dump
140: poses
141: .B must
142: be answered by typing \*(lqyes\*(rq or \*(lqno\*(rq,
143: appropriately.
144: .PP
145: Since making a dump involves a lot of time and effort for full dumps,
146: .I dump
147: checkpoints itself at the start of each tape volume.
148: If writing that volume fails for some reason,
149: .I dump
150: will,
151: with operator permission,
152: restart itself from the checkpoint
153: after the old tape has been rewound and removed,
154: and a new tape has been mounted.
155: .PP
156: .I Dump
157: tells the operator what is going on at periodic intervals,
158: including usually low estimates of the number of blocks to write,
159: the number of tapes it will take, the time to completion, and
160: the time to the tape change.
161: The output is verbose,
162: so that others know that the terminal
163: controlling
164: .I dump
165: is busy,
166: and will be for some time.
167: .PP
168: Now a short suggestion on how to
169: perform dumps.
170: Start with a full level 0 dump
171: .PP
172: dump 0un
173: .PP
174: Next, dumps of active file
175: systems are taken on a daily basis,
176: using a modified Tower of Hanoi algorithm,
177: with this sequence of dump levels:
178: .ce 1
179: 3 2 5 4 7 6 9 8 9 9 ...
180: For the daily dumps, a set of 10 tapes per dumped file system
181: is used on a cyclical basis.
182: Each week, a level 1 dump is taken, and
183: the daily Hanoi sequence repeats with 3.
184: For weekly dumps, a set of 5 tapes per dumped file system is
185: used, also on a cyclical basis.
186: Each month, a level 0 dump is taken
187: on a set of fresh tapes that is saved forever.
188: .SH FILES
189: .nf
190: .ta \w'/etc/dumpdates\ \ 'u
191: /dev/rfsd1c default filesystem to dump from
192: /dev/rcy0s default tape unit to dump to
193: /etc/ddate old format dump date record (obsolete after \fB\-J\fR option)
194: /etc/dumpdates new format dump date record
195: /etc/fstab dump table: file systems and frequency
196: /etc/group to find group \fIoperator\fP
197: .fi
198: .DT
199: .br
200: .SH "SEE ALSO"
201: restore(8),
202: dump(5),
203: fstab(5)
204: .SH DIAGNOSTICS
205: Many, and verbose.
206: .SH BUGS
207: .PP
208: Sizes are based on 1600 BPI blocked tape;
209: the raw magtape device has to be used to approach these densities.
210: Fewer than 32 read errors on the filesystem are ignored.
211: Each reel requires a new process, so parent processes for
212: reels already written just hang around until the entire tape
213: is written.
214: .PP
215: It would be nice if
216: .I dump
217: knew about the dump sequence,
218: kept track of the tapes scribbled on,
219: told the operator which tape to mount when,
220: and provided more assistance
221: for the operator running
222: .IR restore .
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.