DTL Backup & Disaster Recovery
Talk to an engineer
Backup & disaster recovery · AWS · Microsoft Azure · Google Cloud

Backups you’ve tested. Recovery you can count on.

We back up your servers, databases, files and Microsoft 365, protect the copies from ransomware, and set up disaster recovery that matches how long each system can be down. Then we test restores on a schedule, so you know they work before you need them.

Book a recovery assessment See what we cover
  • RTO · RPORecovery targets agreed for each system, then tested
  • 265+Cloud environments managed by our team
  • 3 cloudsAWS, Microsoft Azure and Google Cloud

The reality

When did you last restore a backup?

Most companies have backups. Far fewer know how long a recovery would take, or whether it would work at all. Open a card to see what we do about each gap.

Talk it through with an engineer

Backups that have never been restored

Jobs run every night and show green. Nobody has checked a restore actually works.

What we do

We test restores on a schedule and send you a report: what was restored, how long it took and that it worked.

Ransomware can reach the backups

Backups sit on the same network, in the same account, with the same admin passwords.

What we do

Locked, immutable copies in a separate account, which attackers can’t change or delete.

A DR plan nobody has rehearsed

The plan was written for an audit. Half the steps are out of date.

What we do

We turn the plan into tested runbooks and rehearse failover with your team.

Recovery targets nobody agreed

IT thinks a day is fine. The business thinks an hour. Nobody wrote it down.

What we do

We agree recovery time and data-loss targets for each system with the business, then design to them.

One region, one account, one copy

Everything, backups included, lives in one place that can fail together.

What we do

Copies in a second region and a separate account, kept in India where you need it.

Microsoft 365 isn’t backed up

Mail, OneDrive and SharePoint are assumed safe because they’re in the cloud.

What we do

We back up Microsoft 365 and restore deleted or encrypted mail and files when you need them.

What we cover

Five areas. One recovery plan.

Backup, disaster recovery, ransomware protection, Microsoft 365 and on-premises systems, on AWS, Microsoft Azure and Google Cloud. Pick an area to see what’s included and the tools we use.

Book a recovery assessment
01 · Backup for servers and databases

Backups that run, and restores that work.

Every system backed up to a policy you agree. Policies set by how important each system is, kept in Indian regions, and tested on a schedule.

ClassifyBack upRetainTestReport
Backup policiesFrequency and retention set by how critical each system is.
Servers and VMsSnapshots and image backups, application-consistent where it matters.
DatabasesAutomated backups and point-in-time restore for managed and self-run databases.
Files and object storageVersioning and backups for file shares and buckets.
Restore testsRestores tested on a schedule, with a report each time.
Cost-aware retentionOlder copies moved to cheaper archive tiers automatically.
Tools we use
AWS
  • AWS Backup
  • Amazon RDS automated backups
  • Amazon S3 versioning
  • Amazon S3 Glacier
Microsoft Azure
  • Azure Backup
  • Azure SQL automated backups
  • Azure Blob versioning
  • Azure archive storage
Google Cloud
  • Backup and DR Service
  • Cloud SQL backups
  • Object Versioning
  • Archive storage
02 · Disaster recovery

Back up and running, in the time you agreed.

Recovery designed around your targets. We match the DR approach to each system’s recovery targets, so you don’t pay for more than you need.

Set targetsDesignReplicateRehearseFail back
Recovery targetsRecovery time (RTO) and data-loss (RPO) targets agreed for each system.
The right DR patternBackup and restore, pilot light, warm standby or multi-site, system by system.
Cross-region replicationServers and data copied to a second region.
Infrastructure as codeThe recovery environment rebuilt from code, so it matches production.
DR drillsFailover rehearsed and timed against your targets.
Fail backA tested way back to the primary region once it’s healthy.
Tools we use
AWS
  • AWS Elastic Disaster Recovery
  • Cross-region replication
  • Aurora global databases
  • AWS CloudFormation
Microsoft Azure
  • Azure Site Recovery
  • Geo-redundant storage
  • Azure SQL failover groups
  • Bicep
Google Cloud
  • Backup and DR Service
  • Dual-region Cloud Storage
  • Cloud SQL cross-region replicas
  • Infrastructure Manager
