|
|
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
1.1.1.2 ! root 81: .B b
! 82: The block size
! 83: of the tape, expressed in 1K byte units,
! 84: is taken from the next
! 85: .I argument.
! 86: The default is 10 (10K bytes)
! 87: This block size will be stored in the header so that
! 88: .IR Restore (8)
! 89: will use it to read the tape correctly.
! 90: .TP 5
1.1 root 91: .B W
92: .I Dump
93: tells the operator what file systems need to be dumped.
94: This information is gleaned from the files
95: .I /etc/dumpdates
96: and
97: .I /etc/fstab.
98: The
99: .B W
100: option causes
101: .I dump
102: to print out, for each file system in
103: .I /etc/dumpdates
104: the most recent dump date and level,
105: and highlights those file systems that should be dumped.
106: If the
107: .B W
108: option is set, all other options are ignored, and
109: .I dump
110: exits immediately.
111: .TP 5
112: .B w
113: Is like W, but prints only those filesystems which need to be dumped.
114: .TP 5
115: .B n
116: Whenever
117: .I dump
118: requires operator attention,
119: notify by means similar to a
120: .IR wall (1)
121: all of the operators in the group \*(lqoperator\*(rq.
122: .PP
123: If no arguments are given,
124: the
125: .I key
126: is assumed to be
127: .B 9u
128: and a default file system is dumped
129: to the default tape.
130: .PP
131: .I Dump
132: requires operator intervention on these conditions:
133: end of tape,
134: end of dump,
135: tape write error,
136: tape open error or
137: disk read error (if there are more than a threshold of 32).
138: In addition to alerting all operators implied by the
139: .B n
140: key,
141: .I dump
142: interacts with the operator on
143: .I dump's
144: control terminal at times when
145: .I dump
146: can no longer proceed,
147: or if something is grossly wrong.
148: All questions
149: .I dump
150: poses
151: .B must
152: be answered by typing \*(lqyes\*(rq or \*(lqno\*(rq,
153: appropriately.
154: .PP
155: Since making a dump involves a lot of time and effort for full dumps,
156: .I dump
157: checkpoints itself at the start of each tape volume.
158: If writing that volume fails for some reason,
159: .I dump
160: will,
161: with operator permission,
162: restart itself from the checkpoint
163: after the old tape has been rewound and removed,
164: and a new tape has been mounted.
165: .PP
166: .I Dump
167: tells the operator what is going on at periodic intervals,
168: including usually low estimates of the number of blocks to write,
169: the number of tapes it will take, the time to completion, and
170: the time to the tape change.
171: The output is verbose,
172: so that others know that the terminal
173: controlling
174: .I dump
175: is busy,
176: and will be for some time.
177: .PP
178: Now a short suggestion on how to
179: perform dumps.
180: Start with a full level 0 dump
181: .PP
182: dump 0un
183: .PP
184: Next, dumps of active file
185: systems are taken on a daily basis,
186: using a modified Tower of Hanoi algorithm,
187: with this sequence of dump levels:
188: .ce 1
189: 3 2 5 4 7 6 9 8 9 9 ...
190: For the daily dumps, a set of 10 tapes per dumped file system
191: is used on a cyclical basis.
192: Each week, a level 1 dump is taken, and
193: the daily Hanoi sequence repeats with 3.
194: For weekly dumps, a set of 5 tapes per dumped file system is
195: used, also on a cyclical basis.
196: Each month, a level 0 dump is taken
197: on a set of fresh tapes that is saved forever.
198: .SH FILES
199: .nf
200: .ta \w'/etc/dumpdates\ \ 'u
201: /dev/rfsd1c default filesystem to dump from
202: /dev/rcy0s default tape unit to dump to
203: /etc/ddate old format dump date record (obsolete after \fB\-J\fR option)
204: /etc/dumpdates new format dump date record
205: /etc/fstab dump table: file systems and frequency
206: /etc/group to find group \fIoperator\fP
207: .fi
208: .DT
209: .br
210: .SH "SEE ALSO"
211: restore(8),
212: dump(5),
213: fstab(5)
214: .SH DIAGNOSTICS
215: Many, and verbose.
216: .SH BUGS
217: .PP
218: Sizes are based on 1600 BPI blocked tape;
219: the raw magtape device has to be used to approach these densities.
220: Fewer than 32 read errors on the filesystem are ignored.
221: Each reel requires a new process, so parent processes for
222: reels already written just hang around until the entire tape
223: is written.
224: .PP
225: It would be nice if
226: .I dump
227: knew about the dump sequence,
228: kept track of the tapes scribbled on,
229: told the operator which tape to mount when,
230: and provided more assistance
231: for the operator running
232: .IR restore .
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.