May 2026 · Backups
Backup planning used to mean “make a copy of the server.” Today, small businesses have email, Microsoft 365, OneDrive, SharePoint, local computers, cloud apps, synced folders, and ransomware risk all tied together.
The short version
A copy sitting somewhere is useful only if it is the right copy, protected from the same mistake or attack, and recoverable in a reasonable amount of time. That is why I still like the spirit of 3-2-1 backups, even when the tools look different now.
The practical goal is simple: if a computer dies, a cloud account is compromised, a file gets deleted, or ransomware hits, the business should have a sane path back to work.
OneDrive, SharePoint, Google Drive, Dropbox, and similar tools are great for access and collaboration. They are not automatically a complete backup plan. If a bad delete, bad sync, ransomware change, or account compromise spreads through the synced data, the problem may follow the files everywhere.
Version history and recycle bins help, but they are not the same as having an independent recovery copy with its own retention and controls.
Microsoft keeps Microsoft 365 running, but that does not mean every business file, mailbox, calendar, contact, OneDrive folder, or SharePoint site is protected the way a business expects. Accidental deletes, account compromise, bad retention settings, and user mistakes still happen.
Tools like Dropsuite can back up Microsoft 365 data separately so email, OneDrive, SharePoint, Teams-related data, contacts, and calendars have a clearer recovery path.
Even in a cloud-heavy office, there may be accounting files, scanner folders, QuickBooks-style company files, desktop folders, exported reports, shared folders, or line-of-business data that lives outside Microsoft 365.
That data needs to be identified and protected. Depending on the office, the right answer may include workstation backups, server backups, SyncBackPro-style file jobs, image backups, or a more formal backup appliance or cloud service.
The old 3-2-1 rule was simple: three copies of important data, on two different types of storage, with one copy offsite. The exact tools have changed, but the idea still holds up because it separates the business from a single failure.
If every copy is connected to the same computer, the same account, or the same ransomware event, it may not be enough. Offsite, protected, or harder-to-change copies give the business another way back.
Backup conversations often focus on where the data is stored. Recovery conversations ask the better question: how long would it take to get working again? A backup that exists but takes three days to restore may not fit a business that needs invoices, schedules, or customer records today.
Some files need quick restore. Some systems need full-machine recovery. Some archives only need to exist for historical or compliance reasons. Treating all data the same usually creates either wasted cost or slow recovery.
A backup that quietly stopped running six months ago is not a backup plan. Someone needs to review job status, failed alerts, storage usage, retention, and whether the backup still covers the data the business actually uses.
Testing does not have to be dramatic. Even a periodic restore of a few sample files is better than assuming everything works because the dashboard looked green last year.
A small office may need a mix: Dropsuite for Microsoft 365, IDrive or another cloud backup for selected computers, a local backup for fast recovery, and a simple documented process for what happens if something fails.
The best setup is not always the biggest one. It is the one that protects the right data, fits the budget, can be understood later, and has a real restore path when the business is already stressed.
Quick checklist
Need a backup reality check?
Hughes IT can help review what is protected, what is not, whether Microsoft 365 data is covered, and how the business would actually recover after a mistake, outage, or attack.
