Exchange Server & PO migration
Dana Love
Hi Jerry.
"Jerry Leshaw" <j...@chartwellre.com> wrote:
>I plan to migrate my Exchange server 4.0 application and Exchange Post
>Office (with a Directory Synchronization process, a DirSync Requestor, an
>MS-Mail connector, 130 clients, groups, recipient containers, etc.) from
>its current server to a faster box. Is there an easy way to migrate the
>application without having to re-install Exchange server and rebuild the
>post office on the new server?
Nope. :-) Stick with the tried and true method if mail is mission
critical (and where isn't it these days...) If you try some funky
workaround, you're likely to end up burned.
Dana
---
Dana Love
Manager, Information Systems Engineering
Control Technology Corporation
da...@control.com
Ray Sundstrom
Jerry,
If you don't have it already, download and read the Exchange Server Backup
and Restore white paper at http://www.microsoft.com/exchange/deploy.htm It
has a wealth of information that should help you with your
reimplementation.
Good luck.
--
Ray Sundstrom
MCSE
ra...@asi-consulting.com
Jerry Leshaw <j...@chartwellre.com> wrote in article
<01bc7ffc$9f9d3ee0$4780...@Saltzman.Stamford>...
> I plan to migrate my Exchange server 4.0 application and Exchange Post
> Office (with a Directory Synchronization process, a DirSync Requestor, an
> MS-Mail connector, 130 clients, groups, recipient containers, etc.) from
> its current server to a faster box. Is there an easy way to migrate the
> application without having to re-install Exchange server and rebuild the
> post office on the new server?
>
> Thank you.
>
> Jerry Leshaw
> Chartwell Re Corp.
>
Claus Andersen
"Jerry Leshaw" <j...@chartwellre.com> wrote:
>I plan to migrate my Exchange server 4.0 application and Exchange Post
>Office (with a Directory Synchronization process, a DirSync Requestor, an
>MS-Mail connector, 130 clients, groups, recipient containers, etc.) from
>its current server to a faster box. Is there an easy way to migrate the
>application without having to re-install Exchange server and rebuild the
>post office on the new server?
I would take a full backup. Then I would make a closed network
consisting of one of your BDC's and the new Exchange box. Then restore
the backup. I can only see a few quirks to remember - look at the
following steps and see if it can be of any help.
- Take a new machine and install it as a BDC on your real network.
- Stop all Exchange services and do a complete flat file backup of you
log files and dir.edb, (DS data), pub.edb (Public Folders) and
priv.edb (Private Information Store) (Faster than an online - if you
prefer online - then remember to stop the MTA)
- If the server is very mission critical you can start the Exchange
services again EXCEPT the IMS and MTA. Then you users will be able see
their mail but not generate any new traffic (Except posting in public
folders). I would though recommend to stop all services!
- Synchronize your domain.
- Detach the BDC from your real network
- Connect the BDC with your NEW Exchange server (and NOTHING else)
- Delete the computer account for your Exchange server on your closed
network. (This needs to be done as you install a new machine).
- Install NT on the new Exchange Server. Remember to use the same
computer name as on the old server.
- Apply Service Packs to at least the same level as your old server.
- Install Exchange Server 5.0 on the new box. Create a NEW Org and
site BUT with the EXACT same names as on the old box.
- Use the SAME service account as on the old server.
- Reboot and make sure that the Exchange is up.
- Stop all Exchange services.
- Run Exchange Optimizer and make sure that it places the files where
_you_ want them.
- Restore the files from the old server to the new box to the
locations you need.
- Execute \exchsrvr\bin\isinteg /patch (This makes sure that the DS
and IS are consistent)
- Now the big moment: Start the Exchange service and see if it comes
up.
***********
If you have some large databases all this moving around and
installing can take some time - but if it doesn't work no harm is done
so far. When you are too tired of it all you just start all services
on the old server and go home. Then you can have another go the next
weekend. :-)
***********
IF it all worked out quite nice then you can proceed:
- Turn off the old Exchange server.
- Delete the computer account for the old Exchange server on the real
network.
- Synchronize the entire domain
- Connect the two computers to the real network
- Synchronize the entire domain (Which gives you the new computer
account)
You should now be up and running on the new box. If you used a spare
machine as BDC on your "closed network" that can be removed again.
As far as I can remember a procedure quite similar to what is
described in the Exchange Disaster Recovery Whitepaper which you under
all circumstances should check out!
Even though it sounds like a tedious task you should allow yourself to
do it as too many administrators have their first go of restoring
their Exchange-servers when the flames are coming out of the old box.
A little experience it not out of the way when your boss goes into
panic-mode :-)
Med Venlig Hilsen
Claus Andersen
Tele Danmark Internet
_______
/ / Claus Andersen, cl...@int.tele.dk
---/ TELE / DANMARK -----------------------------------------------------------
/______/ Internet Olof Palmes Alle 36, 8200 Aarhus N,(+45)86783300
Scott Schindler
Please download Microsoft's disaster recovery paper and it will
explain it.
On Mon, 23 Jun 1997 10:34:49 -0700, "Jerry Leshaw"
<j...@chartwellre.com> wrote:
>I plan to migrate my Exchange server 4.0 application and Exchange Post
>Office (with a Directory Synchronization process, a DirSync Requestor, an
>MS-Mail connector, 130 clients, groups, recipient containers, etc.) from
>its current server to a faster box. Is there an easy way to migrate the
>application without having to re-install Exchange server and rebuild the
>post office on the new server?
>