03 · Ransomware protection

Recover even when everything else is encrypted.

Copies attackers can’t touch. Ransomware goes after backups first. We keep locked copies in a separate account, watch for tampering and rehearse a clean recovery.

IsolateLockWatchRecover clean
Immutable backupsCopies locked for a set period, so they can’t be changed or deleted.
Separate backup accountBackups held away from production, with their own access.
MFA and least privilegeStrong controls on who can change backup settings.
Tamper alertsAlerts when backups are deleted, policies change or jobs stop.
Clean-room recoveryRestore into an isolated environment and check it before going live.
Recovery runbooksStep-by-step plans for a ransomware event, rehearsed with your team.
Tools we use
AWS
  • AWS Backup Vault Lock
  • AWS Organizations
  • Amazon GuardDuty
  • AWS CloudTrail
Microsoft Azure
  • Azure Backup immutable vaults
  • Multi-user authorisation
  • Microsoft Defender for Cloud
  • Azure Monitor
Google Cloud
  • Backup vaults
  • Bucket Lock
  • Security Command Center
  • Cloud Audit Logs
04 · Microsoft 365 backup

Your Microsoft 365 data, recoverable.

Mail, OneDrive, SharePoint and Teams, backed up. Microsoft keeps the service running. Your data is your responsibility. We back it up and restore it when you need it.

Back upRetainRestore
Exchange Online mailMailboxes backed up and restorable item by item.
OneDrive and SharePointFiles and sites restorable to a point in time.
Teams dataChats and files backed up where supported.
Leavers’ dataData kept after someone leaves, for as long as you need.
Fast restoresDeleted or encrypted mail and files brought back on request.
Restore testsSample restores tested and reported.
Tools we use
AWS
  • Amazon S3 as a backup target
  • AWS KMS encryption
Microsoft Azure
  • Microsoft 365 Backup
  • Azure Blob storage
  • Microsoft Purview retention
Google Cloud
  • Cloud Storage as a backup target
  • Cloud KMS
05 · On-premises and hybrid

Off-site copies for what still runs in your office.

Office servers backed up to the cloud. File servers, Tally and on-premises databases copied to the cloud automatically, with versions and archives.

ConnectCopyVersionArchive
File serversShared folders copied off-site automatically.
Tally and business appsData backed up on a schedule, encrypted.
On-premises databasesDatabase backups shipped to cloud storage.
VersioningEarlier copies kept, so a bad change or infection can be undone.
Archive tiersLong-term copies in low-cost archive storage.
DR to the cloudOffice servers recoverable in the cloud if the office is down.
Tools we use
AWS
  • AWS Storage Gateway
  • Amazon S3
  • Amazon S3 Glacier
  • AWS Elastic Disaster Recovery
Microsoft Azure
  • Azure Backup (MARS agent)
  • Azure File Sync
  • Azure archive storage
  • Azure Site Recovery
Google Cloud
  • Backup and DR Service
  • Cloud Storage
  • Storage Transfer Service
  • Archive storage

We pick tools for your setup and work with any backup tools you already use.

What you get

Recovery you can prove, not just hope for.

What changes when backups and recovery are designed, tested and reported.

Proof that it works.

Every restore test and DR drill is timed and reported, so you can show your board, customers and auditors exactly how fast you can recover.

TodayGreen backup jobs and hope
With usTested restores, timed drills

Ransomware resilience

Locked copies attackers can’t reach.

Targets that match the business

Recovery time and data loss agreed per system.

No second data centre

Pay for standby capacity only where you need it.

Evidence for auditors

Restore and drill reports ready for audits and regulators.

Data kept in India

Backups and recovery regions in India where you need it.

Find out how fast you could recover.

A recovery assessment checks your backups, tests a restore and compares the result with what the business needs.

Book a recovery assessment

Why recovery fails

Backups fail when nobody tests them.

These are the reasons recoveries go wrong, usually discovered on the worst possible day. Here’s how we prevent each one.

The riskA backup that won’t restore
How we prevent it

Restores are tested on a schedule, so you find out in a test, not an emergency.

The riskBackups encrypted along with production
How we prevent it

