> 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/backups-an-overview.md). # Backup overview Schedule, create, and restore Command Centre configuration backups. A **backup** is a copy of the `CCFTCentral` SQL database. Backups can run on a schedule or be done manually from Command Centre. *** ## Why every site should back up All configuration, cardholders, and other important information is held in `CCFTCentral`. If anything happens to the SQL database (corruption), the physical server (hardware failure), or the configuration (operator error), that information can be lost and unrecoverable. If that happens, the site has only two options: * Restore the last known backup, or * Configure the site from scratch. Auto-backups should be set up on all sites, to a safe and secure location, ideally **not** on the same server. *** ## How to take a backup 1. In Command Centre, go to **File > Backups**. 2. Specify a location for the backup file. 3. Either set up a schedule or perform a manual backup. *** ## What is in a backup file The backup file contains information from the `CCFTCentral` database. **The contents cannot be viewed unless restored to the database the backup came from, using the same license file.** ### Backup file naming ``` [Specified Name]_[Date].FTBackup ``` *** ## How to restore a backup There are a few ways to restore an `.FTBackup` to a SQL database: * Double-click the file when it is on the server. * Use the **Backup Restore Utility**. * Use the **CCFT Service Manager Utility**. > **Note:** When the SQL server is remote, backups initiated from a Command Centre workstation and in-Command-Centre restores do not work. See the remote-SQL limitations in [Databases - An Overview of Command Centre and SQL](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr.md). > **Note:** Backups cannot be restored from user-specific folders (Desktop, My Documents, Downloads) or other restricted locations such as the root of the C: drive. See [Databases - Detaching and Reattaching](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-detaching-and-reattaching.md). *** 🔗 **Related** * [Archiving - An Overview](/knowledge-hub/products/cc-software/configure/archiving-and-backups/archiving-an-overview.md). The other half of database safety: keeping the event database in size. * [Databases - Detaching and Reattaching](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-detaching-and-reattaching.md). Backup file behaviour and restore restrictions. * [Command Centre - Errors - Backup Not Working](/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/command-centre-errors-backup-not-worki.md). Fixing backup failures after a server rename. --- # 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/backups-an-overview.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.