A backup. A result to verify.

Recovering a database may not be enough. NodalX organizes project recovery and application verification.

All guides

Back up what makes the project work

A database record may reference a file, an invoice its PDF, or an application a specific configuration. A backup policy needs to preserve consistency between these elements with an identifiable recovery point.

NodalX is designed for encrypted backups and project-appropriate retention. Copies need to sit outside the failure domain being protected. A backup on the only server’s disk does not protect against losing that server.

Restore into an isolated environment

  • Choose an available recovery point with its date and scope.
  • Restore the database and associated files into a separate copy.
  • Open the restored application and verify a useful outcome.
  • Decide separately whether to switch production.

A test restore leaves production in place. It lets you check data readability, file presence and service operation before making a more sensitive decision.

Know what can be recovered

The available point depends on the latest backup and, where the database supports it, transaction logs. Point-in-time recovery requires a compatible adapter and policy. It is not a general zero-data-loss guarantee.

Recovery keys need to remain accessible to the team performing the restore. Control-plane backups and installation recovery procedures belong in the same preparation.

Distinguish versions from data

Returning to an earlier application version changes the code being run. Restoring a backup changes the state of the data. Writes made after a deployment do not disappear just because the code is rolled back.

NodalX connects versions, backups and restoration operations to preserve each action’s context. Verification focuses on the application and its data, rather than simply the existence of a backup file.