Many people only think about backups after losing data.
What to back up
- The database or data folder with workflows, credentials and executions.
- The encryption key, without which credentials cannot be read.
- Your configuration files.
- Exported copies of important workflows.
How often
Match it to how much you can afford to lose: daily for busy systems, weekly for light ones.
Test the restore
A backup you have never restored is a hope. Try restoring on a spare machine.
Updating
- Read the release notes for breaking changes.
- Back up first.
- Update on a test copy if the workflows matter.
- Update production and check key workflows.
Pin versions
Using a specific version instead of “latest” avoids surprise changes.
Related
Quick answers
What should I back up?
Database or data folder, encryption key and configuration.
Should I update immediately?
Read release notes and back up first.
What is pinning a version?
Using a specific version so updates do not surprise you.
Related reading
- How to Self-Host n8n with Docker: A Practical Overview
- n8n Security Checklist: Credentials, Webhooks and Access
- n8n Queue Mode and Scaling Explained for Beginners
Prefer feedback on your own workflows?
In our live n8n classes you build workflows alongside a trainer who reviews your work. It is a practical 15-day program for beginners to advanced learners.
See the 15-day n8n training | Find your city | Book free counselling