[Mailman-Users] Migrating and Upgrading

[Dave Warchol]

Mark:
         First, thanks very much, your approach much easier and faster than mine.  I setup a testlist on the existing production server (call it server1) and was able to migrate the list and its archvies to a temporary box (call it server2) with a different hostname.  However, when I access the admin pages for the migrated list on on server2, each of the links is to server1 (general options, etc.).  For testing purposes, is there a way to change all of the references to the correct hostname on server2?  
Thanks,
Dave
>>> Mark Sapiro <mark at msapiro.net> 1/2/2008 5:22 PM >>>
Dave Warchol wrote:
> 
>One method I have considered would be "brute force" (a little labor intensive, a little heavier on the downtime, but doable):
>- dumping the metadata from the old lists (configuration, members, etc.)
>- bring the old server down
>- bring the new server up with the same name/IP
>- manually create the new lists
>- import the members for each list
>The only unknown is how to move the archives.
> 
>Any advice would be greatly appreciated.


Too hard.

Do not manully create the old lists on the new server. This is
important.

Copy/backup the lists/<listname>/config.db files from the old machine
and copy/restore them to the new server. There must not be an existing
lists/<listname>/config.pck on the new server at this step. If there
is because you created the list on the new server, remove the
config.pck leaving only the config.db.

Archives can be moved by either moving the entire archives/private/
tree or by moving just the
archives/private/<listname>.mbox/<listname>.mbox file and running
'bin/arch --wipe <listname>' for each list. If you do the latter, it
is a good idea to first check the .mbox files with bin/cleanarch.

Mailman will automatically update the config.db info (list config,
membership, options, etc.) and save a current format config.pck as
each list is accessed. You can force this for all lists by just
running bin/list_lists. Once the lists are converted and there are
config.pck and config.pck.last files, remove the old config.db or you
run the risk at some future time of falling back to the config.db if
the config.pck* files become corrupted.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

------------------------------------------------------
Mailman-Users mailing list
Mailman-Users at python.org 
http://mail.python.org/mailman/listinfo/mailman-users 
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 
Searchable Archives: http://www.mail ( http://www.mail/ )-archive.com/mailman-users%40python.org/
Unsubscribe: http://mail.python.org/mailman/options/mailman-users/warchol%40harthosp.org 

Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&amp;file=faq01.027.htp