A backup is useful only when it contains the required data, is retained long enough, is protected from the same failure as production, and can actually be restored.
Define the recovery need
- Which files, databases, mail, DNS, configuration, and external data must be protected.
- How much recent work can be lost.
- How quickly service must be restored.
- Who requests, performs, validates, and approves a restore.
Hosting snapshots or provider backups should not be treated as the only copy unless the service description explicitly defines frequency, retention, scope, and restore access. Maintain an independent backup appropriate to the value of the website and business data.
Test restores periodically in a safe location. A successful backup job does not prove the application can be recovered.
