Website backup: what to copy, how often, and where to store it
Website backup is not a tick-box in a hosting panel; it is a proven ability to bring back a working site, with its orders and enquiries, in a reasonable time. A backup nobody has ever restored is a hope, not a backup, and you learn the difference on the worst possible day. Below is a scheme for a small business in Uzbekistan: what to copy, how often, where to keep it and how to check it.
Website backup: what exactly to copy
A site has two halves and both matter equally. Files are code, templates, plugins, uploaded images, price lists and documents. The database holds page text, products, orders, enquiries, users and settings. A file-only copy is useless for an online shop: the design comes back without the catalogue or orders. A database-only copy brings back a catalogue with empty image slots because the uploads folder is missing.
The third part is configuration: web server settings, cron jobs, environment variables with integration keys (payment systems, an SMS gateway, a Telegram bot for enquiries), DNS records and domain access. Hosting backups usually skip these, and during a move they take the most time to rebuild. Keep this list in a separate document, and not on the site itself.
Do not forget the services around the site: domain email, CRM data and any 1C exports connected to the website. Their backups are configured separately and are often forgotten.
How often to back up and how long to keep copies
Frequency answers one question: how much data are you willing to lose? A brochure site that changes quarterly is fine with a weekly copy plus an extra one before every edit. A shop taking daily orders needs a database copy at least once a day, and during a sales season every few hours, because half a day of lost orders costs more than disk space.
Retention matters as much. Infection or silent data corruption surfaces a week or two later, and a single overwritten copy already contains the problem by then. A workable scheme is daily copies for the last 14 days, weekly copies for the last month and a few monthly snapshots over six months.
One more rule: take an unscheduled copy before any change, whether it is a CMS or plugin update, a theme switch, a move to another host or a manual database edit. It takes minutes, while a rollback without it can take a day.
Where to store copies: the 3-2-1 rule
The 3-2-1 rule means three copies of your data, on two different types of media or platforms, with one outside your main infrastructure. In practice that is the live site, an automatic backup at the host and an upload to cloud storage or a separate server.
A copy on the same server covers only the 'an update broke something' scenario. It does not help against a suspended hosting account, an intruder who deletes everything, ransomware or a simple unpaid invoice, and those are exactly the cases that end in total loss. At least one copy must sit where the site server has no write access.
For a small site, 50–100 GB of cloud storage is usually enough. As a rough guide that is about 20,000–80,000 UZS a month, though tariffs depend on the provider and the exchange rate. A 1 TB external disk for an office copy is roughly 700,000–1,300,000 UZS once, also a rough guide. Encrypt archives that contain customer data with a password and keep the key apart from the copies.
Setting up backups step by step
Step 1. Make an inventory: what lives on the site, where the database is, which external keys and accounts exist. Step 2. Decide how much data loss and how much downtime you can accept, because frequency and method depend on it. Step 3. Turn on automatic backups at the host and check that they include files, the database and the uploads folder.
Step 4. Set up an off-host upload: a cron script, a CMS plugin or a control panel feature that sends the archive to the cloud or a second server. Step 5. Turn on failure notifications, since a backup that quietly stopped is the most common reason for an empty archive on the day you need it. Step 6. Write restore instructions that a person who did not set the system up can follow. Step 7. Name an owner and the date of the next check.
Restore testing and common mistakes
Once a quarter, restore a copy to a test subdomain and confirm that the site loads, the database attaches, images are present, enquiry forms send and you can log in to the admin panel. Broken archives, partial dumps and backups without the uploads folder only reveal themselves this way.
Time the restore while you are at it, from 'the site is down' to 'the site works'. That number is what you can honestly tell management and customers on an outage day.
Typical mistakes: keeping copies only on the same server; skipping the database or the uploads; relying on a single copy that is overwritten every night; leaving failure notifications off; storing the archive password inside the archive; never trying a restore; and not sharing access with a second responsible person.
FAQ
Can I rely on my hosting backup alone? No. It is necessary, but it lives on the same platform. If the account is suspended, the provider has a failure or someone gets into the panel, you can lose both the site and its copies. Add an off-host upload.
How much space do copies need? Multiply the size of the site and database by the number of copies you keep. For a small site that is usually a few or a few dozen gigabytes, and incremental copies save space because they store only changes.
How do I know the site was hacked and the copy is infected? Look for unfamiliar files, unexpected redirects, spam pages in search results and warning emails from the host. That is why retention depth matters: restore a copy made before the first signs.
What should I do after a restore? Change all passwords and keys, update the CMS and plugins and find how the intruder got in, otherwise it will happen again. Then check forms, payments and Telegram notifications.
Who should be responsible for backups? A specific person and a deputy, not 'someone from IT'. Both should know where the copies are, where to get the password and where the restore instructions are.
Where to start
The easiest start is today: check the host's automatic backup, upload one copy outside the host and try restoring it on a test subdomain. If a site is being built from scratch, it is convenient to design the backup scheme at the planning stage. At 4 Digital, turnkey website creation starts from 1,399,000 UZS, and backup and restore questions can be discussed at the start of the project.