I'm looking for some help on this subject. We are wanting to have a server that is setup with winnt 4.o server and exchange 5.5 for disaster use only. We run arcserve 2000 with the exchange add in. We back up the server daily (full backup). What we want to do is have the arc serve then restore the priv pub and edb (whatever else i need) to the disaster server, and start it up when/if needed. How would i do this with the nt4.0 server? would i have trouble with the cid? Any help with this would be greatly appreciated thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
exchange 5.5 disaster recovery server 1
- Thread starter bigdog92
- Start date
-
1
- #2
You need to record the following information for your live system:
* The name of the service account (look at the Startup options of each service). None of these should be the System account, but a normal user account with Administrator privileges.
* The version of Exchange running. We currently use V5.5 SP3.
* The directories where the various database components are stored. The drive letter can be ascertained by running perfwiz.exe (in \exchsrvr\bin), this is fine if default path names have not been changed. Otherwise look in the registry in HKLM/System/CurrentControlSet/Services/MSExchange???\Parameters, where ??? is the name of a service, e.g. MSExchangeIMC. The path to the stored database files can be seen here. Not all of them are settable through perfwiz.exe.
* The Organisation name and the Site name. These are case sensitive.
* Any message filters. These appeared in SP2 and don’t seem to be part of the Directory information. Look in Exchange Admin, Connections, Internet Mail Service, Connections tab, Message Filtering.
Next, on your recovery server make sure previous installs of Exchange are removed. The following procedure can also be carried out if the new install goes wrong.
To ‘Manually’ remove Exchange:-
* Stop Exchange System Attendant service, if running. Also stop Content Index, FTP Publishing and IIS Admin services.
* Run Setup from the CD and Remove All.
* Run Regedit. Locate HKLM/System/CurrentControlSet/Services. Delete all the keys starting ‘MSExchange…’, also delete ESE97.
* Locate HKLM/Software/Microsoft and delete the keys named EDB (may not exist), Exchange and ESE97.
* Delete C:\exchsrvr and all sub-directories.
* If items have been installed on other drives (as a result of specifying different drives during the performance optimiser), delete these too, e.g. D:\Exchsrvr\…
* Reboot the machine so that loaded Exchange services are removed.
Install Exchange
* If a previous installation of Exch 5.5 exists, carry out the ‘removing Exchange’ procedure above.
* Install Exchange 5.5. Run SETUP /R to allow the to-be-restored database to work. Use identical Organisation and Site names as your live system. These names are case sensitive.
* Do not cancel this stage otherwise Exchange will not be able to re-install or remove itself. Run the configuration tool (starts automatically after the Exchange install), point the files to the correct areas.
* Install latest Exchange 5.5 Service Pack by running UPDATE /R (again, the /R switch is necessary otherwise the restored database won’t work).
* Start the Exchange System Attendant service.
* Install ArcServeIT
* Install ArcServe Exchange Agent
* Install ArcServeIT Service Pack, will need to select the Exchange agent after the main program has been patched.
* Restore both the Directory and Information Store, use all default settings & restore to original location. Log in name Administrator.
* Start the Exchange Directory service.
* Start, then stop the Exchange Information Store service (otherwise the next step will fail).
* From a command prompt, run C:\EXCHSRVR\BIN\ISINTEG –PATCH. You should get a ‘completed OK’ message.
* All Exchange services can now be restarted. Check the Event Log for errors. If Error 4086 occurs, see Errors with IMC service startup below.
* Re-create the turf directory C:\Turfdir. There is a bug in the install procedure that omits this (because the feature came out in SP2?). This is the directory where messages disallowed by the Message Filter end up.
* Run Exchange Administrator. Re-create any message filters.
* Reboot the PC to check services start up OK. Check the event log for errors, if none then plug the router back in.
* Done!
Errors with Internet Mail Connector service startup
When re-starting Exchange services, the IMC failed to start with an error ‘4086/Unable to start the service because the configuration could not be loaded from the Microsoft Exchange Directory or Windows NT Registry’.
Some entries in the registry were incorrect and needed amending. These were all values in HKLM/System/CurrentControlSet/Services/MSExchangeIMC/Parameters.
* The name of the service account (look at the Startup options of each service). None of these should be the System account, but a normal user account with Administrator privileges.
* The version of Exchange running. We currently use V5.5 SP3.
* The directories where the various database components are stored. The drive letter can be ascertained by running perfwiz.exe (in \exchsrvr\bin), this is fine if default path names have not been changed. Otherwise look in the registry in HKLM/System/CurrentControlSet/Services/MSExchange???\Parameters, where ??? is the name of a service, e.g. MSExchangeIMC. The path to the stored database files can be seen here. Not all of them are settable through perfwiz.exe.
* The Organisation name and the Site name. These are case sensitive.
* Any message filters. These appeared in SP2 and don’t seem to be part of the Directory information. Look in Exchange Admin, Connections, Internet Mail Service, Connections tab, Message Filtering.
Next, on your recovery server make sure previous installs of Exchange are removed. The following procedure can also be carried out if the new install goes wrong.
To ‘Manually’ remove Exchange:-
* Stop Exchange System Attendant service, if running. Also stop Content Index, FTP Publishing and IIS Admin services.
* Run Setup from the CD and Remove All.
* Run Regedit. Locate HKLM/System/CurrentControlSet/Services. Delete all the keys starting ‘MSExchange…’, also delete ESE97.
* Locate HKLM/Software/Microsoft and delete the keys named EDB (may not exist), Exchange and ESE97.
* Delete C:\exchsrvr and all sub-directories.
* If items have been installed on other drives (as a result of specifying different drives during the performance optimiser), delete these too, e.g. D:\Exchsrvr\…
* Reboot the machine so that loaded Exchange services are removed.
Install Exchange
* If a previous installation of Exch 5.5 exists, carry out the ‘removing Exchange’ procedure above.
* Install Exchange 5.5. Run SETUP /R to allow the to-be-restored database to work. Use identical Organisation and Site names as your live system. These names are case sensitive.
* Do not cancel this stage otherwise Exchange will not be able to re-install or remove itself. Run the configuration tool (starts automatically after the Exchange install), point the files to the correct areas.
* Install latest Exchange 5.5 Service Pack by running UPDATE /R (again, the /R switch is necessary otherwise the restored database won’t work).
* Start the Exchange System Attendant service.
* Install ArcServeIT
* Install ArcServe Exchange Agent
* Install ArcServeIT Service Pack, will need to select the Exchange agent after the main program has been patched.
* Restore both the Directory and Information Store, use all default settings & restore to original location. Log in name Administrator.
* Start the Exchange Directory service.
* Start, then stop the Exchange Information Store service (otherwise the next step will fail).
* From a command prompt, run C:\EXCHSRVR\BIN\ISINTEG –PATCH. You should get a ‘completed OK’ message.
* All Exchange services can now be restarted. Check the Event Log for errors. If Error 4086 occurs, see Errors with IMC service startup below.
* Re-create the turf directory C:\Turfdir. There is a bug in the install procedure that omits this (because the feature came out in SP2?). This is the directory where messages disallowed by the Message Filter end up.
* Run Exchange Administrator. Re-create any message filters.
* Reboot the PC to check services start up OK. Check the event log for errors, if none then plug the router back in.
* Done!
Errors with Internet Mail Connector service startup
When re-starting Exchange services, the IMC failed to start with an error ‘4086/Unable to start the service because the configuration could not be loaded from the Microsoft Exchange Directory or Windows NT Registry’.
Some entries in the registry were incorrect and needed amending. These were all values in HKLM/System/CurrentControlSet/Services/MSExchangeIMC/Parameters.
- Thread starter
- #3
wow thanks man that was real good. i just have a couple questions that i have seen from reading microsoft white papers. Will i have trouble getting the server on the domain since there will already be a site on there with the same name (cid)? Just to let you know i am running exch 5.5 sp4 with nt4.0 server. thanks for all your help man i really appreciate it!!
The notes assume your old server is offline - it is what I did when we put larger hard disks in our mail server, starting from scratch i.e. re-building the OS and so on. As far as possible I kept things the same although the actual server name can be different if you want - you would have to re-configure all your clients in this case.
What I would do is set it up and test the recovery procedure with your live mail server switched off. Then you can leave the backup server powered down, ready to restore to if things go wrong.
Pete
What I would do is set it up and test the recovery procedure with your live mail server switched off. Then you can leave the backup server powered down, ready to restore to if things go wrong.
Pete
- Thread starter
- #5
- Thread starter
- #6
cq, thanks for all your help just one question i hope you still look at this. On the recovery server part where you do the setup /r this makes the old database work...do you have to load all the backed up files on to the server before you start the exchange setup?
Bigdog92, not quite sure what you're asking here, the Exchange database files must be restored after Exchange setup has been run but before the server is rebooted; the Exch services must be started and stopped in the order given in the 'Install Exchange' part of my original post.
Pete
Pete
- Thread starter
- #8
It's definitely something you want to do before a disaster not after. It took me two weekends to work out the above method, in an emergency situation you don't have the luxury of time...
Hope it goes well for you, maybe have a look at the MS support site for updated documentation. There's bound to be some difference between your setup and mine.
NB The procedure for Exchange 2000 will be nowhere near the same, the above is for Exch5.5 only.
One last thought - if you set up your recovery system and plug it in, you will start to receive emails which will then need to be transferred back to your live system somehow. When I set up the new system it was netwroked up but I unplugged our ISP router so no incoming mails could get through.
Pete
Hope it goes well for you, maybe have a look at the MS support site for updated documentation. There's bound to be some difference between your setup and mine.
NB The procedure for Exchange 2000 will be nowhere near the same, the above is for Exch5.5 only.
One last thought - if you set up your recovery system and plug it in, you will start to receive emails which will then need to be transferred back to your live system somehow. When I set up the new system it was netwroked up but I unplugged our ISP router so no incoming mails could get through.
Pete
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question
