Hello @james ,
Thanks for the response.
My question is more about architecture and best practices for running Cloudron as a more serious mail server setup.
Until now my usage was mostly hobby-level, with small mailboxes. Now I need to host around 60 accounts totaling ~1TB, so I'm trying to design the setup properly before deploying it.
What I'm trying to understand is mainly:
1. Storage layout
I understand I could simply expand the primary disk of the VM. That is straightforward in Proxmox.
However, from a system design perspective, I was wondering if it would be better to:
- keep the system disk small (OS + Cloudron core)
- attach a separate disk dedicated to mail storage
For example mounting something like:
/home/yellowtent/boxdata/mail
on a dedicated volume.
The idea behind this would be:
- better separation between system and mail data
- easier capacity management
- possibility of using a filesystem with compression (e.g. zstd) to maximize storage efficiency
- simpler disk replacement or migration in the future
But at the same time I don't want to diverge from the recommended Cloudron layout, because I would like to keep the installation as "standard" as possible in case I ever need support.
So the main question is:
Is expanding the main disk considered the recommended production setup for Cloudron mail servers?
Or is using a dedicated volume for mail storage also a common and supported approach?
2. Backups
Regarding backups, my doubt is specifically about data located on a secondary disk.
If I move /home/yellowtent/boxdata/mail to another mounted disk:
- Will the Cloudron backup system still include it normally?
- Or are there caveats when the data directory is located on another filesystem / mount point?
I'm not trying to customize Cloudron unnecessarily — I'm mainly trying to understand what a good production storage design looks like when Cloudron is used as a mail server with ~1TB of mail data.
Any recommendations or real-world setups from other users would also be very helpful.
Best regards,
Diego
