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

# Performing Backups

### Introduction

SQL Server performs the backups of Command Centre. Therefore in order to get SQL Server to write to the destination you specify, and for the backup to succeed, you have to run the SQL Server service under the account of a user who has permission to do so.

If your workstation is remote, then the path you specify is relative to the SQL Server machine and not your local machine.

### Procedure

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

   By default the **General** tab of the Backup window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f2dba0ef702ccb69a73998b8cd5050b9ffd53c65%2Fbackup1.png?alt=media)
2. Enter the backup destination, (i.e. both the path and the file name), in the **Backup filename and path** field.

   As you begin entering details in this field the **Save Settings** button is enabled.
3. If you require the Backup filename and path to be saved, click the **Save Settings** button.
4. Click the **Options** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-bfaad0109755892f188d8951774192cd065976b1%2Fbackup2.png?alt=media)
5. Check the **Verify Backup upon completion** box if required.

   **Note:**

   Although not required, verifying a backup checks that the backup is intact physically, and that you can rely on your backup in the event you need to use it. Verifying a backup involves:

   * Checking the backup set to ensure that all files have been written.
   * Checking to ensure that the files in the backup are readable.

   Verifying a backup does not check that the structure of the data contained within the backup set is correct. For example, although the backup set may have been written correctly, it may be possible for some type of database integrity problem to be present within the database files that comprise the backup set. To verify the structure of the data before creating a backup, you can perform database consistency checks.
6. Sometimes database integrity problems can occur with the database files that comprise a backup set. To verify the structure of the data, check the **Write backup checksums** box.
7. Type in a Backup Set Name and Description as appropriate.

   <table><thead><tr><th width="186">Field</th><th>Description</th></tr></thead><tbody><tr><td>Backup Set Name</td><td>This identifies a unit of backup work.</td></tr><tr><td>Backup Set Description</td><td>This provides descriptive or identifying text for the result of a backup operation.<br><br><strong>Note:</strong><br>If you type [TIME] in the Backup Set Description field the actual server date and time will replace it when the backup is created.</td></tr></tbody></table>

   **Note:**

   These fields are embedded in the actual.FTBackup file. When browsing for a backup set (.FTBackup file) using the CCFTRestore program, these names and descriptions appear at the bottom of the browse window, allowing a user to identify a backup even if the file itself has been renamed.
8. Do you wish to run the backup now or schedule it on a regular basis?

   <table><thead><tr><th width="186">If you want to...</th><th>then...</th></tr></thead><tbody><tr><td>run the backup now</td><td>Click the <strong>Start Backup</strong> button.<br>The <strong>General</strong> tab re-displays and shows the progress of the backup. When the backup is complete the message "Backup Successful!" displays in the <strong>Server Status</strong> field.<br>Close the Backup window.</td></tr><tr><td>schedule the backup on a regular basis</td><td>go to Step 9.</td></tr></tbody></table>
9. Check the **Schedule Backup** box.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-68356131d36ed53300373eee1993dd81cf7a63fb%2Fbackup3.png?alt=media)
10. Select the 'Start date' for your backup from the calendar, by using the ![Arrows](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-449cf0a566e7f761c66fcd9eb368723141c6f9cf%2Fcalendararrows.png?alt=media) keys to select the month, then clicking on the day of the month.
11. Adjust the time of day you want the backup to occur as appropriate.
12. Click the appropriate radio button for how often you want the backup to occur.

    <table><thead><tr><th width="180">If you select...</th><th>then a backup will occur...</th></tr></thead><tbody><tr><td>Daily</td><td>at the time you indicated each day.</td></tr><tr><td>Weekly</td><td>on the day of the week you selected as the 'Start date' on the calendar, (e.g. in the previous screen example, the 19th August was selected, which is a Monday. Therefore, a backup would always occur on a Monday).</td></tr><tr><td>Monthly</td><td>on the date selected as the 'Start date' on the calendar, (e.g. in the previous screen example, the 19th August was selected, therefore a backup would always occur on the 19th of the month).<br><br><strong>Note:</strong><br>If you select a day which does not occur in every month, (e.g. Day 31), the backup will occur on the final day of those months.</td></tr></tbody></table>

    **Note:**

    The date specified is the first time the backup will occur, (e.g. a day six months in the future could be specified for backups to start). If a date/time that has passed was specified, the backup would take a 'best guess' as to when the backup was intended to occur, (e.g. if the 9th August 2002 was selected with a monthly schedule, and today's date is the 22nd August 2002, then the backup would advance the first backup time to the 9th September 2002).
13. Click the **Validate Destination** button to confirm the path you have entered. An error message will display if you have entered an incorrect file path.
14. Click the **Save Settings** button.
15. Close the Backup window.

### Result

A backup is either run or scheduled to run on a regular basis.


---

# 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-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.
