About the Customer

The customer is one of Indonesia's largest public-sector companies, operating in the mining and precious metals (gold, silver, and bronze) retail sector. As a state-affiliated enterprise with nation-wide operations, the company manages extensive mining assets and a retail network serving millions of customers across Indonesia. Business operations heavily rely on stable, secure, and highly available IT systems to support high-volume financial transactions, inventory management, and regulatory reporting.

Customer Challenge

As a regulated public-sector entity, the customer faced increasing pressure to meet strict industry compliance requirements for disaster recovery (DR). The company was required by regulation to establish a Disaster Recovery Center (DRC) with a geographically separated secondary environment to reduce single point of failure risk.

However, the customer's existing DR approach was entirely on-premise based:

• Primary data center and DR data center were both located on-premise within the same metropolitan area
• Both facilities shared exposure to the same regional risks (natural disasters, power grid failures, flooding)
• The "secondary" site did not provide true geographic redundancy
• Infrastructure maintenance required significant capital expenditure for underutilized hardware

Beyond these architectural limitations, the customer faced significant business risks if the challenge went unaddressed:

• Regulatory non-compliance penalties — including potential fines, operational restrictions, and reputational damage with government stakeholders
• Estimated revenue impact of approximately USD 50,000–100,000 per hour of downtime during high-volume precious metals trading and retail transaction periods
• Recovery Time Objective (RTO) of 8–12 hours — limited by manual failover processes and cold standby hardware at the on-premise DR site
• Recovery Point Objective (RPO) of 4–6 hours — limited by daily backup windows and batch replication to the on-premise DR facility
• High capital expenditure — the on-premise DR site required dedicated servers, storage, networking, and facility costs, yet remained largely idle
• Single point of failure risk persisted — both on-premise sites shared exposure to regional disasters (earthquakes, floods, power outages)
• Untested DR readiness — full DR drills were expensive and disruptive, leading to infrequent testing and low operational confidence

If not addressed, the company would remain non-compliant with industry regulations while exposing critical national-scale operations to unacceptable operational, financial, and regulatory risk.

Partner Solution

PT Metrodata Electronics Tbk, an AWS Advanced Tier Services Partner, designed and implemented a cloud-based Disaster Recovery solution using AWS Elastic Disaster Recovery (AWS DRS) with a Pilot Light strategy, deployed in the AWS Asia Pacific (Jakarta) region (ap-southeast-3). This replaced the customer's on-premise DR facility entirely.

How the solution was delivered: Metrodata followed a structured five-phase methodology to ensure regulatory compliance, operational readiness, and zero disruption to production systems:

1. Assessment & Compliance Mapping Phase: Metrodata conducted a detailed discovery of the customer's 150+ critical servers, application dependencies, and existing on-premise DR limitations. The team mapped specific compliance obligations to technical DR controls, defining target RPO and RTO in alignment with regulatory expectations.
2. Architecture Design Phase: Metrodata designed a resilient architecture using Multi-AZ deployment across three Availability Zones within the Jakarta region — delivering true geographic separation that the on-premise DR site could not provide. AWS Transit Gateway with Hub-and-Spoke topology was selected to centralize connectivity, improve security, and simplify network management across multiple VPCs.
3. Deployment & Replication Phase: Metrodata deployed AWS DRS agents across the customer's server fleet, configured continuous replication to Amazon EBS volumes, and established the Pilot Light environment where core system components are minimally replicated and can rapidly scale up during a disaster event. All workloads and data were placed in the AWS Jakarta Region to ensure data sovereignty compliance — replacing the on-premise DR facility entirely.
4. Validation & DR Drill Execution Phase: Metrodata executed two full DR drills, validated improved RPO and RTO targets, documented runbooks, and automated failover/failback processes. The team trained the customer's internal IT staff on cloud DR procedures.
5. Operational Handover & Managed Support Phase: Post-implementation, Metrodata provides ongoing managed support, monitoring, and semi-annual DR drill execution (2x per year) with automated failover and failback to maintain continuous operational readiness — eliminating the costly, disruptive drills required by the on-premise DR model.

Primary AWS services used: AWS Elastic Disaster Recovery (DRS), Amazon EC2, Amazon EBS, Amazon VPC, AWS Transit Gateway, AWS Organizations, AWS IAM, and Amazon CloudWatch.

Results and Benefits

Following implementation, the solution is now in production and has delivered measurable business, compliance, and operational outcomes — replacing the customer's on-premise DR facility with a modern cloud-based architecture.

Specific business benefits achieved:

• Regulatory compliance fully satisfied — The company now meets industry DRC requirements with documented, tested DR capabilities that exceed on-premise limitations
• Consistent SLA attainment — RPO of 30 minutes (improved from 4–6 hours) and RTO of 4 hours (improved from 8–12 hours) successfully validated through semi-annual DR drills
• True geographic redundancy — Multi-AZ architecture across three Availability Zones eliminates the shared regional risk exposure of the previous on-premise DR model
• Cost efficiency — The Pilot Light approach consumes only 10–15% of production environment costs, compared to the customer's previous on-premise DR facility which required 50–70% of production CapEx for idle hardware. This represents approximately 85–90% cost savings versus maintaining equivalent on-premise DR capacity
• Eliminated capital expenditure — No more purchasing servers, storage arrays, or networking gear for a standby DR facility that sits idle
• Operational confidence — Routine automated DR drills (2x per year) have replaced costly, disruptive on-premise drills; the IT team can now execute failover with confidence
• Reduced risk exposure — Cloud-based DR eliminates single points of failure related to local power grids, flooding, earthquakes, and other regional disasters
• User-friendly & scalable platform — AWS provides simplified management and the flexibility to scale as business needs grow, without forklift upgrades

By leveraging AWS Elastic Disaster Recovery, the customer transformed from an on-premise DR model with limited geographic redundancy, slow recovery times, and high capital costs to a fully compliant, resilient, and cost-efficient cloud-based DR environment — supporting long-term business continuity for this nationally significant public-sector enterprise.

About the Partner

PT Metrodata Electronics Tbk (IDX: MTDL) is one of Indonesia's leading digital solution providers and an AWS Advanced Tier Services Partner, trusted by more than 200 companies across various industries in adopting and implementing cloud solutions. Metrodata currently holds the AWS Migration and Modernization Competency and AWS Glue Service Delivery designation, demonstrating validated technical expertise in cloud migration, data integration, and disaster recovery. The company's team of certified AWS architects and engineers supports customers across public sector, mining, retail, financial services, and manufacturing industries throughout Indonesia.

Case Study Date: January 2025 (Project completed and in production)
Deployment Region: Asia Pacific — Jakarta (ap-southeast-3)
Customer Type: Top Indonesian public-sector mining and precious metals company (anonymous per customer request)
Previous State: On-premise primary data center + on-premise DR facility (same metro area)