--- title: "Database maintenance best practices" slug: "database-maintenance-best-practices-2" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-09-06T12:33:27Z published: 2026-10-05T15:41:20Z canonical: "docs.trellix.com/database-maintenance-best-practices-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Database maintenance best practices 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. > [!NOTE] > 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. > [!NOTE] > Tip > > During tuning, the SQL query might return empty results. If this occurs, simply retry the query once the tuning is complete. - Make a regular practice of defragmenting the disk of the Manager server, as disk fragmentation can lead to database inefficiency. > [!NOTE] > 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.