Fine with either language as response.
I have automatic backups running of mailcow, the way I do it is to snapshot the underlying filesystem for the volumes using ZFS on an hourly basis. The main issue is that some of the volumes (mostly redis) seem to completely change their content once per hour at least, this means that the backups for those volumes grow drastically in size in a very short time (Total storage usage online is still low, its just the backups that are growing).
I would like to know what each component does (in a bit more detail than in the docs) and which are really needed for a functioning backup (functioning meaning that I can restore it and users/mails/settings are available again).
The official docs for redis (https://mailcow.github.io/mailcow-dockerized-docs/u_e-redis/) for example say:
Used as a key-value store for rspamd and (some of) mailcow’s settings and data.
The problem is that its not clear whether those settings and data are relevant in some way or form. Looking at the monitor log it seems its mostly F2B.
Would be great to just have one sentence at the bottom of the docs that describe what breaks if you don’t backup this particular component.