> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/archiving-and-backups/server-archiving.md). # Server - archiving [Server Configuration](/knowledge-hub/products/cc-software/configure/server-configuration.md) › Server - Archiving ## This page answers * What does archiving do at the server level? * What is the default archiving period, and why does it matter? * How do you set archiving up? Archiving moves events and alarm history out of the `CCFTEvent` SQL database after a period of time, so the database stays within the size the SQL instance can manage. It can run on a schedule or be done manually from Command Centre. *** ## Why set archiving up on the server Event data is pushed into `CCFTEvent` as the site runs. The default SQL instance installed with Command Centre is SQL Express, which is limited to 10 GB. Once that limit is reached, the system can no longer record events. Setting archiving up while the database is still under the limit keeps it at a size the SQL instance can manage, so the problem never arises. Auto-archiving should be enabled on all sites, especially sites left unattended. ## The 90-day default By default, archiving removes events older than **90 days** from `CCFTEvent`. This is the recommended setting. Leaving events in the database for an extended time makes it large and risks exceeding the SQL Express limit. ## Setting archiving up 1. In Command Centre, go to **File > Archives**. 2. Specify a date up to which events and image sequences are to be archived. The date must precede the date of the oldest unprocessed alarm. 3. Set up a schedule, or run the archive manually. The Archiver creates an archive file for each day, working backwards. Archived events can still be browsed from within Command Centre, though searches through them are slower than through the live database. They are unreadable by any other system and are tamper-resistant. *** 🔗 **Related** * [Archiving - An Overview](/knowledge-hub/products/cc-software/configure/archiving-and-backups/archiving-an-overview.md). Full detail: CRC integrity, archive file naming, and importing orphaned archive files. * [Archiving - Database Information](/knowledge-hub/products/cc-software/configure/archiving-and-backups/archiving-database-information.md). SQL Express size caps. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/archiving-and-backups/server-archiving.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.