--- title: "Create a purge events server task best practice" slug: "create-a-purge-events-server-task-best-practice" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:45:37Z published: 2026-09-07T17:45:37Z canonical: "docs.trellix.com/create-a-purge-events-server-task-best-practice" --- > ## 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. # Create a purge events server task best practice Create an automated server task that deletes all events in the database that are older and no longer needed. > [!NOTE] > Note > > Some organizations have specific event retention policies or reporting requirements. Make sure that your purge event settings conform to those policies. For details about product features, usage, and best practices, click ? or Help. 1. To open the **Server Task Builder** dialog box, select **Menu** → **Automation** → **Server Tasks**, then click **Actions** → **New Task**. 2. Type a name for the task, for example `Delete client events`, add a description, then click **Next**. 3. On the **Actions** tab, configure these actions from the list: - **Purge Audit Log** — Purge after 6 months. - **Purge Client Events** — Purge after 6 months. - **Purge Server Task Log** — Purge after 6 months. - **Purge Threat Event Log** — Purge every day. - **Purge SiteAdvisor Enterprise Events** — Purge after 10 days. > [!NOTE] > Note > > You can chain the actions all in one task so that you don't have to create multiple tasks. This example purges Web Control events because they are not included in the normal events table and require their own purge task. The Web Control events are retained for only 10 days because they collect all URLs visited by managed systems. These events can save a large amount of data in environments with more than 10,000 systems. Therefore, this data is saved for a much shorter time compared to other event types. 4. Click **Next** and schedule the task to run every day during non-business hours. 5. Click the **Summary** tab, confirm that the server task settings are correct, then click **Save**.