Operate

Verify a backup and restore

Check that a complete Pūnaha backup can restore consistent services and data.

Your progress

Follow this journey

0 steps complete
0%

Progress is saved only in this browser.

Define the backup set

Include the Control, Workflow, and AI databases from one release checkpoint. Record the Product version and each database version.

Include every file store used by the installation. This can include original documents, knowledge indexes, local model files, runtime files, and retained logs.

Keep the parts consistent

  1. Use the approved method to pause or coordinate writes.
  2. Capture all three databases at the same checkpoint.
  3. Capture the matching file data.
  4. Record storage destination names and safe counts.
  5. Protect the backup and its encryption material under separate approved controls.

Restore away from production

  1. Create a separate recovery system.
  2. Use the recorded product version.
  3. Restore the three databases and matching files.
  4. Apply only the approved recovery steps.
  5. Keep the recovered system out of production traffic.
The tenant document storage settings
Compare the recovered storage choice with the recorded backup set. Earlier development interface, captured 22 August 2026. Follow the current text for RC1. Open the full image.

Check the restored system

  1. Confirm every required service is Live and Ready.
  2. Sign in with an approved test account.
  3. Check one allowed and one restricted access result.
  4. Open a workflow version and a case without changing production work.
  5. Search a restored knowledge database and compare one passage with its source.
  6. Confirm the required model and Connection states.
  7. Check audit and operational records.

Record pass or fail

A restore passes only when the approved checks succeed and the data belongs to the same checkpoint. Record missing data, wrong versions, failed checks, and recovery time.

Do not replace a production system with a failed or incomplete recovery.

Improve the next backup

Correct the backup list, timing, storage, access, or recovery steps that caused the failure. Create and test a new checkpoint.

Next step

Read Plan storage and backups and Fix log, backup, and restore problems.

Include registration state

Restore the matching protected Control allowance record and node state together. Do not clear the TPM or counter to reset registration.

A new host or lost identity may require the signed identity recovery process. Prove that path in a recovery exercise before relying on it.

Pūnaha Docs

Search the guides

Enter at least two characters.

    Product screen

    View the full screenshot