Skip to content
gaporo
Open app
Open app

Backup restore test

How to verify a backup works: pick a successful run, test vs live restore, and confirm the result.

Pick a successful run

Section titled “Pick a successful run”

Restore from successful backup history. Open RMM → Backup & recovery → Restore. Choose a success run — failed runs are not restore sources. The Jobs list shows only the latest run; full history is on the Runs tab. Run cards show status and size — the full Veeam/MSSQL dump is on the run detail.

  1. Open /rmm/backup-recovery?tab=restore (or the Restore tab).
  2. Find the job and a successful run (date, source device, size).
  3. Confirm the backup type supports in-panel restore (some external sources have limits).
  • Test on non-critical data / a lab first.
  • Trial blocks cloud — test restore from local / SMB destinations.

Restore test vs full restore

Section titled “Restore test vs full restore”

A restore test runs a real restore with validation (checksum / structure) as a quality check. Use full / live restore when you truly need production data back.

  • Test = prove the archive can be read and unpacked.
  • Live = put files back where work continues.
  • Do not overwrite production with a test unless the target path is intentional.

Target device and path

Section titled “Target device and path”

Restore to the same device or another (e.g. a new PC). Optionally set a custom path. When finished, check run history: status, target device and file location.

  1. Choose an online target device.
  2. Set a restore path or keep the default.
  3. Start restore / test and wait for success.
  4. On the target PC verify files / archive are present.
  • Target needs an online agent and free disk space.
  • MSSQL (.bak) restores are done in SQL Server, not via the panel ZIP test. Agent staging path: backupPath\<instance>\.
  • RAKS / Firebird (.fbk): on Restore, pick a successful run and Place .fbk files. Windows agent 1.0.343+ writes the files into a folder (for example C:\_restore_test) and decrypts AES when the backup is encrypted. It does not run gbak and does not touch live *.fdb files. Restore the firm in RAKSSQL Administrator → Restore from F00002_arch_yyyy-MM-dd.fbk. Do not choose the Data / Data4 folder.
  • Encrypted backups need the correct password / key.
  • After a Windows reinstall, reconnect the agent first (same hostname), then restore to that device — or to another online PC in the same company.
  • A backup that lived only on the old PC’s local disk cannot be restored to a new machine — you need cloud / SMB / NAS.
  • After a good test, note the last verification date on the device.
Section titled “Related”