Backup & Disaster Recovery
The only backup that counts is the one you have restored.
Tested restores, an offline copy, and a plan with a number on it.
Every company has a backup. Far fewer have one that has been restored recently, one that survives a ransomware attack, or a plan for the day the server room floods. We build all three and test them on a schedule, so a bad day is a bad day, not the end of the business.
- Tested restores
- Offline and immutable copies
- Recovery time you agree in writing
Example: Backup & Disaster Recovery
Sample data- Tested restores
- In place
- Example status
- Offline and immutable copies
- Reviewed
- Example status
- Recovery time you agree in writing
- On track
- Example status
Progress · illustration
What we handle
- Restores, tested on a schedule
- A copy ransomware cannot touch
- Recovery objectives in writing
What does backup and disaster recovery from Quantum include?
Backups that are tested on a schedule, an immutable copy that ransomware cannot alter or delete, and a written recovery plan that states how long it takes to get you running again. Microsoft 365 is covered too, since Microsoft does not back it up the way people assume. If the backup you already pay for holds up when we test it, we tell you so.
- Testing
- Real restores, on a schedule
- Ransomware
- Immutable offline copy
- Plan
- Written recovery target
- Covers
- Servers, PCs, Microsoft 365
How we help
Backup & Disaster Recovery, in four parts
Restores, tested on a schedule
What's included
- Daily backup verification with alerts on any missed or failed job
- Monthly restore tests: individual files, full server boot in a sandbox, mailbox recovery
- Annual disaster-recovery exercise with the owner: a scenario, a clock, and a written result
- Results reported in your quarterly business review
A copy ransomware cannot touch
What's included
- Image-based backups of servers and critical workstations with local and cloud copies
- Microsoft 365 backup: mailboxes, OneDrive, SharePoint and Teams
- Line-of-business databases and SaaS exports where the vendor allows it
- Immutable cloud storage and an offline rotation so a compromised network cannot reach the recovery copy
- Encryption in transit and at rest, keys held by you
Recovery objectives in writing
What's included
- Recovery time and recovery point objectives agreed per system and written into your plan
- Documented recovery runbook: who calls whom, what comes back first, where people work from
- Rapid server recovery to local hardware or to the cloud while replacement equipment is sourced
- Ransomware response coordinated with your cyber-insurance carrier's requirements
Whole-business recovery
What's included
- Recovery time and recovery point objectives agreed per system and written into your plan
- Documented recovery runbook: who calls whom, what comes back first, where people work from
- Rapid server recovery to local hardware or to the cloud while replacement equipment is sourced
- Ransomware response coordinated with your cyber-insurance carrier's requirements
Does any of this sound familiar?
Nobody has ever done a restore.
The backup job says success every night. That is all anyone knows.
The backup sits on the same network.
Ransomware encrypts the server, then the NAS, then the backup.
The cloud is not backed up.
Microsoft 365 and the accounting SaaS are assumed to be safe. They are not backed up by default.
There is no plan, just hope.
If the building were unusable tomorrow, nobody knows who does what first.
We make the backup real, the copy untouchable, and the plan written.
Line by line
What's actually included
Specific deliverables and cadences, so you can hold us to them.
Backup
- Image-based backups of servers and critical workstations with local and cloud copies
- Microsoft 365 backup: mailboxes, OneDrive, SharePoint and Teams
- Line-of-business databases and SaaS exports where the vendor allows it
- Immutable cloud storage and an offline rotation so a compromised network cannot reach the recovery copy
- Encryption in transit and at rest, keys held by you
Testing and monitoring
- Daily backup verification with alerts on any missed or failed job
- Monthly restore tests: individual files, full server boot in a sandbox, mailbox recovery
- Annual disaster-recovery exercise with the owner: a scenario, a clock, and a written result
- Results reported in your quarterly business review
Recovery
- Recovery time and recovery point objectives agreed per system and written into your plan
- Documented recovery runbook: who calls whom, what comes back first, where people work from
- Rapid server recovery to local hardware or to the cloud while replacement equipment is sourced
- Ransomware response coordinated with your cyber-insurance carrier's requirements
What we commit to
How fast we respond
The same published targets that cover every managed IT client.
Business hours
How fast, by how bad it is
- P1
You're down and nobody can work.
Critical outage — total business stop
- First response
- 30 minutes
- Resolution goal
- 2 hours
- P2
Something important is broken or crawling.
High impact — major degradation
- First response
- 1 hour
- Resolution goal
- 4 hours
- P3
One person needs something sorted.
Standard — individual request
- First response
- 2 hours
- Resolution goal
- 8 hours
Targets apply during business hours, Monday–Friday, 8:00am–5:00pm CT. Initial response is when a human has your ticket and has replied — not an autoresponder. Resolution goal is our target, not a guarantee; complex work sometimes runs longer, and we tell you when it will.
Nights & weekends
The phone is answered around the clock.
Call at 2am and a person picks up — not voicemail, not an offshore queue. We triage it on the spot.
- A genuine emergency gets a technician engaged that night. After-hours and emergency rates apply.
- Anything that can wait goes into the queue for the next business day, and you'll be told which it is.
- Round-the-clock coverage is available as an add-on for businesses that can't wait until morning — several of our clients run it.
Find out whether your backup would actually save you.
- A real restore of a file and a system from your current backup
- A check that the copy is isolated from ransomware
- A list of what is not backed up today
- 1.We read every message the day it comes in.
- 2.A real person replies within one business day.
- 3.A quick, no-pitch call — you decide what's next.
Questions, answered
What owners ask us first
Automated verification every day, a real restore of something every month, and a full recovery exercise once a year. Insurers and frameworks such as CMMC now ask for evidence of testing, not just of backups.
A copy stored so that nothing, including an administrator account or ransomware with that account's credentials, can alter or delete it for a set period. It is the control that makes a ransomware attack recoverable instead of a negotiation.
It depends on the system and the plan you choose, which is why we agree the number up front. Critical servers can typically be running again in hours from a local image; a full rebuild from cloud copies takes longer. The plan states the target and the annual test proves it.
You may not need to. We start by testing what you have: a restore, a check that the copy is isolated from the network, and a look at what is not covered (Microsoft 365 is the usual gap). If it holds up, we tell you so.
Yes. Backup and recovery is delivered across Northeast Wisconsin, including Green Bay, Brown County, Kewaunee County, the Fox Valley and the lakeshore, with on-site recovery from Sturgeon Bay and Algoma.
From the blog
All articlesFind out whether your backup would actually save you.
Backups that are actually tested, an offline copy ransomware cannot reach, and a written recovery plan with a number on it: how long until you are back.
No obligation. No sales pressure. Just an honest conversation.