Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
Moving exchange to new hardware - 13.Jan.2009 11:21:49 AM
Posts: 145
Joined: 20.Nov.2001
From: UK
Status: offline
Hi
My basic setup should be in my signature below. Our Exchange server is on its last legs (numerous blue screen crashes in the last week) so I'm planning on using the procedure in this Technet article to restore Exchange to a new box with the same name. Basically taking an online backup, taking the old server offline, resetting the computer account then joining the new one to the domain with the old server's name and setting up Exchange, then restoring from backup.
First question - it specifies that the new box should be installed with the same OS. The old one us Server 2003 Standard SP2 and the new one is Server 2003 RC2. Is that likely to be a problem at all?
Also, in general - the procedure looks almost too straightforward - has anyone tried this and are there any obvious pitfalls I should be looking out for? It's not identical hardware (both HP ML350s, but several years different in age ).
Anyway, any hints and tips gratefully received.
Cheers
Rich
_____________________________
Exchange Server 2003 Standard SP2 on Windows Server 2003 Standard SP2, 45 clients running XP SP3 and Outlook 2003 in cached exchange mode.
Posts: 5428
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Actually that's not the way I would want to approach it given that your store could be a bit screwed up due to the crashes. I would set up the new server and do mailbox moves to it. Fresh mailboxes in a fresh store. Then you know everything came over clean.
Posts: 5428
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Goodness no.
Install the new Exchange server with a new name on the network. Do not worry about the name or IP addressing or anything else. Set up the public folder replicas, remember the system folders, and then create a test mailbox to make sure you can see other people's free/busy information and normal public folder content. Then do the move mailbox process (http://support.microsoft.com/default.aspx/kb/224975 ) will help you do that but really, it's not difficult to right click on a batch of mailboxes.
Posts: 5428
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Why? The short name of the server is irrelevant. When users try to log into email after having their mailboxes moved they will be automatically redirected to the new server and they will never again go to the old one. After a few days you can uninstall Exchange from the old box.
What business requirement have you got to retain the old name? If you can come up with one you'll be the first in over 10 years to do so. This is particularly valid because you're not keeping the old server around so it obviously hasn't got any nasty application on it that needs to remain there. And even if you did you'd reinstall Windows onto the box and recover that application to keep it away from Exchange which should sit on it's own server wherever possible.
Well,, If you have decided on bringing a new server, there are certain options that you need to change (If you ar eplanning to decommission the old server).
These would include the RUS,OAB and sitefolderserver attribute which will cause Public folder issues and free busy issues.
The above mentioned may be pointing to the old Exchange server that you will be decommissioning soon.
Posts: 5428
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
These steps: http://support.microsoft.com/kb/822931 tell you what to replicate, what to configure over to the new one and how to remove the old. It's a very, very simple process as long as you just follow it properly. Luckily, moving to new hardware with a new name lets you do all these things in day time without any pressure to get service back up and running. That's one of the reasons I always recommend the migration rather than a forklift.
Performing a Disaster recovery is much easier. However, as mentioned earlier by Mark, there must be soem corruptiosn which was actually causing the BSOD.
Hence, take time and we would suggest to follow the article and work on it !!!
Be careful with O.S. version, if the recommendation mention the same is the same.
My recommendation is join the new server to existing exchange organization and move all mailboxes to it, configuring connectors if apply and decommising the old server.
Another thign to do before migration on same server is offline database backup.
1. Dismount the Mailbox & public Folder store and copy the MDBDATA folder to a different machine. 2. Make sure we copy over all the logs / EDB / STM / CHK file. 3. Also copy the Mail Queue folder if you have any items in the folder. 4. Also copy if you have any other important data. 5. If the box is also a Domain Controller, use DCPROMO and demote it gracefully. 6. That would clean up the entries of this DC from Active Directory. 7. Install the operating system from scratch and use the same Computer Name as of the old server. 8. IP address can be different, but have the same since it will have a DNS entry already 9. Install the latest service packs / Security updates for Windows. 10. Once the updates are completed install Exchange using Setup /Disasterrecovery switch. 11. This would install the server with the configuration container information available for the server from Active Directory. 12. Install the latest service pack and hot fixes as that of the old server. 13. Once the installation is completed re-start the server and make sure all the Exchange services are started without any issue. 14. Now rename the MDBDATA folder on the new server and copy the old MDBDATA from the backup location. 15. Mount the stores and verify email flow.
Also, I would take a screenshot of the Default Website properties in inetmgr and any other setting we have in the old exchange server.
I strongly agree with Mark, you should go with adding a new exchange box and move mailboxes and later on you can retire your old box. Your server had crashed when the databases where online due to stop screen which might have increased the chances of database corruption, can lead to huge downtimes in future so better is to go with move mailbox which removes corruptions from the database. I have been seeing this kind of posts since very long time and all MVP's suggesting the same action plan. Disasterrecovery is the option when disaster has happened but this is the proactive action that you are planning to take to avoid future disaster http://support.microsoft.com/kb/822931
This is the best article to follow.
You dont have to manually change the Site Folder server it will do it automatically when you decommission your old box. Before you plan to decommission the old box keep its services disabled for a week and see if you get any complaints from users so that you can bring it on back.
Do you guys really do some kind of a research before giving strict suggestions ??? Are you aware of the impact on a client side when you move mailboxes ??
Single instance strorage will be broken.... Whatever client side configurations on outlook will be lost wiz; Rules, delegates and what not ?? And when it comes to a client connecting to outlook, you might have to reconfigure all the profiles in the orgn since outlook will be looking into the old server and I am aware that the GC should update the change and it should not be that way... but what if you have some replication error ?? If clients need to pick up the change, the old server should be entirely out from ADSIEDIT... these are all my practical experiences....
When it comes to moving mailboxes using the move mailbox wizard, you know it when you really start the same....
For the question that Richard has, Microsoft has a Technet article itself. I dont think a post in a blog can be better.
Posts: 145
Joined: 20.Nov.2001
From: UK
Status: offline
Erm, that was the Technet article I was going to follow until I was persuaded otherwise! Totally confused now, but I'm going to try moving mailboxes and if that doesn't work, I'll use DR as plan B.
_____________________________
Exchange Server 2003 Standard SP2 on Windows Server 2003 Standard SP2, 45 clients running XP SP3 and Outlook 2003 in cached exchange mode.
If you have Lab machine or if you get a case to decommission a box, test it practically and let me know if you have to manually change the SiteFolderServer entry.
In gracefull decommissioning I have seen almost in all the cases SiteFolderServer entry getting updated.
Thank you Ashish. I did try a gracefull decommissioning and the same works for me. My point was, in 70-80 % Scenarios, I ve seen the site folder server is pointing to the old exchange server even after a gracefull decommissioning which inturn creates issue with PF's, OWA and FB issues.
When we have a proper procedure to Move exchange to a different box written by MS, dont you think we opt that ?
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Installation >> Moving exchange to new hardware 
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
Moving exchange to new hardware - 
). 
RE: Moving exchange to new hardware - 
but this is the proactive action that you are planning to take to avoid future disaster
RE: Moving exchange to new hardware - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
