Disk space
Configure monitoring of disk space availability on all nodes and database servers and set alerts when the disk space falls below a certain level.
As historical data is gathered in Bravura Security Fabric , the backend database will continually grow. The disk location where MSSQL stores its files has to be at least 50% empty at all times. If the server is not provisioned based on requirements, allocated space will have to be periodically increased by database administrators. See Server requirements for the requirement details.
Bravura Security Fabric has a health check feature , which monitors the C: drive and sends notifications. If the backend MSSQL database is installed on the same server, with its file on a different drive, the health check can be configured to monitor that other drive.
However, if the database files are on a different server, and the drive where the files are cannot be mapped to the Bravura Security Fabric node for the health check to be used, other tools will have to be used to alert Bravura Security Fabric admins of the impending out-of-space situation.
Whether replication is configured or not, the application node’s iddb.cfg file contains a setting that will stop all database-related application processes if available disk space drops under a certain level. It is recommended not to manually modify the config file, but in some cases it may be required.
The default level of "max_disk_space_percentage is 90%. When the available disk space reaches 10% of the total disk space, the application will stop working.
For very large disks, that setting is too small; for example, 10% of 1TB is 100GB. In extreme cases, the 90% value can be increased as long as the available free space is still more than the size of the database files as mentioned above.
The iddb.cfg records the max percentage the database service will still work, while the healthcheck MIN_PERCENT_FREE setting is the opposite. When increasing the setting in iddb.cfg (for example to 95), decrease the one in healthcheck (for that example, to 5).
If the instance is replicated, that setting can be configured in the WebUI in the nodes Configuration tab under Manage the system > Maintenance > Database replication .
The transaction file itself can grow daily to more than the size of the database itself.