> 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/databases-an-overview-of-command-centr/databases-recovering-from-a-dead-serve.md). # Database recovery * How do you recover a site after a server failure? * What if you have the recovery code, and what if you do not? This is a disaster-recovery scenario, distinct from routine maintenance. Provided the hard drive is not the reason the server died, and you can recover the database or backups from the old drive, you can usually get a site running again without too much trouble. *** ## Prerequisites and constraints * From **version 7.70 and above**, you need access to the **recovery code** to get the system running straight away. * When installing the new server, the Channel Partner should change the **IP address and server name to match the old server BEFORE installing Command Centre**. * The new server needs the **same build version or newer**, AND the SQL version needs to be the **same or later** than the original server. *** ## Path 1: new server and you can locate the recovery code 1. Install the new server and apply the appropriate customisations. 2. Restore the backup and apply the recovery code. 3. The system should run without further issues. Afterward: * If the site has **Mobile Client** devices, they must be re-added to the system. * If the site has **Mobile Cloud** configured (Mobile Credentials), the Cloud service must be deleted so it can be recreated on the new server. **Contact Technical Support.** *** ## Path 2: new server and you cannot locate the recovery code This is more complicated, but if you have access to the databases or a recent backup, all is not lost. Note that **customisations on the server** can cause complications and will most likely rule out the Template option. Initial steps: 1. Install the new server, then attempt to restore the backup. When it reaches the point asking for the recovery code, click **Cancel**. This imports the backup but not the recovery code, so the services will not start yet. 2. Run the **FTSupport tool** now: this captures the IP configurations and MACs of the controllers, which you will need to enter later (especially before using the Template option, which wipes them). Then choose one of two options. ### Option 1: Template Utility Use the Template Utility to create a template of the site, then restore that template to the system. This **resets** the following: * Removes all MACs and IP settings from the controller configurations (which is why the FTSupport tool was run earlier). * Removes all operator passwords. * Removes all PINs and CODEs from users. * Resets the System User account back to default (system / blank password). * Resets the MIFARE keys and Enhanced MIFARE site keys. * Resets the DESFire Default AppKey. * Resets the Macro password to the shared folder. * Resets the Archive password to the shared folder. * Resets the Alarm transmitter encryption key. * Resets the EDI passwords. * Resets the RestClient encryption. * Resets the Commend Intercom system. > **Important:** This requires the controllers to have the **DIP Switch 2 procedure** carried out to bring them back online. ### Option 2: Database Anonymiser Utility Use the Database Anonymiser Utility to reset the recovery code to one you can use again. Technical Support holds the step-by-step procedure for resetting the recovery code when the original is lost. *** 🔗 **Related** * [Databases - Setting up Command Centre with remote SQL](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-setting-up-command-centre-wi.md). Rebuilding against a separate SQL server. * [Databases - Detaching and Reattaching](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-detaching-and-reattaching.md). Recovering the database from the old drive. --- # 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/databases-an-overview-of-command-centr/databases-recovering-from-a-dead-serve.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.