--- title: "Performing a full vacuum on the lighthouse database using the CLI" slug: "performing-a-full-vacuum-on-the-lighthouse-database-using-the-cli" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-09-23T17:25:03Z published: 2026-09-23T17:25:03Z canonical: "docs.trellix.com/performing-a-full-vacuum-on-the-lighthouse-database-using-the-cli" --- > ## 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. # Performing a full vacuum on the lighthouse database using the CLI If the Lighthouse database becomes overloaded with data, it can cause performance issues and delays in the Endpoint Security (HX) server. A full vacuum removes bloat from the database to address this performance issue. Use the CLI commands in this topic to perform a full vacuum on the Lighthouse database. Prerequisites - Administrator access To perform a full vacuum on the Lighthouse database: 1. Go to CLI configuration mode: ``` hostname > enable hostname # configure terminal ``` 2. Perform a full vacuum on the Lighthouse database: ``` hostname (config) # hx server db full-vacuum ``` Use the optional `track` parameter to perform a full vacuum in the foreground. Use the optional `no-confirm` parameter to perform a full vacuum without confirmation, for example, to automate a task. 3. Confirm that you want to continue: ``` hostname (config) # yes ``` 4. Verify the status of the full vacuum: ``` hostname (config) # show hx server db full-vacuum status ``` ### Example The following example shows how to perform a full vacuum on the server Lighthouse database, and how to verify the status of the full vacuum. ``` hostname (config) # hx server db full-vacuum ``` ``` This will disable tasking and the web interface while being completed and run in ``` ``` It will be re-enabled after completion. ``` ``` Do you want to continue?. ``` ``` Type 'yes' to confirm: yes ``` ``` Beginning Lighthouse DB vacuum in the background. See logs for output. ``` ``` hostname (config) # show hx server db full-vacuum status ``` ``` Vacuum Status ``` ``` Last Run Info ``` ``` Start Date        : 2021-03-02 17:23:29 ``` ``` End Date          : 2021-03-02 17:23:33 ``` ``` Size before vacuum: 45 MB ``` ``` Size after vacuum : 39 MB ``` ``` State             : vacuum is NOT running. ``` :