dump.bsd(1M) dump.bsd(1M)NAME dump.bsd, rdump - create a dump.bsd archive by making copies of files from a given file system SYNOPSIS dump.bsd [Tfstype] [dumplev] [b] [d] [f] [n] [s] [u] [bdfs-arg]... fs-reference dump.bsd [Tfstype] [dumplev] c [d] [f] [n] [s] [u] [dfs-arg]... fs-reference dump.bsd [Tfstype] [dumplev] F [d] [f] [n] [s] [u] [dfs-arg]... floppydev dump.bsd [Tfstype] w dump.bsd [Tfstype] W rdump [Tfstype] [dumplev] [b] [d] [f] [n] [s] [u] [bdfs-arg]... host:fs-reference rdump [Tfstype] [dumplev] c [d] [f] [n] [s] [u] [dfs-arg]... host:fs-reference rdump [Tfstype] [dumplev] F [d] [f] [n] [s] [u] [dfs-arg]... host:fs-reference rdump [Tfstype] w rdump [Tfstype] W ARGUMENTS dumplev Specifies the dump level of the specified file system. Replace dumplev with a one digit value from from one to nine. The /etc/dumpdates file records a separate date for each file system and each dump level. All files in the specified file system that were modified since the last dump date stored in the dumpdates file which have a lower dump level are copied. If a date is not determined by the level, the beginning of time is assumed; thus the option 0 causes the entire file system to be dumped. b Lets you specify a blocking-factor as one of the supplied bdfs-arg values. The default blocking-factor for the backup device is 1. Use this option with the raw versions of device files. To indicate a number of blocks, kilobytes, megabytes, or feet, you can append one of the following letters to the value: b January 1992 1
dump.bsd(1M) dump.bsd(1M)k m f bdfs-arg Specifies one of the arguments associated with the b, d, f, and s command options. Note that these values are detached from their associated command options, but they must be entered in an order that matches the order of the command options. For more information on the legal replacement values, refer to each of the specific command options elsewhere in this alphabetical list. c Sets the blocking-factor and size parameters to those appropriate for the Apple Tape Backup 40SC. This includes 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. d Lets you specify the density of the tape as one of the supplied bdfs-arg or dfs-arg values. The default value is 1600 BPI. This option is used in calculating the amount of tape used per reel. dfs-arg Specifies one of the arguments associated with the d, f, and s command options. Note that these values are detached from their associated command options, but they must be entered in an order that matches the order of the command options. For more information on the legal replacement values, refer to each of the specific command options elsewhere in this alphabetical list. f Lets you specify the device file or other file in which the archive data is to be written as one of the bdfs-arg or dfs-arg values supplied. The default value is /dev/tape. If the environmental shell variable TAPE is set and this option is not used, the value of TAPE is used as the device file to which the output is written. If this option is specified along with an associated value of -, dump.bsd writes to standard output. floppydev Specifies the floppy device file onto which the archive is written. For example, you may replace floppydev with /dev/rfloppy0. 2 January 1992
dump.bsd(1M) dump.bsd(1M)fs-reference host:fs-reference Specifies the name of the file system device to be archived. To specify the partition associated with slice 2 of the drive with SCSI ID 0, specify the raw device file /dev/rdsk/c0d0s2. If you specify a block device that is listed in /etc/fstab, dump.bsd will use the corresponding raw device instead. However, a reference to the root file system should always be made in terms of the raw device file because the /etc/fstab entry for it is set to be ignored. If rdump is used, the second syntax format should be used. A colon separates the remote-system name from the device file, as in rdump bf 8k server:/dev/rmt/tc3 Tfstype Specifies the file system type. Replace fstype with one of these two options: 5.x Specifies a System V file system (SVFS), such as 5.2 (this is the default). Replace x with the last digit of the revision for the file system, such as 2, 3, and so on. 4.x Specifies a Berkeley System Distribution (BSD) file system. Replace x with the last digit of the revision for the file system, such as 2, 3, and so on. The default is 4.2. If this option is not used, dump.bsd attempts to determine the type of the file system. F Sets the blocking-factor and size to those appropriate 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. n Notifies all of the operators in the operator group whenever dump.bsd requires operator attention. The operators are notified by a means similar to the wall(1) command. The dump.bsd command 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 January 1992 3
dump.bsd(1M) dump.bsd(1M)all operators implied by the n option, 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. s Lets you specify the size of the backup media as one of the supplied bdfs-arg or dfs-arg values. To indicate a number of blocks, kilobytes, megabytes, or feet, you can append one of the following letters to the value: b k m f The default tape size is 2300 feet. When the specified size is reached, dump.bsd waits for the next floppy disk or tape volume. u Writes the date that the dump began on the /etc/dumpdates file, if the dump was completed successfully. 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 format dump date. If necessary, the /etc/dumpdates file may be edited to change any of the fields. w Prints out the most recent dump date and level for only those file systems that need to be dumped. When this option is set, all other options are ignored, and dump.bsd exits immediately. This option is similar to W. W Prints out the most recent dump date and level for each file system in the /etc/dumpdates file, then highlights those file systems that should be dumped. dump.bsd informs the operator of the file systems that need to be dumped. This information is gleaned from the files /etc/dumpdates and /etc/fstab. When this option is set, all other options are ignored, and dump.bsd exits immediately. DESCRIPTION dump.bsd and rdump copy, to a backup file or device, any files within the specified file system that have been changed after a certain date. The rdump command allows use of a remotely connected backup device (see the f option). 4 January 1992
dump.bsd(1M) dump.bsd(1M)If no options are given, dump.bsd uses dump level 9, writes to the dump dates file as if the u option were specified, and writes the archive of the root file system onto the device referenced by /dev/tape. 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. The dump.bsd command 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 before 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. EXAMPLES To create a full (level 0) backup on /dev/tape containing all the files in the root file system, enter: dump.bsd 0un /dev/dsk/c0d0s0 The device file /dev/dsk/c0d0s0 normally refers to an internal drive, factory set to SCSI ID 0. Next, backups 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 ... For the daily backups, a set of 10 tapes per dumped file system is used on a cyclical basis. Each week, a level 1 backup is performed, 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 backup is performed on a set of fresh tapes that is saved forever. STATUS MESSAGES AND VALUES If you are successful in creating an archive, dump.bsd exits with zero status on success. Startup errors are indicated with an exit status of 1 and abnormal termination is indicated with an exit status of 3. LIMITATIONS Fewer than 32 read errors on the file system are ignored. Each reel requires a new process. Parent processes for January 1992 5
dump.bsd(1M) dump.bsd(1M)reels already written hang around for the duration. The dump.bsd command with the W or w option does not report file systems that have never been recorded in /etc/dumpdates, even if listed in /etc/fstab. FILES /etc/dump.bsd Executable file /etc/rdump Executable file /etc/dumpdates Dump date record file /etc/fstab File containing a list of normally mounted file systems /etc/group Group accounts file /dev/tape Default device file SEE ALSO finc(1M), restore(1M), volcopy(1M) cpio(1), tp(1), tar(1) in A/UX Command Reference fstyp(3), dump.bsd(4), fstab(4) in A/UX Programmer's Reference 6 January 1992