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