Website Security: Essential Measures Every Site Should Take
Learn the essential defensive measures that protect your site, including updates, two-step verification, HTTPS, security headers, backups and monitoring, with a checklist.
View →Learn what the 3-2-1 backup strategy is, how to apply it to your website, and how to confirm your backups actually work with a restore test.

The 3-2-1 backup strategy is the principle of keeping at least three copies of your data, storing those copies on two different media, and keeping one copy physically in another location (offsite). It sounds simple, but it saves your work after a server failure, ransomware, accidental deletion or a fire. This guide explains each number in the rule, how to apply it to your website and business data, and the step that is most often skipped: the restore test.
The rule consists of three numbers:
Many experts also recommend adding an “immutable” or access-restricted copy. Because ransomware may try to encrypt every backup it can reach, a backup that cannot be overwritten or that only allows appending is an important safeguard.
In many hosting panels, the backup is stored on the same server's disk. If the server disk fails, the account is closed, or an attacker takes over the account, the backups go away together with the live data. A backup on the server is only useful for small incidents such as “I deleted it by mistake.” For real protection, a copy outside is essential. You can find the difference between hosting options in terms of backups in our web hosting types guide.
For a website, the things to back up are usually these:
| Method | Advantage | Point to watch |
|---|---|---|
| Hosting panel backup | Easy, often automatic | Usually on the same server; not an offsite copy by itself |
| Cloud storage | Provides an offsite copy, can be automated | Protect your access keys and calculate the additional cost |
| External disk / NAS | Fast restore, full control | Must be connected and updated regularly; there is physical risk |
| Server snapshot | Brings the whole server back | Usually stays with the same provider; check database consistency |
| Immutable / versioned storage | Strong against ransomware | Setup and retention settings require some technical knowledge |
The question that determines backup frequency is: how much data are you willing to lose in the worst case? For a corporate brochure site that changes a few times a month, a daily backup may be enough. For an e-commerce site that receives orders every day, the database may need to be backed up much more often, even several times a day. It is also possible to schedule files and the database at different frequencies: a database that changes often can be backed up often, while images that rarely change can be backed up less frequently.
Think in tiers for retention too: keep backups from recent days frequently and backups from older periods less often. A problem is often noticed only days later; if you only have yesterday's backup, that backup may already contain the problem. Keeping several restore points reduces this risk.
An untested backup is nothing more than a hope. Having a backup taken does not mean it can be restored: the file may be corrupted, the database may turn out incomplete, or the password may not be found. For this reason, run a restore test regularly:
If you have never run a test, do one this week, then repeat it at regular intervals. For the rest of the security measures, see our website security essentials article.
Let us make the rule concrete with a small business that uses a corporate website and business email:
This arrangement lets you recover from the cloud copy if the server fails, and from the external disk if the cloud account runs into trouble. Set the retention period in tiers as well: daily backups for the last few days, weekly backups for the last few weeks, and monthly backups for the last few months can be kept. Determine the figures according to your own data change rate and storage budget.
On a site that takes orders, the database changes constantly. An order placed in the middle of the day will not be in a backup until the night backup is taken. On such a site, shortening the backup interval or using continuous (incremental) database backup reduces the possible data loss. After a restore, orders and payments made between the backup and the time of the failure may also need to be compared with the payment provider's records and any missing ones processed by hand; include a checking step for this in your recovery plan. For e-commerce setup details, you can review our own guides.
Ransomware encrypts the files in the storage it is connected to, making them unreachable. If your backups are constantly connected and writable, they can be encrypted too. To reduce this risk, pay attention to the following:
Backups are a copy of live data, so they must be protected with the same care. Do not leave the encryption key and access details with only one person, but do not keep them where everyone can reach them either. A shared vault in a password manager, or a recovery code kept in a sealed envelope, is a reasonable balance. The restore document you prepare includes the steps that keep you calm in a crisis: where each backup is stored, the order in which to restore, who should be informed, and how to verify the backup and the live environment.
The 3-2-1 rule consists of three copies, two media and one offsite location. Its real value, however, lies in taking these backups regularly and testing that they can be restored. If you need support in setting up your regular backups and recovery plan, you can contact us.
It means at least 3 copies of your data, stored on 2 different storage media, with 1 copy kept in an offsite location.
Usually not. A backup on the same server can be lost together in a server failure or an account takeover. You should also keep a copy in an offsite location.
It depends on how often your data changes and how much you are willing to lose. Sites that take orders frequently may back up the database several times a day.
A backup may be corrupted or incomplete, and you only find out when you try to restore it. Testing prevents surprises in a disaster.
Yes, especially if they contain customer or user data. Keep the encryption key in a place separate from the system being backed up.
Hosting, security, backups, SSL certificates and version upgrades.
Learn the essential defensive measures that protect your site, including updates, two-step verification, HTTPS, security headers, backups and monitoring, with a checklist.
View →
Learn what SPF, DKIM and DMARC records do for business email, how to set them up correctly and how to test them so your messages stop landing in spam.
View →
What is an SSL certificate, and what types are there? A step-by-step HTTPS switch, common post-migration issues, HSTS and renewal tips for your site.
View →We would like to use Google Analytics cookies to understand how the site is used. If you decline, no statistics cookies are set. Details