Unsolved
This post is more than 5 years old
3 Posts
0
502
June 1st, 2006 13:00
Exchange 2003 Cluster Support
We are about to implement Replistor on an Exhange 2003 Active/Passive cluster in our corporate office which need to manually fail over at our DR site to a single node Exchange cluster. Who has been successful in setting up this type of configuration and how did you it? I do not see much infomation on the support site.
0 events found
No Events found!
dramjass
151 Posts
0
August 16th, 2006 06:00
- The Exchange cluster name must be the same on both the Source and Target sites.
- RepliStor clusters resources need to be dependencies of the System Attendant resource.
-> Purpose: RS Spec¿s gets disabled before Exchange services; therefore not all data may get Mirrored.
-> System Attendant is the last Exchange service to stop.
- A RepliStor Virtual IP should be created on a different physical interface for replication traffic
- On the target, disk and cluster IP resources need to be online.
- On recovery of DR back to Production Exchange cluster:
- Turn on the Disk Resources in the PROD site.
- Turn on the RepliStor Virtual IP (is used)
- Use a Full Sync to validate
- QUOROM Resource is in its own group from other resources
- IP's are assigned for QUOROM, RepliStor and application (Exchange)
- RepliStor resources must be dependent on the disk resources of the corresponding Specification.
- The data paths for the Exchange DB¿s and Logs must be identical on the Source and Target nodes.
- The Exchange Virtual IP should be the same on the Source and the Target
- When installing Exchange on the Target node, the Source cluster nodes should be disabled/down so there is no conflicting installation issues.
dramjass
151 Posts
0
August 29th, 2006 08:00
http://www.microsoft.com/technet/prodtechnol/exchange/guides/DROpsGuide/2493c2d6-618c-4c49-9cb1-fff556926707.mspx