What to have ready before an incident.
WHAT TO ASSEMBLE
A recent full backup, downloaded and verified
Your recovery documentation: what runs where, and how to restore
Credentials, in a password manager you can reach
Contact details: us, your registrar, your developer
A record of DNS records A record of cron jobs and third-party integrations
WHERE TO KEEP IT
Not on the hosting account. A folder in cloud storage, plus a copy on a machine you control.
If the emergency kit is on the thing that failed, it is not a kit.
WHO SHOULD HAVE ACCESS
More than one person, in any business with staff. A recovery plan only one person can execute is a continuity risk.
WHAT ELSE TO INCLUDE
A note of what "normal" looks like: typical traffic, normal file count, expected backup size. Deviations are easier to spot against a baseline.
TESTING IT
Attempt a restore using only what is in the kit. The gaps become obvious.
REVIEWING
Quarterly, alongside your restore test.
WHY
During an incident nobody thinks clearly. Everything assembled in advance is something you do not have to find under pressure.
