I the info about clustering. I focused on Clusterrecovery.exe, the part that stood out was "In the event of the disk failure, special care must be taken to restore the data and recover the applications. The Server Cluster Recovery utility was designed to do just that."
Is this the point you were trying to emphasize?
Also, I read that "The computers are physically connected by cables and programmatically connected by clustering software"
Would I have problem clustering if I had servers at differention locations not physically connected with cable.
I kept reading I read the info below, is this something I should be on the lookout for?
In a typical failover, the standby serve takes over the IP address from the failed primary server. Routers on the subnet learn the media access control (MAC) address of the NIC that now owns the IP address, and network packets now flow to the new active server. However, failover isn't so easy when the new server is on a different subnet.
One solution is to update your DNS servers so that the host name users typically connect to resolves to the new server's address. This approach can be feasible when all users reside on a private network and the propagation delay for DNS updates is minimal. However, when your users are connected over the Internet, they can wait hours or longer before the host name resolves to the new address, and decreasing that time by setting a short Time to Live (TTL) for the host name increases traffic to your DNS servers.
As another alternative, you can use Virtual LAN (VLAN) technology to route application requests to the remote site. This approach lets servers at the remote site operate as though they're on the local subnet and use its IP addresses...
My server wills be on two different subnet for sure, so I'm guessing this is something I should look out for?
