Backup and Disaster Recovery You Can Trust

Backups fail because they are stored on the same server, stopped running without anyone noticing, missed the database, or no one knew how to restore them.

Many businesses think they have backups, until the day they need one. Common surprises: the backup was on the same server that crashed, it stopped running months ago, it only had files and not the database, or no one knew how to restore it.

Disaster recovery means planning for the bad day before it comes: a hack, ransomware, a server failure, a wrong update or a staff mistake.

A good plan is short and practical. It does not need to be a thick document. It needs to answer a few clear questions: what to restore first, where the backups are, who has access to them, how long a restore takes, and who to call. We help you write this in one or two pages and keep a copy where your team can find it, even if the main systems are down.

The 3-2-1 backup rule means keeping three copies of your data, on two different types of storage, with one copy off-site. It is a simple way to avoid losing everything to one failure.

For protection against ransomware, we also keep one copy that cannot be changed or deleted for a set time.

This extra copy matters because some ransomware looks for backups and tries to delete them first. A locked copy stays safe even if an attacker gets admin access.

Back up website files and databases daily, business files daily with version history, server settings after each change, and email and CRM data as the platform allows.

We set how long to keep each backup based on your needs, for example daily copies for 30 days and monthly copies for a year.

Platforms we commonly back up

• WordPress and WooCommerce sites, including uploads and the database
• Laravel and other custom apps, including the database, uploaded files and settings
• Shopify store data such as products and content, using export or backup apps
• Google Workspace and Microsoft 365 data, using exports or backup tools
• VPS server settings, so a new server can be built quickly

RTO is how long you can be offline. RPO is how much recent data you can afford to lose. Your answers decide how often to back up and how fast your restore must be.

These are examples to help you think, not fixed rules. We agree the right targets with you on a free call. Online stores often need extra care, which our ecommerce security service covers.

List your key systems, decide how long each can be down, write restore steps, name who does what and test a restore every few months. Keep the plan short and easy to find.

1. List key systems and how long you can be without each one
2. Decide how much data you can afford to lose (last hour, last day)
3. Write simple restore steps for each system
4. Name who does what and who to call, including our 24x7 emergency line
5. Test a restore every few months and note the time it took
6. Update the plan when systems change

If your website is hacked, a clean backup lets us restore fast while we close the entry point. See malware removal and cloud security.

What to keep in the plan

• Contact list: owner, IT person or agency, hosting support and our emergency line
• Where each backup is stored and who can log in to it
• Domain, DNS and hosting account details, kept in a password manager
• A short message template to tell customers if the site is down for long
• The date of the last restore test and how long it took

Find a clean backup from before the hack, restore it to a safe place first, close the entry point, change all passwords, then put the clean site live. Restoring without closing the gap often leads to a repeat hack.

1. 1

   Contain

   Put the site in maintenance mode and change hosting, admin and database passwords.

2. 2

   Find a clean point

   Check backup dates against when the problem started, as hacks often begin before anyone notices.

3. 3

   Restore safely

   Restore to staging first and scan it for hidden bad code.

4. 4

   Close the gap

   Update software, remove weak plugins and fix the entry point.

5. 5

   Go live and watch

   Switch the clean site live and watch closely for a few weeks.

If no clean backup exists, the site must be cleaned by hand. Our website malware removal team handles this, with 24x7 emergency support for hacked sites.

Backup and disaster recovery cost depends on how much data you have, how often backups run, how long they are kept, where they are stored and how often restores are tested. You get a clear quote after a free call.

• Amount of data and number of systems
• How often backups run and how long they are kept
• Storage location and costs
• How often restores are tested

You get a clear quote after a free call.

Other mistakes to avoid

• Do not keep backup logins in the same place as your server logins.
• Do not back up only files and forget the database.
• Do not skip alerts for failed backups.
• Do not keep the only recovery plan on the system that might go down.

Backups work best with other protection. See security monitoring for early alerts, cloud security services for server settings and data security for business files.

Related Pages