Trellix recommends the following best practices for database backup and tuning:
Perform regular manual backups of your database using the Backup feature in the Manager software. Your configuration tables are saved by default once a week on Sunday.
Database backups are cumulative and the size of a backup file can become quite large. Perform regular file maintenance to prevent disk space issues.
Caution
A database left untuned can lead to performance issues over time.
Online database tuning operation causes the creation of temporary alerts and packet log tables; if you are using an agent that queries the database, your agent may attempt to interact with these tables during tuning.
Tip
During tuning, the SQL query might return empty results. If this occurs, simply retry the query once the tuning is complete.
Further information on the impact of online database tuning of the Manager database will be sent to the third-party vendors that are directly accessing this database. If you have any specific questions, contact Technical Support. Also note that there is no change in database SQL query behavior if online database tuning is disabled.
Make a regular practice of defragmenting the disk of the Manager server, as disk fragmentation can lead to database inefficiency.
Tip
Ensure at any point of time the free space available in the database directory is at least one and a half times that of the maximum size occupied by a table (generally Event Tables and Trend Tables).
When scheduling certain Manager actions (backups, file maintenance, archives, database tuning), set a time for each that is unique and is a minimum of an hour after/before other scheduled actions. Do not run scheduled actions concurrently.
While a database crash in the Manager is an uncommon occurrence, it can be triggered by various factors and may lead to sudden unavailability of its critical operations. You must restart the Manager and its database services to restore proper functionality of the Manager application.