rdump(8c)rdump(8c)Namerdump - 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.
The command relies on the user having access to the remote system
through entires in the or files, as documented in
This utility supports EOT handling which allows the use of multiple
media. The utility prompts for the next volume when it encounters the
end of the current volume.
This utility supports the TA90 style sequential stacker loader device.
The device ejects a cartridge when it is taken off line. This utility
performs the device ejection on behalf of the user when it encounters a
multivolume boundary during write or read operations involving tape.
The device then automatically loads the next available tape (if there
is one). The utility then attempts to access this next tape for a rea‐
sonable amount of time (approximately three minutes) before prompting
the user for a manual reload operation.
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 modi‐
fied 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.
b The next argument is a number that specifies the blocking fac‐
tor for tape records. The default is 10; the maximum is 63.
The tape records are stored in 1024-byte blocks.
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
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 preallo‐
cation 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 con‐
sists of one free format record per line: filesystem name,
increment level and format dump date. The superuser can care‐
fully 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 out‐
put. 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
performed 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.
Restrictions
The program does not interface with sequential stacker loader tape
drives.
Using a blocking factor other than the default may lead to higher per‐
formance. However, you must select a value that is compatible with the
hardware limitations of the source and destination machines.
Do not attempt to write non-default sized tape records to a remote sys‐
tem running ULTRIX Version 4.3 or earlier, because for those systems
the program is limited to the default record size.
Diagnostics
Same as with a few extra related to the network.
Files
Required for user interface
See Alsodump(8), rmt(8c)rdump(8c)
