cluster volume system questions/ HA hyper's

im trying cluster storage/ha on 3 server have 4x600gbsas drives in raid 10 giving me 1.1 or tb  dont need more 1.1 tb need ha if 1 dies or w/e.

i seam having difficulites storage concept.

i moved away citrix/iscsi solution because my network cant handle type of setup...

i have more 3 servers, , meanwhile have hyper-v running plenty of vm's on other machines. not clustered. want have 1.1 on each box redundancy data/vm storage. kind of raid of servers, per say.

i have 2 of 3 clustered , seam waiting on storage thing move forward.

please point me in right direction.

-whats differance between clustering , replicating? want instead?

-nic teaming takes 2 nic's plus 1 more nic management = 3 nic's?

-hyper-v cant transfer cluster name, node-server nams, if put fqdn of cluster.

-c:\clusterstorage says access denied?

-hyper-v wont move vm node machines either, gives error hardware requirements. machie identical source server.

"whats differance between clustering , replicating? want instead?"

clustering makes use of shared storage accessed 2-64 nodes.  if single node fails, resources running on node automatically started on node.  because both hosts reading/writing same storage, there no data loss.  replication asynchronously copies changes occuring within vm host across network.  destination can stand-alone host or cluster.  if source host fails, manual steps must taken restart vm on replica host.  because replication occurs asynchronously, there possibility of data loss when replica started.  business decision whether use failover clustering or replica, based on recovery objectives , time.

"nic teaming takes 2 nic's plus 1 more nic management = 3 nic's?"

really depends on how things configured.  technically, if put cluster, recommended have @ least 4 networks - management of physical host, live migration, cluster shared volume, , vm access.  can accomplished single teamed pair of adapters - running on 1 network - or 4 nics assigned individually.  or, can use teaming software create individual vlans - 1 each of mentioned networks.  key want ensure none of networks have single point of failure , have enough bandwidth satisfy needs expected.  host management low volume, unless run backup on it.  csv minimal, when needed, uses bandwidth.  live migration similar.  since live migration planned, can planned times when there low network demand.  , vm access totally dependent upon vms doing.  have vlans on team allows define quality of service handle different workloads.  if don't want use teaming, need ensure availability various networks.  using 1 nic each host management, csv, live migration, , vm access not provide ha might want.  can set cluster communication on both management , csv networks, , live migration can enabled on 2 or more nics, leaves host management , vm access on single nics no backup.  @ point have go method ensure availability on 2 nics.  can handled in network switch environment virtual port channels.

but, explanation getting long.  basically, there lot of ways skin cat on network configuration.  lot depends on business justifications.

"hyper-v cant transfer cluster name, node-server nams, if put fqdn of cluster."

you going need provide more complete description of problem.  mean 'transfer'?  explain trying accomplish , tell did accomplish that?

"c:\clusterstorage says access denied?"

again, more information needed.  getting message?  trying do?

"hyper-v wont move vm node machines either, gives error hardware requirements. machie identical source server."

again, more information needed.  in addition vr38dett questions, remember how hyper-v configured on hosts determines 'hardware' seen vms.

---

.:|:.:|:. tim

Windows Server  >  High Availability (Clustering)