A conversation about backup as a service that starts with a cloud folder — “it’s in OneDrive,” “we have versioning,” “IT can restore the share” — usually fails at the first untested restore, not at the first sync icon. A cloud folder is a working copy with history. It is not backup as a service.
This page is the first Cloud advisor brief. It is not a backup product sheet, not a ranked list of platforms, and not a substitute for internet failover design. It is the set of questions that keep a folder tree from being treated as the service.
Why a cloud folder is not the service
Sync and versioning keep a live file available. They do not prove an isolated copy, a retention clock, or a restore someone has actually run. Two tenants can look identical in a folder tree and still leave ransomware-encrypted files as the only copy, leave SaaS mail off the register, and leave no one who can prove a restore before a reviewer asks. A Supplier Matrix or Hub catalog view has the same limit. It is a screen. It can show that backup-shaped offerings exist among Cloud, Security, and Colocation. It cannot name your systems of record, the restore window you will accept, or the information that must stay out of an uncontrolled first form. Treat the catalog as an outbound screen, not as the shortlist. The Data Partner is the advisor on that frame, not the backup operator.
Decision grid
Fill the same columns before anyone treats a folder tree as backup as a service.
| Question | Cloud folder | Copy job | Backup as a service |
|---|---|---|---|
| Isolated from production? | No — same tenant | Sometimes | Must be written |
| Retention you can prove | Version history | Until someone deletes it | Written clock |
| Who runs the restore? | User or IT guess | Unowned | Named owner |
| Survives wipe or ransomware | Often not | Depends | Design requirement |
| Evidence a reviewer accepts | Sync icon | Export file | Tested restore |
| Comparison format | Seat or storage | One-time dump | Same columns every option |
The live cloud security responsibility matrix is the companion when backup and restore tests are still unowned buyer controls. The live backup internet options page is a different job — path failover, not data restore. The colocation provider brief is the companion when media or gear still sits in a cage. The MSSP provider shortlist and the managed cybersecurity provider evaluation are the companions when someone is treating a folder copy as the security shortlist.
First-meeting scorecard
| Check | Written? | Owner |
|---|---|---|
| Systems of record in scope — and what is out | ||
| Isolated copy and any immutability need | ||
| Restore window you will accept | ||
| Last restore test, what failed, failback | ||
| What a later reviewer would receive |
If those answers are a cloud folder and a promised storage total, you do not have backup as a service. You have a working copy.
What this page is not
This is not a platform ranking, not a backup brochure, and not a claim that The Data Partner already restored anyone’s tenant after a folder walk-through. It is not internet failover design and not a substitute for the live cloud security matrix. Skip incentive talk, skip sync icons as a substitute for a tested restore, and skip any suggestion that a catalog row replaces a shared brief. Write the rows. Then request comparable replies. If you want a second set of eyes on the brief, start with a conversation.