RE: mail server changing machines
For what it's worth this is how I did it: Since I only had 100 users I added them new. If you have more users you will want to script this. Then I copied the contents of the squirrelmail data directory to my new machine. Since I already had samba on both boxes I then copied the /home directory from old box to new box. When all was copied over, I called the ISP and had them change the MX record to point to the new box. After that was done, I did a final check for any missed messages and copied them across. Once again if you have allot of users, you will definitely want to script out some of this. I had no downtime, and no lost mail. -Original Message- From: Nick Smith [mailto:[EMAIL PROTECTED] Sent: Friday, June 04, 2004 3:16 PM To: [EMAIL PROTECTED] Subject: mail server changing machines im going to be moving my mail server to another machine, and moving it off site at another location (more bandwidth). what would the easiest way and least down time way of doing that? i have the other machine already installed debian and updated stable, courier is installed, squirrelmail, etc, can i just copy over the config files and the Mailbox folders in each account and have it work? i really dont want to have to go through the hassle of reconfiguring everything and risk alot of downtime if i dont have to. TIA nick -- ComputerNick a.k.a. Nick Smith Email - [EMAIL PROTECTED] Web - https://www.ComputerNick.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mail server changing machines
hi ya On Fri, 4 Jun 2004, Nick Smith wrote: im going to be moving my mail server to another machine, and moving it off site at another location (more bandwidth). what would the easiest way and least down time way of doing that? i have the other machine already installed debian and updated stable, courier is installed, squirrelmail, etc, can i just copy over the config files and the Mailbox folders in each account and have it work? i really dont want to have to go through the hassle of reconfiguring everything and risk alot of downtime if i dont have to. moving mail means you have zero down time - other than telling your pop servers where to pop mail from ( MX 30 or MX 20 or its already load balanced ) MX 30 ( secondarymail.ComputerNick.com) will be handling all your mail while your primary MX 20 ( mail.ComputerNick.com ) is down and being moved when mail.ComputerNick.com comes back online, all mail will be forward to it from secondarymail.ComputerNick.com - than move secondarymail when you have time each and any mail server should be able to do everything the other was doing ( especially antispam and antivirus rules ) c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mail server changing machines
I dealt with this problem recently, my mail server had one of it's raid disks failed. I had to move it to another machine. While I powered the machine off to put in a new disk. I didn't want the downtime required for the reboot and putting in the new disk. I use the vserver project to use virtual server images, so it was trivial to do a full move of the system. Steps: Rsync data from vserver1 for virtual host mailserver1 to vserver2. stop mailserver on vserver1. Rsync data again, from vserver1 for virtual host mailserver1 to vserver2. start mailserver1 on vserver2. Downtime: 10 seconds to stop instance of mailserver1. 30 seconds to sync changes after system shutdown. 10 seconds to start up new vserver instance. Then the new system comes up with the exact same configuration as the old system, and mail just starts flowing through it again. I use this method to cluster webservers/database servers/mail servers. If you use heartbeat and drbd you can get transparent replication of the data in realtime, whith automatic failover if the primary server dies. -- --Luke CS Sysadmin, Montana State University-Bozeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
