Home > Veritas Storage Foundation™ File System Manual Pages
[-d density] [-f file_name] [-s size] [-t tracks]
[-T time] files-to-dump
vxdump option [argument...] files-to-dump
On most devices, vxdump detects end-of-media and prompts you to change the media if there is insufficient space, so it is not necessary to specify the size of the device. However, if the dump requires multiple tapes and the tapes are to be read using an older version of vxrestore, or if the tape device handles end-of-media in a way that vxdump does not recognize, then you must specify the size of the device using the -B option or combining the -d and -s options.
Up to 32 read errors on the file system are ignored.
Each reel requires a new process; parent processes for reels already written remain until the entire tape is written.
Neither vxdump nor vxrestore work with Storage Checkpoints.
If no options are specified, vxdump assumes -9u, and dumps a default file system to the default device. /dev/rfd0 is the default diskette device.
- number is a single digit in the range [0-9] and indicates the dump level. All files modified since the last date stored in the file /etc/dumpdates for the same file system at a lesser dump level are dumped. So the option -0 dumps the entire file system. If the specified level does not determine a date, the beginning of (UNIX) time is assumed.
- -b block_size
- The vxdump command writes in units of logical record size times block_size. The logical record size is 1024 bytes. The vxdump command uses a blocking factor of 10 for tapes with densities less than 6250 BPI, 32 for tapes with densities of 6250 BPI or greater, and 63 for cartridge tapes by default. This can be overridden by the -b option. The vxrestore command dynamically determines the blocking factor up to the default maximum of 63.
- -B records
- The number of logical records per volume. The vxdump logical record size is 1024 bytes. records can also be specified with a suffix to indicate a unit of measure other than 1024 bytes. You can append a k, m, g, or t to the number to indicate that the value is in kilobytes, megabytes, gigabytes, or terabytes, respectively. This option overrides the calculation of tape size based on length and density.
- Cartridge. Specifies using a cartridge instead of the standard half-inch reel. This sets the density to 1000 BPI and the blocking factor to 63. The length is set to 425 feet. -c is incompatible with the -d option, unless you specify a density of 1000 BPI with that option.
- -d density
- The density of the tape (expressed in BPI) used to calculate the amount of tape used per tape reel. If -s is specified, a default density value of 1600 is assumed for a reel tape.
- -f file_name
- Places the dump on the file file_name instead of the tape. If the name of the file is - (dash), vxdump writes to the standard output. This option can be of the form machine:device to specify a tape device on a remote machine.
- Whenever vxdump requires operator attention, notifies all users in group operator in similar fashion to that described in the wall manual page.
- Specifies /etc/vxdumpdates as the dump record file instead of the VxFS default file /etc/dumpdates.
- -s size
- The size of the dump tape in feet. When the specified size is reached, vxdump waits for reels to be changed. If -d is specified, a default size value of 2300 is assumed for a reel tape.
- -T date
- Uses the specified date as the starting time for the dump instead of the time determined by the /etc/dumpdates file. The format of date is the same as that described in the ctime manual page. -T is useful for automated dump scripts to perform dumps over a specific period of time.
- You can specify -T only for incremental dumps; using -T for a level 0 dump returns an error.
- -T is mutually exclusive with the -u option.
- If you enter an improperly formatted date, -T returns an error message and terminates the dump.
- If the dump completes successfully, -u writes the date when the dump started to the file /etc/dumpdates. This file records a separate date for each file system and each dump level. The format of /etc/dumpdates is user-readable and consists of one free format record per line: file system name, increment level and dump date in ctime format. The file /etc/dumpdates can be edited to change any of the fields if necessary. The -u option is ignored for partial dumps.
- Operates like W, but prints only file systems that need to be dumped.
- For each file system in /etc/dumpdates, prints the most recent dump date and level, indicating which file systems should be dumped. If the -W option is specified, all other options are ignored and vxdump exits immediately.
- end of tape
- end of dump
- tape-write error
- tape-open error
- disk-read error (if errors exceed threshold of 32)
In addition to alerting all operators implied by the -n option, vxdump interacts with the control terminal operator by posing questions requiring yes or no answers when it cannot proceed or if there is a serious problem.
Because making a full dump typically requires considerable time, vxdump establishes a checkpoint at the start of each tape volume. If for any reason writing that volume fails, vxdump, with operator permission, restarts from the checkpoint after the old tape is rewound and removed and a new tape is mounted.
vxdump periodically reports information to the operator, including estimates (typically low) of the number of blocks to write, the number of tapes it requires, time required to complete, and the time remaining until tape change. The output is verbose to inform other users that the terminal controlling vxdump is busy and will be for a long period of time.
- Files larger than 2 GB cannot be restored by earlier versions of vxrestore. If a file larger than 2 GB is encountered, an older vxrestore skips the file and returns the message:
Resync restore, skippednumblocks
- Files larger than 2 GB cannot be restored on a file system that does not support large files (see mount_vxfs(1M)).
- A file with a large (greater than 65535) user ID or group ID cannot be restored correctly on a file system that does not support large IDs. Instead, the owner and group of the invoking vxrestore is substituted.
- Files with VxFS extent attributes (see the setext(1) manual page) cannot be restored on a file system of a type that does not support extent attributes.
If you use vxdump to produce a dump intended for an earlier version of vxrestore, and if the dump requires multiple tapes, use the -s, -d, or -B option.
Dumps produced by older versions of vxdump can be read by the current version of vxrestore.
In this example, the entire file system (/mnt) is dumped on /dev/vx/dsk/rvol00 and the size of the tape is two gigabytes.
vxdump -0 -B 2g -f /dev/vx/dsk/rvol00 /mnt
Specifying the tape size in logical records:
vxdump 0Bf 2097152 /dev/vx/dsk/rvol00 /mnt
The option argument 2097152 goes with the option letter B as it is the first option letter that requires an option argument. The option argument /dev/vx/dsk/rvol00 goes with the option f as it is the second option letter that requires an option argument.
Last updated: 01 April 2006
Copyright ©2009 Symantec Corporation
All rights reserved.