Set-and-forget automated data protection
A backup you have to remember will eventually stop happening. Give it a schedule, and decide in advance how much history to keep.
Why the clock matters more than the button
Manual backups fail in a predictable way. They happen while the habit lasts, and then they stop. Nothing announces it. The last successful run simply gets older, and the gap between your copy and your workspace grows. You find out on the day you need the backup.
Automation turns that into a setting. You set the times when a backup should run, and NotionManager does the rest. There is no reminder to dismiss and no habit to keep.
Two ways to say when
Most workspaces want the same thing every time: once a day, or once a week. That is a fixed schedule. If you want more flexible control, use an advanced schedule. It accepts a cron expression, which can say anything from every ten minutes to the second Tuesday of the month.
Choosing a schedule
| Schedule | Written as | Good for |
|---|---|---|
| Daily, fixed time | A time of day | Workspaces that change most days; the usual default |
| Weekly, fixed time | A weekday and a time | Reference material that changes slowly |
| More flexible control | A cron line | Off-hours windows, several runs a day, month-end jobs, anything irregular |
Retention: the setting that makes automation sustainable
An automated backup that keeps every version forever will fill the destination disk. Retention lets you decide how much history to keep before the disk fills up. You can keep every version from the last three months, or keep the most recent twenty runs. It depends on what you need.
Retention also decides which questions your copy can still answer. Keeping one run a day for three months answers "what did this page say in April". Keeping twenty runs answers "what did this page say in the last twenty changes". Neither choice is wrong. They answer different questions, so pick the one you need.
What automation covers
The schedule itself
Each profile has its own schedule, so you can back up a fast-changing workspace and a slow archive at different times.
The retention window
You set how long history is kept and how many runs are kept on each profile.
The history of the backup
Automated backups are listed in the backup history, just like manual ones. You can check at any time that they are running as expected.
Let the backup handle itself
Download NotionManager, set a daily time or a cron line, and use retention to keep the history you want.
Where to go next
Frequently asked questions
How often should I back up a Notion workspace?
Once a day is the usual answer. If you lose a day of work, you can still recover it. Daily runs are not so frequent that the copies are mostly duplicates. Workspaces that are edited all day can run more often. Reference material can be weekly.
Will it fill my disk?
It grows only as fast as your settings allow. Retention bounds the history to three months or twenty runs, and the destination is a folder you chose. The growth is a decision you made, not a surprise.
Do the runs happen on my machine?
Yes. The schedule runs locally and writes to the destination you set. You need to keep the machine running, with NotionManager also running in the background.
Is scheduling part of the free tier?
Scheduled and advanced-schedule backups, and retention, come with a paid licence. The free tier triggers backups by hand, without a limit on how many runs you make.