The backup with full data sovereignty
Data in the cloud is not really lost until the one service that can open it has a problem. Keep a local copy of the data you cannot afford to lose.
Redundant is not the same as reachable
Cloud storage is built to survive a failed disk, and it does that well. What it does not survive is a failure in its own infrastructure. Notion runs on AWS, and when AWS has an availability problem, Notion can do nothing about it. Your data may still be there, and you cannot open it. Large providers have had more than one regional outage, and the story is the same every time: the data was never in danger, the account just would not open.
An account problem cuts you off just as completely. Somebody steals your account, or the provider bans it, and your data suddenly shuts you out while you wait for the outcome of an appeal. In each case the files still exist, and you cannot read a single one of them.
Worse still, a provider can end its service, and the terms of service keep that right. Waiting until you receive a notice of service termination before you think about your data is usually too late.
What a local copy actually buys you
A copy on your own disk is readable with no service involved: no login, no API, no rate limit, no policy and no subscription, and full data sovereignty. You can test it yourself today. Unplug the network and open it.
The properties that matter
Readable without permission
You do not need an account to read the copy. If you can open the destination folder, you can open the backup.
Data sovereignty
The copy stays in your hands and under your rules. Your retention setting decides how long you keep it, not a policy somebody else wrote.
The version history you chose
Keep the versions you decided to keep. Retention is a setting on your profile, not a plan tier you have to buy into.
The copy the rest depends on
Cloud copies, remote browsing and automation are extras on top. The local copy is what makes them safe to rely on.
The 3-2-1 rule, applied honestly
The oldest rule in backup still holds, because it answers one question: what if this copy is the one that fails? Keep three copies of the data on two different kinds of media, with at least one of them off-site. NotionManager writes the first copy and one of the media by definition. The rest depends on where you point your other profiles.
Three copies, two media, one off-site
| Copy | Where it lives | What it protects against |
|---|---|---|
| Working copy | The provider | Nothing on its own. This is the copy you are protecting |
| Local copy | A folder or external drive you own | Service outages, account bans, account loss, provider risk |
| Second local copy | A second disk or NAS | The failure of the first disk |
| Off-site copy | Another location, or a cloud folder you control | Fire, theft, flood, ransomware in the same place |
Local does not mean no cloud
Local backup and cloud storage are not opposites. Most cloud drives can be mounted as an ordinary folder. You point a NotionManager profile at that folder. The copy then goes to the cloud through the tool you already use. There is no integration to trust and no second account to open. Two providers, two folders and two independent copies, all written by one application. You get them by configuration, without a multi-cloud contract.
Your disk will fail too
Local storage fails in its own ways, and ignoring that is how people lose data twice. Disks die without warning. External drives are dropped or stolen, and they also get left in a drawer nobody checks. Ransomware encrypts everything it can reach, including a backup drive that is always mounted. Bit rot corrupts a file that nobody opens for two years.
So the local copy is not the safe one. It is one of the copies. Keep several copies. Keep one of them somewhere else. Leave one of them disconnected when you are not writing to it. Open a restored copy and read it now and then. A backup works because you have several copies. No single failure can take them all.
Put a copy under your own control
Download NotionManager, point a profile at a disk you own, and keep the first copy locally.
Where to go next
Frequently asked questions
Where does a NotionManager backup actually go?
Wherever the profile points: a folder on your machine, an external drive or a NAS share. A mounted cloud drive is an ordinary folder, so it works as a destination too.
Does a local copy replace the provider?
No, and it is not meant to. Keep the workspace where you work in it every day. The copy is there for the day the provider cannot serve you, so you still have your data.
How many copies should I keep?
Three, on two kinds of media, with one off-site. That is the 3-2-1 rule. NotionManager can write several profiles to several destinations and also offers a full export for cold storage, but it cannot decide for you how much your data is worth.
How do I know the copies are still good?
Open one and read it. A local copy can be browsed offline at any time. This is the only backup check that does not depend on the service you are protecting yourself against.