I’m looking to migrate several mailing lists from one server running MM3/Django/Hyperkitty to another. Same operating system and python environment and venvs for both. Although the canonical hostnames for the two servers will differ, I can use the same hostnames for lists once I’ve got everything set up.
Is this really as simple as building the new server, creating the same lists on the new server, and rsync’ing the archives from the old server? If not, how to do the migration?
I checked the archives and saw many threads on MM2 -> MM3, but did not see anything on MM3 migration. Thanks in advance.
dn
On Wed, Feb 1, 2023 at 12:35 AM David Newman <dnewman@networktest.com> wrote:
I’m looking to migrate several mailing lists from one server running MM3/Django/Hyperkitty to another. Same operating system and python environment and venvs for both. Although the canonical hostnames for the two servers will differ, I can use the same hostnames for lists once I’ve got everything set up.
Is this really as simple as building the new server, creating the same lists on the new server, and rsync’ing the archives from the old server? If not, how to do the migration?
I checked the archives and saw many threads on MM2 -> MM3, but did not see anything on MM3 migration. Thanks in advance.
Seeing as a venv is a self-contained container, I am tempted to say that it's possible to move one from one server to another - AS LONG as you also migrate the DB.
I am not an expert on this so I stand corrected.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 1/31/23 13:34, David Newman wrote:
Is this really as simple as building the new server, creating the same lists on the new server, and rsync’ing the archives from the old server? If not, how to do the migration?
If you want to mirror the entire installation, you can dump the databases off the old server and import them to the new server. Depending on the installation, everything may be in one database or there may be separate ones for mailman core and mailman web. This is a little tricky because some of the tables have to do with Django stuff.
To do only selected lists is much more difficult and there are no scripts that I am aware of.
HyperKitty can dump a list's archive as a mbox which could then be used as input to hyperkitty_import on the new server to move archives, but there are no similar scripts to dump list settings, users, memberships, etc. in a format that can be imported.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/31/23 2:01 PM, Mark Sapiro wrote:
On 1/31/23 13:34, David Newman wrote:
Is this really as simple as building the new server, creating the same lists on the new server, and rsync’ing the archives from the old server? If not, how to do the migration?
If you want to mirror the entire installation, you can dump the databases off the old server and import them to the new server. Depending on the installation, everything may be in one database or there may be separate ones for mailman core and mailman web. This is a little tricky because some of the tables have to do with Django stuff.
To do only selected lists is much more difficult and there are no scripts that I am aware of.
HyperKitty can dump a list's archive as a mbox which could then be used as input to hyperkitty_import on the new server to move archives, but there are no similar scripts to dump list settings, users, memberships, etc. in a format that can be imported.
Thanks for this. Would I need to create the lists first on the new server before restoring databases and running hyperkitty_import?
Also, I'm unclear about there not being scripts for settings, users, etc. –– isn't that stuff in the mailman database?
Thanks!
dn
On 1/31/23 18:35, David Newman wrote:
Thanks for this. Would I need to create the lists first on the new server before restoring databases and running hyperkitty_import?
No. If you transfer the database, that will bring the lists and hyperkitty archives with it.
Also, I'm unclear about there not being scripts for settings, users, etc. –– isn't that stuff in the mailman database?
Yes, it's all in the database. What I was referring to is an abstract need to export everything for a single list from the database to some kind of flat file and a way to import that into another installation, but none of that is relevant if you are going to transfer the whole database.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
David Newman -
Mark Sapiro -
Odhiambo Washington