Skip to main content
The Backbase Agent Platform stores agent and knowledge data in Azure Database for PostgreSQL Flexible Server. The platform manages backup and retention. You don’t configure backup policies.

​
At a glance

The following table summarizes platform backup standards.

​
How backups work

Azure automatically protects each PostgreSQL Flexible Server with:
  • Daily snapshot backups (full initial snapshot, then differential snapshots when data changes)
  • Continuous transaction log (WAL) archiving for point-in-time restore within the retention window
Backups cover all databases on a runtime’s PostgreSQL server. The platform can restore to a specific point in time within the retention period for that environment.
Point-in-time restore creates a separate restored instance for recovery workflows. It does not overwrite your live database in place.

​
Recovery objectives

The following table lists recovery objectives. These are planning targets, not customer-specific contractual SLAs unless agreed separately with your organization.

​
Backup vs disaster recovery

The following table compares backup protection with disaster recovery and archival. Standard backups stay in the same Azure region unless geo-redundant backup is agreed at server creation.

​
What you need to know

  • You don’t configure backup retention. The platform sets retention per environment class.
  • You provision databases through your applications-live repository and the infra-resources self-service flow.
  • If you need a data restore, submit a Jira request to the platform team. Include the runtime, database name, and the point in time you need to recover to. The platform team performs operational restore steps.
For more information, see: