Plan Your Rollback Before You Start
Every backhaul migration needs a tested rollback plan before work begins. If the new link fails to perform, you need to be back on the old link in minutes, not hours. This means:
- Keep the old equipment powered and configured until the new link is validated
- Identify the specific failure scenarios that would trigger rollback
- Assign clear responsibility for making the rollback call
- Test the rollback procedure during a maintenance window before migration night
Parallel Operation Period
Whenever possible, operate the new and old links in parallel for a period before cutover. This lets you:
- Validate the new link under real load conditions
- Observe weather-related performance over multiple days
- Identify any issues with path alignment or interference
- Build confidence before committing to the cutover
The Cutover Window
Choose your maintenance window carefully. For most rural networks, Sunday morning 2-4 AM local time represents minimum customer impact. Have all personnel staged and ready before the window opens — don't start troubleshooting when you should be executing.
We use a strict go/no-go checklist before every backhaul cutover. If any item is red, we don't cut over — even if the maintenance window is already open and stakeholders are watching.
Backhaul Planning and Implementation
Richesin Engineering plans and executes wireless backhaul projects with a rigorous zero-downtime methodology.
Network Services