TMF Supplement for Large Audit Files (G06.24+)

TMF Planning and Configuration Guide
HP NonStop TMF Supplement for Large Audit-Trail Files—527391-001
3-2
Why Start Over? (Page 1-9)
Why Start Over?
(Page 1-9)
You should delete TMF in a production environment only after careful consideration,
because all audit dumps and online dumps are lost, and new dumps must be taken.
In a development environment where you are testing your application modules, and
perhaps experimenting with a variety of configuration alternatives, you need to delete
the TMF configuration and completely reconfigure it if you want to add or delete audit
trails from your configuration. You may also need to delete the TMF configuration and
completely reconfigure it if you are attempting to fall back from a format 2 audit-trail file
environment to a format 1 audit-trail file environment.
Aspects of the TMF configuration other than the audit-trail file format can be changed
while TMF is running, although some of them do not take effect until you subsequently
stop and restart TMF.
Audit-Trail File Size
(Pages 2-2 through 2-3)
You use the FILESIZE parameter of the ADD AUDITTRAIL or ALTER AUDITTRAIL
commands to specify the desired audit-trail file size.
The minimum recommended file size is 300 megabytes.
The maximum recommended file size is the daily audit generation rate (this gives you
approximately one audit dump per day).
Your service provider can help you estimate the anticipated audit generation rate. This
rate is highly variable depending on your application and data, and you might need to
experiment with your TMF configuration to find the optimal rollover frequency for your
application. If you are running applications that have already been functional under a
previous release of TMF, the audit generation rates from that environment will be close
enough to use in planning for the current TMF environment.
If you are designing new applications, however, you should consult your systems
analysts and application programmers to estimate the following:
1. How many disk writes, typically, would be involved in each transaction
2. How many bytes of data, typically, would be transferred in each disk write
3. How many transactions, typically, would occur during each business hour
Table 3-1
summarizes these guidelines.