If your computer fails today, how much work could you recover without relying on memory or luck? A useful backup plan gives you more than another copy of files: it gives you a tested way to get important projects and personal data back.
For a solo developer or small team, start with an automated local backup and a separate off-site copy. Keep older versions, protect access to the backups, and practice restoring files. This is more reliable than assuming file sync or a Git hosting account will recover everything.
Decide what you need to recover
List the files and services that would take the most time or money to replace:
- Active projects, including local Git repositories, uncommitted work, project assets, and files ignored by Git.
- Local databases, customer exports, documentation, and other data that cannot simply be regenerated.
- Personal documents, photos, and business records.
- Operating-system settings or a system image, if rebuilding the machine would be costly.
You usually do not need to preserve every downloaded dependency or build cache; those can often be recreated from source. Keep credentials and encryption keys in a password manager or another protected system rather than in an unencrypted backup archive.
Version control remains important for code history, but a remote repository is not a full computer backup. It may not include uncommitted changes, ignored files, local databases, or personal documents. Keep a separate backup of project files and machine data. If you need a refresher, see this guide to version control systems.
Use the 3-2-1 rule as a starting point
A common starting point is to keep three copies of important data in total, on two kinds of storage, with one copy off-site. For example:
- Keep your working files on your computer.
- Back them up automatically to an external drive or another local device.
- Keep a second backup in a separate physical location, such as a reputable online backup service or a drive stored away from your workspace.
The rule is a simple way to avoid relying on one device or one location; it is not a guarantee against every failure. Keep at least one backup offline or otherwise protected from changes made to your everyday computer. The CISA ransomware guide recommends maintaining offline, encrypted backups and regularly testing that they can be restored.
Automate a local backup
An external drive is often a practical first backup destination: it can restore large files faster than downloading them and does not require an ongoing cloud subscription. Use a backup tool that saves older versions, not just a one-way mirror of the current folders.
On macOS, Time Machine can back up files to an external storage device. On Windows, Windows Backup can help restore selected folders, settings, and app information when setting up a PC. Check what each tool actually includes: syncing selected folders or settings is not the same as keeping an offline, versioned copy of all the files you need.
Set the schedule according to how much recent work you can afford to lose. Daily backups are a sensible baseline for actively changing projects. If you change your tool or replace a drive, confirm that the new backup is running and includes the folders you expect.
An attached drive can be affected by theft, fire, accidental deletion, or malware while it is connected. Encrypt it, keep its recovery key somewhere safe, and disconnect it when a backup is complete if your workflow allows. A second drive stored elsewhere can provide an off-site copy without sending data to a cloud provider.
Add an off-site copy carefully
An online backup can protect against damage or loss at your home or office, but choose it for its recovery features—not just storage capacity. Check:
- Which folders and operating systems it supports, including external drives if you need them covered.
- How long it retains old versions and deleted files, and whether ransomware-encrypted files could replace healthy copies.
- How you can restore a large backup if your internet connection is slow.
- Whether data is encrypted in transit and at rest, how account recovery works, and what happens if you lose an encryption key.
- Ongoing cost, storage limits, and whether you can retrieve your data if you stop paying.
Cloud sync services are useful for keeping files available across devices, but synchronization can also copy an accidental deletion or corrupted file. Version history and recycle bins can help, but their retention may be limited. Do not count a synced folder as your only backup unless you have confirmed how far back you can restore it.
Protect the backup account with a unique password and multi-factor authentication. If you handle sensitive client or business data, review the provider's access and retention policies before uploading it. Keep an offline or otherwise isolated copy as an additional safeguard.
Test that recovery works
A backup job that reports success is not proof that you can recover your files. Every so often, restore a few files to a separate folder and check that they open. Also confirm that you know:
- Where the latest backup is and when it last completed.
- How to restore a previous version or recover deleted files.
- Which account, password, or recovery key is needed.
- How you would reinstall the operating system and restore critical projects if the computer were unusable.
If you keep a full-system image, make sure you understand its recovery process before you need it. A written checklist and a tested restore are more useful than a backup format you have never tried to open.
A simple plan to put in place
For many independent developers, a practical first setup is:
- Schedule a daily backup of active projects, local data, and personal files to an encrypted external drive.
- Keep a second, versioned copy off-site or with a provider whose retention and restore process meet your needs.
- Disconnect or isolate one copy when possible, and protect online accounts with multi-factor authentication.
- Test a file restore and review the backup schedule after major changes to your projects or computer.
Start with the files you cannot replace, then expand coverage as your needs grow. The right plan is one that runs consistently and that you can actually restore from.
