🎉 Black Friday Sale starts soon! 23 Save the date

0Days

0Hours

0Minutes

0Seconds

Home / Services / Managed services / Backup and recovery

Backup and recovery

The real test of a backup is the restore

We set up backups for your website, store or application, store them away from the server, and restore them regularly so you know they work.

What you get
  • Backup policy covering frequency, retention and storage
  • Automated backups to separate off-site storage
  • Restore test log updated on schedule
  • Written recovery plan with roles and contacts
  • Access register for backup accounts
  • Alerts when a backup fails or is missed

What is included

The work, piece by piece.

Backup design

What to back up, how often and for how long, based on how much data you can afford to lose and how quickly you need to be running again.

Off-site storage

Copies kept in separate cloud storage, in a different account and region from the live server, so one failure cannot take both.

Database and file coverage

Databases, uploads, configuration and code backed up together, including order data from WooCommerce or your custom application.

Scheduled restore tests

Backups restored to a test environment on a schedule, with the result recorded, rather than assumed to work.

Recovery plan

A written plan covering who does what if the server fails, data is deleted or the site is compromised, with contacts and access listed.

Point-in-time restores

For busy stores and applications, database backups frequent enough to recover to shortly before a problem, not to last night.

Signs you need this

When teams usually call us.

01

The only backup is the one your host makes

Host backups often sit on the same infrastructure and may not be kept long. A separate copy protects you if the host has a problem.

02

Someone deleted something important by mistake

A product catalogue, a set of pages or customer records gone in one click is a common reason to look at backups properly.

03

You cannot say how long a recovery would take

If the answer is a guess, a tested recovery plan replaces it with a known process.

How we work

No surprises, start to finish.

Talk to the developers doing the work, by email or call, whenever you need.

01

Talk

Tell us what you need. We ask questions until the scope is clear.

02

Plan and quote

A clear scope with an hourly, fixed or monthly-hours price.

03

Build on staging

Every change is built on a staging site first, never on your live site.

04

Sign off and launch

You review and approve. Then we go live with zero downtime.

05

Care

We stay on for updates, fixes and new features, if you want us to.

For agencies

Your development team for WordPress, under your name.

Agencies around the world send us their builds on WordPress. We do the work, you keep the client, and our name appears nowhere.

White-label

Your brand on everything. No Elicus credit, ever.

NDA-friendly

Happy to sign yours before we see a brief.

Scale on demand

We grow the team to fit the project.

Your terms

Something specific in mind? We'll talk it through.

Questions

Before you ask.

How long are backups kept?

You decide with us. A common pattern keeps daily copies for a month and monthly copies for longer, but stores and regulated businesses often need different retention.

Where are backups stored?

Away from the live server, in storage we run or in a cloud account your company owns, depending on how your hosting is set up. The region is agreed with you, which matters if your data must stay in a particular country.

Can you restore a single page or order?

Often, yes. We can restore a copy to a test environment and recover individual records or files without rolling back the whole site.

Do you back up systems other than websites?

We cover the web systems we manage: websites, stores, web applications and their databases. For office systems such as Microsoft 365 or Google Workspace we can recommend a suitable approach.

Start a project

Tell us what you’re building.

A few lines is enough. The developers who will do the work read every message.

What do you need?