Skip to main content
Aquika

05 / Backup & DR

Backup isn't the goal. Recovery is.

Backups are only useful if you can actually recover. We design backup and recovery around your business requirements.

Let's TalkWhat’s included

Overview

Almost every business has "backups." Far fewer have restored from them recently, know how long a full recovery would take, or have confirmed the backups would survive the same event that took out the primary systems. A backup that lives on the same network as the server it protects, with the same credentials, is not a recovery plan — it's a second copy waiting to be encrypted alongside the first.

We design backup and recovery around two plain questions: how much data can you afford to lose, and how long can you afford to be down? From there we build the appropriate tiers — local, offsite, immutable, and SaaS backup for cloud data — and, critically, we test them. Recovery objectives are set with you, documented, and revisited as the business changes.

What you get

Outcomes, not a parts list.

  • 01

    Designed around your tolerance

    Recovery point and recovery time objectives set with the business, then engineered — not assumed.

  • 02

    Isolated and immutable

    Offsite and immutable copies that ransomware, mistakes, and hardware failure can't reach.

  • 03

    Cloud data included

    Microsoft 365 and Google Workspace data backed up independently of the platform's own retention.

  • 04

    Tested, not assumed

    Scheduled restore tests and recovery drills so you know it works before you need it.

  • 05

    A real plan

    Documented recovery procedures, priorities, and contacts — so an outage is a process, not a scramble.

What's included

Capabilities

The specific things we design, build, and manage under this service. If something you need isn't listed, ask — this is representative, not exhaustive.

  • Backup strategy and recovery objective (RPO / RTO) planning
  • Local backup infrastructure and appliances
  • Offsite and cloud backup targets
  • Immutable and air-gapped backup tiers
  • Server and virtual machine image backup
  • Microsoft 365 and Google Workspace backup
  • Endpoint and file-level backup
  • Database and application-aware backup
  • Disaster recovery planning and documentation
  • Restore testing and recovery drills
  • Backup monitoring and reporting
  • Recovery site and failover options where warranted

Questions

Common questions

Isn't Microsoft or Google already backing up our email and files?

They keep the service running and offer limited retention, but they are explicit that protecting your data from deletion, ransomware, and user error is your responsibility. A separate backup of cloud data is inexpensive insurance and something we recommend for nearly every business.

How fast could we recover after a serious failure?

That depends entirely on how the environment is designed, and it's exactly the question we design around. We'll set realistic recovery objectives with you and build to meet them; we don't promise recovery times that haven't been engineered and agreed in writing.

We already have a backup product. Do we need to replace it?

Not necessarily. We'll assess what's in place: what it protects, where the copies live, whether they're isolated, and when they were last restored. Sometimes the fix is configuration and testing; sometimes it's a change of approach.

Related

Often paired with

Let's figure out what your technology needs.

Tell us what's going on — a project, a problem, or a general sense that things could be better. We'll give you a straight answer about what we'd do and whether we're the right fit.

Let's Talk