Manual backups work well for the first week, then they are forgotten. Site owners usually discover this at the worst moment: after an update breaks the site, an accidental deletion or a hack. Automatic backups solve the forgetting problem, but they need two deliberate decisions: how often to back up, and how many copies to keep.
Why manual backups fail
- They depend on one person remembering, and they stop when that person is busy or leaves.
- They usually happen after important changes rather than before, so the latest copy is older than the latest important work.
- Copies pile up in different places without clear names, so nobody knows which is the newest when it matters.
How often? Based on how fast your data changes
The simple rule: back up as often as the amount of data you cannot afford to lose.
| Type of site | What changes | Suggested frequency |
|---|---|---|
| Company brochure site | Occasional page edits | Weekly |
| Blog or content site | Posts and comments several times a week | Daily |
| Online store | Orders, customers and stock throughout the day | Daily or more |
| Internal system or app on a VPS | Continuous operational data | Up to hourly |
Treat this as a starting point rather than a fixed rule: take an extra manual copy before any major change to a brochure site, back up a store's database more often during busy order seasons, and set the frequency of internal systems by the maximum period of data you can afford to lose.
How many copies to keep?
Keeping a single copy is risky because problems are not always noticed right away; if the site was hacked a week ago without you noticing, yesterday's backup is infected too. A common, balanced pattern is to keep the last 7 daily copies, the last 4 weekly copies and one monthly copy for several months. Adjust it to your available space and the nature of your site; what matters is being able to go back to before the problem, not just to yesterday.
Where are automatic backups stored?
Copies on the same server are useful for quick rollbacks, but they do not protect against a server failure or an attacker who reaches the account. Add a regular off-server copy following the 3-2-1 rule, even if it is just a weekly copy you download yourself.
How do you know backups actually work?
- Turn on email notifications for successful and failed backups if your tool supports them, and read them.
- Once a month, check the date and size of the latest backup; an unusually small backup is a warning sign.
- Every few months, run a full test restore in a staging environment, following the cPanel restore steps.
What EngHosting plans include
According to the plan pages, shared hosting and WordPress plans include a free daily backup from the Economy plan upwards, and the reseller plans include daily backups. VPS and dedicated servers need a backup plan set up by the customer, and backup tool licences and backup storage are available for them in the extra services. Remember that the acceptable use policy makes customers responsible for regular backups of their own data, so treat your plan's daily backup as the first layer and add an off-site copy under your own control.
Summary
Automatic backups do not mean forgetting about the topic; they move it from memory to a clear schedule: a frequency that matches how fast your data changes, a retention period that lets you go back to before the problem, a copy off the server, and regular test restores. With these four elements you greatly reduce the risk of losing data.
Ready to start with EngHosting?
Fast, secure hosting with 24/7 Arabic support. Refund terms are in our acceptable use policy.
Order Now