A backup plan is only useful if you can restore it

Your files appear on your laptop and your phone. Does that mean they are backed up? Not necessarily. Synchronization makes the current state available in more places. An independent backup gives you a way to recover when that current state is wrong, missing or inaccessible.

Microsoft's OneDrive documentation gives a concrete example: deleting a synced online-only file removes it from the cloud and other connected devices too. A recycle bin can help, but recovery depends on the service's retention rules and whether the item was permanently removed.

Choose what deserves protection first

Start with files that would be difficult or impossible to recreate: original photographs, finished creative work, personal documents, active projects and the data behind a website. Then separate them from downloads that can easily be obtained again.

Write down where the originals currently live. A folder called “backup” on the same failing device does not protect against that device being lost. Likewise, several accounts on one service may still share a common access or provider dependency.

Use the 3-2-1 idea as a starting structure

CISA's backup guidance describes keeping three copies of important data, using two different storage types, with one copy elsewhere. The purpose is to avoid a single incident affecting every copy. CISA also recommends offline, encrypted backups and regular recovery testing in its ransomware guidance.

For a small personal collection, an example could be the working copy on a computer, a separate external drive and an appropriately protected remote backup. This is an example architecture, not a claim that every combination meets every threat. Keep at least one recovery copy outside continuous synchronization, and protect its encryption or recovery credentials separately.

Decide how much work you can afford to lose

Backup frequency should follow the value and rate of change of the files. A project edited every day needs a different schedule from an archive that changes twice a year. Choose a routine you can actually maintain, then document the last successful backup.

Keep more than one dated version when mistakes might remain unnoticed. Overwriting the only backup immediately after a corrupted file appears may replace the good copy you needed. Check whether your backup tool preserves versions and for how long; do not infer this from the presence of a cloud icon.

Run a harmless recovery test

Create a small test folder with a document and a photograph. Back it up, then restore the copy to a different location. Open both files and compare them with the originals. Do not delete your only real files to test recovery.

Repeat the exercise for a representative project with its folder structure intact. A website export may contain text and metadata but not the original image bytes. Confirm what each export includes before treating it as a complete backup.

Keep a recovery note

Record where each copy is stored, what it contains, when it was last checked and how to access it if your main device is unavailable. Store sensitive recovery information securely rather than in a public document.

Review storage space and error notifications periodically. A backup job that stopped months ago is not current protection. The goal is not to collect the most cloud accounts; it is to know which independent copy you can restore, how recent it is and what steps will bring your work back.