> 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/configuration-client/site-management/archives-backups-and-restores/understanding-archives-backups-and-restores.md).

# Understanding Archives, Backups and Restores

### Archives

Every [*event*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#event) that appears in the Event window gets logged in the Event database (CCFTEvent). As a way of keeping the size of the Event database down, the Archiver manipulates the data in the Event database and stores it in a number of files, (i.e. one per day), in the location the user specified. After an archive, events from the period specified are removed from the Events database.

The archived data is restored when an operator runs an Activity report that covers a period in which the data only resides in archive files, otherwise the data is retrieved from the Event database.

The Archiver has three main responsibilities:

1. Copy and/or move activity from the online database into external files.
2. Recover space by removing archived activity from the online database.
3. Retrieve archived activity from external files when needed for a report.

**Notes:**

* If an Archive and Backup are required, perform the Archive before the Backup.
* Because reporting from archived data can be slow, it is recommended that you keep data on which you want to report within the event database, and only archive the data which you do not report on regularly.

### Backups/Restores

The Backup/Restore process records the state of the sites setup (CCFTCentral) at a single point in time, (i.e. when the backup is launched). After a backup, the system will behave as normal and a restore should only be required if something happens to your system.

**Backups:**

You can backup the systems working data to a file. The system can be backed up while it is online and operators are logged in.

**Restores:**

You can restore the working system from a backup file record.

### Archive List Window

The **Archive** List Window opens in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md).

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5f17e4e12a3a6096ff4832b322980719ac22da26%2Farchivesmlw.png?alt=media)

This window displays the status of an archive. If an archive is running, then it displays the percentage complete. If the last archive was stopped or failed, or the archive cannot start, then it displays the reason, otherwise it displays nothing.


---

# 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/configuration-client/site-management/archives-backups-and-restores/understanding-archives-backups-and-restores.md?ask=<question>&goal=<user_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.
