01 / PLANNING
Start with the outage workflow
For a Dallas office or Fort Worth trade counter, identify the work that stops when the main circuit fails: taking payments, accessing cloud software or reaching dispatch. Select a small set of essential applications before sizing the backup. Large transfers and guest traffic may need a different policy during an outage.
02 / PLANNING
Let the network owner define the handover
Tell RNP which firewall or router your MSP manages, whether it has a spare WAN port and who can approve a configuration change. Mounting a dish does not automatically configure failover. The quote should state whether router work, testing and a return to the primary link are included.
03 / PLANNING
Test power and internet separately
A powered dish does not keep an unpowered switch online. Include the router and other essential equipment in the power plan, then test a controlled primary-link interruption. Weather can affect the satellite path too; backup connectivity is a resilience measure, not an uptime guarantee.
| Part of the project | Information that helps |
|---|---|
| Existing circuit | Provider, handoff and reason for adding a second path |
| Critical traffic | Payments, voice, remote access or another named workflow |
| Acceptance check | Observed failover, application check and return to primary |