Azure Disaster Recovery for Mid-Market: RTO and RPO Benchmarks 2026

Azure Disaster Recovery: RTO and RPO Benchmarks for Mid-Market 2026

Most mid-market companies have a disaster recovery plan. Few have tested it. Fewer still know what their actual RTO and RPO are under realistic failure scenarios. This post covers Azure DR architecture, realistic targets by application tier, and what it actually costs.

RTO and RPO Targets by Application Tier

Tier 1 (Mission Critical): ERP, payment processing, customer-facing web applications. Target RTO: 1-4 hours. Target RPO: 15 minutes. Azure approach: Active-passive with automated failover, Azure Site Recovery with 15-minute replication frequency, geo-redundant databases.

Tier 2 (Business Critical): Internal applications, HR systems, reporting. Target RTO: 4-24 hours. Target RPO: 1-4 hours. Azure approach: Azure Site Recovery with 1-hour replication, daily database backups to geo-redundant storage.

Tier 3 (Standard): Development environments, non-critical internal tools. Target RTO: 24-72 hours. Target RPO: 24 hours. Azure approach: Azure Backup with geo-redundant vault, restore from backup on failure.

Azure Site Recovery Configuration

Azure Site Recovery (ASR) replicates Azure VMs from a primary region to a secondary region. For UK deployments: Primary region: UK South (London). Secondary region: UK West (Cardiff). The Azure paired regions ensure that Microsoft does not update both regions simultaneously, reducing simultaneous planned maintenance risk.

ASR configuration steps: Enable replication for each VM in the Recovery Services Vault. Set replication frequency (15 minutes for Tier 1, 1 hour for Tier 2). Configure recovery points: retain multiple crash-consistent recovery points (every 5 minutes) and app-consistent recovery points (every hour). Create a Recovery Plan that defines the failover sequence (database VMs first, then application VMs, then web tier) and includes pre- and post-failover scripts.

Database DR Strategy

For ERPNext on MariaDB: ASR replicates the VM including the database — this achieves crash-consistent recovery. For app-consistent recovery (no data loss at the database level), configure MariaDB-aware backup scripts as ASR pre-snapshot scripts. For Azure SQL Database: Use Active Geo-Replication to maintain a readable secondary in UK West. Failover is manual or automatic depending on your failover group configuration. RPO with geo-replication: typically under 5 seconds for transaction log replication.

Failover Testing: The Non-Negotiable

A DR plan that has never been tested is not a DR plan — it is a guess. Azure Site Recovery supports test failovers that spin up the DR environment in an isolated network without affecting production. Techseria recommendation: Run a test failover quarterly. The test failover should include: Verifying the secondary environment starts successfully. Verifying the application is functional (automated smoke tests, not manual clicking). Verifying the actual RTO — time the failover from initiation to verified application availability. Verifying the RPO — check the last replicated data point against the target.

DR Cost Benchmarks

Azure Site Recovery licensing: £16/month per protected VM. Secondary region VM costs (in standby — compute not running until failover): £0 for compute. Storage costs for replicated disks: approximately 30-50% of primary disk costs. For a 10-VM production environment: ASR licences: £160/month. Secondary storage (50% of primary): £65/month. Total DR overhead: approximately £225/month = £2,700/year. This is a reasonable DR cost for protecting a production environment worth £50,000+ in annual licence/infrastructure spend.

Techseria designs and manages Azure DR for mid-market companies. Book a Strategy Session to discuss your RTO/RPO requirements and current DR gaps.