Docs
DBaaS
Backup & Recovery

Backup and Recovery

This feature is currently in beta.

While we strive to provide a stable service, we may introduce changes to the service that are not backwards compatible. We will do our best to notify you of any changes that may affect you.

During the beta period, documentation may be incomplete or outdated. Please let us know if you find any issues or have any feedback.

Interested in joining the beta program? Contact us

Thalassa Cloud’s Database as a Service (DBaaS) provides comprehensive backup and recovery capabilities to protect your data and ensure business continuity. Our backup solution is designed to minimize data loss and provide quick recovery options for various scenarios.

Backup Overview

Our backup strategy is built around three core principles:

  1. Automated backups: Regular automated backups with configurable retention
  2. Point-in-time recovery: Restore to any point within your retention period (available soon)
  3. Disaster recovery: Cross-region backup replication for disaster recovery (roadmap)

Automated Backups

Backup Schedule

Automated backups are performed daily and provide:

  • Daily backups: Full database backups performed automatically
  • Configurable retention: Set retention periods from 7 days to 35 days (object storage backups will support longer retention periods)
  • Encrypted storage: All backups are encrypted at rest
  • Cross-AZ storage: Backups are stored across multiple availability zones

Manual Backups

On-Demand Backups

Create manual backups for special events or before major changes:

  • Pre-deployment backups: Before application deployments
  • Schema change backups: Before database schema modifications
  • Data migration backups: Before data migration operations
  • Compliance backups: For regulatory compliance requirements

Point-in-Time Recovery

Continuous Backup (available soon)

Our point-in-time recovery feature provides:

  • Continuous backup: Transaction logs are continuously backed up
  • Granular recovery: Restore to any point within your retention period
  • Minimal data loss: Recovery point objective (RPO) of minutes
  • Fast recovery: Recovery time objective (RTO) of minutes to hours

Recovery Scenarios

Point-in-time recovery is useful for:

  • Accidental data deletion: Recover from accidental DELETE operations
  • Data corruption: Recover from data corruption events
  • Application errors: Recover from application-level data issues
  • Malware incidents: Recover from ransomware or malware attacks

Backup Storage and Management

Storage Locations

Backups are stored securely across multiple locations:

  • Primary storage: Local storage within your region
  • Cross-AZ replication: Backups replicated across availability zones
  • Cross-region backup: Optional backup replication to other regions

Backup Lifecycle

Backup lifecycle management includes:

  • Creation: Automated and manual backup creation
  • Verification: Automatic backup integrity verification
  • Retention: Configurable retention policies
  • Cleanup: Automatic deletion of expired backups

Backup Monitoring

Monitor your backup operations:

  • Backup status: Track backup success and failure rates
  • Storage usage: Monitor backup storage consumption
  • Recovery testing: Regular backup restoration testing
  • Performance impact: Monitor backup impact on database performance

Disaster Recovery

Recovery Strategies

Our disaster recovery approach includes:

  1. High Availability: Multi-AZ deployment with automatic failover
  2. Recovery Procedures: Documented recovery procedures
  3. Testing: Regular disaster recovery testing

Recovery Procedures

Full Cluster Recovery

To recover an entire database cluster:

  1. Identify backup: Select the appropriate backup for recovery
  2. Create new cluster: Create a new cluster with the same configuration
  3. Restore from backup: Restore the backup to the new cluster
  4. Update applications: Update application connection strings
  5. Verify data: Verify data integrity after recovery

Point-in-Time Recovery

To recover to a specific point in time:

  1. Identify recovery point: Determine the exact time for recovery
  2. Create recovery cluster: Create a new cluster for recovery
  3. Restore to point: Restore to the specified point in time
  4. Verify data: Verify data at the recovery point
  5. Switch applications: Switch applications to the recovered cluster

Database-Level Recovery

To recover specific databases:

  1. Identify database: Select the database to recover
  2. Create new database: Create a new database in the cluster
  3. Restore database: Restore the specific database
  4. Update permissions: Update database permissions and grants
  5. Test connectivity: Verify application connectivity
Database Management