---
locale: "en"
updated_at: "2025-10-27T11:00:40.985Z"
canonical: "https://www.isdecisions.com/en/userlock/docs/guides/installation/backup-settings-data"
---

# Backup UserLock settings and data

Configuration, logs, customizations, database and license.

## Why and when to back up

A UserLock backup is not only useful before an upgrade, it can save you in many situations.

Creating regular backups helps you:

- **Prepare for a version upgrade.** Before installing a new version, always make a full backup to restore your environment if something goes wrong during the process.
- **Recover from configuration mistakes.** If a policy or MFA setting is changed in error, restoring a previous configuration lets you revert safely.
- **Protect against data loss.** Hardware failure or database corruption can happen at any time. Backups ensure continuity.
- **Audit and troubleshoot issues.** Keeping logs and configuration copies helps analyze unexpected behavior or verify past actions.

Each backup element described below explains **what it contains**, **where to find it**, and **why it’s important**.

## 1. Configuration files

**Path:**
`%ALLUSERSPROFILE%\ISDecisions\UserLock\Config`

Back up all files with the `.cfg` extension.

These files define your **UserLock configuration**, including access policies, MFA settings, and other core parameters.

They are essential to restore your environment exactly as it was before the upgrade.

UserLock also automatically generates **archived configuration backups** in ZIP format (daily, weekly, monthly, and quarterly).
These archives allow you to roll back to an earlier configuration if an error or unwanted change occurs.

> **Tip**
>
> Keep at least the most recent automatic archives before starting an upgrade, as they can help recover from configuration mistakes made prior to the update.

## 2. Logs

**Path:**
`%ALLUSERSPROFILE%\ISDecisions\UserLock\Logs`

These logs record all service activity. 

They are not mandatory for system recovery, but they can help **diagnose problems** or **audit actions** during and after an upgrade.

Retaining them ensures full traceability if an issue occurs.

## 3. Console customizations

**Path:**
`%ALLUSERSPROFILE%\ISDecisions\UserLock\WebData`

This folder includes a **local SQLite database** that stores all **UserLock console customizations**, such as:

- Saved views and filters
- Per-user display options and interface settings

These files allow administrators to recover their personalized console environment after an upgrade.

> **Note**
>
> This backup is particularly important in multi-admin environments, where several users may have customized their views.

### Legacy console options

**Paths:**

- `%ALLUSERSPROFILE%\ISDecisions\UserLock\default.xml`
- `%appdata%\ISDecisions\UserLock\Default.xml` (one per UserLock administrator profile)

These files store settings and display preferences of the **legacy console**, which is no longer updated, but backing up these XML files can help restore settings for administrators still using the older interface.

## 4. Database

The database contains all **session activity history** and **audit data**.

- **If using the default database (UserLock.mdb):**
  `%ALLUSERSPROFILE%\ISDecisions\UserLock\Database`
- **If using Microsoft SQL Server:**
Use your usual SQL backup tool to create a database backup.

This is the most critical element for recovery, without it, UserLock cannot restore historical session or audit information.

## 5. License information

In the **UserLock Server Console**, open⚙ **Server Properties → License**

Copy your **License Key** and other details into a text file.

This ensures you can quickly reactivate UserLock in case of a reinstallation.