Synconix Backup Manager ( SBM ) is a self-hosted platform that centralizes all your server backups in one place. You add your production servers and one or more storage servers, set a schedule and retention, and SBM takes care of running fast incremental, encrypted backups you can browse and restore at any time.

What it is

A control panel for backups. It lets you manage multiple machines, policies, and destinations from a single UI, with point-in-time “backup points” you can open like a read-only filesystem to fetch or restore exactly what you need.

Who it’s for

• Hosting providers and sysadmins who need consistent, auditable backups across many servers.
• Agencies/dev teams who want reliable rollbacks and quick file/database restores.
• Anyone replacing ad-hoc scripts with a predictable, secure backup workflow.

What it does (at a glance)

• Adds unlimited production and storage servers under one dashboard.
• Runs incremental jobs after the first full backup for speed and low bandwidth.
• Supports encryption in transit; optional at rest depending on your storage.
• Lets you set include/exclude rules (folders, file patterns) and skip specific MySQL/MariaDB databases if needed.
• Creates browsable backup points—open a point, view folders, preview file contents, and download files.
• Provides quick restores: single files, directories, databases, or full server restores.
• Includes cPanel/WHM full restores and Disaster Recovery flows for fast rebuilds.
• Adds guardrails: 2FA, optional IP-based access, and support for running backups over an isolated network.

How it works (60-second tour)

1) Connect a storage server (where backups live).
2) Add one or more production servers (what you back up).
3) Create a backup job: choose paths/databases, schedule, retention, and excludes.
4) Run the first full backup; subsequent runs are incremental and fast.
5) When you need something back, open a backup point, pick files or databases, and restore or download.

Restore options

• Granular: restore a file/folder exactly as it was at a chosen point in time.
• Database: restore a database dump from the selected backup point.
• Full server: use the guided cPanel/WHM or Disaster Recovery workflows to rebuild quickly.

Security & control

• Optional two-factor authentication for panel access.
• IP restrictions to limit who can sign in.
• Ability to keep backup traffic on a separate network from production.

Key terms

• Production server — the machine being backed up.
• Storage server — where backups are stored.
• Backup job — a policy: what to back up, when, and how long to keep it.
• Backup point — a specific snapshot in time you can browse and restore from.

Before you start

• Make sure your storage server has enough free space for the first full backup plus growth.
• Decide your retention (e.g., daily for 7 days, weekly for 4 weeks, monthly for 6 months).
• List folders/databases to exclude (caches, temp exports, local archives) to keep backups lean.

Next steps

• Add your storage server.
• Connect your first production server.
• Create a backup job and run your first backup.
• Browse the newest backup point and try a small test restore.