Backup & disaster recovery services

Disaster recovery that works on the worst day

From preventing the outage to getting every system back: Digital Edge designs, runs and tests your backup and disaster recovery, and steps in at whatever stage you are in today, including in the middle of an incident.

Immutable backups Tested recovery AWS & Azure cloud DR 24×7 NOC

Recovery time by tier

Example targets (RTO, hours) from a recovery matrix

Illustration; your targets come from your business impact analysis

What is disaster recovery?

Disaster recovery (DR) is the plan, technology and practice that bring your IT systems and data back after a disruption: ransomware, a cloud or data center outage, a failed change, human error or a natural disaster. Backup keeps copies of data; DR decides how fast each system must return (the recovery time objective, RTO), how much data you can afford to lose (the recovery point objective, RPO), where systems run in the meantime, and who does what. Disaster recovery as a service (DRaaS) means a provider runs and tests all of it for you; our disaster recovery services cover every step, from the first analysis to the last restore test.

96%of ransomware attacks go after the backups (Veeam)
10%of attacked organizations recovered more than 90% of their data (Veeam, 2025)
$300K+per hour of downtime for over 90% of mid-size and large firms (ITIC, 2024)
76%needed more than 100 days to fully recover from a breach (IBM, 2025)
Recovery from any stage

Where are you today?

Most companies are somewhere in between. Pick your situation: this is where we start.

Starting from zero

No reliable backups or a plan nobody has seen. We put the essentials in within weeks, then build up.

  • Off-site, immutable backups of servers, databases and Microsoft 365 within the first weeks
  • A business impact analysis: critical systems, cost of downtime, RTO and RPO for each
  • MFA and separate credentials for the backup platform
  • A one-page emergency runbook while the full plan is written

Backups, but no plan

Copies exist, but nobody knows how long a restore takes or what comes back first.

  • Recovery matrix: every system with its tier, RTO, RPO, owner and dependencies
  • Gap check of the backups against the matrix: frequency, retention, immutability, coverage
  • A secondary site: cloud DR in AWS or Microsoft Azure, or DR into our private cloud
  • Runbooks your team can follow, with contact trees and chain of command

A plan that was never tested

An untested plan is a hypothesis. We prove it, fix what breaks and keep the proof.

  • Restore tests of critical systems, with measured RTO and RPO
  • Tabletop exercise with management: decisions, communications, insurer and legal
  • Full failover test to the DR site, then failback
  • Reports and evidence for auditors, insurers and the board

We are down right now

Ransomware, a failed update, a lost site: call us. Our incident response and recovery teams work together from the first hour.

  • Containment first, so the restore does not bring the attacker back
  • Choosing a clean restore point: scanning and recovery into an isolated (clean-room) network
  • Restoring in business priority order, with status updates for management
  • Evidence preserved for insurers, regulators and law enforcement

Call (718) 370-3353 now Incident response

After an incident

Systems are back; now make sure it cannot happen the same way again.

  • Root cause and lessons learned, with a prioritized fix list
  • Hardening of the backup platform and the paths the attacker used
  • Updated plan, recovery matrix and runbooks
  • 24×7 monitoring (MDR and NOC) so the next attempt is caught early
A to Z

Everything between “nothing has happened yet” and “everything is back”

1. Business impact analysis

Critical processes and systems, the cost of an hour of downtime, and the maximum tolerable outage.

2. Recovery objectives

RTO and RPO per system, grouped into tiers and agreed with the business.

3. Prevention

Patching, MFA, segmentation, 24×7 monitoring of servers and backup systems: most disasters are stopped before they start.

4. Backup architecture

The 3-2-1-1-0 rule: three copies, two media, one off-site, one immutable or air-gapped, zero errors in restore tests.

5. DR site & replication

Cloud DR in AWS or Azure, DR into our private cloud, or replication between your sites, sized to each tier.

6. Runbooks & roles

Who declares a disaster, who calls whom, what comes back first, where the keys and passwords are.

7. Testing

Restore tests every quarter, a yearly failover and tabletop exercise, with reports your auditors accept.

8. Recovery & return

Clean restore, verification, failback to production and lessons learned, documented end to end.

Ransomware

Attackers go after the backups first

Ransomware crews look for the backup console before they encrypt anything, because deleting backups is how they force a payment. Recent incident reports describe attackers wiping backup catalogs and cloud storage so the business cannot recover. We design backups to survive that.

  • Immutable and air-gapped copies that admin accounts cannot delete
  • Separate credentials and MFA for the backup platform, outside the main domain
  • 24×7 alerts on failed jobs and deletion attempts, watched by our NOC and SOC
  • Malware scanning of restore points and clean-room recovery before production
Review my ransomware recovery
1immutable copy no admin account can delete (3-2-1-1-0 rule)
24×7monitoring of backup jobs and deletions
≤15 minexample RPO for tier-1 systems
2×a year: minimum full restore tests
Recovery matrix

Not every system needs the same recovery

Spending follows the business impact. A typical matrix looks like this; yours comes from the business impact analysis.

