---
title: "Comment by Rishabh Mishra on \"Automatic n8n backups: cron, encrypted copies and a tested restore\" | Hashnode"
description: "The restore test is the part most people skip, and checking that credentials still decrypt after the restore is the detail that makes it real. One thing I'd add"
url: "https://hashnode.com/posts/n8n-automatic-backup/6b003f755a93c41a0c992fbb/comment/6b0109752af2e1d651dbfc98"
---

[Discussion](https://hashnode.com/posts/n8n-automatic-backup/6b003f755a93c41a0c992fbb)

Comment [Automatic n8n backups: cron, encrypted copies and a tested restore](https://hashnode.com/posts/n8n-automatic-backup/6b003f755a93c41a0c992fbb)

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[1d ago](https://hashnode.com/posts/n8n-automatic-backup/6b003f755a93c41a0c992fbb/comment/6b0109752af2e1d651dbfc98)

The restore test is the part most people skip, and checking that credentials still decrypt after the restore is the detail that makes it real. One thing I'd add is a longer-lived monthly snapshot alongside the 30-day rotation, since a bad workflow edit can sit unnoticed for weeks. That way a restore point from before the problem still exists.
