部署

¥Deployment

Feature availability

Embed requires an embed license. For more information about when to use Embed, as well as costs and licensing processes, refer to Embed on the n8n website.

请参阅 托管文档 文档了解详细的设置选项。

¥See the hosting documentation for detailed setup options.

用户数据

¥User data

n8n 建议你遵循 n8n Cloud 内部使用的相同或类似的实践：使用 Rook 保存用户数据。如果 n8n 服务器宕机，则会在另一台机器上使用相同的数据启动一个新实例。

¥n8n recommends that you follow the same or similar practices used internally for n8n Cloud: Save user data using Rook and, if an n8n server goes down, a new instance starts on another machine using the same data.

因此，除非发生灾难性故障，或用户希望在你规定的保留期限内（n8n Cloud 为两周）重新激活其账户，否则你无需使用备份。

¥Due to this, you don't need to use backups except in case of a catastrophic failure, or when a user wants to reactivate their account within your prescribed retention period (two weeks for n8n Cloud).

备份

¥Backups

n8n 建议通过附加另一个容器并将所有数据复制到该容器来创建每日备份。这样一来，内存占用几乎可以忽略不计，因此不会影响服务器可容纳的用户数量。

¥n8n recommends creating nightly backups by attaching another container, and copying all data to this second container. In this manner, RAM usage is negligible, and so doesn't impact the amount of users you can place on the server.

重启

¥Restarting

如果你的实例宕机或正在重启，在此期间遗漏的执行（例如，Cron 或 Webhook 节点）将无法恢复。如果你需要保持 100% 的正常运行时间，则需要在其前面构建另一个代理来缓存数据。

¥If your instance is down or restarting, missed executions (for example, Cron or Webhook nodes) during this time aren't recoverable. If it's important for you to maintain 100% uptime, you need to build another proxy in front of it which caches the data.