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

# Restoring Archives

### Introduction

Most of the archive configuration also applies to the restore. The archive paths are also restore paths, and the same user account will be used to access restore paths on network shares. The only restore-specific property is the additional restore path on the **Paths** tab. This allows a site to specify another path that is searched for archive files.

Restores are started automatically whenever an event requires activity that has been archived and removed from the Event database.

***

### Procedure

1. Click **Report** from the menu bar, then **Report Descriptions**.

   The **Report Description** 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. **Right click** and select **New\...Activity Report**.

   The first screen ('Reporting Dates and Times' screen) of the wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cc3b43b516785a34965b536ca28a6e5852570431%2Farchiverpt.png?alt=media)
3. Specify the report period as appropriate for the archive you wish to restore.
4. Step through each of the wizard screens, following the instructions displayed and clicking the **Next** and **Back** buttons.

   When the report generates, (i.e. after you click the **Next** button on the 'Report Generation and Saving' screen), a dialog box displays.
5. Enter the location of the archive files for that period, and click the **OK** button.

### Result

The events are loaded into the Restored database (CCFTRestored) and are included if they are relevant, then deleted after the report is generated to maintain free disk space.

**Note:** If the restorer can not find an archive file in any of the restore paths, the following screen displays:

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

You have several options, as follows:

1. Retry the operation by clicking the **Retry** button.
2. Specify a new restore location.
3. Skip the missing file by clicking the **Skip** button.

   The Restorer will add a missing file entry to the report output and will move on to the next file.
4. Skip all missing files by clicking the **Skip All** button.

   This has the same result as clicking the Skip button for this file and all subsequent missing files.

   If there is more than one server with missing files, then you may be presented with several **Restorer waiting for media location** screens, (i.e. one for each server).

***

### Hint

{% hint style="info" %}
**Stopping a Restore**

A restore can be stopped by cancelling the search which initiated the restore, (e.g. by cancelling the report or stopping the Find Tool).
{% endhint %}

{% hint style="info" %}
**Restoring from a remote workstation**

If you are a user on a remote workstation, (i.e. in a different city to the server), a number of scenarios may occur when you try to restore the archive by running an Activity Report.

Take the appropriate action indicated below:

<table><thead><tr><th width="240">If...</th><th>then...</th></tr></thead><tbody><tr><td>at report generation you receive a request for an archive file</td><td>contact the system administrator where the server is, to get them to place the archive files in the server PC.</td></tr><tr><td>the files are on DVD</td><td>type in the DVD drive letter.</td></tr><tr><td>the files are on a network drive</td><td>specify the drive letter of the mapped network drive.<br><br><strong>Note:</strong><br>All paths are referenced from the Command Centre server PC and not the workstation PC.</td></tr></tbody></table>
{% 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/restoring-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.
