Ken, I recently upgraded and migrated at the same time. However, this was from 2.1.2 to 2.1.3.
I turned off external mail/web access to Mailman, confirmed I had no mail left to be processed and then tar'd n' zipped the 2.1.2 installation. I moved and unpacked it on the new box and then ran the 2.1.3 installation process overwriting the 2.1.2 files. All of my lists, subscribers, etc. remained intact and I was able to start using the lists immediately. I would suggest a dry run, but suspect that a similar approach would work from 2.0.13 to 2.1.3. Cheers, n. On Tue, Nov 04, 2003 at 11:08:15PM -0600, Ken Scott wrote: > We presently have Mailman v2.0.13 installed, with several lists created. > We're going to be moving shortly to a new system, on which I have > installed v2.1.3. Can I: > > (a) copy all appropriate files and aliases, etc., to the new system and > have the lists run successfully, without actually having to re-create > them? > > (b) re-create the lists, then copy all appropriate files and aliases, > etc., and have them run successfully? > > If the answer is no to both, what then would be the proper procedure to > follow in such a situation? One of these lists alone has several thousand > subscribers, so I'd hate for my list owners to have to start over from > scratch. > > Thanks in advance for any help. > > -- > Ken, > [EMAIL PROTECTED] > -- Nate Perry-Thistle Director of Technology Performance Learning Systems, Inc. http://www.plsweb.com/ ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
