Diagnostics database archiving guide

 

SASPROVDB

 

 

5553 kB

 

 

 

 

 

 

 

 

SASPROVARCHDB

 

 

5464 kB

 

 

 

 

 

 

 

 

FCPROVDB

 

 

5553 kB

 

FCPROVARCHDB

 

 

5464 kB

 

 

 

 

 

 

 

 

DISKPROVDB

 

 

5553 kB

 

DISKPROVARCHDB

 

 

5464 kB

 

 

 

 

 

 

 

 

Total Disk Space

 

 

 

44068 kB

 

 

occupied

 

 

 

(IO Providers)

 

 

 

 

 

 

 

 

Note: Often the name of the DB i.e., postgres is confused with the postgres DBMS which is software for storing the data using the relational model. In this document, the convention followed is the term postgres will be used to specify the name of the s/w and not the DB.

The actual size occupied by these database can be found on the system by listing the size of the data directory /var/opt/psb/db/pgsql/base ( for IA) or /var/opt/sfmdb/pgsql/base (for PA).

Size of database on a system without IO Providers

du -sk /var/opt/psb/db/pgsql/base 76864 kB

Size of database on a system with IO Providers

du -sk /var/opt/psb/db/pgsql/base 122248 kB

Note: The sizes specified above for the DBs are only the approximate values and should not be considered as exact values.

The path /var/opt/psb/db/pgsql (IA) or /var/opt/sfmdb/pgsql (PA) are the reference paths for the postgres for its data directories. It is configured during the installation of the diagnostic products. There is no provision to changes or re-configure this path during the installation. Any attempt to change this path later or during the installation can break the product functionality and may lead to unexpected errors in the installation.

Data storage using Database in diagnostic Products

In the typical postgres database, all the data is stored in the data directory. Database internally stores data in the pages. The typical page size is 8kB.

How the DB size growth is maintained

The SysFaultMgmt uses archiving mechanism to limit the growth of its databases. The archiving mechanism ensures DB sizes are maintained to configurable limits. Based on archiving policies, data is moved from the current DB to archive DB. Data from archive DB is further pruned based on the configuration.

The two policies used for transferring data from current DB to archive DB are:

1.Age policy

2.Space policy

Age Policy

The value for this policy can be configured using configuration file DBConfig.xml. For more info on DBConfig.xml

and its parameters, see Configurable parameters of DBConfig.xml.

4