WINDOWS SERVER 2003 cluster preparation!!!

HI.  Im in the process of planning a project with a  'two-node' cluster using Windows Server 2003 R2 Enterprise.  My main reason for going down this path is because i need high availabilty for exchange.  Because it is indeed costly, im gonna put install exchange on both the nodes that will be domain controllers.  Other than the usual setbacks of putting exchange on a DC, is there anything else i should know that might cause the machines to behave differently because of the clustering??

Also, what types of storage can i use for the quorum?  Its not only scsi devices? is it??

and on this one im clueless:  at which point should i promote node 1/node 2 to Domain Controller /Secondary Domain Controller ?  As soon as ive finished the basic windows installation on both? should it be done pre- or post- clustering??


any insight will be much appreciated

LVL 1
pk24573Asked:
Who is Participating?
 
oBdACommented:
Installing cluster services on a domain controller is not really recommended (and, as you already noticed, neither is installing Exchange on a DC).
What with the costs for a cluster solution involved, two comparatively cheap machines for DCs shouldn't matter enough to justify using the cluster nodes as DCs.
Note that you can *NOT* use any two somewhat similar machines, attach a SAN, and install cluster services on them, at least not if you really require the high availability.
The *complete* hardware combination (and *not* only the single components!) has to be cluster certifed, otherwise it might well happen that you have increased downtime instead of increased uptime.
The Microsoft support policy for server clusters, the Hardware Compatibility List, and the Windows Server Catalog
http://support.microsoft.com/?kbid=309395
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.