Business Continuity and Disaster Recovery for a National Real Estate Agency 

Business Continuity and Disaster Recovery for a National Real Estate Agency
Business Continuity and Disaster Recovery for a National Real Estate Agency

Name and Sector of Client:

The client is one of the largest real-estate business agencies in India spanning business throughout the country.

Client Overview 

The client is one of the largest real estate agencies in India, operating pan-India. Their business operations require access to critical applications and data, both on-premises and in the cloud

Current Infrastructure 

On-Premises Environment 

The agency maintains three key applications in its own data center. Each is built in three layers (web, application and database) and is used exclusively by internal teams to process and protect highly confidential business data. 

  • Vendor Management Portal lets your team track vendor payments, process invoices and note material requests. 
  • Construction Management System plans project schedules, keeps budgets on track, assigns resources, stores all documentation and manages every workflow 
  • Employee ERP monitors staff attendance, handles HR tasks, runs payroll and offers self-service tools for employees.  

Data volumes: 

  • Vendor database: 2 TB 
  • Construction database: 7 TB 
  • Employee HR database: 6 TB 

AWS Cloud Environment 

In AWS, the agency runs a microservices-based platform on an EKS (Elastic Kubernetes Service) cluster with 20 worker nodes across four node groups. Over 50 microservices support customer-facing functions: 

  • Property Listings & Management: Browse and filter properties for sale or rent. 
  • Customer Feedback Portal: Submit feedback, raise support tickets, and track resolutions. 
  • Interior Design Requests: View design options and place orders. 
  • Investment Analysis: Year-over-year market insights by location. 
  • Sales Inquiry Chat: Real-time conversations with sales agents. 

Data volume in AWS: approximately 5 TB. The data includes buyer/seller registrations, property documents, architectural plans, land records, and legal instruments—entirely regulated under Indian data-protection laws (PDPB, DPDP, RERA). 

Challenges 

The agency’s data center relied on manual backups without a clear restoration procedure, causing unexpected outages and occasional data loss. In AWS, the Kubernetes setup couldn’t switch over automatically, so any glitch services entirely. 

All the core applications and databases are physically located in one place; every single day-to-day operation came to a halt due to this site’s being offline. Extended downtimes translate to a heavy risk on revenue; they also annoy customers and expose one to fines.  

Keeping all information in one location also makes the agency vulnerable to any breaches or local-level disasters that could somehow wipe out critical records. Indian laws such as RERA, PDPB, and DPDP require encrypted and fully auditable backups with automatic failover to ensure compliance. 

Disaster Recovery Solution 

Teleglobal designed and implemented an integrated DR strategy combining on-premises backups with AWS cloud failover. 

1. Unified Backup & Replication 

  • Veeam Backup & Restore agents installed on key on-premise servers. 
  • Incremental and synthetic-full backups run continuously, sending snapshots to Amazon S3 as AMIs. 
  • Older snapshots archive to Amazon S3 Glacier for cost-effective long-term retention. 

2. Network Connectivity & Traffic Routing 

  • Established a Site-to-Site VPN between the on-premises network and the AWS VPC. 
  • Primary on-prem DNS records migrated to Route 53. Under normal operation, traffic stays on-site. In an outage, Route 53 automatically reroutes requests to AWS. 
  • On-prem private load balancer registered in Route 53 ensures seamless cutover. 

3. AWS Infrastructure Failover 

On-Premises DR: 

  • In a disaster event, Veeam-triggered AMIs spin up EC2 instances in AWS, recreating the web, app, and database tiers with a 6-hour RTO/RPO. 
On-Premises DR Architecture
On-Premises DR Architecture

EKS Cluster DR: 

  • Amazon RDS read-replica created in a secondary region. 
  • Two parallel pipelines (main and DR) deploy microservices in both regions for active/active capability. 
  • AWS Global Accelerator monitors ALB health in each region. If the primary cluster fails, traffic shifts instantly to the DR cluster. 
  • The RDS replica is promoted to primary, supporting full read/write operations within a 4-hour RTO/RPO. 
EKS DR Setup
EKS DR Setup

4. Cost Management & Security 

  • Encryption: All S3 objects encrypted with KMS-managed keys (SSE-KMS). 
  • Least-privilege IAM policies govern bucket access. 
  • Lifecycle policies transition backups from S3 Standard to less expensive tiers, optimizing storage costs. 

5. Ongoing Validation 

  • Quarterly DR drills verify failover workflows against SLA targets. 
  • Post-drill reports document actual RTO/RPO achievements and highlight improvement areas. 

Technology Stack 

Component Service / Tool 
On-Prem Backup & DR Veeam Backup & Replication 
Cloud Storage Amazon S3 (Standard, Glacier) 
DNS & Traffic Management Amazon Route 53, Global Accelerator 
Kubernetes Service Amazon EKS 
Database Amazon RDS (Primary & Read Replica) 
CI/CD AWS CodePipeline, CodeBuild, ECR 
Load Balancing AWS ALB 
Networking Site-to-Site VPN, VPC 

Measurable Outcomes 

  • Downtime Reduction: 95% of potential outages are eliminated. 
  • Durability: Cross-region replication assures 99.9% durability of data. 
  • Storage Savings: Storage costs have been reduced by half by backing up incrementally, lesser than AMI. 
  • Faster Recovery: A.k.a. Cloud restores make 80% improvement in RTO.  
  • Statutory Compliance: Fully compliant with regulations RERA, PDPB, and DPDP.  

This implies that vital applications and data related to the agency are accessible and secure whether on-premise or hosted in AWS, thus protecting its revenues, reputation, and compliance.

teleBot

close
send

Tell us about you