PostgreSQL Storage and Backups

PostgreSQL on Thalassa Cloud DBaaS uses Thalassa Cloud block storage for database data. Backups are handled by Barman and stored in an object storage bucket. This page covers how storage and backups work and how to configure them.

Block storage

Database volumes use Thalassa Cloud block storage. Block storage is replicated across all availability zones in the region automatically. That applies even when you run a single instance - your data is still replicated across AZs for durability.

When you configure multiple instances (instance count > 1), the DBaaS provisions replica instances. Instances are spread across all availability zones in the region. If the primary instance fails, the platform detects it and an instance in another AZ takes over (failover or switchover). For more detail, see the High availability guide.

Backups with Barman

Thalassa Cloud DBaaS uses Barman (Backup and Recovery Manager) for PostgreSQL backups. Backups are stored in an object storage bucket that is automatically created and configured by the DBaaS service.

Configuring backups

1. Configure a Backup Object Store - Attach a backup object store to your database cluster. The DBaaS provisions the bucket and configures Barman to use it.
2. WAL archiving - WAL (Write-Ahead Log) archiving starts automatically when backups are configured. This is required for point-in-time recovery (PITR).

Backups can be triggered manually or via a schedule.

Backup schedule and retention

• Schedule - We recommend a weekly backup schedule. With Barman and PITR, shorter intervals are usually unnecessary; WAL archiving allows recovery to any point in time between full backups.
• Initial backup - Take an initial backup manually after configuring backups. This ensures proper PITR until your scheduled backup has run at least once.
• Retention - Configure retention so backups are kept for a defined period. We advise 14 days or 30 days depending on your compliance and recovery needs.

Backup bucket and access

• The backup bucket appears in your Bucket overview in the Thalassa Cloud console. It is created and managed by the DBaaS service. It will also be automatically deprovisioned upon deletion of the backup object store resource in DBaaS (You will see a warning about this).
• The bucket’s policy includes a DBaaS statement that allows the service to write backups. Do not remove this statement - removing it will prevent backups from functioning.
• In the future, you will be able to add additional policy statements to grant read access to the backup bucket to your own Service Account users (for example, for exit scenarios, disaster recovery, or copying backups elsewhere).
• Backup best practice: We recommend replicating your backups to another object storage location outside Thalassa Cloud (for example, another cloud provider or on-premises). This improves business continuity and aligns with common backup best practices.