TMF Reference Manual (G06.26+)
TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-153
DUMP FILES
BLOCKSIZE { 4 | 8 | 12 | 16 | 20 | 24 | 28 | 32 | 36
| 40 | 44 | 48 | 52}
for dumps to tape, sets the tape data block length, when multiplied by 1024 bytes.
It is more efficient to use large data block lengths, but this is limited by the density
in bits per inch (bpi) at which the tape drive writes tapes. The default is 8.
A BLOCKSIZE of 52 is recommended for a density of 6250 bpi or for streaming.
If you specify a BLOCKSIZE value larger than 28, but the tape drive selected
cannot handle data blocks this long, TMF uses a block size of 28 KB for the dump
and generates a warning message.
COPIES { 1 | 2 } [PARALLEL]
for dumps to tape, specifies the number of copies made of each online dump. If
you set COPIES to 1, only one tape drive is required and the copy is directed to
that drive. If you set COPIES to 2, two tape drives are required and the copies are
always produced in parallel, not in serial order, regardless of whether you enter the
PARALLEL option. When producing two copies:
•
If you specify only one node name in the SYSTEM parameter, TMF produces
the two copies in parallel, using two tape drives on that node.
•
If you specify two node names in the SYSTEM parameter, TMF produces the
two copies in parallel, using one tape drive on each node.
COPIES 2 is recommended in case one tape cannot be read because of a tape
media failure or if each copy of the dump requires multiple tape volumes.
The default for this parameter is COPIES 1.
DISKMEDIA
for dumps to disk, identifies the disk volume on which the online dumps are
recorded. At least one disk must be specified. The maximum number of disks
allowed is 16, each specified in any of the following formats:
remote-node.volume.prefix
local-node.volume.prefix
local-node.volume
volume
volume.prefix
prefix is a sequence of two alphabetic characters, to which TMF appends a 6-
digit integer to name the online dump.
If you specify a list of disks, TMF tries to send the online dump to the first disk
listed. If that disk cannot be accessed or is out of space, TMF tries the next disk,
and so forth.
The optional and required syntax items for disk and the naming conventions for
prefix depend on whether the specified disk is on a remote or local node.