|
Curious about your problems with the PowerEdge's
with built-in Intel Pro 100s...we've been running that combination for
years with no problems...so it must be something else, or a combination of
things that's causing the problems you experienced.
Darin. ----- Original Message -----
From: Todd Ryan
Sent: Saturday, April 03, 2004 11:37 AM
Subject: Re: [IMail Forum] Server Migration / Version
Upgrade We've done several similar upgrades/migrations. But as others have suggested, you're probably better off not doing both at the same time. We've moved IMail from an NT Domain controller to an AD Domain controller with few issues. I just recently moved it from an older DC to a brand new one. I even reconfigured the drives so that programs were on one drive, spool/logs another, and mailboxes yet another. With a little planning, it was transparent to the users. I did not do the MX record ahead of time as was suggested. But rather I did the switch in the wee hours of the morning at the same time I migrated the mail server. Anything servers that were attempting to deliver to the old server because they didn't have the new MX record kept retrying until they got the updated record. One thing that made the migration easier/faster was using robocopy from the resource kit to migrate the mailboxes. I ran it once well before the final migration to get a baseline copy of the the user data. I used the /MIR parameter to make an identical copy. I ran it frequently up to the cutover date and the last time I ran it, it only took a few minutes to get the last few changes. I wrote a batch file with several robocopy commands to stop the services on the old box, copy folders to one drive, programs to another, spool to the third. Then I exported the registry key on the old box, did search/replace in the reg file to change the IP address and drive letters. Imported to the new box, changed MX records, fired up the services and waited. You didn't mention the hardware for your new server. We run Dell Poweredge servers and I ran into similar hardware problems with the last two servers we migrated to. That is, the built-in NICs do NOT work well with IMail. The last time we did it, IMail simply was slow. We disabled the Intel Pro 100 NIC in the bios and installed a new 3com NIC. Worked great. This time I figured the problem should be resolved by now. But after running in test mode with no issues, once we put a load on the brand new 2600 with Intel 1000 NIC onboard, the entire network stack quit. Couldn't even ping it. No errors, no nothing. Just quit. Again, disabled the NIC in the bios, insert 3com NIC, then it was rock solid. I can't wait until Ipswitch works reliably with something other than 3com NICs! Good luck! --Todd. Matthew Brandes wrote:
|
- [IMail Forum] Server Migration /... Matthew Brandes
- RE: [IMail Forum] Server Mi... Hostmaster Online Services AS
- Re: [IMail Forum] Server Mi... serge
- RE: [IMail Forum] Serve... Laura Bhandari
- Re[2]: [IMail Forum... Sanford Whiteman
- Re: [IMail Forum] Server Mi... Sanford Whiteman
- Re: [IMail Forum] Server Mi... Todd Ryan
- Re: [IMail Forum] Serve... Darin Cox
- Re: [IMail Forum] S... Todd Ryan
- Re: [IMail Foru... Darin Cox
- [IMail For... Panda Consulting S.A. Luis Alberto Arango
- RE: [IMail Forum] S... Troy Atwood
- RE: [IMail Foru... Dave Riddle
- Re: [IMail... Todd Ryan
