Backups protect you from deletion, hardware failure, ransomware and human error.
What to back up:
The database: scheduled full backups, plus differential or transaction-log backups if you cannot lose much data. In SQL Server, use native backups with checksum.
The website files: uploads, configuration and the application itself (or the code repository plus the deploy process).
Configuration and secrets (stored securely).
Rules that matter:
3-2-1 rule: three copies, on two different kinds of storage, one of them off-site (another region or cloud storage).
Keep backups off the main server, and keep some copies isolated or immutable so ransomware cannot encrypt them.
Encrypt them and control who can access them.
Automate and monitor, so you are alerted when a backup fails.
Test restores regularly, on a separate machine. Many people find out their backup is broken only when they need it.
Decide how much data loss (RPO) and downtime (RTO) your business can accept, and set the schedule accordingly.
Markdown for AI
A clean, structured version of this page for AI assistants and LLMs.
We use cookies to ensure you have the best browsing experience on our website. By using our site, you
acknowledge that you have read and understood our
Cookie Policy &
Privacy Policy.
Backups protect you from deletion, hardware failure, ransomware and human error.
What to back up:
Rules that matter:
Decide how much data loss (RPO) and downtime (RTO) your business can accept, and set the schedule accordingly.