Data Recovery: Restoring Lost or Corrupted Data
Accidental deletion, data corruption, and failed migrations can all result in data loss. This article explains our data recovery capabilities and what you should do if data is lost.
Immediately Report Data Loss
If you discover missing or corrupted data, raise a P1 or P2 support ticket immediately. Time is critical — the sooner we act, the better the chance of full recovery and the lower the risk of backups being overwritten before we can use them.
How We Recover Data
Our primary recovery method is restoring from backups:
- We identify the most recent backup that predates the loss or corruption
- We restore a copy of the database or file system from that backup to a temporary environment
- We extract the specific lost data and reintegrate it into the live system
- You verify the recovered data before we confirm the restoration is complete
Point-in-Time Recovery
For database systems with transaction logging enabled, we may be able to recover data to a specific point in time — not just to the last backup. This is particularly valuable when the loss window is small (e.g. "we need data as it was at 3:47pm today").
Limits of Recovery
Recovery is limited by backup frequency. If backups are daily, data created between the last backup and the loss event may be unrecoverable. For business-critical systems where even an hour of data loss is unacceptable, speak to your Account Manager about more frequent backup schedules or real-time replication.
Prevention: Best Practices
- Never delete data directly in a production database without taking a backup first
- Use soft-delete patterns (marking records as deleted rather than physically removing them)
- Require confirmation dialogs for bulk delete operations
- Test restores periodically — a backup you have never tested is a backup you cannot trust