Saving files in OneDrive, SharePoint, Google Drive or Dropbox can protect them from a failed laptop. It does not automatically give the business a complete, separate and tested backup.
Cloud storage and cloud backup solve different problems. Storage helps people access and share current files. A backup keeps recoverable copies under a defined schedule and retention policy.
Sync can copy unwanted changes
When a synced file is deleted, overwritten or damaged, that change may be copied to the cloud and other devices. Version history or a recycle bin may help, but the available history depends on the service, plan, settings and time since the change.
Before relying on those features, check how far back the business can recover and who is allowed to remove retained data.
The service may not cover everything
Staff may save documents on the desktop, in downloads or inside an application rather than in an approved cloud folder. Accounting databases, line-of-business software and locally stored email may need their own backup method.
Microsoft 365 also contains more than files. Email, shared mailboxes, Teams and SharePoint data need a recovery plan that matches how the business uses them.
Do not include passwords in ordinary file backups. Store them in an approved password manager with an appropriate recovery process.
Recovery time matters
Recovering one deleted document is different from restoring a whole team after an account compromise or major outage. The business should know:
- which data is protected
- how often a recoverable copy is created
- how long copies are kept
- who can request and perform a restore
- how long a useful restore is expected to take
- what happens if the original account is unavailable
These answers should be documented rather than assumed.
Keep recovery separate from the original system
A common backup approach keeps more than one copy and avoids placing every copy under the same account or system. The exact design depends on the business, but one compromised administrator should not be able to destroy the working data and every backup without another check.
Restrict backup administration, protect it with a second sign-in check and review alerts about failed jobs or deleted copies.
Test a real restore
A successful backup status does not prove the data can be recovered. Test restores using files and systems the business actually needs.
Record what was restored, how long it took and any missing steps. Repeat the test after major changes to applications, storage or providers.
Choose one file, mailbox or business system that matters and ask for it to be restored. If nobody can complete that test, contact JCPIT for a backup and recovery review. We will document what is protected, what is missing and what a real restore requires.
