Back up and restore mailcow with its supported helper

mailcow provides a backup/restore helper in its repository. Follow its documented component model rather than assuming a copy of mailbox files also restores accounts, metadata, or encrypted content.

Capture the selected components

1. Read the backup guide for your release and run the helper from its supported repository location.
2. Select required components such as vmail, crypt, mysql, redis, and filtering state, or the documented all set.
3. Use a protected destination and preserve the suite’s deployment configuration and secrets through your secure recovery process.
4. Keep an off-host copy and monitor backup age/errors.

The helper’s backup form is ./helper-scripts/backup_and_restore.sh backup all; it creates real backup data and can consume substantial space. Review options before execution. Do not add automatic deletion flags until retention requirements are approved.

Prove a usable restore

Follow the matching restore guide on an isolated host. Keep its network/DNS from competing with production and prevent old queued mail from escaping. Verify account access, existing messages, encrypted-content readability, and controlled receipt/submission.

Test the restore procedure before an upgrade, not during an outage. A database backup without mailbox/encryption material is incomplete, while mailbox data alone loses suite metadata. Keep a compatible version/configuration record and an operator-owned rollback plan for the full stack.