> 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/performing-archives.md).

# Performing Archives

### Introduction

At least one archive path must be configured before an archive can be started. Archives can be started manually or automatically by setting a schedule. This procedure covers a manual archive. For detail on setting a schedule for an automated archive, refer to [Configuring Archives](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/archives-backups-and-restores/configuring-archives.md).

To perform this procedure you must have the "View Site" and "Backup and Archive" operator privileges. Having these privileges will allow you to run an archive, but you will not be able to configure or alter an archive.

### Procedure

1. Click **File** from the menu bar, then **Archives**.

   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)).
2. Highlight the Archive item you want to run.
3. **Right click** the mouse button.
4. Click **Properties**.

   **Note:** Alternatively, you can click **Start Archive**. While a "percentage complete" figure will display in the "Status" column on the list window, this method does not provide enough detail about the progress of the archive.
5. Click the **Status** tab.

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

   The **Last archive** section of this tab displays the results of the last archive, and the **Current archive** section will remain empty if an archive is not currently running.

   The fields in the **Last archive** section are described below:

   <table><thead><tr><th width="180">Field</th><th>Description</th></tr></thead><tbody><tr><td>Last successful:</td><td>The time the last successful archive started.</td></tr><tr><td>Last attempt:</td><td>The time the last attempted archive started.<br>If the last attempted archive succeeded, this will be the same as 'Last successful'. The result of the last archive attempt will also be displayed, (e.g. 'Success', 'Stopped by operator', 'Insufficient disk space' or 'Server offline').</td></tr></tbody></table>
6. Click the **Start** button to start an archive.

   **Note:** If the **Start** button is disabled, it will be for one of the following reasons:

   * the archive item has not been configured, (i.e. it does not have a server and at least one archive path),
   * an archive is already in progress, or
   * the server is offline.

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

   The progress bar indicates the progress of the archive, and the fields in the **Current archive** section are now populated as described below:

   <table><thead><tr><th width="180">Field</th><th>Description</th></tr></thead><tbody><tr><td>Status:</td><td>Describes what the archiver is currently doing, (e.g. searching for data to archive, compacting database, etc.). This will usually include the day that is currently being archived.</td></tr><tr><td>Started:</td><td>The time the current archive started.</td></tr></tbody></table>

   **Note:**

   Once the archive has completed, it is a good time to perform a Backup, however not absolutely necessary. Refer to [Performing Backups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/archives-backups-and-restores/performing-backups.md) for procedure.

### Result

An Archive is complete, and archive files are stored in the destination(s) specified.

### Hints

{% hint style="info" %}
**Stopping an Archive**

An archive can be stopped while it is running, either by:

* clicking the **Stop** button on the **Status** tab, or by
* right clicking on the Archive in the list window, and clicking **Stop Archive** from the drop-down menu.

When an archive is stopped, any incomplete archive files will be deleted.
{% endhint %}

{% hint style="info" %}
**Archive failures**

If the Archiver is unable to complete an archive for any reason, (e.g. lack of disk space, or SQL Server is shut down), then the archive will stop and the archive files will be removed from the archive file index (if necessary), and deleted. If the archive files cannot be removed from the archive file index then they will not be deleted.
{% endhint %}


---

# 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/performing-archives.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.
