Short answer: A second Internet connection does not automatically mean resilient operations. Branch connectivity design must account for independent failure paths, firewall policies, DNS, application behavior and a tested failover procedure.
Branches connected to a regional data center may rely on ERP, file shares and cloud services. When the main connection fails, a backup line that cannot carry the VPN is not useful.
What can go wrong without a proper plan?
- Two links share the same building conduit or upstream failure point.
- Failover changes the public IP and breaks an application with IP allowlisting.
- VPN routes and firewall rules exist only for the primary ISP.
- The second link is never tested until a real outage occurs.
During discovery, treat these items as testable risks rather than accepting a generic supplier promise. Capture the affected service, the likely business impact, and the person authorized to accept any remaining exception.
Practical implementation checklist
- List critical applications, acceptable downtime and traffic requirements for each site.
- Verify whether providers offer genuinely independent paths and equipment where feasible.
- Design health checks, routing, NAT, DNS and VPN tunnel behavior during failover.
- Simulate a main-link outage and test ERP, calls, email and remote support end to end.
- Document escalation, provider contacts, diagrams and rollback procedures.
Keep the resulting configuration, evidence and decisions in a customer-accessible handover folder. This matters when the local operator changes, headquarters requests an audit, or another vendor must take over a critical system.
Example: applying the checklist in a Vietnam office
A factory that ships through a cloud ERP should test order submission across both links, not just a successful ping. Also verify whether headquarters security rules still apply after the failover.
A good handover should leave evidence rather than just a verbal statement that the work is finished. Record the business owner, technical operator, exceptions and next review date. For an international company, the same record must be understandable to both the Vietnam branch and its headquarters.
Questions to ask before approving a supplier
- Which items are included in the recurring service, and what requires a separate project or quotation?
- Who approves a high-impact change, and how will the vendor report completion to headquarters?
- What documentation and administrator access will remain under the customer’s control?
- What measurable acceptance or recovery test proves the solution works in the real environment?
Frequently asked questions
Will dual WAN double Internet speed?
Not necessarily. Load balancing, session behavior and the service contract determine throughput; resilience and speed are different goals.
Can VPN connect automatically after failover?
It can be designed to, but routing, tunnel negotiation and external dependencies must be tested with the real applications.
How SMNET can support the next step
SMNET works with business customers in Vietnam across managed IT, network infrastructure, cybersecurity, cloud and backup. We recommend starting with a scoped assessment rather than assuming a fixed product or SLA will fit every location. See our Network Infrastructure service or browse the English technology insights. For project requirements, contact hello@smnet.vn or call +84 28 7301 6068.
Editorial note: These are planning guidelines. Service hours, languages, onsite coverage and contractual response times must be confirmed in an individual proposal. Illustrations are conceptual, not photographs of a particular customer site.



