Diagnostics database archiving guide

All the events that qualifies the age limits in the configuration are moved from current DB to archive DB. All the events in archive DB that qualifies the age limit gets purged from archive database.

Space policy

The space policy triggers when the actual size of the db (in pages) exceeds the configured size. When actual size of archive DB exceeds the configured size, it gets pruned.

NOTE:

The diagnostics products with Postgres 8.4.8 are fine tuned to call the autovacuum on each of the databases. The autovacuum daemon is tuned to run after every 30 minutes to ensure all the dead pages and tuples are flushed and space is made available. The vacuum operation can also be initiated by restarting the Postgres services.

What happens on archiving?

In case of LOGDB,

1.The events from tables namely rawlog/rawlogdetails are moved to the corresponding tables of the LOGARCHDB if the size of the current DB exceeds the configured size

2.Also the LOGARCHDB is checked for the pages it occupies on the disk. If the pages exceeds configured limits, events are pruned from the LOGARCHDB.

In case of evweb db,

1.The events from tables namely evt_summary_t, evt_prop_t etc. tables are moved to the corresponding tables of the evweb_history db.

2.The evweb_history DB is then checked for the space condition. If the number of pages occupied by the evweb_history DB exceeds configured limits then archiving deletes certain events from the evweb_history DB.

How to trigger Archiving in the Product

To Trigger Archiving in SysFaultMgmt

In SysFaultMgmt, the archiving is triggered periodically by means of the archiving job.

Archiving in evweb/evweb_history database

The archiving in evweb/evweb_history database can be triggered by starting the products by using the following command:

cimprovider -dm SFMProviderModule

(disabling the SFM)

cimprovider -em SFMProviderModule

(enabling the SFM)

 

OR

 

cimserver –s

(stopping the cimserver)

 

cimserver

(starting the cimserver)

 

Once the product is restarted, the job responsible for triggering the archiving in evweb/evweb_history, registers itself as repetitive job, as soon as the first event is inserted in the database. Thereafter, the archiving job is called every 6 hours to check the need of archiving on the evweb/evweb_history.

5