Ok, so I've opted to do my migration as a more gradual process rather than stressing myself out and trying to cram it all into one operation. Although this will end up taking longer and doesn't accomplish my original goal right away, I think it'll be easier for everyone.

The newest production mail servers we have is Q2, which runs QMT, and is only hosting 10 or so domains. Very little usage, and the traffic is at about 100MB per day on average. My new plan of action is to break down my list of domains into reasonable sized groups, which for the sake of simplicity we'll call "migration 1", "migration 2", and so on and so forth. I'll develop a timeline for each migration group, and coordinate with the domain admins for those domains - providing them with dates, changes necessary, etc. Then I'll do the process I've been doing already, and migrate a domain at a time, but this time copy the mail and make the necessary changes to smtproutes, dns, etc as needed.

Seems easier than doing 4,000+ users all at once, right? ;-)

One of my goals was to eventually setup some form of replication (ideally it would be offsite, so if our main location ever went down we could keep things going at the secondary). I've watched Jake's "Replicated QMT" videos, and I'm watching the "QMT ISP Array" series now. I'm trying to do a better job planning this one out, and wanted to get some recommendations from other out there. Anyone else doing replication? Say I setup a replicated toaster like Jake does in "Replicated QMT"...how difficult, if even possible would it be to convert that into something more like the "QMT ISP Array" setup down the road?

I have a stack of unused servers, but I really want to get everything moved from the Solaris box to a newer Linux machine ASAP, and I need to figure out how to integrate everything in with my current setup (or change it accordingly).

Gateway 1 & Gateway 2 -- QMT's running Spamdyke
                |
        SA1 & SA2 -- QMT's running SpamAssassin
                |
Pop (old Solaris server) & Q2 (QMT)

Essentially that's the majority of it. So I guess what I'm asking is, is it possible to setup a QMT, add replication, and then grow it into a cluster? If so, what might the best approach be? Keep in mind, I'm trying to have as little impact as possible on my users, so they aren't having to change their settings every 5 minutes.

Thanks in advance!

--
Casey

Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com <http://www.smileglobal.com>

Reply via email to