TierExamplesRTO (back within)RPO (data lost at most)How we usually do it
Tier 1: mission criticalERP, EHR, payment and trading systems, identityUnder 1 hourUnder 15 minutesContinuous replication to a warm standby in AWS, Azure or our private cloud
Tier 2: business criticalEmail, file shares, CRM, line-of-business apps4–8 hours1–4 hoursFrequent backups with pre-built recovery templates in the DR site
Tier 3: importantInternal tools, reporting, test systems24 hours24 hoursDaily immutable backups, restored on demand
Tier 4: archiveHistorical data, retired systemsDaysWeeklyLow-cost cloud archive with long retention
Cloud DR on AWS and Azure

A second site in the cloud, without running a second data center

Digital Edge uses an AWS or Microsoft Azure region as your recovery site: systems replicate continuously, recovery resources start only when needed, and tests are simple to repeat. No second building, no idle hardware. We pick the cloud you already run on, or the one that fits your data residency and licensing.

AWSMicrosoft Azure
Replication and failoverAWS Elastic Disaster RecoveryAzure Site Recovery
Ransomware-proof backup copiesS3 Object Lock, AWS Backup vault lockImmutable Azure Backup vaults, immutable Blob storage
Backup softwareVeeamVeeam
Microsoft 365 backupSeparate backup of Exchange, OneDrive, SharePoint and Teams
Partner statusAWS Level 1 MSSPMicrosoft Solutions Partner, certified Azure team
  • Recovery matrix maintained across its whole lifecycle
  • Offsite backup with Veeam to AWS or Azure
  • Scheduled DR tests with reports for auditors
  • Runbooks your team can follow

Download: Digital Edge DR in AWS (PDF)

Private cloud DR

Recover into Digital Edge infrastructure in New York when data must stay in a dedicated environment.

Microsoft 365 and SaaS backup

Mailboxes, OneDrive, SharePoint and Teams backed up separately, because SaaS retention is not a backup.

Watched by our NOC

Backup jobs, replication lag and storage health monitored 24×7 with tickets and fixes, not just reports.

Free check

How ready is your disaster recovery?

Ten questions, about three minutes. You get a readiness score and the first gaps to close right away.

FAQ

Disaster recovery FAQ

What is the difference between backup and disaster recovery?

Backup is a copy of your data. Disaster recovery is everything needed to run the business again: recovery objectives, a place for systems to run, runbooks, people and tested procedures. You can have perfect backups and still be down for weeks without DR.

What are RTO and RPO?

The recovery time objective (RTO) is how quickly a system must be back after a disruption. The recovery point objective (RPO) is how much data, measured in time, you can afford to lose. An RTO of 4 hours and an RPO of 15 minutes means the system is back within 4 hours with at most 15 minutes of data missing.

How often should disaster recovery be tested?

At least once a year for the full plan, and more often for critical systems: we recommend restore tests every quarter and a failover test and tabletop exercise every year. NIST SP 800-34 and most frameworks expect regular, documented testing.

Can you help if we have been hit by ransomware right now?

Yes. Call (718) 370-3353. Our incident response team contains the attack while recovery engineers identify clean restore points and bring systems back in business priority order.

What is an immutable backup?

A backup that cannot be changed or deleted for a set period, even with administrator credentials. It is the main protection against ransomware crews, who try to delete backups before encrypting servers.

Do we need to back up Microsoft 365?

Yes. Microsoft keeps the service running, but retention and the recycle bin are not a backup: deletions, ransomware syncs and expired retention can remove data permanently. We back up mailboxes, OneDrive, SharePoint and Teams separately.

What is disaster recovery as a service (DRaaS)?

DRaaS means a provider runs your recovery site, replication, monitoring and testing as a managed service. With Digital Edge the recovery site can be AWS, Microsoft Azure or our private cloud, and the service includes runbooks and test reports.

How much does disaster recovery cost?

It depends on the recovery objectives. Tier-1 systems with minutes of RPO cost more than daily backups of archives, so we size each tier to its business impact. Cloud DR keeps costs down because standby resources only run during tests and real recoveries.

Explore next

Keep exploring

Insights

Latest from Edge Insights

ARTICLE
ArticleCloud & infrastructure

Hurricane Florence: A Message from the Digital Edge Disaster Recovery Team

By tomorrow, Hurricane Florence is expected to make landfall in North Carolina, South Carolina and Virginia. With strong winds predicted up to 130 mph, the storm should…

Digital Edge··3 min
Digital Edge Disaster Recovery Team Provides IT Assistance to Businesses Impacted by Hurricane Damage
ArticleCloud & infrastructure

Digital Edge Disaster Recovery Team Provides IT Assistance to Businesses Impacted by Hurricane Damage

In the wake of these storms, Digital Edge Team is here to provide emergency technology recovery services, for any IT distressed company who is in need of immediate assis…

Stacey PetrovStacey Petrov··2 min
ARTICLE
ArticleCloud & infrastructure

Hurricane Irma: A Message from the Digital Edge Disaster Recovery Team

By tomorrow, Hurricane Irma is expected to make landfall in Florida. With storm surges predicted up to 11 feet, the storm could cause catastrophic damage to those in its…

Digital Edge··3 min

More insights

Find out how long your recovery would really take

Book a 30-minute call. We review your backups and recovery objectives and show you the first three fixes, whatever stage you are in.