📑 Table of Contents

    The sentence website owners use most often: "I don't need backups, my hosting company already takes them." This is a dangerous misconception. Hosting backups look like a safety net, yet they can come up empty at the exact moment you need them. This article explains the hidden risks of hosting backups and why you need an independent backup .

    1. The Hosting Backup Usually Sits in the Same Place

    This is the biggest problem: hosting companies most often keep the backup on the same server or in the same data centre . Which means:

    • If the server hardware fails, both your site and its backup are gone.
    • If there's a fire or flood at the data centre (this has really happened), both are destroyed.
    • If the server is hacked, the attacker can reach the backups too.

    This violates the 3-2-1 backup rule's "different location" requirement — meaning you are effectively unprotected.

    2. "I Forgot to Pay" = Your Backup Is Gone Too

    If your hosting account is suspended over a late payment, an alleged terms violation or a complaint, you usually lose access to your backups as well. Your data may technically still "exist", but you cannot get to it. With an independent backup, the data is always under your control.

    ⚠️ Other hidden risks

    Hosting backups are generally never tested (they may be corrupt), not encrypted (a data protection risk), keep limited history (e.g. only the last day or two) and offer no partial restore (single file or table). When you actually need them, each of these is a separate disappointment.

    3. What Does an Independent Backup Give You?

    A backup layer independent of your site and your host guarantees the following:

    • Location independence: Your backups live in your own cloud accounts (Google Drive, S3 and so on) or across several providers.
    • Ownership: Even the moment your relationship with the host ends, your data is in your hands.
    • Encryption (BYOK): Only you can open the contents of the backup.
    • Tested backups: Restorability is proven on a regular basis.
    • Flexible restore: Full, partial or single-file recovery.

    4. The Two Backups Don't Exclude Each Other

    This doesn't mean "turn off the hosting backup". The soundest approach is to keep the hosting backup as an extra layer and place your real trust in an independent, encrypted and tested backup. In scenarios such as ransomware this independence is a lifesaver — for the details see our ransomware recovery article.

    In short: a hosting backup is better than nothing, but it isn't enough to rely on by itself. Take control of your own data.

    Frequently Asked Questions

    Is my hosting company's backup enough?

    Not on its own. Hosting backups usually sit on the same server or in the same data centre; if the server fails, your account is suspended or the site is hacked, the backup can be lost too. An independent backup layer is essential.

    What does an independent backup mean?

    It means storing your backups separately from your site and your host, in external or multi-cloud locations that you control. That way no risk originating from the server or the host can reach them.

    Should I keep both a hosting backup and an independent backup?

    Yes, that is the ideal approach. Keeping the hosting backup as an extra layer while placing your real trust in an independent, encrypted and tested backup is the safest strategy.

    Back Up Your Website Automatically and Securely

    Sign up completely free right now, connect your site with the PHP Backup Module in five minutes (without handing over FTP or database passwords) and enjoy one-click recovery when disaster strikes. No credit card required.

    Related pages: server backup · cPanel backup · all backup solutions

    Start Your Free Trial