Start by naming the work that can’t stop: card payments, phone calls, the cloud applications your team lives in, email, remote access for staff who work off-site. That list is what your business internet backup has to carry. Then prove it carries them. Have your IT team disable the main line on purpose, run every task on the list, then switch back and run the list again. The backup itself is a second connection, such as a cellular device or a second wired line, that takes over when the main one fails.
A line that shows as connected proves only that it’s connected. If it can’t run the card payments, the phones or the cloud applications, an outage you thought you’d covered still stops sales and idles staff, and customers can’t reach you. A quiet afternoon won’t show that. An outage does, because the setup was accepted without proof.
What should your business internet backup keep running?
It should keep running the tasks that stop money coming in or work going out. The list starts with taking card payments, answering the phone, reaching the cloud applications your team works in, email, and remote access for staff who aren’t in the building. You decide that list. Your equipment doesn’t.
Name the tasks, not the equipment
Ask the people doing the work what they couldn’t do. The front desk may name card payments. Whoever answers the phone may name the phone. Bookkeeping may name whatever it logs into every morning. A router won’t be on that list, and that’s the point. The list comes from the work, not from the equipment on the wall.
Phones earn their own line. If your calls travel over the internet instead of a dedicated phone line, they depend on the same connection as everything else, and a backup that can’t carry them may leave callers unable to reach you while your office looks open. O&O Systems offers VoIP phone systems for business, so it’s fair to ask whether your handsets belong on this list. Add anything else your business can’t trade away for an afternoon: a scheduling system, a dispatch screen, the time clock. That’s your must-run list.
Decide what’s allowed to wait
A backup path can be slower than the main line, or carry limits the main one doesn’t. So decide what you’re willing to pause. Big file transfers, video meetings, syncing a shared drive: a business might agree in advance that those wait while the office is on the backup. That conversation is easier before an outage than during one. Write the must-run list and the can-wait list in plain words, then give your IT team or provider a copy.
How do you test a backup connection before an outage does it for you?
The test is planned, not accidental. You agree a time with your staff, your IT team disables the main line on purpose, and everyone works through the must-run list on the backup. You note what failed and whether the switch happened on its own or needed a person. Then you restore the main line and run the list again.
- Agree a time with your staff, and warn whoever answers the phone and takes payments.
- Have your IT team disconnect or disable the main line on purpose, the way an outage would.
- Work down the must-run list on the backup: run a card payment the way you normally would, place a call, take a call, open each cloud application, send yourself an email, have someone off-site sign in.
- Write down what failed, what behaved differently, and whether anyone had to step in to make the switch happen.
- Restore the main line, then run the whole list again.
Whether the switch needs a person matters more than it sounds. Automatic switching, which your IT team may call failover, means the office can keep working while someone looks into the main line. Manual switching means a person has to be there and has to know what to do. Either can be reasonable. You just need to know which one you have.
None of that is unusual thinking. Ready.gov, the U.S. Department of Homeland Security’s preparedness website, counts connectivity to a service provider among the IT components a recovery plan should expect to lose, and its standing advice on IT disaster recovery planning is to test the plan periodically to make sure that it works. Switching to the backup on purpose is how the connection part of that plan gets tested.
Switching back is half the test
A connection can switch over cleanly and never switch back. The main line returns, nothing moves to it, and the office keeps working on the backup path without anyone noticing, until a usage limit or a sluggish afternoon makes it obvious. So run the list a second time once the main line is restored. Ask your IT team to confirm that traffic moved back rather than only appearing to, and that nothing is still sitting on the backup.
What can go wrong when the backup takes over?
A backup can carry traffic and still break specific tasks. The connection comes up, the internet works, and yet a remote login is refused or a filtering rule behaves differently. These are general principles, not predictions about your setup, and each one is a question for your IT team or provider.
- A backup path can present a different public address to the internet. Your public address is the number other systems see when your office connects out; if a remote-access tool or an outside service only accepts connections from an address it already knows, it may turn your office away while you’re on the backup. Ask whether anything you depend on is tied to a known address.
- The protections that sit between your office and the internet should apply on the backup path too, including your firewall rules and your content filtering. A backup can be wired in a way that bypasses some of them. The test is the moment to check it, and your IT team or provider can confirm what’s in place.
- A backup can be slower, and it can carry usage limits. Ask for those limits in writing, along with what happens when they’re reached, before you accept the setup.
- Two connections can fail together. If they share a cable route, a building entrance or the same provider upstream, one problem may take down both. Ask what the second path does differently from the first.
- The equipment that performs the switch needs power. As a general rule, a connection backup assumes that hardware is still running, so ask your IT team how that equipment is powered.
A long regional outage sits outside this. When power and cellular service go down together, a second connection may not help, and the planning that matters is different; there’s separate reading on how to prepare your office IT for hurricane season.
Who should run the test, and what should you ask for?
Your IT team or provider runs it, because someone has to disable a live connection and put it back. You’re there for the business half: you decide which tasks count and you judge whether they worked. What you should ask for afterward is short: a written record of what happened.
Ask for one page, or one email that does the same job. It should record:
- the date of the test
- which tasks were run
- whether the switch to the backup was automatic or manual
- what failed, and what was done about it
- what happened when the main line came back
- who accepted the result
O&O Systems’ network and Wi-Fi services include failover solutions and backup connections that help a business stay online during outages. Whoever installs or supports yours, ask for that written record before you accept the setup, and keep it where the next person can find it.
The same habit belongs on your files. A connection backup is proven by using it, and so is a copy of your data, which is the argument for taking the time to test your data backups instead of assuming they’d work.
Then retest after change. A different provider, a new phone system, a replaced firewall, a reorganized office: any of those can undo what the last test proved, quietly. Put the retest on whatever schedule you already use to review your systems, and treat the written record as the thing that expires.
Frequently Asked Questions
Do we need a backup connection at all?
That depends on what a day without the internet costs you. A business that takes card payments, answers calls over the internet or runs on cloud applications can lose the ability to trade when the line drops. If a quiet day of paperwork is the worst outcome, the case is weaker. Weigh it against the work that stops.
Is a cellular backup enough for one office?
It can be, and the honest way to find out is to run your own list of tasks on it. A cellular backup can be slower and can carry usage limits, so it may handle payments and calls while struggling with heavier work. Decide which of those you need, then test for exactly that.
How often should the backup be tested?
After anything changes, at minimum. A new provider, a new phone system or a change to the network can undo a result you trusted. Beyond that, fold the test into whatever review cycle you already run for your systems, and keep the written record from each one so you can compare.
Will our card machines and phones work on the backup?
That can’t be known without testing. Payment terminals and internet-based handsets that connect through your office network depend on how they’re set up, and that decides whether a different path works for them. Run a real payment and a real call during the test, in both directions, rather than checking that the devices show a connection.
Does a backup connection replace our data backups?
No. A backup connection can keep work moving when the line fails. A data backup brings your files back when they’re deleted, damaged or lost. One doesn’t cover the other, and both are worth proving before you need them.
What if the backup fails the test?
Then the test did its job on a day you chose. Note which task failed, hand that to your IT team or provider, and ask for a retest once it’s addressed. A backup that fails a planned test can be fixed. A backup that fails during an outage can’t, at least not while customers are waiting.
Before you accept the backup, make it prove itself
A second connection earns its keep once you know what it carries. Name the tasks. Watch the office switch over, then watch it come back. Keep the page that says what happened and who signed off. If you have a backup connection to accept, renew or question, contact O&O Systems about your backup internet.