Timothy H. Schilbach
03-26-2002, 09:28 AM
Hi There,
I am doing something that is very unique as far as a restore goes. The end result I am trying to accomplish is the restore of an Exchange database (priv/pub) to a cluster with the same Machine name as the server backed up.
Now that we have established a motive, here is what I am doing currently. I have backed up my production server (we will call it SERVER1) which is Exchange 5.5 SP4 Running on WIndows 2000 SP2.
In my lab I have a cluster (only 1 server is in it at this time). I have Windows 2000 Adv Server with SP2 and MSCS running on it. The Server Name is SSERVER and the Cluster Name is SERVER1. I have installed a cluster aware version of Exchange 5.5 Enterprise with SP4.
Now my backup is a FULL OFFLINE backup. I shut down my production server for 2 hours to do a full offline backup. I the restored the Priv and Pub to the cluster server. I also restored the directory service (ds.edb) to this server.
I started the Directory Services without an issues (since the cluster is named SERVER1 and the back is from SERVER1). Now I restored the Priv and Pub directories and started the service. I get a service specific error 1202. When I llok in the event log I see Event ID's:
1005: Unable to start the Microsoft Exchange Information Store. Error 0x3f4.
7202: The database has been copied from the server SSERVER to the server SERVER1. The database cannot function until ISINTEG -PATCH has been run.
Ok so I go to the command prompt and the exchsrvrin directory and run an ISINTEG -PATCH. It completes successfully no problem. So I go to restart the Information store and I get all the same errors.
So I looked up this problem with MS Premier support and found an article stating that cluster restores may have to have a full offline defrag to restore properly to a different machine name. I also reset the CLUSTER PATH at the command prompt as suggested by by Q article Q198893.
I do another restart and I still get the same issue. So I do an eseutil /r to recover the database. I re-run ISINTEG -PATCH and again I get the same results in my event log!
Any suggestions?
Timothy H. Schilbach
Sr. Messaging Administrator
Snap-on Incorporated
262-656-6184
I am doing something that is very unique as far as a restore goes. The end result I am trying to accomplish is the restore of an Exchange database (priv/pub) to a cluster with the same Machine name as the server backed up.
Now that we have established a motive, here is what I am doing currently. I have backed up my production server (we will call it SERVER1) which is Exchange 5.5 SP4 Running on WIndows 2000 SP2.
In my lab I have a cluster (only 1 server is in it at this time). I have Windows 2000 Adv Server with SP2 and MSCS running on it. The Server Name is SSERVER and the Cluster Name is SERVER1. I have installed a cluster aware version of Exchange 5.5 Enterprise with SP4.
Now my backup is a FULL OFFLINE backup. I shut down my production server for 2 hours to do a full offline backup. I the restored the Priv and Pub to the cluster server. I also restored the directory service (ds.edb) to this server.
I started the Directory Services without an issues (since the cluster is named SERVER1 and the back is from SERVER1). Now I restored the Priv and Pub directories and started the service. I get a service specific error 1202. When I llok in the event log I see Event ID's:
1005: Unable to start the Microsoft Exchange Information Store. Error 0x3f4.
7202: The database has been copied from the server SSERVER to the server SERVER1. The database cannot function until ISINTEG -PATCH has been run.
Ok so I go to the command prompt and the exchsrvrin directory and run an ISINTEG -PATCH. It completes successfully no problem. So I go to restart the Information store and I get all the same errors.
So I looked up this problem with MS Premier support and found an article stating that cluster restores may have to have a full offline defrag to restore properly to a different machine name. I also reset the CLUSTER PATH at the command prompt as suggested by by Q article Q198893.
I do another restart and I still get the same issue. So I do an eseutil /r to recover the database. I re-run ISINTEG -PATCH and again I get the same results in my event log!
Any suggestions?
Timothy H. Schilbach
Sr. Messaging Administrator
Snap-on Incorporated
262-656-6184