|HP-UX Reference > D
HP-UX 11i Version 3: February 2007
dump, rdump — incremental file system dump, local or across network
/usr/sbin/dump [option [argument ...] filesystem]
/usr/sbin/rdump [option [argument ...] filesystem]
The dump and rdump commands copy to magnetic tape all files in the filesystem that have been changed after a certain date. This information is derived from the files /var/adm/dumpdates and /etc/fstab. option specifies the date and other options about the dump. option consists of characters from the set 0123456789bdfnsuWw. The dump and rdump commands work only on file systems of type hfs. If the given file system is not of type hfs, dump and rdump will abort after printing an error message.
If no arguments are given, option is assumed to be 9u and a default file system is dumped to the default tape.
Sizes are based on 1600-BPI blocked tape; the raw magnetic tape device must be used to approach these densities. Up to 32 read errors on the file system are ignored. Each reel requires a new process; thus parent processes for reels already written remain until the entire tape is written.
The rdump command creates a server, /usr/sbin/rmt or /etc/rmt, on the remote machine to access the tape device.
dump and rdump require operator intervention for any of the following conditions:
In addition to alerting all operators implied by the n option, dump and rdump interact with the control terminal operator by posing questions requiring yes or no answers when it can no longer proceed or if something is grossly wrong.
Since making a full dump involves considerable time and effort, dump and rdump each establish a checkpoint at the start of each tape volume. If, for any reason, writing that volume fails, dump and rdump will, with operator permission, restart from the checkpoint after the old tape has been rewound and removed and a new tape has been mounted.
dump and rdump periodically report information to the operator, including typically low estimates of the number of blocks to write, the number of tapes it will require, the time needed for completion, and the time remaining until tape change. The output is verbose to inform other users that the terminal controlling dump and rdump is busy and will be for some time.
Access Control Lists (ACLs)
The optional entries of a file's access control list (ACL) are not backed up with dump and rdump. Instead, the file's permission bits are backed up and any information contained in its optional ACL entries is lost (see acl(5)).
In the following example, assume that the file system /mnt is to be attached to the file tree at the root directory, (/). This example causes the entire file system (/mnt) to be dumped on /dev/rmt/c0t0d0BEST and specifies that the density of the tape is 6250 BPI.
dump will not backup a file system containing large files.
Tapes created from file systems containing files with UID/GIDs greater than 60,000 will have a new magic number in the header to prevent older versions of restore(1M) from incorrectly restoring ownerships for these files.