pete_killick
asked on
Migration from Exchange Server 2000 to Exchange Server 2003 on new hardware
This is the story, we currently have a Windows 2000 domain with Exchange Server 2000 the databases total about 120Gb. We have built a new Windows 2003 Server domain with Exchange Server 2003. The question is what is the best way of migrating the data, as I know from past experience that migrating a single mailbox that contains about 4Gb through a Gigabit ethernat connection takes about 5 hours, so this will make my migration impossible to complete across a weekend. I was thinking there may be a possibility just to upgrade the old 2000 exchange to 2003, then take a copy of the databases and put them in the correct location on the new server, where I will have created the user accounts with mailboxes already, how will exchange react to bringing up databases on a new server with different computer name and domain, or any other suggestions.
ASKER
The link between the two domains is purely a trust on the same subnet.
If exmerge is the only way is there anyway of speeding up the process?
If exmerge is the only way is there anyway of speeding up the process?
Not really.
Any reason you went with a new domain? With a store that size I would have advised the client to go with the same domain so that it could be done on a conventional swing.
You are doing too many changes to allow for an easy database move.
You could look at one of the migration tools, I would start with Quest. However they will probably suggest the same thing, because you are going across a domain.
Otherwise you are looking at some kind of staged migration plan, with the servers co-existing.
Simon.
Any reason you went with a new domain? With a store that size I would have advised the client to go with the same domain so that it could be done on a conventional swing.
You are doing too many changes to allow for an easy database move.
You could look at one of the migration tools, I would start with Quest. However they will probably suggest the same thing, because you are going across a domain.
Otherwise you are looking at some kind of staged migration plan, with the servers co-existing.
Simon.
ASKER
Hi Simon
I just wanted a fresh start on a new system, remove all the old info so start a fresh...
Surely with the way technology is these days there is a more reliable and simplified method.
Pain in the wotsits if you know what I mean...
I just wanted a fresh start on a new system, remove all the old info so start a fresh...
Surely with the way technology is these days there is a more reliable and simplified method.
Pain in the wotsits if you know what I mean...
As technology gets more advanced, the applications increase in complexity. That includes moving data around. Hence why companies like Quest develop their products. Exchange is very closely tied in to the active directory, and moving databases around usually fails.
I too like to start a fresh, but sometimes it reaches a point where starting fresh will make things worse because the company cannot tolerate the pain.
Simon.
I too like to start a fresh, but sometimes it reaches a point where starting fresh will make things worse because the company cannot tolerate the pain.
Simon.
ASKER
I take it I will have to use the rendom utility with 2003 to add the new network to the old, might winge as both have master browsers, what do you reckon?
ASKER
I am taking the plunge and reloading all the new servers to join them onto the existing domain, will I have to run adprep on all the servers in the existing domain, and if so can I do that on a live system?
Cheers
Cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If they are totally separate then you only have one choice - and that is exmerge.
Trying to move the databases around will not work - a change in domain and servername will not be accepted by Exchange and the databases will not mount.
Simon.