The challenge
The carrier ran production in the Northeast, with disaster recovery already replicated to a site in the Southwest. But a regional Northeast event, an internet, power or disaster outage, could cut its people off from everything, including the path to that DR site. They needed genuine geographic separation and an alternate access layer outside the Northeast, without the cost of standing up a second full replication site.
Our approach
- Layered resilient architecture: designed a three-tier model, Northeast production, a new Midwest continuity edge, and the existing Southwest full-DR site, so production, continuity access and catastrophic recovery are cleanly separated.
- A lightweight continuity edge: because DR already replicates to the Southwest, the new Midwest site stays lean, an alternate internet ingress and egress, a secondary security edge and remote-access continuity, rather than a second full data center, which keeps cost and complexity down.
- Procurement and build: handled colocation and carrier procurement, Palo Alto firewall deployment (HA or single), Citrix failover design, DNS and routing strategy, and the dedicated connectivity between sites.
- Testing and runbooks: DR testing and validation, with operational runbooks so the carrier’s own team can actually execute a failover, not just read about one.
The solution
VeeMost designed a continuity architecture that keeps the carrier working through a regional outage. In normal operation, production runs in the Northeast and the continuity edge stays active with alternate internet. If the Northeast is cut off, users connect through the Midwest edge with VPN and Citrix access intact and a clear path to the Southwest DR. In a catastrophic failure, the DR systems take over and users reach them through the continuity edge. Because the heavy replication already lives at the DR site, the new edge stays lightweight, resilient without the price of a second full data center.
