Backup and Restore

Backup and restore capabilities in CertiNext are designed around a clear separation of responsibilities between the application layer and the data layer. This approach ensures flexibility in deployment while aligning with enterprise-grade operational practices for both on-premises and cloud-hosted environments.


Cloud-Hosted Deployments

For cloud-hosted (SaaS) deployments, backup and restore operations are fully managed by the CertiNext operations team. This includes:

  • Regular, automated backups of customer data stored in the data layer

  • Secure storage of backups in line with platform availability and recovery objectives

  • Tested restore procedures as part of operational readiness

Customers using cloud-hosted CertiNext do not need to configure or manage backups themselves.


On-Premises Deployments

For on-premises deployments, backup and restore responsibilities lie with the customer’s infrastructure and operations teams.

Important considerations:

  • CertiNext does not natively implement backup or restore mechanisms for on-prem environments

  • The platform relies on database management systems or other control-plane layers (such as backup tools, storage snapshots, or infrastructure automation) to handle backups and restores

  • Customers are expected to use enterprise-approved backup strategies consistent with their internal IT policies

This allows organizations to integrate CertiNext into existing backup and disaster recovery frameworks without introducing parallel tooling.


Application Layer vs Data Layer

CertiNext is architected so that:

  • No customer data is persisted at the application layer

  • The application layer contains only configuration and runtime state required to direct the operation of the application server

  • All customer-specific data (certificates, metadata, audit records, configurations) resides in the data layer

As a result:

  • Restoring the database restores the full operational state of CertiNext

  • Application servers can be redeployed or replaced without data loss

  • Backup and restore processes remain simple, predictable, and infrastructure-driven


Restore Scenarios

In an on-prem environment, typical restore scenarios involve:

  • Restoring the database from a known good backup

  • Restarting or redeploying CertiNext application servers

  • Verifying connectivity and configuration

No additional application-level recovery steps are required.


Summary

CertiNext’s backup and restore strategy emphasizes clean separation of concerns:

  • Cloud-hosted deployments are fully managed by CertiNext

  • On-prem deployments rely on customer-managed database and infrastructure backups

  • No customer data is stored in the application layer

This design simplifies recovery, reduces operational complexity, and ensures CertiNext integrates cleanly into enterprise backup and disaster recovery models without imposing proprietary mechanisms.

Last updated