Immutable copies in a separate account, with their own access controls.

The riskA DR site that has drifted
How we prevent it

The recovery environment is built from the same code as production.

The riskRecovery steps nobody remembers
How we prevent it

Runbooks written, rehearsed and kept up to date.

The riskRetention that’s wrong
How we prevent it

Retention set to policy and regulation, with old copies moved to archive.

The riskThe one person who knew has left
How we prevent it

Drills include your team, so the knowledge isn’t in one head.

Drills that don’t disrupt. DR drills run in isolated environments or agreed windows, so testing never causes the outage it’s meant to prevent.

Book a recovery assessment

How we work

From first check to recovery you’ve rehearsed.

The same method on AWS, Azure and Google Cloud, for one critical system or your whole estate.

Book a recovery assessment
  1. Stage 01 · Know where you stand

    Assess

    We list what you run, how it’s backed up today and what the business needs.

    What happens
    1. 1.1Systems and data listed, with owners
    2. 1.2Current backups, retention and copies checked
    3. 1.3A sample restore tested
    4. 1.4Ransomware exposure of backups reviewed
    5. 1.5Business impact of downtime discussed
    You get
    • A recovery gap report
    • A restore test result
    Your part

    An hour with IT and someone from the business.

    Your safety net

    Read-only, except for one test restore into an isolated space.

  2. Stage 02 · Agree targets and the approach

    Design

    Each system gets recovery targets and a matching DR pattern.

    What happens
    1. 2.1RTO and RPO agreed for each system
    2. 2.2DR pattern chosen per system
    3. 2.3Backup frequency and retention set
    4. 2.4Second region and backup account planned
    5. 2.5Cost of each option shown in rupees
    You get
    • A recovery design
    • Costs per option
    Your part

    Agree the targets and the budget.

    Your safety net

    Nothing is built until you’ve agreed the design.

  3. Stage 03 · Put protection in place

    Build

    We set up backups, locked copies, replication and runbooks.

    What happens
    1. 3.1Backup policies applied to every system
    2. 3.2Immutable copies in a separate account
    3. 3.3Replication to a second region
    4. 3.4Recovery environment defined in code
    5. 3.5Runbooks written for each scenario
    You get
    • Backups and DR in place
    • Runbooks
    Your part

    Approve changes to production systems.

    Your safety net

    Changes are tested first and logged.

  4. Stage 04 · Prove it works

    Test

    We test restores and rehearse failover, and time both against your targets.

    What happens
    1. 4.1Restore tests for each tier of system
    2. 4.2A full DR drill with your team
    3. 4.3Recovery time and data loss measured
    4. 4.4Gaps fixed and retested
    5. 4.5Results reported to you
    You get
    • Restore test reports
    • A DR drill report
    Your part

    Join the drill and sign off the result.

    Your safety net

    Drills run in isolation or in agreed windows.

  5. Stage 05 · Keep it working

    Operate

    Backups are watched, restores are retested and the plan stays current.

    What happens
    1. 5.1Backup jobs and alerts watched
    2. 5.2Restore tests on a schedule
    3. 5.3DR drills repeated each year, or as agreed
    4. 5.4Runbooks updated as systems change
    5. 5.5A monthly report
    You get
    • A monthly report
    • Evidence for audits
    Your part

    Tell us about new systems and changes.

    Your safety net

    Everything is documented, so your team can run it too.

Disaster recovery patterns

Pay for the recovery each system needs.

Not every system needs instant failover. We choose a pattern per system, from the cheapest to the fastest.

Backup and restore

Rebuild from backups when you need to. Lowest cost.

  • Typical recovery time: hours
  • Data loss: since the last backup
  • Good for: internal tools, archives, test systems

Pilot light

Data replicated; core systems ready to switch on.

  • Typical recovery time: tens of minutes to hours
  • Data loss: minutes
  • Good for: business apps that can wait a little

Warm standby

A scaled-down copy running in a second region.

  • Typical recovery time: minutes
  • Data loss: seconds to minutes
  • Good for: customer-facing apps and ERPs

Multi-site

