---
title: "Backup of Decisions Database and File System"
slug: "backup-of-decisions-database-and-file-system"
description: "This document shows how to backup the Decisions database and file system. Users should back up their database to prevent instances of data loss. "
updated: 2024-06-25T12:19:35Z
published: 2024-06-25T12:19:35Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Backup of Decisions Database and File System

## Overview

In instances that involve any update or alteration to an installation, it is important to backup all **Flows, Forms, Portal settings**, etc that are stored within the **Decisions Databas****e**to avoid data loss. Doing so ensures that all files can be accessed in the event of potential errors that may occur during installation, such as a database overwrite, and offers a point of restoration for the database. The following document demonstrates how to back up an **MS SQL-based** **Decisions****Database**, as well as any applicable or desired **Settings**, **Modules**, and **Encryption****Files**.

Warning!This backup process can only be performed on **Microsoft****SQL**(MS SQL) databases. 

---

## Backing up Decisions Database

1. From the Local File System, Open **Microsoft** **SQL Server Management**.
2. Enter the **Login**and **Password**for the Server and click **Connect**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2020-02-10_13h49_52(1).png)
3. From the **Object****Explorer**on the left, navigate to **Databases > [NAME OF DATABASE]**. Then, right-click the **Database**and select **Tasks > Back Up**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-03-29_13h43_26.png)
4. From the **Back****Up****Database**window, under **Source**, select a **Backup****type**from the dropdown menu. Then, under **Destination**, click **Add**and select the desired location for the **Backup**, and click OK. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-03-29_13h49_29.png)

---

## Important Files to Backup

In addition to the **Decisions****Database**, users should also back up the following to ensure that a machine could be rebuilt entirely from **Backups**.

Installer ArchivingIn addition to backing up the suggest files below. as well as the database, the **Decisions****Installer**used to set up the machine should be archived to allow for easy reinstallation in the event of **Disaster****Recovery**.

| Name | Location | Description |
| --- | --- | --- |
| File Storage Files | C:\Program Files\Decisions\FileStorage\* | This contains any files that have been added to the portal such as **File References** (FileData is stored in the Database). If File References were not created, then this folder may be empty. |
| "Keys.dat" File | C:\Program Files\Decisions\Decisions Server\Instances\Control\Keys.dat | This file contains the encryption keys to decrypt any encrypted database values. This file will not exist if users have not created any encrypted data |
| "Settings.xml" File | C:\Program Files\Decisions\Decisions Server\Settings.xml | This file contains low-level settings about the server like connection string to the database, base URL to the portal, enabled logging levels. |
| Modules Files | C:\Program Files\Decisions\Decisions Server\modules\* | This folder should be backed up if users have created any custom modules but do not need to be if users are only using built-in modules from Decisions. |

---

For further information on Administration, visit the [Decisions Forum](https://community.decisions.com/categories/Administration).