- 08 Jan 2021
- 1 Minute to read
Backup of Decisions Database and File System
- Updated on 08 Jan 2021
- 1 Minute to read
In instances certain instances, such as updating or reinstalling Decisions, it is important to backup all Flows, Forms, Portal settings, etc that are stored in the Decisions Database. Users should back up their database to prevent data loss under any circumstance. The following tutorial covers how to back up a Decisions database.
Backing up Decisions Database
- Open MS SQL Server Management.
- Enter the Login and Password for the Server and click Connect.
- Navigate to the Database for backup.
- Right-click and select Tasks > Back Up.
- From the Back Up Database window, under Source, select a Backup type from the dropdown menu.Users are offered the option to either do a Full or a Differential backup.
- Under Destination, click Addand select where the backup will be saved to. Users have to option to select a Disk or a URL source for the Destination.
- Under Destination, click Addand select where the backup will be saved to.
- Click OK.
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.
|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.|