bob B via Mailman-users writes:
Thanks, but how would make backup mbox files in mailman3 with Hyperkitty?
You don't do it with HyperKitty (I'm pretty sure you can export mboxes from HyperKitty, but I don't think it would be timely, you have to do it by hand). The sample archiver (which you can enable in mailman.cfg IIRC, haven't done it in a while) would make the mbox files directly from the core at the same time that they are sent to HyperKitty. It's possible to have both HyperKitty and the sample archiver enabled at the same time.
I thought all the messages were stored in the database and there were no mbox files anymore.
That's true in HyperKitty. The sample archiver is a separate facility that's part of core. All it does is append to an mbox on the core's host. It has no facility for display to users. It's basically a developer demo for how you attach an archiver to Mailman core, but it's also a possible backup approach for a very careful admin like you.
I would assume I would just be able to restore the database
True, but how frequently do you back up the database? The "also store to mbox" approach I described loses no messages even if your database gets trashed (unless the mbox also gets trashed in the the disaster, but if I understand your setup correctly, the mbox would be on the core's host, while the database server and storage is on a different host, so trashing both would be a really bad situation, hopefully very unlikely).
and reinstall/rebuild mailman and then run maybe a script to make sure the archives are rebuilt?
If the database restore is successful, there's no rebuilding to do. The database is the archive. You just need to reattach it to HyperKitty.
and then I would be good to go.
Yes, modulo the period between most recent database backup and disaster.
Regards, Steve