Home / Business IT / Infrastructure / Backup & DR
Backup & Disaster Recovery

Backup that actually restores. DR that actually works.

3-2-1 backup architecture, immutable storage for ransomware protection, off-site copies, tested restore procedures, written DR plans. Veeam, Nakivo, Vinchin, Acronis and open-source options — chosen for your environment. Because a backup that doesn't restore is worse than no backup.

The uncomfortable truth

Most businesses discover their backup didn't work — during the disaster.

"We have backup" is different from "we have tested, working, current backup that will actually restore." In real disaster scenarios we've seen: backups that hadn't run in months without alerts, backups that ran but produced corrupted/unrestorable files, backups on the same server as production (destroyed together), backup credentials compromised alongside the domain during ransomware. Structured backup + DR prevents all of these.

3-2-1 backup architecture

3 copies (production + 2 backups), 2 different media types (disk + cloud/tape), 1 off-site. Modern extension: 3-2-1-1-0 (1 immutable copy + 0 errors verified). Baseline for meaningful protection — anything less is inadequate for business data.

Immutable backup storage

Backup copies that can't be modified or deleted for their retention period — even by admins with credentials. Object storage with object lock, immutable ZFS snapshots, S3 with governance retention. Primary defense against ransomware encrypting your backups.

Off-site replication

Secondary copy at physically separate location. Cloud object storage (S3, Azure Blob, Backblaze B2, Wasabi) or secondary site. Protects against site-level disasters — fire, flood, theft, extended power failure.

Cloud services backup

M365 email, OneDrive, SharePoint, Teams — needs explicit backup. Same for Google Workspace. Microsoft/Google preserve data per service terms, not indefinitely against admin errors or ransomware. Third-party backup for these is standard.

Tested restore procedures

Regular verification that backups actually restore to alternative locations. Integrity checks, spot-check restore of random files, quarterly full-system restore exercises. Discovery of backup failures during test, not during disaster.

Written DR plan

Documented recovery procedures — step-by-step actions per scenario, RTO/RPO per system, contact tree, alternate infrastructure. Rehearsed periodically. Plan that works when needed because it's been used before.

Backup platforms

Choosing backup software.

Veeam Backup & Replication

Industry standard for VMware, Hyper-V, physical servers, cloud services (M365). Most mature feature set, best documentation, strongest ecosystem. Higher cost but best-in-class capability. Standard choice for larger environments.

Nakivo Backup & Replication

SMB-friendly, competitive pricing. Good VMware/Hyper-V/Proxmox/physical/M365/Google Workspace coverage. Solid feature set for the cost. Popular choice for growing SMBs.

Vinchin Backup

Competitive alternative with strong virtualization support (VMware, Hyper-V, Proxmox, Xen, RHV). Good value for virtualization-heavy environments. Growing feature set for physical and cloud.

Acronis Cyber Protect

Integrated backup + security. Combines traditional backup with anti-ransomware, endpoint protection. Different value proposition — one product for backup + security instead of separate tools.

Open-source alternatives

Bacula, Restic, Borgbackup, Kopia — capable open-source options for cost-sensitive environments or specific requirements. Require more setup expertise but zero licensing cost. Often combined with commercial for specific tiers of the backup strategy.

Common scenarios we prepare for

What DR planning actually protects against.

Ransomware

The biggest current DR scenario. Immutable backup targets, isolated backup credentials, tested restore paths. Multiple recent examples of businesses saved by proper backup — and destroyed by inadequate backup.

Hardware failure

Server dies, RAID array fails catastrophically, storage system loses data. Restore to alternative hardware or new hardware. RTO depends on backup architecture and restore infrastructure availability.

Data corruption / user error

Accidental deletion of critical files, corrupt database, user error on shared folders. Restore from point-in-time snapshot. Common scenario — happens more often than dramatic disasters.

Site disaster

Fire, flood, extended power outage, physical theft. Off-site backup + alternate infrastructure recovery. Lower probability but severe impact — off-site copies are what save the business.

Cloud service outage

M365 outage, Google Workspace outage, ISP outage. Backup accessibility during cloud outages, alternate connectivity, offline access to critical data.

Compliance retention

Regulated sectors — legal, healthcare, finance — need specific retention periods, audit trails, secure deletion capabilities. Compliance-aware backup architecture with proper documentation.

Frequently asked

Common questions.

What's the difference between backup and disaster recovery?

Backup — copies of data that can be restored. Disaster recovery — complete strategy for recovering business operations after a serious incident (fire, flood, ransomware, hardware failure). DR includes backups plus recovery infrastructure, procedures, tested restoration processes. Backup without a DR plan is just half the answer.

What is the 3-2-1 backup rule?

3 copies of your data (production + 2 backups), on 2 different media types (e.g., disk + cloud), with 1 copy off-site. Baseline standard for meaningful data protection. Modern variant is 3-2-1-1-0: adds 1 immutable copy (ransomware protection) and 0 errors verified via test restore. What we implement.

What backup software do you deploy?

Enterprise-grade: Veeam (industry standard, extensive features, VMware/Hyper-V/physical), Nakivo (SMB-friendly, good VMware/Hyper-V/M365 coverage), Vinchin (competitive pricing, good virtualization support), Acronis (integrated with security). Open-source options: Bacula, Restic, Borgbackup for cost-sensitive scenarios. Choice based on environment.

How often should we back up?

Depends on data change rate and RPO (Recovery Point Objective — how much data you can afford to lose). Typical business file server: nightly backup, minimum. Databases and email: multiple times daily or continuous. VMs: nightly to hourly. Structured backup schedule aligned with actual business RPO.

What about ransomware?

Ransomware specifically targets backup systems — attackers encrypt backups too. Defense: immutable backup targets (can't be modified/deleted for retention period), air-gapped or off-site copies, credentials for backup system isolated from Windows domain, tested restore procedures. If backup falls to ransomware, DR falls to it too.

Do you test restores?

Yes — this is critical and often skipped elsewhere. Regular test restores to alternative locations verify backups actually work. Untested backup = maybe a backup. We've seen businesses discover during disasters that their "backups" for months were failing silently. Backup verification is a distinct service, not just backup running.

What's your DR planning approach?

Written DR plan documenting: RTO (Recovery Time Objective) and RPO per system, recovery procedures with step-by-step actions, contact list and escalation, alternate site or infrastructure, communication plan for staff and customers, tested restore exercises. The plan actually works when needed because we've rehearsed it.

Do you cover cloud services backup too?

Yes. M365 and Google Workspace need explicit backup — Microsoft and Google preserve data per their service terms, but not indefinitely, and not against admin-error or ransomware scenarios. Backing up cloud email, OneDrive/Drive, SharePoint, Teams — with dedicated tools like Veeam for M365 or Nakivo for M365/Google Workspace.

Related services

Other infrastructure services.

Get in touch

Talk to Priyank directly.

Call, WhatsApp, or request a free IT assessment. Business enquiries typically get a same-day response.