Platform layout gives you the big picture of how Synconix Backup Manager (SBM) is organized: who signs in, what they can see, and where your servers, schedules, and backup points live. You don’t need SSH to operate the panel—everything below happens from the web UI once installation is complete.

What the platform is

The Panel is the “brain” that connects to your Production servers (what you back up) and your Storage servers (where backups are kept). It sets policies (“schedules”), runs incremental backups, and lets you browse and restore files or databases from point-in-time snapshots (“backup points”).

Main areas in the left menu

• Servers — add/edit the machines you back up. The panel deploys a dedicated system user and SSH keys automatically.
• Storages — add/edit storage nodes (Linux or cloud). You choose the partition/folder that will hold backup points.
• Schedules — create policies for files and/or MySQL: paths, includes/excludes, frequency, retention, compression, and transport.
• Points — browse backup points by server/schedule; preview or download content; start restores.
• Logs — real-time job logs and status (started, completed, warning, error).
• Users & Roles — create users, grant permissions, and scope what servers/storages they can access.
• Settings — URL/SSL, timezone, SMTP, updates, and security allow-list.
• License & Version — add your license, see version tier (stable/release/beta).

User accounts & roles (who can do what)

• Admin at install — at the end of installation, the panel creates the first admin user and a default admin role with full permissions.
• Additional users — go to Users → Add User. You set: full name, company, email, username, role, and which Servers/Storages they’re allowed to see. A random password is generated and shown to you once.
• Roles — roles are permission bundles (e.g., “view schedules”, “run/stop backups”, “restore files/db”, “manage users”, “change settings”). Create roles in Users & Roles → Roles and then assign them to users.
• Access scoping — users can be limited to specific production servers and storage nodes. Their dashboards, schedules, points, and logs are filtered automatically.
• 2FA — users with 2FA enabled must pass a second step on sign-in. Admins can temporarily disable a user’s 2FA when needed.
• Email alerts — per-user notification toggles for started, stopped, completed, warnings, errors, and connection issues. Optional “running over N hours” reminders can be enabled per user.
• Activity log — every sensitive change is recorded (who changed what and when).

Servers (what you back up)

• Add a server with its SSH port; the panel logs in as root once (key-based), creates an internal system user “synconix”, installs utilities, and deploys keys.
• The panel auto-detects control panels (cPanel/WHM, Plesk, DirectAdmin) to enable one-click end-user restore plugins.
• You can reset the SSH access if something changes on the server (the panel will redeploy keys safely).

Storage servers (where backups live)

• Add a Linux storage server via SSH, or configure a Cloud storage target (using rclone config).
• For Linux storages, you choose the destination partition/folder. The panel can use direct SSH transfer or an optimized rsync tunnel mode when enabled.
• Cloud storages keep the same structure, but transfers run via rclone with include/exclude filters.

Schedules (your backup policies)

• Files: pick production server, storage, partition, include paths (e.g., “/” for full) and exclude patterns (logs, caches, archives, etc.). Incremental mode is on by default after the first full run. Optional compression may be enabled.
• Databases: separate options for SQL dumps (storage, partition, DB excludes, host/port/user/password).
• When: cron-style minutes/hours/days/months/weekdays.
• Retention: daily points kept for N days; optional weekly/monthly promotion (e.g., oldest daily → weekly on Mondays; oldest weekly → monthly on day 1).
• Transport: direct SSH or optimized tunnel mode (where the storage exposes a controlled rsync daemon to the production IPs; the panel configures this for you).
• Actions: Run now, Stop, Clone, Install/Remove end-user restore plugins (cPanel/Plesk).

Backup points (what you can restore)

• Each run creates a point (timestamped folder) under the schedule’s path on the storage (or the cloud remote). Files and MySQL points are distinct.
• Browse a point to preview file content, download items, or start a restore. Weekly and monthly points are clearly labeled.
• The panel cleans up according to your retention: oldest daily/weekly/monthly points are flagged and removed automatically.

Restores

• Granular — restore individual files/folders from a point back to the original server path.
• Database — restore specific DB dumps from a chosen point.
• End-user restores — optional cPanel/WHM or Plesk plugin lets customers browse & restore their own backups safely from their panel UI.
• Disaster Recovery — guided flow to rebuild a full server to a new destination using a selected point.

Where things live (paths & structure)

• On storage servers, each schedule stores its points under your chosen partition in a schedule-specific folder (internal ID). Files and MySQL have separate locations.
• On production servers, the panel uses a dedicated “synconix” system user and deploys tools under /opt/synconix/ (no disruption to your apps).
• The Panel’s own database keeps configuration tables for users, roles, servers, storage, schedules, logs, activity, and settings.

Security at a glance

• All data moves over SSH (or over a controlled rsync tunnel you explicitly allow).
• Optional IP allow-list for Panel access (security file).
• 2FA and role-based permissions help keep least-privilege boundaries.
• Email alerts notify the right people when a job starts, completes, or triggers warnings/errors.

Typical flow

1) Add a Storage → 2) Add a Server → 3) Create a Schedule (files and/or MySQL) → 4) Run the first backup → 5) Browse the new point → 6) Test a small restore → 7) Tune retention & alerts.
Repeat for each server you manage.