HP NonStop G-Series - Manual (Page 126)

Appendix A- 2
5) The DSM/TC database is a SQL Catalog, comprised of SQL tables and
indexes. The BACKUP program will not adequately save any SQL Catalogs
for recovery. A save solution that incorporates Backup and TMFCOM DUMP
FILES to save the system for a full recovery needs to be implemented.
6) If the TMF Dump is chosen as part of the recovery solution, it will be
necessary to add TMF tapes to the TMF database. These are totally separate
from DSM/TC tapes. They do not share. TMF and DSM/TC use $ZSVR to
handle the tape mount/dismount. We suggest labeling these tapes differently
from the DSM/TC tapes.
An example, DSM/TC 000001-000099
TMF TMF001-TMF099
Not all Tandem systems share TMF tapes. Each Tandem host has its own
pool of tapes. This is a ‘feature’ of TMF. Verify the numbering scheme takes
this into account. Below is an example of the Add Tapemedia command:
TMFCOM ADD TAPEMEDIA TMF001, LABEL ON!,
DRIVE $, UNLOAD ON
This command will set the status of the tape to SCRATCH and add it
to the TMF catalog. TMF allows the same RELEASED option as
discussed in #1 for Mediacom. It works the same way. Instead of a
tape going straight to SCRATCH status, it goes into a RELEASED
state, so they can be kept in racks. The status can then be set to
SCRATCH when the tapes are entered into the silo.