- A proper backup strategy follows the 3-2-1 rule: 3 copies, on 2 types of storage, with 1 copy in a different location.
- Sync is not a backup: Google Drive, OneDrive and Dropbox pass on deletions too.
- If an AI works on your files, you additionally need earlier versions and a backup that the AI cannot reach.
- How much you need comes down to one question: what happens if your data is gone tomorrow? Would you have to close your company?
- A backup only counts once you have restored a file from it.
This guide takes you step by step to a backup strategy that fits your company, even if you let AI access your files or are just starting to. You get the rules, my own system as an example and a checklist to tick off. How AI can get started sensibly in a company overall is covered in the guide introducing AI in your company. What an AI agent is, I explain in AI agents explained simply.
What happens if your data is gone tomorrow?
Would you then have to close your company, or do you keep working after 2 days? The answer determines how extensive your backup strategy needs to be. If it is "That would be the end of the company", a single drive is not enough. If it is "I lose 2 days and keep working", less is enough.
Answer 4 questions about your company:
- Which data do you need to work? Invoices, quotes, customer data, plans, photos, e-mails, source code.
- How long can you work without it? A day is different from a week.
- How much work can be lost at most? CISA calls this the Recovery Point Objective (permissible data loss) and the Recovery Time Objective (permissible recovery time).
- Does someone else already hold a copy? For example the bookkeeping at your tax advisor.
2 obligations come with it. In Austria, you must keep books, records and receipts for 7 years under § 132 para. 1 of the Federal Fiscal Code (Bundesabgabenordnung). If you process personal data, Art. 32 para. 1 lit. c GDPR requires the ability to restore availability and access quickly after a physical or technical incident.
How much backup does your business need? 3 levels
Anyone who works with little data needs a leaner backup strategy than an IT company, but everyone needs a minimum. A carpenter or tiler who mainly manages invoices, quotes and construction-site photos loses receivables and records in a total failure. An IT company loses customer systems, source code and configurations.
| Level | For whom | At least |
|---|---|---|
| 1 | Skilled trades and service providers with invoices, quotes and photos on one computer | Automatic backup to an external hard drive at the computer, plus a second copy in another location (hard drive in rotation or cloud), restore a test file |
| 2 | Companies with mail, calendar and files in Google Workspace or Microsoft 365 and several employees | Level 1 for all computers, plus a separate copy of the cloud data with earlier versions, with it set down in writing who backs up what and when |
| 3 | IT companies and businesses that work with software, servers or AI agents | Level 2, plus version control for working files, server backup, a copy at a second location or in the cloud, an error message when a backup fails, restore test on a schedule |
Start at the level that matches your answer to the key question, and build up your backup strategy layer by layer. The Wirtschaftskammer advises putting the concept in writing. It defines which data is backed up by whom and when, how long older versions are kept, and who checks the restore.
Why are AI undo and sync not enough as a backup?
Both functions feel like a backup but don't back up permanently. This section shows what AI changes and why sync is something different from a backup.
Why does AI change the risk for your files?
An AI agent with access to your computer can create, rename, overwrite and delete files, and do so faster than you can check every change. That is no reason to do without AI. I work this way myself every day. Most of the time everything goes right, but when it doesn't, I want to be back at yesterday's state with a few steps.
3 things change your backup strategy compared with an office without AI:
- More changes in a short time: An agent edits many files in one session. A mistake then affects many files at once.
- Mistakes are noticed later: A wrongly renamed file is sometimes only noticed days later. A backup from this morning then only helps if you have kept older versions.
- The AI's undo function is not a backup: According to the Claude Code documentation (Anthropic, accessed in November 2026), /rewind only covers files that Claude edited in the session with its file tools. A file changed only by a shell command is not covered, nor are changes made by hand or from other sessions. For lasting versions, the documentation points to Git.
A 4th point comes on top: a backup hard drive that stays permanently connected to the computer can be reached by the AI too. The German Federal Office for Information Security (BSI) requires in module CON.3 (Edition 2023) that data backups cannot be overwritten, deliberately or accidentally. CISA recommends offline copies for this. A copy that isn't connected can't be changed by any AI or malware.
Why is sync not a backup?
A sync keeps files the same in 2 places, a backup preserves earlier states. The Synology Knowledge Center explains the difference like this: synchronization transfers changes at one location to the other and is meant for collaboration, not for long-term retention. A backup creates independent copies, preserves earlier versions and restores data after accidental deletion, damage or ransomware.
In everyday use this means: if you delete a file in Google Drive, shortly afterwards it is also gone on the synced computer. If an AI overwrites a file in the Drive folder, you have the wrong version in both places. Mail and calendar at Google or Microsoft are also your data in the provider's account, but not your own copy. If the account is blocked, both are unreachable at the same time.
You can recognize a backup by one property: you can bring back a state from a week ago, even if the file looks different today.
What is the 3-2-1 rule, and how do you put it into practice?
The 3-2-1 rule requires 3 copies of your important data, on 2 different types of storage, 1 of them in another location. CISA names it in its guide for SMEs as a proven rule of thumb, with a hard drive and the cloud as an example of 2 types of storage.
You put it into practice in 3 steps:
- 3 copies: the original on your computer and 2 backups. Time Machine on the Mac or backup software to an external hard drive is the first. Apple recommends a drive with at least twice the capacity of your Mac, used only for backups.
- 2 types of storage: for example an internal hard drive and an external hard drive, or a hard drive and the cloud. 2 partitions on the same hard drive don't count.
- 1 copy off-site: in a cloud, on a hard drive at your home or in a second building. In the event of a fire or break-in at the site, all copies would otherwise be gone at the same time. The Austrian Federal Economic Chamber considers a NAS worthwhile as a backup only if it is separated, in terms of both location and fire protection, from the computers being backed up.
The 3-2-1 rule is the framework of every backup strategy and protects against failure and loss of a location. Against mistakes that are only noticed later, only versions help, and with AI work they come in as the 4th layer.
The type of backup also plays a role. A full backup copies all data every time. Incremental means: only what has changed since the last backup is backed up. That is how Time Machine works after the first backup. Differential means: everything that has changed since the last full backup is backed up. Incremental saves space and time, but for restoring you then need the whole chain of backups.
Second NAS or 2 external hard drives in rotation: how does the copy get to another location?
There are 2 workable ways without a cloud: a second NAS in a different location or 2 external hard drives used in rotation. Both satisfy the “1 copy in a different location” part of the 3-2-1 rule.
Second NAS in another location: A second device in another building is additional security, and it backs up automatically. Many people don't want to set up a second NAS somewhere, though, and it isn't a must. It remains a good option for anyone with a lot of data who doesn't want to depend on a cloud provider.
2 external hard drives in rotation: This is common practice, and it works if a fixed routine is behind it:
- Drive A is connected to the computer and backs up automatically.
- Drive B is kept in another place, for example at home.
- Every 2 weeks on the same weekday, you swap the drives: drive A goes away, drive B is connected to the computer.
- Enter the swap as a recurring appointment in your calendar and tick it off.
- At each swap, you restore a test file (see the section on testing).
With AI work, swapping has one advantage: a hard drive that isn't connected can't overwrite anything. The drawback is the rhythm. Everything that has happened since the last swap is not yet on the off-site hard drive. The Wirtschaftskammer calls manual backup to removable media cheap and simple, but error-prone, because it is hard to automate. The routine is therefore part of your backup strategy.
What does a backup strategy look like in practice? My system as an example
My backup strategy consists of 4 layers that complement each other: version control, Time Machine, a NAS with cloud sync and a copy in a cloud. You don't need all of them, but the example shows which layer protects against what. I work with an AI agent directly on my Mac, so for me version control is the layer against AI mistakes.
| Layer | What it does | What it protects against |
|---|---|---|
| Version control (Git) | Stores regular versions of my text files and sits on a dedicated server at a hosting provider in the EU. Every night at 2 a.m., the current state lands there. | Wrongly changed or deleted files, including by the AI: I jump back to the state of an earlier night |
| Time Machine | Backs up the whole Mac hourly to a drive at the computer. According to Apple, it keeps hourly versions for the last 24 hours, daily ones for the last month and weekly ones for the time before that. | Defective hard drive, deleted file, apps and photos that aren't in Git. The hard drive is permanently connected to the Mac, so it isn't my only copy |
| NAS with cloud sync | Pulls my Google Drive files onto my Synology NAS via Cloud Sync. | Blocked account, provider outage |
| Copy in a cloud | The NAS backs up to a cloud with Hyper Backup. | Fire, burglary or theft on site |
The layers interlock. Every night, my Mac puts a copy of my working folder in Google Drive, and from there Cloud Sync fetches it to the NAS. That way, the work from the Mac automatically ends up in a second place without my having to do anything. Together this is more than the 3-2-1 rule requires: 3 copies on 2 types of storage, 1 of them off-site, plus versions.
As with any sync, the same applies here: cloud sync passes on deletions and does not replace versions. Git and Time Machine therefore protect against accidentally deleted or overwritten files. If you also want to back up mail, calendar and contacts from Google Workspace or Microsoft 365, you can use a NAS for that, for example with Active Backup for Google Workspace or Active Backup for Microsoft 365.
One detail I recommend for every cloud backup: choose a provider with a data center in the EU and encrypt the data before it leaves your line. The Austrian Economic Chamber advises encrypting sensitive data before transmission and names the “Austrian Cloud” seal of quality for Austria.
How do you test whether you can get something back?
A backup is only proven once you have restored a file from it. In module CON.3 (2023 edition), the BSI requires as a basic requirement to regularly test whether backed-up data can be restored correctly and in reasonable time. CISA recommends also checking whether you can roll data back at least 7 days.
The test takes a few minutes:
- In a test folder, create a file, for example "Testdatei.txt" with one sentence of text.
- Wait until the next backup has run. With Time Machine, choose "Back Up Now" in the menu.
- Delete the file and empty the trash.
- Bring it back from the backup. With Time Machine, you open the folder, start Time Machine, choose the state from a moment ago and click “Restore”. With Git, the command
git restorewith the file name is enough. - Open the file and check that it is complete.
Luckily, I have never yet had to restore anything from a backup. I have several ways to get a file back, and I know them because I have run through them with test files, not because I needed them in an emergency. That is exactly why the test with the test file matters: you want to know the process before you need it.
BSI and CISA give no fixed frequency for the test, only “regularly” and “according to plan” respectively. A workable rhythm is: 1 time right after setup, then after every change to the system, and with rotating hard drives at every swap.
Backup checklist to tick off
With this checklist, you can check in 10 minutes where your backup strategy stands and what is still missing. Every box that stays open is your next task. The checklist is also available as a printable PDF (in German).
Basics
- The key question is answered: what happens if my data is gone tomorrow, and would I have to close my company?
- I know which data I need to work and where it is stored.
- It is set down in writing who backs up what and when.
3-2-1
- My important data exists in at least 3 copies (original plus 2).
- The copies are on at least 2 different types of storage.
- At least 1 copy is stored in a different location.
- The backup runs automatically, or the manual swap is in the calendar as an appointment.
Cloud and AI
- My cloud data (Drive, mail, calendar) has its own copy with earlier versions.
- My working files that an AI works on are under version control.
- The AI reaches only the folders it needs, and not my backup hard drive.
- At least 1 copy is disconnected at times (drive in rotation or cloud with its own access).
- A cloud copy is encrypted and stored in a data center in the EU.
Recovery
- I deleted a test file and restored it from the backup.
- The next test is in the calendar as an appointment.
- I get a notification when a backup fails, and it doesn't just end up in a log file.
Frequently asked questions about backup strategy
How often should I make a backup?
Often enough that the loss between 2 backups is bearable for you. Ask yourself how much work may be lost at most: 1 day, 1 week? Time Machine on the Mac backs up hourly; swapping 2 external hard drives every 2 weeks only secures the state from the last swap. For files that change daily, you therefore need an automatic backup in addition to the swap.
Is Google Drive or OneDrive enough as a backup?
No. A cloud like Google Drive keeps files in sync between your devices; it does not back them up. If you delete a file or an AI overwrites it, that is carried over to all devices. A backup keeps earlier versions and can be restored after accidental deletion, damage or ransomware (Synology Knowledge Center).
Is a NAS with several hard drives a backup?
No, a NAS with RAID protects against the failure of a single hard drive. A deleted or overwritten file is just as gone in a RAID. According to the Austrian Federal Economic Chamber, a NAS only makes sense as a backup if it is physically separated from the backed-up computers and fire-protected.
Do I need a second NAS in another location?
No, it is an additional safeguard and not a must. Many people don't want to set up a second device in another location. The simpler alternative is 2 external hard drives in rotation, for example every 2 weeks, or an encrypted copy in a cloud in the EU.
How do I test whether my backup works?
Create a test file, delete it and restore it from the backup. This takes a few minutes. In the Grundschutz module CON.3 (2023 edition), the BSI requires regularly testing whether backed-up data can be restored intact and within a reasonable time. It doesn't specify a fixed frequency; a fixed date in your calendar helps.
How do I protect my files from AI mistakes?
Give the AI access only to the folders it needs, and keep those folders under version control, for example with Git. That way you can restore earlier states. An AI tool's undo function does not replace this: in Claude Code, /rewind only covers files that Claude edited with its file tools, and according to Anthropic it is no substitute for version control.
Sources
- CISA (Cybersecurity and Infrastructure Security Agency): “Back Up Business Data”, cisa.gov, accessed on 18 November 2026
- Austrian Federal Economic Chamber (Wirtschaftskammer Österreich): “Datensicherung mit Konzept: darauf müssen Sie bei der Planung achten”, wko.at, accessed on 18 November 2026
- Synology Knowledge Center: "Was ist der Unterschied zwischen Cloud Sync und Active Backup for Microsoft 365/Google Workspace?", kb.synology.com, accessed on 18 November 2026
- Apple Support: “Back up your Mac with Time Machine”, support.apple.com, accessed on 18 November 2026
- Anthropic, Claude Code Docs: “Checkpointing”, code.claude.com, accessed on 18 November 2026
- BSI (Federal Office for Information Security): “IT-Grundschutz-Kompendium, Baustein CON.3 Datensicherungskonzept, Edition 2023”, bsi.bund.de, accessed on 18 November 2026
- Legal Information System of the Federal Government (RIS): "Bundesabgabenordnung § 132 Abs. 1", ris.bka.gv.at, accessed on 18 November 2026
- EUR-Lex: “Regulation (EU) 2016/679 (GDPR), Art. 32 para. 1 lit. c”, eur-lex.europa.eu, accessed on 18 November 2026