Where I work, I've setup MSSQL, Exchange and Citrix clusters. Microsoft clustering won't work if it doesn't have some sort of storage device on the backend (NAS, SAN, DAS, etc.). Also, you will have to have a quorum drive for each machine to access. This drive stores information about the cluster. The other thing is that you will need to have NICs that connect to your network, as well as NICs that do nothing but provide heartbeat between the two systems. You will need a hostname for each machine, a hostname for the cluster itself, as well as a hostname that will be dynamic depending on which machine currently is the master in the cluster.
You really don't want to do this with a desktop system and a laptop. You would have to have at a minimum Windows Server 200x Standard edition to even get clustering services in a Windows OS.
Also, you have to be aware that the applications you will be using need to be cluster aware, meaning that they have to have code written in them to have them function on a cluster. MSSQL, Exchange, Citrix, etc. are all cluster aware applications.
__________________
"You hear the one about the fella who died, went to the pearly gates? St. Peter let him in. Sees a guy in a suit making a closing argument. Says, "Who's that?" St. Peter says, "Oh, that's God. Thinks he's Denny Crane."
|