1. Choose what you cannot easily replace
Begin with a short inventory: personal documents, photographs, project files, and any exports needed to reopen your work in another application. Installed software is often replaceable; the work you created with it may not be.
Check where applications really store their data. A shortcut on the desktop is not the document itself. Some programs keep a collection in a database or require an export to make a portable copy. Consult the application’s instructions before copying live data files.
Write down the locations you intend to protect. Include files outside the obvious Documents or Pictures folders. Keep recovery codes and other sensitive records in a suitably protected location, with an access plan that does not depend entirely on a lost device.
2. Separate a backup from a mirror
Synchronisation keeps locations aligned. That is convenient, but an accidental edit or deletion may propagate to every synced device. Some services retain older versions; others have limits you need to check. Sync is not automatically a complete backup plan.
A backup gives you a recoverable copy from an earlier point in time. A useful starting pattern is three copies of important data, on two kinds of storage, with one copy somewhere else. Treat this as a way to reduce shared points of failure, not a promise that nothing can go wrong.
- The working copy: the files you use each day.
- A local backup: for example, a versioned backup on an external drive.
- A separate copy: for example, a suitable remote backup service or a drive stored in another location.
Two folders on the same drive are not independent protection against that drive failing. Two drives beside the same computer can still be lost together. A disconnected backup can limit exposure to mistakes or malicious changes, but only if you reconnect it often enough to keep useful copies.
3. Set a routine you can maintain
Choose a schedule based on how much work you could tolerate losing. If losing a day would be painful, a monthly copy is not enough. Automatic backups reduce the need to remember, but still need occasional checks.
Keep more than the most recent version. You may not notice a missing folder or damaged file immediately. Retention—the length of time older copies are kept—matters as much as frequency.
Check available storage and failure notifications. A job that ran is not necessarily a job that saved everything. If a drive must be connected manually, attach that step to a habit you already have and disconnect it safely afterward.
Protect the copy as well as the original. Backups may contain everything an unwanted reader would need. Consider encryption and access controls appropriate to the data. Keep recovery keys available separately: an encrypted backup without its key may be impossible to restore.
4. Practise a small restore
- Choose a harmless test file. Create a short text document with a recognisable sentence and let the next backup include it.
- Find that backup. Confirm the saved date and locate the test file using the normal recovery interface.
- Restore to a different folder. Do not overwrite the working copy. Use an empty destination so you can clearly see what was recovered.
- Open and inspect it. Check the contents, not just the filename. For a real-world sample, also try a photograph or a document in the application that uses it.
- Record the result. Note the date, the backup used, and any steps that were unclear. Repeat after changing tools or storage.
Recovering one file demonstrates one path, not complete disaster recovery. A full device replacement may also require software, account access, licence information, and more time than a small file test. Plan those dependencies separately.
5. Keep a short recovery checklist
Write down where the backups live, how to access them, and which folders are included. Do not put passwords directly into a shared checklist. Make sure you can find the instructions without the computer you are protecting.
- Can you identify the most recent successful backup?
- Is there an older version if a mistake went unnoticed?
- Can you access at least one copy if the main device is unavailable?
- Have you opened a restored file, rather than only seeing it listed?
A modest routine with a tested recovery path is more useful than an elaborate setup you no longer understand or maintain.