Diagnostics database archiving guide

Diagnostics database archiving guide
3
Database background in Diagnostics Products
The diagnostics products such as SysFaultMgmt and IOProviders uses database (Postgres 8.4.8) for storing and
processing data related to events (error logs, WBEM events, etc.).
All the data pertaining to these products are stored in database tables created during the product installation.
The list of databases used by the diagnostics products are given below:-
Product Name
User DB Name
DB Purpose
SysFaultMgmt
LOGDB
Current DB
LOGARCHDB
History DB
evweb
Current DB
evweb_history
History DB
ProviderSvcsBase
cer
Lookup DB
IO Providers
DISKPROVDB
Current DB
DISKPROVARCHDB
History DB
FCPROVDB
Current DB
FCPROVARCHDB
History DB
RAIDSAPROVARCHDB
History DB
RAIDSAPROVDB
Current DB
SASPROVDB
Current DB
SASPROVARCHDB
History DB
Apart from the above mentioned databases, there are three other databases, namely template1, template0 and
postgres which gets created during product installation. These are default reference databases used by Postgres
for its internal purposes. The size of these default databases remains constant throughout. ProviderSvcsBase (It
is a pre-requisite for SysFaultMgmt and IOProviders) is also responsible for creating a lookup database for the
events. This database is known as “cer” database. The size of the cer database is approximately 36 MB. No data
gets added to this database and its size remains constant
Upon fresh installation of the SysFaultMgmt, the size of the disk occupied by these databases is approximately 75
MB.
DB Name
DB Size
template1
5384 kB
template0
5384 kB
postgres
5384 kB
cer
36 MB
evweb
6185 kB
evweb_history
6088 kB
LOGDB
5697 kB
LOGARCHDB
5545 kB
Total Disk Space
occupied
76531 kB
(SysFaultMgmt+ProviderSvcsBase)
RAIDSAPROVDB
5553 kB
RAIDSAPROVARCHDB
5464 kB