> 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-backups.md).

# Restoring Backups

### Introduction

This procedure enables you to restore the working system from a backup file record, therefore a backup must already have been performed. See [Performing Backups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/archives-backups-and-restores/performing-backups.md) for the procedure.

**IMPORTANT:** If you are restoring a backup to another machine you will need the [*Database Recovery Code*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#database-recovery-code), otherwise you will be prevented from restoring your database.

**Notes:**

* If you have performed a backup over the network, the backup should be copied to a non-network drive before restoring. A restore can only be performed on the Server.
* Some of the screen shots in this topic may differ depending on your operating system.
* The procedure below describes one method for restoring backups. Alternatively, you could **double-click** on a backup file OR Restore from the Service Manager Utility.
* The Gallagher Command Centre CA certificate is copied from the Gallagher Database into the Trusted Root certificate store for New Installs, Upgrades and when the Recovery tool is used. The Gallagher Command Centre CA certificate is used for Mobile Client authentication and can be safely removed if the Mobile Client is not utilised on site.

### Procedure

1. From the **Start** menu, click **Programs**, then **Gallagher**.
2. Click **Command Centre Restore**.

   The Restore window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-08d048fe3e7abe5594784636dc94159d5308512f%2Fdbrestore.png?alt=media)
3. Click the **Select File** button.
4. From the displayed pop-up window, path your way to the backup file you wish to use for the restore.

   **Note:**

   The names you entered in the **Backup Set Name** and **Backup Set Description** fields when you performed a backup appear at the bottom of the browse window, allowing you to identify a backup even if the file itself has been renamed.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-95ce5414b37a41423bee304de4d51178f7458c30%2Frestorefile.png?alt=media)
5. Click the **Open** button.

   The file path and name display in the **Restore File** field, and the **Start** button control is enabled.

   The restore utility requires exclusive access to the CCFT Central database and needs to shut down the following FT services to allow this:

   * FT Command Centre Service
   * FT Controller Service
   * FT Bootstrap Protocol Service
   * FT Import - Export Service
   * FT Intercom Service
   * FT Visitor Management Service
6. If ‘Write backup checksums’ was selected when the backup was performed, check the **Verify Checksums** box.

   **Note:** If you check the **Verify Checksums** box and ‘Write backup checksums’ was NOT selected at the time of the backup, an error message will display to indicate the backup file does not contain checksum information. If this occurs, deselecting **Verify Checksums** will let you continue with the restore.
7. Click the **Start** button.

   A message displays indicating that the Services need to be stopped.
8. Click the **Yes** button.

   The Restore starts. When the Restore Progress bar reaches 100% the Restore is complete, and a pop-up message *"The Restore has Completed. Do you want to restart the Command Centre Services?"* displays.
9. Click the **Yes** button.

   Once the FT Services have restarted, another pop-up message *"Restore completed successfully!"* displays.

   **Note:** At the end of the restore the code checks to see if it can work with the database. If it can't (probably due to it being a database backup from another system), the following dialog displays to prompt for the corresponding recovery code (for the source database):

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4900a70dd1d22f947fbad33dbe4e5abd84c74bdc%2Frestore_recoverycode.png?alt=media)
10. Click the **OK** button, then the **Exit** button.

### Result

A restore of a backup file is complete.

### Hint

{% hint style="info" %}
**Restore from Windows Explorer**

An alternative method of restoring a backup is to double-click on the **.FTBackup** file from Windows Explorer on the Server machine.

The Restore window displays, and you complete the previous procedure described, with the exception of selecting the Backup file, as the name is already displayed in the **Database File Location (From)** field.
{% 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-backups.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.