Two regions running live, sharing the load.

  • Typical recovery time: near zero
  • Data loss: near zero
  • Good for: payments and systems that can’t stop

Typical ranges, not promises. Actual recovery times depend on your systems and data. We agree targets per system and prove them in a drill.

Help me choose

Proof

Recovery that’s set up and working.

Stories from clients who agreed to be named, or asked us not to name them. Every detail is from the original case study.

Ask about a setup like yours
  • 265+cloud environments managed
  • 30+certified cloud engineers
  • 30 daysdatabase backups for Devine Globe
  • 3 of 3public clouds
AWS
Dynawiild Engineering · Manufacturing

Business data copied to Amazon S3 automatically, for disaster recovery

Data only in the officeEncrypted off-site copies

  • SyncAutomatic, off-site
  • VersionsEarlier copies kept
  • ArchiveS3 Glacier
Read the story
AWS
Devine Globe · Web application

Automated backups and audit logs for a production app

Limited backup reliabilityBackups and logs on AWS

  • Database backups30-day retention
  • Audit logsKept 1 year
  • RecoveryFaster, with central logs
Read the story
AWS
SMB on AWS · Production workload

Backups that are monitored, not assumed

Inconsistent backup practicesAutomated, monitored backups

  • BackupsAutomated for EC2 and databases
  • MonitoringBackup and retention checks
  • ReadinessStronger audit readiness
Read the story

Full stories are on our Resources page. The SMB client isn’t named on the original case study.

AWS Advanced Tier Services Partner badge

AWS Advanced Tier Services PartnerAlso: AWS Partner with SMB Competency

Microsoft Solutions Partner for Cloud and AI Platforms badge

Microsoft Solutions Partner for Cloud and AI PlatformsAlso: Infrastructure (Azure)

Google Cloud Partner badge

Google Cloud Partner

Why DevOps TechLab

Engineers who test the recovery, not just the backup.

One team for backup, disaster recovery and the cloud underneath, on all three clouds.

Meet a recovery engineer
What it often looks likeWith DevOps TechLab
ProofGreen backup jobsRestore tests and DR drills, timed and reported
TargetsOne plan for every systemRecovery targets and a DR pattern per system
RansomwareBackups on the same networkLocked copies in a separate account
DR siteBuilt by hand, drifts over timeBuilt from the same code as production
CostA second data centre for everythingStandby capacity only where it’s needed
Microsoft 365Assumed safeBacked up and restorable
CloudsOne cloudAWS, Azure and Google Cloud
Your teamHears about the planRehearses it with us

Where this fits

One stage of the journey. Here’s what comes next.

Recovery sits alongside security and day-to-day running.

  1. 01
    Before

    Cloud security & compliance

    Guardrails and monitoring that make recovery less likely to be needed.

    Explore

  2. 02
    You are here

    Backup & disaster recovery

    Backups you’ve tested and recovery you’ve rehearsed.

    This page

  3. 03
    Next

    Managed cloud services

    Backups watched and restores tested as part of day-to-day running.

    Explore

  4. 04
    Next

    Cost optimisation (FinOps)

    Keep backup storage and standby costs in check.

    Explore

FAQ

Backup and recovery, answered.

Straight answers on backups, disaster recovery, ransomware and cost. If yours isn’t here, ask us.

Ask a question

Cloud providers keep their services running, but your data, settings and accidental deletions are usually your responsibility. Most services need backups configured, and Microsoft 365 is no exception.

It depends on how much data each system can afford to lose. Critical databases may need continuous backups; internal tools may be fine nightly. We agree it per system.

We test it. Restores run on a schedule and every test is reported: what was restored, how long it took and whether it worked.

Yes. We back up Exchange Online mail, OneDrive, SharePoint and Teams data where supported, and restore it when you need it.

Recovery assessment

Find out how fast you could really recover.

An engineer reviews your backups and DR setup, tests a sample restore and compares the result with what the business needs. No obligation to work with us.

  1. 01What you have todaySystems, backups, retention and copies.
  2. 02A test restoreOne sample restore, timed, into an isolated space.
  3. 03Ransomware exposureWhether attackers could reach your backups.
  4. 04Targets and a planRecovery targets per system and the right DR pattern.