System requirements
| Read first: Synconix Backup Manager (SBM) uses separate machines for each role. You need at least two servers: one Panel (fresh/empty VPS) and one Storage server. Your Production servers are existing machines and must NOT host the Panel or Storage role. | ||
|---|---|---|
| Role | Separate server? | Purpose / Notes |
| Panel (SBM) | Yes — dedicated | Install on a fresh/empty VPS. Hosts the web UI and orchestrates backups. Do not combine with Storage or Production roles. |
| Storage server | Yes — dedicated | Where backups are saved. At least one required; you can add more for capacity or redundancy. |
| Production servers | No (existing hosts) | Your live servers being backed up. Never install the Panel or Storage role here. |
Topology at a glance
[You] → [SBM Panel — fresh VPS] ── SSH ── [Production servers] (pull backups)
└── SSH ── [Storage server(s)] (push backups)Minimum setup (2 servers)
- 1× SBM Panel — dedicated, fresh VPS for the web UI and orchestration.
- 1× Storage server — dedicated host where backups are saved.
Role requirements
1) SBM Panel (must be on its own fresh server)
- OS: RHEL 7.x or 8.x (or compatible).
- SELinux disabled.
- Resources: 2 CPU, 2 GB RAM, 20 GB free on
/. - Network: SSH reachability to Production (pull data) and to Storage (push backups).
- Do not install the Panel on a production or storage server. It must be fresh/empty.
2) Storage server(s) (each is a separate host)
- OS: RHEL 7/8/9, Ubuntu, or Debian.
- SELinux disabled.
- SSH access from the Panel so SBM can write backups.
- Plan capacity according to your retention/rotation strategy.
3) Production server(s) (what you back up)
- OS: RHEL/CentOS/AlmaLinux 6/7/8/9, Ubuntu, Debian, Fedora.
- Control panels supported: cPanel/WHM, Plesk, DirectAdmin, or plain Linux.
- Must be reachable over SSH from the Panel (and from Storage if your topology requires it).
- Do not install the Panel or Storage role here.
DNS & SSL (Panel)
- Create a DNS A record for the Panel hostname pointing to the Panel server’s public IP before install.
- Used to automatically issue the SSL certificate during installation.
- Example:
synconix.yourdomain.com → 203.0.113.10(replace with your Panel server’s IP).
Network note
All connectivity is over SSH. Ensure firewalls allow SSH between Panel ↔ Production and Panel ↔ Storage according to your layout. Internal-only links are fine if hosts can reach what they need.
Quick preflight checklist
☐ Panel VPS ready (RHEL 7/8), fresh/empty, SELinux disabled, 2 CPU / 2 GB RAM / 20 GB on /.
☐ DNS A record set for the Panel hostname; resolves publicly to the Panel server.
☐ Storage server provisioned (separate host), reachable via SSH from the Panel; enough free space.
☐ Production servers reachable via SSH from the Panel (and from Storage if required by your topology).
☐ Firewalls updated to allow necessary SSH paths.