Unsolved
This post is more than 5 years old
3 Posts
0
506
April 22nd, 2008 06:00
Replistor and Exchange 2003 in cluster mode
Hi all,
I'm looking for a solution to set up Replistor (6.2 Sp4 and Exchange 2.1.2) in an Exchange 2003 cluster environment.
My Production configuration is a two node Exchange cluster.
My target configuration is a one node Exchange cluster.
On this forum, i found a lot of information like this step by step :
1. Create the target cluster. (This is usually a single node cluster) This will be a completely separate cluster from the source.
2. Install Exchange.
3. Create Exchange Cluster group with only the disks. (Needs to be same drive letters as production)
4. Bring disks online and replicate the data from source to Target.
5. Take cluster group on production server offline (including the specs)
6. Create the network name and IP resources in the cluster group on the target. (The name MUST be exactly the same as on the source. IP will be different.)
7. Add the System Attendant cluster resource. (This will complete the Exchange install. When Exchange is clustered, it will go to Active Directory first to see if the exchange server exists. If it does, it will perform a disaster recovery install which just puts the binaries in place.
8. When that is completed, you should have a cluster group that is identical to the production cluster group with the exception of the Virtual IP address. Also, if you configure the network name to update DNS then that will be taken care of for you as well.
It seems this solution works fine and I think I will implement this solution. But I still have one question : What about the failback ?
I only need to stop the backup cluster and restart the production cluster ?
Restarting the production cluster (or taking online the Exchange cluster ressources) will automatically mount my Exchange Virtual Server configuration (storage groups, databases, ...)
Or should I Re-install the Exchange Virtual Server (in Disaster Recovery mode) like I did for the failover ?
Thanks for your help.
I'm looking for a solution to set up Replistor (6.2 Sp4 and Exchange 2.1.2) in an Exchange 2003 cluster environment.
My Production configuration is a two node Exchange cluster.
My target configuration is a one node Exchange cluster.
On this forum, i found a lot of information like this step by step :
1. Create the target cluster. (This is usually a single node cluster) This will be a completely separate cluster from the source.
2. Install Exchange.
3. Create Exchange Cluster group with only the disks. (Needs to be same drive letters as production)
4. Bring disks online and replicate the data from source to Target.
5. Take cluster group on production server offline (including the specs)
6. Create the network name and IP resources in the cluster group on the target. (The name MUST be exactly the same as on the source. IP will be different.)
7. Add the System Attendant cluster resource. (This will complete the Exchange install. When Exchange is clustered, it will go to Active Directory first to see if the exchange server exists. If it does, it will perform a disaster recovery install which just puts the binaries in place.
8. When that is completed, you should have a cluster group that is identical to the production cluster group with the exception of the Virtual IP address. Also, if you configure the network name to update DNS then that will be taken care of for you as well.
It seems this solution works fine and I think I will implement this solution. But I still have one question : What about the failback ?
I only need to stop the backup cluster and restart the production cluster ?
Restarting the production cluster (or taking online the Exchange cluster ressources) will automatically mount my Exchange Virtual Server configuration (storage groups, databases, ...)
Or should I Re-install the Exchange Virtual Server (in Disaster Recovery mode) like I did for the failover ?
Thanks for your help.
0 events found
No Events found!
dramjass
151 Posts
1
April 25th, 2008 07:00
This solution is a Microsoft solution and we are using RepliStor to move the data from one MSCS to the other. take a look at the following TechNet article that describes this process:
http://technet.microsoft.com/en-us/library/aa996470.aspx
The article some what describes the failback steps as well.
If you were just testing the failback, then you would follow the same procedure as the failover. The one important step here is to toggle the 'Enable Kerberos' option in the Exchange Network Name resource. This reset the virtual Exchange account in AD.