G06.30 Software Installation and Upgrade Guide

Overview of Installing G06.30
G06.30 Software Installation and Upgrade Guide—543764-002
1-51
TMF
Otherwise, you must use the appropriate DP2 (T9053) fallback SPR if you have not
performed a clean TMF shutdown.
You must successfully complete a clean TMF shutdown (with all audited disks up)
before falling back to a prior RVU. This step is particularly important whenever the RVU
you are falling back from supports any new format files or objects or audit records for
them, and the fallback RVU does not.
To establish complete TMF file recovery protection for your SQL/MX metadata tables,
update your TMF online dump (and Backup) scripts to include the names of all
SQL/MX metadata tables, including those that are SQL objects and their resource
forks. The TMFCOM DUMP FILES and RECOVER FILES commands support all the
new SQL/MX metadata tables (using their Guardian names).
TMF Migration Considerations for Format 2 Audit Trails
TMF provides the capability to create much larger audit-trail files with the introduction
of the G06.24 RVU, but TMF must be stopped in a clean state to execute the
TMFCOM command that enables this ability. If audit-trail files greater than 2 GB are
part of the long-term audit-trail configuration strategy, consider altering the audit-trail
format at migration time, given that TMF is already stopped. If not done at this time,
altering the audit-trail configuration to enable format 2 audit-trail files will require a
STOP TMF command at some later date.
TMF Fallback from G06.30
For a complete summary of TMF features, see the Interactive Upgrade Guide 2.
TMF Fallback for Format 2 Files
If you are migrating to G06.30 from G06.24 or later, there are no migration issues. If
you are on a pre-G06.24 RVU and you do not plan to make changes to the TMF audit-
trail configuration, there are no issues related to fallback associated for TMF. However,
if you are on a pre-G06.24 RVU and you do plan to change the audit-trail configuration,
such as altering the file size of a given trail or changing the audit-trail configuration to
use format 2 files, you must understand the fallback issues.
After you execute either the ALTER AUDITTRAIL command with the new FILESIZE
option, or the ALTER TMF command with the new ATFORMAT option, you must then
follow certain fall back steps precisely. For example, if you have to fall back, you might
have to execute a DELETE TMF command if you altered the audit-trail format.
For details related to falling back after using these new TMF command options
introduced in G06.24, see the HP NonStop TMF Reference Manual.
Falling Back from TMF 3.3
If you add one or more auxiliary audit trails while TMF is started, you can fall back only
to G06.24 or a later RVU because the TMF audit reading facilities prior to the G06.24