Lobster implements daily automated backup procedures for all cloud systems. This page covers backup schedules, retention periods, Recovery Time Objectives (RTO), Recovery Point Objectives (RPO), and the Disaster Recovery Plan.
Backup schedule
All backups run automatically. No action is required from your side.
Service | System type | Backup time | Retention period |
|---|---|---|---|
RDS Database | Production | Continuous (point-in-time recovery) | 30 days |
RDS Database | Test / DEV | Daily, 02:00 to 03:00 UTC | 7 days |
EC2 / EBS Volumes | Production | Daily, 02:00 to 03:00 UTC | 30 days |
EC2 / EBS Volumes | Test / DEV | Daily, 02:00 to 03:00 UTC | 7 days |
EFS / FSx File Systems | Production | Daily, 02:00 to 03:00 UTC | 30 days |
EFS / FSx File Systems | Test / DEV | Daily, 02:00 to 03:00 UTC | 7 days |
All backups are stored in AWS Backup Vaults with governance-level protection. Production databases benefit from continuous Point-in-Time Recovery (PITR), which allows restoration to any second within the 30-day retention window.
Quality assurance
Lobster continuously validates the integrity and reliability of the backup infrastructure:
Activity | Frequency |
|---|---|
Recovery tests (randomly selected systems) | Monthly |
Full disaster recovery drill (complete site failover simulation) | Quarterly |
Compliance testing | Quarterly |
Backup execution monitoring (New Relic) | Continuous |
Automated backup success rate alerts (threshold above 99%) | Continuous |
Backup cost analysis and optimization review | Monthly |
Requesting a restore
If you need a backup restored, submit a support ticket to support@lobster.de with the following information:
Information | Description |
|---|---|
System | Which system needs to be restored (production, test, DEV). |
Component | What should be restored (database, server, file system). |
Target point in time | The date and time you want to restore to (within the retention window). |
Reason | Brief description of why the restore is needed. |
Restores are processed according to the SLA priority matrix. Production database restores with critical priority have the fastest RTO of less than 2 hours.