Surviving the worst case.
WHAT MUST BE RECOVERABLE
The database Customer files Configuration Secrets and credentials
WHAT TO DEFINE
How much data you can afford to lose How long you can afford to be down
WHAT THOSE DETERMINE
Backup frequency and recovery approach.
WHAT TO TEST
Restoration, on a schedule, actually performing it.
WHY
Backups that have never been restored routinely fail when needed.
WHAT TO STORE BACKUPS
Separately from production, in another account or provider.
WHY SEPARATELY
A compromised or deleted account takes everything within it.
WHAT TO PROTECT AGAINST
Deletion by an attacker who obtained access.
WHAT ACHIEVES THAT
Backups that cannot be deleted for a defined period.
WHAT ELSE TO PLAN FOR
Accidental deletion by a customer Accidental deletion by you Corruption discovered late
WHY THAT LAST ONE
If backups only cover a week and corruption began a month ago, they are useless.
WHAT TO RETAIN
Several generations, over a longer period.
WHAT TO BUILD FOR CUSTOMERS
The ability to recover their own deleted data, for a period.
WHY
It removes a large category of support requests and prevents genuine loss.
WHAT TO DOCUMENT
The recovery procedure, step by step, testable by someone else.
