How to check a provider's backups actually restore

You've bought backup software, your provider has set up the schedule, and files are copying to their server every night. Good. But here's what keeps business owners awake: *Does it actually work when we need it?* A backup that won't restore is just storage eating money. The only way to know is to watch them prove it.

Request a test restore before you sign on

Don't accept "we've tested it" as an answer. Ask to run a real restore test *together* while you're evaluating them. This is your chance to see the process move from start to finish. A solid provider will welcome this—they know it builds trust and often surfaces small setup issues before they become emergencies.

Tell them you want to restore a non-critical file or folder to a test location. Watch them do it. Time it. Note whether they had to think hard about where things lived in the backup, whether permissions came through intact, or whether the file size matched the original. If they push back, hesitate, or say "it takes too long to demo," that's a red flag. Restores shouldn't be a surprise performance.

Check what they test and how often

Ask your provider directly: how often do they run test restores on *your* backups, not just their generic system? Some run checks weekly, others monthly, others almost never. You want to know the rhythm.

Also ask what they test. Do they pull a few random files, or do they run a full restore to a separate environment to make sure everything comes back? Do they test the recovery of specific business applications your company relies on—accounting software, databases, mail servers? Generic file restoration is easier; application recovery is harder and more critical.

Request documentation of their test results. Any competent provider keeps logs or reports showing *when* they tested your data and *what* was verified. If they can't show you this, they probably aren't doing it.

Verify their registration and track record

Ask for their company registration number and check it on CIPC to confirm they're a real, accountable business. This matters because if a restore fails and you lose data, you need a legal entity you can pursue.

Also ask for references—specifically, customers who've actually *used* their recovery service after a real incident. Call them. Don't just ask "Are you happy?" Instead, ask: "Did the restore work the first time? How long did it take? Did anything go wrong that they had to fix?" A provider with happy customers and clean restores will have people willing to vouch for them.

If they've recovered data after ransomware hits or hardware failure, ask those references about the process. Real-world stories matter far more than marketing claims.

Document the restore process and timescales

Before anything bad happens, get *written* answers to these questions:

• How long does a full restore take (not from backup size alone, but from the moment you ask until the data is usable)?
• Will they restore to your existing location or a temporary one first?
• Who pays if they have to recover from tape archives or off-site copies—does that change the cost?
• If you need data back on a Sunday at 3 a.m., can they respond, or is it business hours only?
• What format do restored files come back in, and will metadata (modification dates, permissions) be preserved?

These details matter because a restore that takes four days is no use if your business stops after two. Keep these answers somewhere safe and easy to find.

The real test: talk to someone who's been through it

The strongest sign a provider is reliable is that their customers have survived actual data loss and bounced back. When you're comparing options, prioritise the ones who can connect you with a business that has *recovered* data, not just backed it up. A provider confident in their restore capability doesn't hide this story.

When you're ready to pick a provider, Strove's verified IT support specialists can show you their track record and let you run those critical checks before you commit. Don't assume backups work—make them prove it first.