Metric data

You can estimate the space that is required to back up the working metric data.

In process metric data

The space that is required to back up the working metric data is relative to the total size of all working tablespaces, plus the most recently loaded non-working metric tablespaces. Working metric data tablespaces end with 0000000000. The size of these tablespaces depends on the following:
  • The size of your network
  • The frequency of collection
  • The number of collected metrics
  • The way your data and data remerge windows are grouped
An estimate of this volume can be obtained from Tivoli® Netcool® Performance Manager when you have an accurate estimate of your collection volumes. Assuming a nightly backup, you need this space for each backup you want to retain.

READ ONLY Metric Data

Oracle
You can save a significant amount of space by selecting a particular backup method. A traditional backup method backs up the entire database regularly, and retains a week or two of these backups on tape. As READ ONLY tablespaces are used, these tablespaces require a single backup after they are placed into READ ONLY mode (assuming you are using the traditional Tivoli Netcool Performance Manager backup method). Therefore, the total space that is required to back up the READ ONLY metric data is equal to the total size of these tablespaces. An estimate of this volume can be obtained from Tivoli Netcool Performance Manager after you have an accurate estimate of your collection volumes. The amount of space that is required during each nightly backup is relatively small, as only the tablespaces that were most recently loaded need to be backed up.

If you use the alternative Tivoli Netcool Performance Manager backup method, the space requirements for READ ONLY metric data is slightly higher than the traditional Tivoli Netcool Performance Manager method. The total requirements depend on how frequently you perform a reset and backup.