Clustering with Windows 2003 Server Enterprise

[PurePeon]

Anyone here tried clustering 2 Servers? Which is the better way to go...active-passive or active-active? What are the differences?

 

[stash]

That depends on what application you are clustering. Assuming Windows, if you run Exchange, it is recommended to do active-passive clustering. In AP clustering, you can have up to 8 nodes in the cluster, and up to 7 seven virtual instances of Exchange (called EVS, exchange virtual server). So you have 7 nodes, each running a separate EVS, and one passive node. If any single node fails, the passive node will assume responsibility for that failed node's EVS. If a second node fails, that node's EVS will remain offline until a node becomes available.

In the active-active Exchange scenario, you are limited to two nodes, and two EVSs. In this case, each node is running a separate EVS. If one node fails, the other node will run both EVSs. However, if the second node fails before the first node is restored, you have nothing.

If you want to learn about Windows clustering, start here: http://www.microsoft.com/windowsserver2003/technologies/clustering/default.mspx

 

[PurePeon]

it'll mostly be for data storage with a license server running educational software. i think it's overkill but my work wants it.

 

[stash]

For data storage, you will want to look at DFS.

http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/default.mspx

 

[spyordie007]

with a license server running educational software

Does your application even support clustering?

I'm assuming it's a service that gets installed on the server(s). If that's the case you're going to need to find out what it can do for clustering as the app has to support it.

 

[PurePeon]

Thanks for the input. I didn't even think about the software. The licensing doesn't support clustering so there goes that idea.