The Backup Points pages let you browse, search, and restore content from completed runs. You can open File system points or SQL points, preview text files, and kick off restores to a destination server. Actions shown depend on your role and the server(s) you’re allowed to access.

Picking a schedule & navigating

• Use the top selector to choose a schedule; the page auto-loads its latest points.
• The gray breadcrumb under the info cards shows where you are inside the point. Click folders to drill in / back.
• Two tables are shown side-by-side when both are enabled: Files (left) and SQL (right). Each has a quick search box at the top.

What the rows/icons mean

• items are backup point folders; click to open.
• items are files (text/code can be previewed).
• scheduled_for_deletion_* — retention cleanup is removing this point.
• point.*.in.progress — a run is still writing here.
• Delete on an orphan point removes a stuck, incomplete folder left by an interrupted run.

Storage types & previews

• Linux storage — browsing uses SSH/SSL Tunnel; file sizes/modes/dates are listed. Text files can be opened inline.
• Cloud storage (Drive/Dropbox/S3) — browsing uses rclone; shows folder/file name and modified time. Only text/code is previewable.

Restoring files & folders

Click Restore selected (Files table) to open options:

• Destination server — choose where to restore (only linked servers you can access).
• Overwrite existing — if enabled, changed files are replaced on destination.
• Progress bar — shows a live progress widget; the restore continues in background even if you leave the page.
• Optional path — leave empty to restore to the original path; or set a custom folder.
• Transfer engine: Linux storages use rsync (ACL-aware when available). Cloud storages use rclone copy. All runs execute safely in a detached screen session.

Disaster Recovery (full server)

• Restores the entire system from a single point to a chosen destination server (OS family/version should match).
• Requires a full backup (you must have backed up “/”). Cloud storages do not expose DR in this UI.
• You can add extra excludes (tags field) to skip paths. Operation runs non-interactively and cannot be interrupted.

cPanel account restores

If the source server runs cPanel/WHM, use Restore cPanel/WHM accounts: select users and what to restore (schema/data/mail/SQL). The panel transfers the data and tracks per-account status (queued / running / completed) with a live progress modal. An Abort session button can terminate the active screen session if needed.

Restoring MySQL/MariaDB

On the SQL page (right table):

• Select whole databases or individual tables inside a database folder.
• Choose a destination server.
• Import directly — data is piped into the DB server (overwrites existing rows). Optional “Create DB if doesn’t exist”.
• Export as dumps — writes SQL files to a custom folder on the destination instead of importing.
• The panel validates DB existence (and can create it if you allow) before import. Progress is shown in the banner widget.

Roles & permissions (why some buttons are disabled)

• View points: view_backup_points_page.
• Browse inside points: browse_backup_points.
• Restore files: restore_files_backup.
• Restore cPanel accounts: restore_cpanel_accounts.
• Disaster Recovery: restore_disaster_recovery.
• Restore MySQL: restore_mysql_backup.
If a permission is missing, actions appear grayed out or hidden.

Good to know

• Leaving the page does not stop a restore; jobs run in detached sessions on the storage/destination.
• “scheduled_for_deletion_*” points are retention cleanup; let them finish before restoring from nearby runs.
• Previews are limited to text/code; binaries should be downloaded/restored, not opened inline.
• For DR and big file restores, network speed, CPU, and target disk I/O will dominate runtime.