Bobcares Logo
Search Phone User Profile Emergency Contact
Client

NDA Protected Technology Client

Services used

Managed Cloud Services
See similar case studies

Disaster Recovery Implementation for Business Continuity

A medium-sized financial services company was running online banking, payment processing, and customer support applications in a hybrid cloud environment. Its infrastructure included virtualized servers, Microsoft SQL databases, Active Directory, file servers, and web applications. A formal recovery process was not in place, leaving critical services exposed to long recovery periods and possible data loss.

Bobcares assessed the workloads, established recovery priorities, and defined RTO and RPO targets. The resulting DR setup combined VM replication, automated backups, SQL high availability, failover and failback, monitoring, and recovery testing.

Case Study Section

Business Challenge

The client had no formal recovery process for its critical applications. Infrastructure failures could result in lengthy recovery, while irregular backups increased the risk of data loss. Manual recovery added further delays, and regulatory requirements made defined RTO, RPO, backup visibility, and recovery validation necessary.

Technology Used

VMware vSphere Microsoft Azure Site Recovery Microsoft SQL Server Always On Availability Groups Veeam Backup & Replication Azure Blob Storage Active Directory DNS Failover Microsoft Sentinel / Azure Monitor VPN and secure site-to-site connectivity

Blueprint

The recovery design started with Business Impact Analysis and workload classification. Critical virtual machines were replicated to a secondary DR facility, while Veeam handled automated incremental backups. SQL databases used Always On Availability Groups, with monitoring, failover, failback, and DR testing covering the wider recovery process.

web

Managed Cloud Services

Key Outcomes

  • Mean recovery time reduced from 8 hours to 45 minutes.
  • Potential data loss reduced from 24 hours to 15 minutes or less.
  • Application availability reached 99.95%.
  • Failover required little manual intervention.
  • Backup and replication health became easier to track.
  • Recovery procedures could be tested and validated.
  • RTO and RPO requirements were incorporated into the DR plan.

Customer Profile

The client was a medium-sized financial services company providing online banking, payment processing, and customer support. Its applications and supporting systems ran across a hybrid cloud environment that included virtualized application servers, Microsoft SQL databases, Active Directory, file servers, and web applications. Because these systems supported critical financial services, the company needed a recovery setup that could restore services quickly while limiting data loss.

The Challenges

  • Critical workloads did not have a formal Disaster Recovery process.
  • Recovery from an infrastructure failure could take around 8 hours.
  • Irregular backups left the environment exposed to up to 24 hours of potential data loss.
  • Recovery depended heavily on manual steps.
  • RTO and RPO targets needed to be defined for regulatory and operational requirements.
  • There was no centralized view of backup and replication health.
  • The recovery plan needed testing rather than relying only on documented procedures.

Why Bobcares?

  • The recovery plan was based on workload criticality rather than treating every application the same way.
  • RTO and RPO targets were established before the recovery mechanisms were put in place.
  • Replication and backups were used together to address both recovery time and data protection.
  • SQL high availability was included for database workloads that required continued access.
  • Automation reduced the number of manual steps involved during recovery.
  • Monitoring and testing were included so that recovery readiness could be checked instead of assumed.

What We Delivered

  • Classified workloads through Business Impact Analysis.
  • Defined RTO and RPO requirements for the applications.
  • Set up continuous replication of virtual machines to the secondary DR facility.
  • Configured automated incremental backups using Veeam Backup & Replication.
  • Implemented SQL Server Always On Availability Groups for database replication.
  • Set up automated failover and failback procedures.
  • Used Azure Blob Storage for backup storage.
  • Configured DNS failover for service recovery.
  • Established secure site-to-site connectivity using VPN.
  • Centralized the monitoring of backups, replication, and recovery readiness.
  • Used Microsoft Sentinel / Azure Monitor for monitoring.
  • Tested and validated the Disaster Recovery process.

The Results

Recovery Time

  • Before: Recovering the environment after an infrastructure failure could take up to 8 hours on average.
  • After: Mean recovery time was brought down to 45 minutes.

Data Protection

  • Before: Irregular backups meant that a failure could result in up to 24 hours of potential data loss.
  • After: The RPO was reduced to 15 minutes or less.

Application Availability

  • Before: Critical applications did not have a formal recovery framework to protect them from extended infrastructure outages.
  • After: Application availability reached 99.95%.

Failover Process

  • Before: Recovery involved manual procedures, which added time during an incident.
  • After: Automated failover and failback reduced the need for manual intervention.

Recovery Validation

  • Before: The client had limited visibility into whether backups and replication were ready for recovery.
  • After: Centralized monitoring and DR testing provided a way to check the state of the recovery environment and validate the plan.

The Business Impact

  • Critical services could be restored considerably sooner after an infrastructure failure.
  • The smaller recovery window reduced the amount of customer and business data at risk.
  • Automated recovery removed several manual tasks from an already time-sensitive process.
  • Defined RTO and RPO targets gave the business a clearer basis for prioritizing recovery.
  • Regular DR testing made it possible to identify issues before an actual disaster.
  • Centralized monitoring gave the operations team better visibility into backup and replication status.
  • The approach strengthened the client’s ability to meet its business continuity and regulatory requirements.

Ongoing Collaboration

  • Monitor backup completion and replication health.
  • Review recovery readiness across critical workloads.
  • Test failover and failback procedures periodically.
  • Validate that RTO and RPO targets continue to match application requirements.
  • Review application availability and DR performance.
  • Monitor the health of the recovery environment.
  • Update the recovery approach as workloads and business requirements change.

Conclusion

The client needed to move from a largely manual recovery process to a defined Disaster Recovery framework for its critical financial applications. Bobcares combined VM replication, automated backups, SQL high availability, failover, monitoring, and testing around clear RTO and RPO targets. Recovery time fell from 8 hours to 45 minutes, while potential data loss was reduced from 24 hours to 15 minutes or less.