dump(1m) [v7 man page]

DUMP(1M)																  DUMP(1M)

NAME

       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)

rdump(8c)																 rdump(8c)

Name
       rdump - file system dump across the network

Syntax
       /etc/rdump [ -key [ argument ... ] filesystem ]

Description
       The command copies to magnetic tapes, disks, or a dump image file all files changed after a certain date in the filesystem.  The command is
       identical in operation to except the f key must be specified and the file supplied should be of the following form:

       remote-system-name:device-or-file

       The command initiates a remote server, on the remote system to access the remote device or file.

Options
       With the command, you specify a string of one or more of the options described below.  If no options are specified, the key 9u is assumed.

       0-9     This number is the ``dump level.''  All files that were modified since the last date stored in  the  file  for  the  filesystem	at
	       lesser  levels  will be dumped.	If no date is determined by the level, the beginning of time is assumed.  Thus, the level 0 causes
	       the entire filesystem to be dumped, a level 5 is used for a weekly backup and a level 9 for a daily backup.

       B       The next argument is a number that specifies the size, in 1024-byte blocks, of a storage medium, such as a diskette or a  removable
	       disk.  See the first example.

       d       The  density  of  the  tape,  expressed in bits per inch, is taken from the next argument.  This density is used in calculating the
	       amount of tape used per reel.  The default density is 1600 bpi.

       f       Place the dump on the file or device specified by the next argument.  This file is specified as remote-system-name:device-or-file.

       n       Notify, by means similar to a command, all users in the group ``operator'' when needs operator attention.

       o       Provides compatibility with non-ULTRIX or pre-ULTRIX Version 2.0 remote systems.

       S       Displays amount of space used by without performing the dump operation.	This is used for presizing either for  file  preallocation
	       or to ensure the correct number of tapes or disks are on hand.

       s       The  next  argument  specifies  the  size of the dump tape (in feet).  When the specified size is reached, waits for the reel to be
	       changed.  The default tape size is 2300 feet.

       u       If the dump completes successfully, writes the date of the beginning of the dump to file This file records a separate date for each
	       filesystem  and	each  dump level.  The format of consists of one free format record per line: filesystem name, increment level and
	       format dump date.  The superuser can carefully edit to change any of the fields.

       W       The utility tells the operator what file systems need to be dumped.  This information is taken from the files and The option causes
	       to print out, for each file system in the most recent dump date and level, and highlights those file systems that should be dumped.
	       If the option is used, all other options are ignored, and exits immediately.

       w       Unlike lists only those filesystems that need to be dumped.

Examples
       This example reports number of bytes to be output for a level 0 dump of the root file system.  Please note: the file is not created.
       rdump OSf system:test /
       This example dumps the root(/) file system from the local system to a remote system named ``nihil''.  A level 0 dump to tape  is  performed
       and the file is updated.
       rdump 0uf nihil:/dev/rmt0h /

       This  example  dumps the user (/usr) file system from the local system to a remote system named ``dickens'' using the RX50 device named for
       output.	A level 0 dump is performed, but the file is not updated.
       rdump 0f dickens:/dev/rra1a /usr

       This example dumps the root file system to a non-ULTRIX or ULTRIX before Version 2.0 remote system.  A level 0 dump to a tape drive is per-
       formed and the file is updated.
       rdump 0ouf system:/dev/rmt0h /

       This  example  dumps the root file system to a non-ULTRIX or ULTRIX before Version 2.0 remote system.  A level 0 dump to the rx50 device is
       performed and the file is updated.  Note the specification of 400 as the device size in 1,024 byte blocks.
       rdump 0ouBf 400 system:/dev/rra1a /

       If you want to use / and you must have these entries in the file.

Diagnostics
       Same as with a few extra related to the network.

Files
       Required for user interface

See Also
       dump(8), rmt(8c)

																	 rdump(8c)