Database management overview
The Entuity database comprises a set of databases, each within their own folder. By default, these folders are held under entuity_home/database/data/.
|yes||contain network management information collected and processed by Entuity.|
|mysql||yes||database users table.|
|flowdb||yes||contains data used with the Entuity Integrated Flow Analyzer.|
|greenit||yes||contains data used for the Green IT Perspective.|
|secdb||yes||contains details of Entuity user accounts, and is referenced when authenticating user logon.|
|udadb||yes||contains details of User Defined Polling.|
|Virtualization||no||database used by Entuity for the initial collection of data from VM platforms.|
|AtriumExport||no||a module specific databases used with Entuity Integration Module for BMC Atrium CMDB.|
|XMLAPIDB||no||part of the XML Data Collector. It receives the queried XML data before it is copied into the main database.|
|no||deprecated or not used in Entuity.|
Note, alongside these database folders is a temp folder, which is used for holding temporary tables. It is not backed up.
The Entuity backup utility backs up the database. It generates zipped backup files in directories under the Data directory.
The Entuity restore utility restores the backed up data.
When to back up data:
You are advised to make a system backup of the installed software and data before:
- running Entuity for the first time.
- reinstalling Entuity.
- reconfiguring Entuity.
- applying a new Entuity patch.
This will ensure that you are up and running more quickly in the event of a file system corruption, or when upgrading Entuity. Further, if you encounter a problem, e.g. a file system corruption, inadvertently deleting data when upgrading, or misapplying a patch, you can quickly revert to the backed up implementation.
Backup can run while Entuity continues to manage the network. By default, provost schedules backup to run daily at 23:00. Please see the section below on running a nightly backup for further help and information.
To perform a full system backup:
To perform a full system backup, you should:
- ensure the Entuity server is not running.
- back up everything included within entuity_home.
- check that the Entuity database is backed up. During configure, you may have installed the database directory somewhere other than entuity_home/database/data.
- back up the configuration and archive configuration file folders, when using Configuration Monitor.
If, during the install or configuration process, you decide to rebuild the database, then all files under entuity_home/database/data are deleted. If you have configured backup to save the database backup tables under that path, then to preserve the backup folders you should move them outside of the Entuity directory tree.
To save on disk space, the Entuity backup utility does not back up those StormWorks objects that are specified (through the StormWorks configuration) as not being part of the backup.
If you are backing up the Entuity database files but not using the Entuity backup utility, e.g. using standard copy-paste commands, then you should stop the Entuity database. Conversely, to use the Entuity backup utility, the database must be running.
Checking the database:
dbcheck is run each time that Entuity starts. dbcheck checks that the databse was previously correctly closed down (for example, a power failure can leave some database tables open).
dbcheck runs before the database starts. If it identifies problems that require repairing, it calls myisamchk.
The time taken to run a full check and repair of the database varies according to the size of the managed network.