Understand what a single connection actually protects
One connection through one device at one site can fail on its own. Use separate connections and devices, ideally at separate sites. Physical cable paths and network providers should also differ.
Check where the fiber cables actually run, not just the building names. Two cables sharing one pipe can fail together if digging damages it. Marketing descriptions do not prove that paths are separate.
Design the routing policy explicitly
Border Gateway Protocol, or BGP, controls which network paths carry traffic. Decide the main path, how to handle a slowing link and how traffic returns. Firewalls tracking connections may reject traffic when outgoing and returning paths differ.
Use BGP path settings to control preferred and backup routes. Filter allowed network addresses both ways and limit the number of routes shared. Bidirectional forwarding detection checks whether a path still works. It can cut detection from tens of seconds to less than one second.
Back the interconnect with an encrypted tunnel
A site-to-site virtual private network, or VPN, is an encrypted internet tunnel between locations. It can back up a dedicated link if its speed and delay suit the applications. Record which applications can run with reduced performance and which must stop.
Decide encryption needs during design. Encryption protects data from being read while it travels. Dedicated links are private but do not automatically encrypt traffic. Regulated work may require both.
Test failover on a schedule
During planned maintenance, turn off a path and measure how quickly traffic switches. Check that monitoring detects the event. Check packet size limits and how data is split into smaller packets on the backup path.
Record observed results in the operating instructions. Repeat tests after major network or firewall changes. The aim is to understand failure behavior before an outage.
Review failure domains at the business-service level
Separate connections can still share a router, power supply or application firewall. Map the full path and the services each application needs. Identify shared parts that could fail together. Record limits outside the network design rather than treating backup links as complete service recovery.
Test traffic both ways and include applications expected to use the backup. Path switching, capacity, packet sizes and firewall checks can all affect results. Record test conditions and results in operating instructions. Tests explain behavior under specific failures; they do not guarantee that every outage will be prevented.
Key takeaways
- Check that devices, sites, providers and physical cable paths are separate.
- Set clear BGP rules and address filters for main and backup paths.
- Match backup VPN capacity to the applications that need it.
- Turn off a path during testing and record switching times.
TalentOp Systems offers IT software services in cloud, application development and cybersecurity.
Contact us →Related: Cloud platforms service →