# Backup and Restore Overview

**Last Updated On**: 03 Jun 2026  
**5 minutes read**

## Why Backup and Restore Is Important

Endpoint Central server stores critical data in its database and file system. Important configuration files and certificates also reside on the server file system. Hardware failures, disk corruption, or accidental misconfiguration can lead to permanent data loss.

Regular backups help you:

- Recover quickly if something goes wrong
- Restore after a system failure
- Protect important reports and historical data
- Ensure business continuity and disaster recovery readiness

**Warning**

**Important:** It is recommended to store backup files on a different machine or network share to protect against local disk failures.

## How Backup and Restore Works

Each backup consists of **two distinct components** that run sequentially:

| Component | How It Works |
|---|---|
| **File System Backup** | Copies configuration files, certificates, keystores, license files, MDM data, and other server files from the installation directory |
| **Database Backup** | Backs up all relational data (reports, policies, AD data, software inventory, etc.) using a method specific to your database type — see below |

**Warning**

**File system and database must always be in sync.** Both components depend on each other — if one is from a different point in time, the server will fail to start.

- **Only VM Snapshot Revert - Not Recommended.** Rolls back server files but not the remote database, causing an unrecoverable mismatch.
- **Only Remote backup Restore - Not Recommended.** Restores only the remote database without matching application files, certificates, and keys. Server will not start.

Always use the built-in **Backup-Restore Utility** (`backuprestore.bat`) — the only supported method that restores both components together.

## Backup and Restore Methods Summary

Each method is covered in detail below — click any method name to jump directly to its section.

| Method | When It Runs | Who Starts It |
|---|---|---|
| [Scheduled Backup](https://www.manageengine.com/products/desktop-central/help/server/scheduled-data-backup.html) | At your scheduled time (daily) | System (automatic) |
| [Manual Backup](https://www.manageengine.com/products/desktop-central/help/server/manual-data-backup.html) | Whenever you choose | You (administrator) |
| [Restoring Your Backup](https://www.manageengine.com/products/desktop-central/help/server/restore-data-backup.html) | When recovery is needed | You (administrator) |

## Backup and Restore File Format

All backup methods produce a single compressed file named using the format:  
`<buildnumber>-<date>-<time>.7z`

## Backup and Restore Compatibility

A backup can only be restored on the **same build number** and the **same database type** as when the backup was created.

| Requirement | Rule |
|---|---|
| **Build Number** | Must match exactly. A backup from build 11.3.2440.01 can only be restored on build 11.3.2440.01. To restore on a newer build, install the matching version first, restore, then upgrade. |
| **Database Type** | Must match exactly. Bundled PostgreSQL → Bundled PostgreSQL, Remote PostgreSQL → Remote PostgreSQL, MSSQL → MSSQL. Cross-type restore is **not supported**. |
| **Database Version** | Major version must match. For example, PostgreSQL 14 → PostgreSQL 14 (minor version differences are OK). MSSQL 2019 → MSSQL 2019. |

**Warning**

If you plan to switch your database type or upgrade the database version, do so **before** you need to restore. After switching, your older backups will no longer be compatible.