Managed IT
Backup and Disaster Recovery for Dealerships
When the data’s gone, nobody desks a deal and the service drive goes back to paper. Helion keeps a separate copy of every system and proves it restores.
Backup and disaster recovery for dealerships means keeping a separate, protected copy of every system the store runs on, from Microsoft 365 to Azure and on-site servers, and proving it restores before an outage stops sales and service.
Last updated: October 16, 2026
An Outage Hits the Sales Floor and the Service Drive First
Picture a Saturday with no files. The sales desk can’t pull a deal jacket, F&I can’t print a contract, and the service advisors are writing repair orders by hand while customers stand at the counter wondering why it’s taking so long. Nobody’s selling anything. When dealers get hit by a cyberattack, the downtime averages 3.4 weeks, according to CDK Global’s 2023 State of Cybersecurity in the Dealership study. Ransomware is only one way to get there. A failed server, a deleted mailbox or a bad sync can do it too. And when the DMS provider itself goes down, your own DMS outage plan is what keeps the doors open while they fix it.
Dealership backup and disaster recovery is the part of managed IT for dealerships that decides how fast you’re selling again. Helion Technologies runs it with the same team that handles your cybersecurity, so the people who spot an attack are the same people who bring the data back and get the desk working again. If you’re in the middle of an incident right now, our incident response plan template shows who does what in the first hours.
A backup you’ve never restored is a hope. We test ours before you need them.
Shared responsibility
Who Keeps a Copy of Your Dealership’s Data
Microsoft puts this in writing. Its shared responsibility model leaves your data with you every time, whether it sits in Microsoft 365, in Azure or in your own building. Read across any row below. The middle column is the work that falls to the dealership, and it’s usually where nobody was assigned.
| Where it lives | Microsoft handles | Left to the dealership | What Helion does |
|---|---|---|---|
| Microsoft 365 email | Keeps deleted email 14 days by default, 30 at most | A copy for anything older, or a mailbox someone emptied before they quit | A separate backup of every mailbox, restorable to a point before the damage |
| OneDrive, SharePoint and Teams | Keeps deleted files 93 days across the recycle bins | A copy that ransomware in a synced folder can’t reach | A separate backup of files and sites, kept outside the tenant |
| Servers in Azure | Runs the hardware and offers backup tools | Switching backup on for each server, setting the schedule and checking it ran | Backup turned on for every server we manage, with failed jobs chased the same day |
| Private cloud built in Azure | Provides snapshots, backups and other region options | Designing snapshots, how long they’re kept and the order systems come back | A snapshot and retention plan, plus a written recovery order your managers can follow |
| On-site servers and shares | Nothing, these never touch Microsoft’s datacenters | All of it, from the backup job to the copy that leaves the building | Backups with a copy kept off-site, so a fire or a flood in the store isn’t the end of the data |
| A copy ransomware can’t touch | Offers delete protection and locking on storage | Keeping at least one copy offline or locked against deletion | At least one offline or immutable copy, out of reach of a stolen admin password |
| Restore testing | Nothing, testing is the customer’s job | Proving a restore works, and how long it takes, before an outage | Test restores on a schedule, with the results written down where your managers can see them |
The retention numbers come from Microsoft’s own pages on deleted email in Exchange Online and the SharePoint recycle bin. For servers in Azure, Microsoft’s page on Azure VM backup shows that a backup only runs for the machines somebody selected and gave a schedule.
From the field
Where Erik Finds Dealers With No Backup at All
We asked Erik Nachbahr, Helion’s founder and a CISSP, where dealership backups fall apart. It isn’t the old server in the closet anymore. It’s the cloud, because moving there made people stop thinking about the copy. “They just don’t think about backups at all,” he says, and he sees it in three places.
Already hit?
Call us first, then open the incident response plan template. It lays out the first decisions, in order, before anyone restores anything.
Three gaps Erik sees in dealer clouds Erik Nachbahr, Helion founder
Microsoft 365 Mail and files nobody backs up
“Microsoft doesn’t guarantee you backups of all of your data. It retains it for a bit, but that’s not a backup and restore, like what you typically expect.” A deleted email waits in Exchange Online for 14 days by default. A deleted OneDrive or SharePoint file waits 93. After that, it’s purged. The deal jacket that lived in a shared folder is gone for good. Our page on managed Microsoft 365 covers the rest of the tenant.
Retention isn’t a restore.
Azure servers The server moved. The backup didn’t.
A store lifts its accounting server or file server out of the closet and into Azure, which is often a smart move, and the backup box that used to sit next to the old server gets unplugged and forgotten. So whose job is the copy now? Microsoft answers that in its shared responsibility guide for reliability, and the answer is yours. Azure offers backups. Switching them on, and checking that they run, stays with the customer.
Offered isn’t switched on.
Private cloud Built in Azure with no snapshot plan
“Now you’re putting these mission-critical things in your own cloud, in private cloud, and Azure, and in 365, but you don’t actually have any backups of any of that information.” Larger groups build their own environment in Azure for the domain controllers, the file shares and the apps every store logs in to each morning. Most days it works fine. Then we ask when the last snapshot was taken and who checks that the job finished. Usually nobody knows.
Nobody owns it.
Who Brings Your Systems Back
Outages don’t wait for business hours, and neither do we. Our help desk is live from 6 a.m. to midnight Eastern, Monday to Saturday, with after-hours and weekend support included, and security monitoring runs around the clock with live, US-based analysts. It’s one team. You call one number.
Disaster Recovery Only Counts if the Restore Works
Ransomware crews know where backups live. They check there first. CISA’s #StopRansomware Guide warns that many variants go looking for accessible backups and delete or encrypt them first, which is why it tells organizations to keep offline, encrypted copies and to test them regularly. A backup sitting on the same network, signed in with the same admin password, tends to go down with everything else. Catching the attacker before the encryption starts is the job of managed detection and response. The backup is the fallback.
The other half is time. A general manager doesn’t care that the data exists somewhere. The question is when the desk can work deals again and when the service drive can print a repair order, so we restore in that order and we time it during tests, not during the real thing. You’ll know the number. If your cyber insurance renewal asks how your backups are stored and when a restore was last tested, you’ll have the answer in writing. Our post on cyber recovery for dealerships walks through the steps after an attack.
Test it before you need it.
What CISA recommends
Offline, encrypted backups of critical data, delete protection or object lock on cloud storage, and regular tests that the backups are available and intact in a disaster recovery scenario.
Out of reach, and tested.
What a restore test proves
That the copy opens, that nothing important was left out of the job, and how many hours it takes to get the sales desk, the service drive and accounting working again.
A real recovery time, not a guess.
How Backup and Disaster Recovery Starts
-
1
Request the assessment
Fill in the short form for our complimentary IT and cybersecurity assessment. There’s no cost and no obligation, and you don’t need to be shopping for a new provider.
-
2
We map where your data lives
An engineer lists every place your stores keep data, from Microsoft 365 and Azure to the server in the parts room, and what’s backing each one up today. Our guide to the dealership technology stack makes a good starting list.
-
3
Gaps arrive in writing
You see which systems have no copy, which copies a ransomware crew could reach, and which ones nobody has ever restored. It’s a short list, and it’s honest.
-
4
You decide what’s next
Fix it in-house, or hand us the backups and the testing. Onboarding starts within weeks of signing. On the co-managed path your own IT manager stays in charge.
Common Questions
Not sure what’s backed up today?
A complimentary IT and cybersecurity assessment answers that in writing. Already know what you need? Get a price quote.
What does backup and disaster recovery cover for a dealership?
Doesn’t Microsoft back up our Microsoft 365 data?
We moved our servers to Azure. Aren’t they backed up automatically?
How often should we test a restore?
Will a backup save us if ransomware hits?
Can our own IT person keep running the backups?
Find out which of your systems could come back tomorrow, and which ones couldn’t come back at all.
Request a Complimentary Assessment →