Build a backup plan with separate failure paths

Count copies, not devices

A backup plan begins with a list of the files you cannot comfortably recreate. Documents, family photographs, and current projects usually matter more than downloaded installers that can be fetched again. Locate the original data before buying storage, because it may be spread across a laptop, phone, external drive, and cloud account.

The Australian Cyber Security Centre's guidance describes the familiar three-copy approach: a primary copy and two backups, with different media and an offsite copy. The purpose is to reduce shared failure risks. Three folders on the same drive do not provide the same protection as copies that can survive different events.

Likewise, moving a photo collection from a laptop to a large external drive does not increase the copy count. If the laptop copy is deleted, the external drive has become the primary location.

Map the events you want to survive

A failed drive, accidental deletion, stolen bag, damaged room, and compromised account are different problems. A second drive sitting beside the first helps with some hardware failures but may be lost in the same theft or spill. A synchronized cloud folder can help with a lost computer, yet a mistaken deletion may also synchronize.

Write the likely events in plain language and identify which copy would remain. This is more useful than labeling a setup safe because it has a certain number of devices. If every answer points to the same desk or the same account, the copies are not as independent as they appear.

A disconnected backup can reduce exposure to some mistakes or malicious changes while it is offline. It also becomes stale until reconnected, so the routine must balance separation with freshness.

Set a schedule around change

A monthly backup may be adequate for a collection that rarely changes and inadequate for daily work. Decide how much recent work you could tolerate recreating, then schedule backups more frequently than that loss window. Large first backups can take time, so begin while the primary data is still healthy.

Automatic software is useful because memory is unreliable. Microsoft File History is one example of a tool that keeps versions of supported personal files on another destination. Whatever tool you choose, check its included folders and exclusions. An external project drive may not be covered merely because the laptop's Documents folder is.

Keep notifications visible and investigate missed backups. An automatic task that has failed quietly for weeks is not an active protection plan.

Use a simple role map

A household might keep current files on a computer, a versioned local backup on a separate drive, and an additional protected copy in another location or service. The details depend on data size, connection speed, and privacy needs. The following role map is a starting point, not a requirement to buy three particular products.

Prove recovery before calling it finished

Restore a few sample files to a separate folder and open them. Include a photograph, a document, and a file from any specialized application you rely on. Check that older versions can be found if version history is part of the plan.

Record where the backups live, which software reads them, and where recovery credentials are stored. Keep the record understandable to your future self. A drive full of unnamed backup files can be difficult to use under pressure.

Review capacity and coverage as the collection grows. New folders, replacement computers, and changes to cloud plans can create gaps. A successful backup plan is not a one-time purchase; it is a small repeatable process that keeps independent copies current and makes restoration familiar.