Managed backup and disaster recovery

When something goes wrong, you are back up before it becomes a crisis.

Backups that are checked every day, copies kept offsite, ready replicas for the systems you cannot do without, and a recovery plan written down before you need it. Restoring over live data always waits for a person.

Checked every dayOffsite copiesRestores approved by a person
Backup · morning checktypical activity
$ backup watch --all

Illustrative. These are the kinds of steps taken; names and times are made up.

What is protected

Everything you would miss the morning after.

Backup and disaster recovery are different jobs. Backup gets your data back. Recovery gets your business running again. We plan for both.

Servers and virtual machines

Whole-machine backups, so a failed server can come back as it was, not rebuilt from scratch.

Microsoft 365 data

Mail, files and Teams backed up separately from Microsoft, so an old email or a deleted site can be recovered.

Files, databases and shares

The data your business actually runs on, found and included, not assumed.

Offsite copies

At least one copy lives somewhere else, so a fire, a flood or ransomware in the office cannot take everything.

Ready replicas

For the systems that cannot wait, a copy kept current at a second location, ready to start.

A written recovery plan

Who does what, in what order, with the phone numbers, written down and rehearsed before the bad day.

How much downtime can you take?

Match the protection to the system.

Not everything needs the same level. Paying for minutes on a system that can wait a day is waste. Pick one to see what it usually means.

How long can it be down?

Down for a day would be painful, not fatal.

Usually that means: Backup and restore. Each system gets its own target, agreed with you.

Regular backups kept in more than one place, one of them offsite.
Backup jobs checked every day, and a failure becomes a ticket, not a surprise.
If it fails, we restore onto replacement hardware or a virtual machine.
Typical for: file shares, archives, back-office systems.
General guide. We set recovery targets system by system, after we read what you run.

Watch a recovery

Four bad days, step by step.

Reading, checking and preparing happen on their own. Anything that overwrites live data or switches servers stops for a person.

Request · accounting folder

Someone deletes a folder of client files.

The fastest recovery there is: put back just what was lost, from the last good copy.

Press “Watch it work” to see each step, in order.

Illustrative walk-through. Names, times and machines are made up; the order of steps and the approval gate are how it really works.

Why it works

The difference between having backups and being protected.

Checked every day

Backup jobs are read every morning. A failure becomes a ticket with the log attached, and a ticket closes only when a later run proves it is fixed.

We look for what is missing

A backup report only lists what is backed up. We also look for what is not: a new data drive, a new server, a database somebody added.

Restores, not just backups

A backup you have never restored is a hope. Recovery is planned, and tried, so you know how it behaves.

Contained before restored

After an attack, the damaged machine is cut off first and restored from a clean point. Nothing is deleted from it.

The standard we build to

More than one copy, in more than one place, tested.

Most lost backups fail the same way: everything sat in one place, one account or one building. The plan is built so one mistake, one attacker or one disaster cannot take every copy.

BACKUP PLANwhat we build to
3 copies
the live data and two backups
2 kinds of storage
so one failure cannot take both
1 copy offsite
away from the building and the network
Out of reach
at least one copy an attacker cannot change
Checked daily
job results read, failures ticketed
Restore tested
so you know it works before you need it
Recovery targets are set system by system, after we read what you run.

Find out what you could not get back.

Book a recovery review. We will list what is backed up, what is not, and how long each system could be down.

(888) 851-0237