Question about Server 2016 Hyper-V Failover (Stretch) Cluster with Storage Replica between multiple SAN based CSVs
this first time posting on these forums, please bear me.
my company has on-site hyper-v failover cluster of 24 hosts, right around 150 vms, located in midwest. have 5 csvs (where vms housed) located on netapp san. year ago, decided implement dr site near our denver office. have identical environment there (not many hosts), has it's own similar failover cluster , netapp san. currently, entire infrastructure running server 2012 r2, we've started testing few free nodes on 2016. before knew awesome new features 2016 offers, decision made implement hyper-v replication dr site. has proven quite frustrating process, continually have issues vm replicas breaking , have remove , re-add replication, requires entire initial replication again.
i have few questions 2016 failover stretch cluster, can't seem find answers to...
1. if wanted drop hyper-v replication , use storage replica, happens regards ip addressing on vms? no hyper-v replication means no place put in failover ip on replica vm... each site operates on different subnet.
2. how failover work exactly? if primary site goes down, understand vms should failover dr site, can't find description of how process works, of if there need configure beforehand, ips...
any on appreciated!
thanks!
hi,
1. ip addresses inside vms not change if configured replication.
2. i'm afraid there no documents underlying mechanism.
here references you:
https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-replica/storage-replica-frequently-asked-questions
best regards,
leo
please remember mark replies answers if help.
if have feedback technet subscriber support, contact tnmff@microsoft.com.
Windows Server > High Availability (Clustering)
Comments
Post a Comment