A business file backup strategy: built for resuming, not for copying

The backup question is not whether files copy somewhere; it is whether the company could resume tomorrow from two independent copies, one beyond the failure's reach.

A company's files live scattered until the day one of them fails: invoices on the accountant's laptop, contracts in a partner's phone, the shared work in one cloud drive nobody has opened the settings of. The failure is rarely dramatic. A laptop that will not start, an account locked by a botched recovery, a deletion that synced everywhere before anyone noticed. The backup question arrives at that moment, and it is not whether the files copied somewhere.

The real question is whether the company could resume. That takes two independent copies, and one of them should live offline or in a different system from the originals, because the failures that hurt most are precisely the ones that reach into the same account the backup lives in. Ransomware that encrypts a drive encrypts the synced copy with it. A deletion by a signed-in user deletes it everywhere the sync reaches. A backup inside the same account as the originals is not a second copy; it is the same copy waiting to share the fate.

Sync is the word that hides this. File syncing is availability, and availability is valuable, but it is not backup: it makes the current state of a file present in many places, including its worst state. Backup means history and independence: versions from before the mistake, stored where the mistake could not follow. A company that says the files are in the cloud has answered the availability question and left the recovery one untouched.

The honest test of a backup is a restore, not a green tick. Restoring something real, on a schedule, to a different place, is the only proof the copy works, and it takes minutes; trusting the tick takes nothing and proves nothing. The drill also answers the questions the tick cannot: who holds the credentials, how long a full recovery takes, and whether the files that come back are the files the business needs.

What belongs in the protected set is the company's memory: invoices and contracts, licenses and formation papers, client work, and the record of accounts and who owns them. The site is its own discipline with its own copies; this folder is the one that keeps the company running while everything else is rebuilt. And the backups belong to the company account, not to whoever set them up, because a backup that leaves with an employee was never the company's.

The discipline is small and recurring: a rhythm on the calendar, an owner named, a restore drill a few times a year, and a note of what was restored and how long it took. None of it is technical heroics. The reason companies skip it is that backups are invisible until the day they are everything, and by then the cheap version of the work has stopped being available.

The honest limit is regulatory: how long records must be kept, and in what form, differs from one country and industry to another, and those specifics belong to counsel and the provider's own documentation. Where we sit is the structure: our cloud and domains service sets up the copies, the offline leg, and the restore test as routine. Guidance, not guarantees: the point of a backup is not that files exist somewhere; it is that the business does.