Automating n8n backups with cron, encrypted offsite copies and a tested restore
A guide describes how to turn a manual n8n backup into a daily automated process on a VPS. A script dumps the PostgreSQL database, saves the .n8n folder and the .env file containing the encryption key, and uploads everything encrypted to an off-server S3-compatible bucket while pruning old copies. The author stresses that the encryption key must be included, since without it saved credentials cannot be read after a restore. Setup uses rclone, installed from the project's own package, with a dedicated bucket and access key, plus an encryption layer that protects both file contents and names. The process ends by restoring the backup into a separate project to verify that workflows and credentials are recoverable.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in