Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dump(1m) [v7 man page]

DUMP(1M)																  DUMP(1M)

dump - incremental file system dump SYNOPSIS
dump [ key [ argument ... ] filesystem ] DESCRIPTION
Dump copies to magnetic tape all files changed after a certain date in the filesystem. The key specifies the date and other options about the dump. Key consists of characters from the set 0123456789fusd. f Place the dump on the next argument file instead of the tape. u If the dump completes successfully, write the date of the beginning of the dump on file `/etc/ddate'. This file records a separate date for each filesystem and each dump level. 0-9 This number is the `dump level'. All files modified since the last date stored in the file `/etc/ddate' for the same filesystem at lesser levels will be dumped. If no date is determined by the level, the beginning of time is assumed; thus the option 0 causes the entire filesystem to be dumped. s The size of the dump tape is specified in feet. The number of feet is taken from the next argument. When the specified size is reached, the dump will wait for reels to be changed. The default size is 2300 feet. d The density of the tape, expressed in BPI, is taken from the next argument. This is used in calculating the amount of tape used per write. The default is 1600. If no arguments are given, the key is assumed to be 9u and a default file system is dumped to the default tape. Now a short suggestion on how perform dumps. Start with a full level 0 dump dump 0u Next, periodic level 9 dumps should be made on an exponential progression of tapes. (Sometimes called Tower of Hanoi - 1 2 1 3 1 2 1 4 ... tape 1 used every other time, tape 2 used every fourth, tape 3 used every eighth, etc.) dump 9u When the level 9 incremental approaches a full tape (about 78000 blocks at 1600 BPI blocked 20), a level 1 dump should be made. dump 1u After this, the exponential series should progress as uninterrupted. These level 9 dumps are based on the level 1 dump which is based on the level 0 full dump. This progression of levels of dump can be carried as far as desired. FILES
default filesystem and tape vary with installation. /etc/ddate: record dump dates of filesystem/level. SEE ALSO
restor(1), dump(5), dumpdir(1) DIAGNOSTICS
If the dump requires more than one tape, it will ask you to change tapes. Reply with a new-line when this has been done. BUGS
Sizes are based on 1600 BPI blocked tape. The raw magtape device has to be used to approach these densities. Read errors on the filesys- tem are ignored. Write errors on the magtape are usually fatal. DUMP(1M)

Check Out this Related Man Page

RESTOR(8)						      System Manager's Manual							 RESTOR(8)

restor - incremental file system restore SYNOPSIS
restor key [ argument ... ] DESCRIPTION
Restor is used to read magtapes dumped with the dump command. The key specifies what is to be done. Key is one of the characters rRxt optionally combined with f. f Use the first argument as the name of the tape instead of the default. r or R The tape is read and loaded into the file system specified in argument. This should not be done lightly (see below). If the key is R restor asks which tape of a multi volume set to start on. This allows restor to be interrupted and then restarted (an icheck -s must be done before restarting ). x Each file on the tape named by an argument is extracted. The file name has all `mount' prefixes removed; for example, /usr/bin/lpr is named /bin/lpr on the tape. The file extracted is placed in a file with a numeric name supplied by restor (actually the inode number). In order to keep the amount of tape read to a minimum, the following procedure is recommended: Mount volume 1 of the set of dump tapes. Type the restor command. Restor will announce whether or not it found the files, give the number it will name the file, and rewind the tape. It then asks you to `mount the desired tape volume'. Type the number of the volume you choose. On a multivolume dump the recom- mended procedure is to mount the last through the first volume in that order. Restor checks to see if any of the files requested are on the mounted tape (or a later tape, thus the reverse order) and doesn't read through the tape if no files are. If you are working with a single volume dump or the number of files being restored is large, respond to the query with `1' and restor will read the tapes in sequential order. If you have a hierarchy to restore you can use dumpdir(8) to produce the list of names and a shell script to move the resulting files to their homes. t Print the date the tape was written and the date the file system was dumped from. The r option should only be used to restore a complete dump tape onto a clear file system or to restore an incremental dump tape onto this. Thus mkfs /dev/hp0a 4807 restor r /dev/hp0a is a typical sequence to restore a complete dump. Another restor can be done to get an incremental dump in on top of this. A dump followed by a mkfs and a restor is used to change the size of a file system. FILES
/dev/rmt1 default file name rst* temporary files SEE ALSO
dump(8), dumpdir(8), mkfs(8) DIAGNOSTICS
There are various diagnostics involved with reading the tape and writing the disk. There are also diagnostics if the i-list or the free list of the file system is not large enough to hold the dump. If the dump extends over more than one tape, it may ask you to change tapes. Reply with a newline when the next tape has been mounted. Dump tapes made before the new ondisc directory structure will be converted automatically by restor . BUGS
There is redundant information on the tape that could be used in case of tape reading problems. Unfortunately, restor does't use it. 3rd Berkeley Distribution RESTOR(8)
Man Page