SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Planning Database Security and Recovery
HP NonStop SQL/MX Installation and Management Guide—523723-004
5-17
Using the TMF DUMP FILES Command
Using the TMF DUMP FILES Command
The TMF DUMP FILES command takes a series of Guardian file sets as its arguments.
A file set is an individual file name or a wild card representing multiple files. You can
specify entire SQL/MX schemas, using wild cards of the form DUMP FILES
$*.subvolume.* to specify every Guardian file in the SQL/MX schema whose schema
subvolume is subvolume. You can then use an exclude file list to specify individual
files in the given schema that are not to be dumped. This process can be repeated for
each schema and subvolume combination.
For information about using the MXGNAMES utility with TMF to facilitate use of the
TMF DUMP FILES command, see Appendix B, Using Guardian Names With TMF,
RDF, and Measure.
In situations where large numbers of individual file names are to be included or
excluded, note that:
•
The file set information for a given TMF DUMP FILES command cannot exceed 28
KB in length. If the number of Guardian names to be specified exceeds this limit,
specify them in multiple commands.
•
When specifying individual file names, it is also necessary to specify resource fork
names. TMF does not automatically include or exclude resource forks in an
operation. They must be included or excluded as part of the specified Guardian file
set.
MOVE
(simple move)
Creates a new partition
and deletes the existing
partition, invalidating
online dumps.
Make a new online dump
of the moved partition to
retain TMF file recovery
protection.
REUSE Does not invalidate any
online dumps of the
reused partition.
No action needed.
RESTORE Does not invalidate any
existing online dumps.
Redo the online dumps of
the restored object to
ensure TMF file recovery
protection.
Table 5-1. SQL/MX Operations That Impact TMF Online Dumps (page 2 of 2)
Operation Option Effect Recovery Strategy