dump.bsd(1M) dump.bsd(1M)NAME dump.bsd, rdump - copy the files within the named file system to a dump.bsd archive SYNOPSIS /etc/dump.bsd [-Tfile-system-type] [key]... [argument...] [filesystem] /etc/rdump [-Tfile-system-type] [key]... [argument...] [filesystem] DESCRIPTION dump.bsd and rdump copy to the backup device any files within filesystem that have been changed after a certain date. rdump allows use of a remotely connected backup device (see the -f flag option). The key specifies the date and other options about the dump and consists of characters from the set 0123456789bcfusdFwWn. FLAG OPTIONS The -T flag option indicates the file-system type, such as 4.2 or 5.2. If this option is not used, dump.bsd attempts to determine the file-system type. If more than one key is used that requires an associated ar- gument, then the arguments must be supplied in the same ord- er as each key. The following options may be used for the value of key : 0-9 Set the ``dump level'' to the one-digit value speci- fied. All files modified since the last date stored in the file /etc/dumpdates for the specified file system at lesser levels are dumped. If a date is not deter- mined by the level, the beginning of time is assumed; thus the flag option 0 causes the entire file system to be dumped. b Use the associated argument as the blocking-factor for the records of the backup device, rather than the de- fault blocking-factor of 1. This option should only be used with the raw versions of device files. The letters b, k, m, or f may be used at the end of the as- sociated argument to indicate a number of blocks, kilo- bytes, megabytes, or feet, respectively. c Set the values for flag options b and s to those ap- propriate for the Apple(Reg.) Tape Backup 40SC, includ- ing a default size of 37.5 MB and a blocking-factor of 8K. If a value is also specified for the size of the media by using the s option, then it is interpreted as the number of disk blocks rather than the number of feet of tape. April, 1990 1
dump.bsd(1M) dump.bsd(1M)f Place the dump on the associated argument instead of the default device file /dev/tape. If /etc/rdump is used, the associated argument should include a refer- ence to the system where the backup device is located. A colon separates the remote-system name from the dev- ice file, as in /etc/rdump -rbf 8k server:/dev/rmt/tc3 If the environmental shell variable TAPE is set and the f option is not used, the value of TAPE is used as the device file to which the output is written. If the f option is specified along with an associated argument of -, dump.bsd writes to standard output. F Set the values for flag options b and s to those ap- propriate for dual-density, 3.5-inch disks, including a default size of 800K. If a value is also specified for the size of the media by using the s option, then it is interpreted as the number of disk blocks rather than the number of feet of tape. u If the dump completes successfully, write the date of the beginning of the dump on the file /etc/dumpdates. This file records a separate date for each file system and each dump level. The contents of /etc/dumpdates is readable as text, consisting of one free-format record per line: file-system name, increment level, and ctime(3) format dump date. If necessary, /etc/dumpdates may be edited to change any of the fields. s Specify the size of the backup media in feet. The number of feet is taken from the associated argument. The letters b, k, or m may be used at the end of the associated argument to indicate a number of blocks, ki- lobytes, or megabytes instead of feet. When the speci- fied size is reached, dump.bsd waits for the next flop- py disk or tape volume. The default tape size is 2300 feet. d Specify the density of the tape, expressed in BPI and taken from the associated argument. This is used in calculating the amount of tape used per reel. The de- fault is 1600. W Cause dump.bsd to print out, for each file system in /etc/dumpdates, the most recent dump date and level, and highlight those file systems that should be dumped. dump.bsd tells the operator what file systems need to be dumped. This information is gleaned from the files /etc/dumpdates and /etc/fstab. If the W flag option is 2 April, 1990
dump.bsd(1M) dump.bsd(1M)set, all other flag options are ignored, and dump.bsd exits immediately. w Similar to W, but print only those file systems that need to be dumped. n Whenever dump.bsd requires operator attention, notify, by a means similar to a wall(1), all of the operators in the group operator. If filesystem is a block device and is listed in /etc/fstab, dump.bsd will use the corresponding raw device instead. If no arguments are given, key is assumed to be 9u, and a default file system is dumped to the default tape. The de- fault file system is the root file system (/), and the de- fault tape is /dev/tape. dump.bsd requires operator intervention on these conditions: end of tape, end of dump, tape write error, and tape open or disk read errors (if there are more than a threshold of 32). In addition to alerting all operators implied by the n key, dump.bsd interacts with the operator on the dump.bsd control terminal at times when dump.bsd can no longer proceed, or if something is grossly wrong. All questions dump.bsd poses must be answered by typing yes or no, appropriately. Making a full dump involves a lot of time and effort, so dump.bsd initiates a checkpoint at the start of each tape volume. If writing to that volume fails for some reason, dump.bsd, with operator permission, restarts itself from the checkpoint after the old tape is rewound and removed and a new tape has been mounted. dump.bsd informs the operator of its progress at periodic intervals, including usually low estimates of the number of blocks to write, the number of tapes or floppy disks it will take, the time before completion, and the time remaining be- fore the tape change. The output is verbose, so others will know that the terminal controlling dump.bsd is busy and will be busy for some time. To perform dumps, start with a full (level 0) dump dump.bsd 0un Next, dumps of active file systems are taken on a daily basis by using a modified Tower of Hanoi algorithm with this sequence of dump levels: 3 2 5 4 7 6 9 8 9 9 ... April, 1990 3
dump.bsd(1M) dump.bsd(1M)For the daily dumps, a set of 10 tapes per dumped file sys- tem 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. FILES /etc/dump.bsd /etc/dumpdates new format dump date record /etc/fstab dump table: file systems and frequency /etc/group to find group operator /dev/tape default tape unit to dump to SEE ALSO cpio(1), tp(1), finc(1M), restore(1M), rdump(1M), tar(1M), volcopy(1M), fstyp(2), dump.bsd(4), fstab(4). DIAGNOSTICS dump.bsd exits with zero status on success. Startup errors are indicated with an exit code of 1; abnormal termination is indicated with an exit code of 3. BUGS Fewer than 32 read errors on the file system are ignored. Each reel requires a new process, so parent processes for reels already written just hang around until the entire tape is written. dump.bsd with the W or w flag option does not report file systems that have never been recorded in /etc/dumpdates, even if listed in /etc/fstab. It would be convenient if dump.bsd knew about the dump se- quence, kept track of the tapes scribbled on, told the operator which tape to mount and when, and provided more as- sistance for the operator running restore. 4 April, 1990