Managing Databases › Time Series Facility Database › TSF Database Recommendations

TSF Database Recommendations

Given that each site and configuration can vary significantly, use the following examples as a general reference as you plan your TSF database sizing activities. Each example includes the key variables to consider when sizing the database for your CA Chorus discipline.

These examples assume that you are using default settings for metrics management. If you lengthen the retention period, the database should be larger and vice versa. For more details, see metrics management settings.

As you review each example, consider the following points:

• G04 receives all data feeds.
• Data moves from the G04 area to the larger G03 area on an hourly basis.
• Metrics management runs nightly to manage G03.

In general, G04 is about half the size of G03. To retain data longer using Metric Management parameters, increase the size of G03. To capture more data (for example, from many LPARs), increase the size of G03 and G04.

CA Chorus for DB2 Database Management TSF Database Recommendations

This example uses the following CA Chorus for DB2 Database Management default metric management parameters:

• MMT1EXPIRY = 1D = 1 day
• MMT2EXPIRY = 3M = 3 Months

The following estimates are based on a given model size for a DB2 subsystem. Consider the size of each DB2 subsystem in your environment and total these together to arrive at the recommended cylinder requirement.

Example Environment

Total Recommended Cylinders: 11086

CA Chorus Infrastructure Management for Networks and Systems TSF Database Recommendations

CICS

This example uses the following Infrastructure Management default metric management parameters:

• MMT1EXPIRY = 7D = 7 days
• MMT2EXPIRY = 8D = 8 days

Given the following Infrastructure Management CICS TSF feeds:

IMS

This example uses the following Infrastructure Management default metric management parameters:

• MMT1EXPIRY = 7D = 7 days
• MMT2EXPIRY = 8D = 8 days

Given the following Infrastructure Management IMS TSF feeds:

CA NetMaster NM for TCP/IP

This example uses the following Infrastructure Management default metric management parameters:

• MMT1EXPIRY = 7D = 7 days
• MMT2EXPIRY = 8D = 8 days

The database size calculations for the other Infrastructure Management components adequately support the data provided by the NetMaster TSF feeds.

MVS

This example uses the following Infrastructure Management default metric management parameters:

• MMT1EXPIRY = 7D = 7 days
• MMT2EXPIRY = 8D = 8 days

This example also assumes that the default CA SYSVIEW TSF feed configuration where channel and device feeds are turned off.

Given the following Infrastructure Management MVS TSF feeds:

If TSF device monitoring is turned on, add the following space recommendations to the initial MVS recommendation:

If TSF channel monitoring is turned on, add the following space recommendations to the initial MVS recommendation:

WEBMQ

This example uses the following Infrastructure Management default metric management parameters:

• MMT1EXPIRY = 7D = 7 days
• MMT2EXPIRY = 8D = 8 days

Given the following Infrastructure Management WEBMQ TSF feeds:

CA Chorus for Security and Compliance Management TSF Database Recommendations

The following chart uses the following TSFPARMS (member of CETJOPTN) metric management tier parameters:

• MMT1EXPIRY = 1D = 1 day
• MMT2EXPIRY = 14D = 14 days

The following chart is based on the statistics interval value taken from the security products parameter: CHORUSSTATI

If your security product collects statistical data for Command Propagation Facility (CPF) nodes, this chart also provides recommended values for up to five CPF nodes.

The following chart uses the following TSFPARMS (member of CETJOPTN) metric management tier parameters:

• MMT1EXPIRY = 7D = 7 days
• MMT2EXPIRY = 8D = 8 days

The chart is based on the statistics interval value taken from the security products parameter: CHORUSSTATI

If your security product collects statistical data for Command Propagation Facility (CPF) nodes, this chart also provides recommended values for up to five CPF nodes.

CA Chorus for Storage Management TSF Database Recommendations

Using the following storage discipline objects and Intervals Per Day examples, we recommend 7,957,846 KB (approximately 141 cylinders) for your TSF database. Review your PERFOM_EVT_PROC=INTERVAL= statement in each CA Vantage SRM logging script to determine how many Intervals Per Day are occurring and the cylinders required for growth.

For the Storage Management TSF parameters, this tier is set where MMT1EXPIRY = 14D = 14 days.