A botched backup gives a false sense of security: you know that, “in theory”, a copy of the site exists, but you don’t know whether it is complete, recent enough, or whether it would actually work in an emergency. The difference between a business that recovers from an incident in a few hours and one that loses days (or months) of work almost always lies in the quality of the backup, not in the severity of the problem that made it necessary.
In brief
A complete website backup must include both the files (themes, plugins, images, media) and the database (content, orders, users, settings). It should be run with a frequency proportional to how much the site changes — daily for an ecommerce site, weekly for a rarely updated brochure site — and stored in at least two different locations, never only on the same server as the site. A backup stored exclusively on the same hosting as the site does not protect against hardware failures, attacks or problems with the hosting itself: in those cases it risks being compromised along with the site it is meant to protect.
What data should be saved in a website backup?
A complete backup covers two distinct and equally necessary components: the site files and the database. Forgetting either one makes the backup useless in a real restore, even if it looks “done”.
The site files
These include the CMS core, themes, plugins and, above all, the media/uploads folder with images, PDFs and documents uploaded over time: it is often the heaviest part of the site and the easiest to forget in a partial backup.
The database
It contains textual content, settings, users and, for an ecommerce site, the entire order and customer history. It is the most critical component: a site without an up-to-date database can be rebuilt visually, but loses all the operational and commercial data accumulated.
How often should the site be backed up?
The right frequency depends on how much content changes on the site every day, not on a fixed rule that suits everyone. An ecommerce site receiving orders daily needs far more frequent backups than a static brochure site updated once a month.
- Ecommerce with daily orders: daily database backup (so as not to lose orders), file backup at least weekly.
- Blog or business site with frequently updated content: full weekly backup, possibly more frequent during periods of heavier editorial activity.
- Static brochure site, rarely updated: a full monthly backup may be enough, but one should still be run before any important change or update.
- Before every major update (core, theme, critical plugins, migration): an “event-based” backup, regardless of the planned schedule, is always good practice.
Where should website backups be stored?
The most widespread and reliable rule in the industry is the 3-2-1 rule: at least three copies of the backup, on two different types of media, with at least one copy kept away from the main hosting server. Applied to a website, it means never trusting a single backup stored in the same folder as the site.
Why a backup on the same hosting is not enough
If the hosting suffers a hardware failure, an attack or an account suspension, a backup kept only there is lost along with the site. Keeping at least one copy on external storage (dedicated cloud storage, space separate from the server) is the difference between a manageable incident and permanent data loss.
Automatic backups vs manual backups
Automatic, scheduled and recurring backups eliminate the risk of human forgetfulness and guarantee continuity even in the quieter periods of the year. Manual backups remain useful as a complement before specific operations (a major update, a migration), but they should never be the only protection strategy for the site.
How can you verify that a backup really works?
An untested backup is a backup you cannot trust until the moment you need it, and that is often too late to discover it does not work. Periodic verification — ideally quarterly — consists in actually restoring the backup in a separate test environment, checking that files and database are complete and consistent with each other. Many businesses discover they have an incomplete or corrupted backup only at the worst possible moment: during a real emergency.
Studio Mate includes scheduled, verified automatic backups in the preventive maintenance packages for WordPress, WooCommerce and Laravel applications, with copies kept separate from the production server, so that we can act quickly when needed, also in 2026.
What are the most common mistakes in backup management?
Even businesses that “do their backups” often make mistakes that cancel out their usefulness at the very moment they are needed. Recognising them in advance avoids nasty surprises just when the backup should be the safety net.
Partial backups that look complete
A backup covering only the files or only the database gives the impression of being protected, but a restore is always missing half of the picture. It is one of the most frequent mistakes among those who set up a backup without checking its actual contents.
A single copy, in the same place as the site
Keeping the backup in the same folder or the same hosting account as the site exposes it to the same vulnerability: if the server is compromised or goes offline, the backup and the site are lost together, cancelling out the usefulness of the copy.
No restore verification
A correctly generated backup can still turn out to be corrupted, incomplete or incompatible at the time of restore, for technical reasons that are not always foreseeable. Without a periodic test, this is only discovered during a real emergency, when there is no room left to fix it.
Backups and data retention: what to consider for an ecommerce site
For an ecommerce site, the database backup also contains customers’ personal data (names, addresses, order history): the retention of backup copies must therefore be aligned with the same security and privacy policies applied to the main site, avoiding keeping copies on services that are not properly protected or lack access control. This aspect is often overlooked while focusing only on backup frequency, but it is just as relevant for compliance and the overall security of business data.
Frequently asked questions
How long should older backup versions be kept?
A common strategy is to keep daily copies for one or two weeks, weekly copies for one or two months, and at least one monthly copy for a longer period, so that you can also go back to a problem discovered late.
Is a free backup plugin enough?
It can cover the basic needs of a simple site, but it often lacks automatic off-server retention, failure notifications or integrity checks: elements that become important for sites with critical data such as an ecommerce.
What happens if I discover the backup does not work during an emergency?
In that case, the restore requires a more complex technical intervention, based on the manual recovery of whatever is available (cache, partial versions, residual data), with longer times and a result that is not always complete compared to a backup verified in advance.
Does the site backup also include business emails?
Generally no: emails follow a system separate from the website (often managed by the mail provider) and require a dedicated backup strategy, independent from the one for the site.
How much space is needed to store backups over time?
It depends on the size of the site and the number of versions kept at the same time: a site with many images or an ecommerce with a large order history requires more storage space than a simple brochure site.
