Cloud backup details

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.

Hier die englische Version, eng angelehnt an die deutsche Fassung und an den Stil der bestehenden englischen Doku:

Disaster Recovery: What to Consider on Your Side

In the event of a disaster recovery, we restore your Lobster Cloud environment automatically. To make sure this runs as smoothly as possible for you, please take the following points into account when configuring your VPN and integrations.

Internal IP Addresses May Change

After a recovery, the internal IP address of your Lobster systems may change. The CIDR range of your environment, which we have communicated to you, remains the same.

What this means for you:

Always address your Lobster systems via the DNS name (e.g. your-system.lobster-cloud.com), never via a fixed IP address.
In your VPN and firewall configuration, allow the entire CIDR range we have assigned to your environment. Please do not configure individual IP addresses. This way, your configuration remains valid even if individual IPs have changed after a recovery.

Automated Recovery (Infrastructure as Code)

Your Lobster Cloud environment is fully defined as Infrastructure as Code (IaC) on our side. This means your entire environment (network, systems, configuration) is described as an automated blueprint and can be rebuilt reproducibly in a disaster recovery scenario.

We restore your environment as close to its original state as possible. In particular, the following will remain unchanged:

The DNS name you use to reach Lobster
The size, configuration, and software version of your system
The assigned internal network range (CIDR)

Public IP Address

We cannot guarantee the public IP address of your Lobster environment in a disaster recovery scenario. It may change after a recovery, but the DNS name will stay the same.