Hyper-v Replica: Planned Failover from Cluster to another Cluster Failed

Hi Guys,
i have one issue and i cannot find a way to troubleshooting
i Have one Primary Site running 8 nodes Hyper-v with Failover Cluster and Hyper-v Replica Broker confguration
i have one Replica Site running 8 nodes Hyper-v with Failover Cluster and Hyper-v Replica Broker
Replica Broker Configuration:
https://onedrive.live.com/redir?resid=45C59B28F67FC71C%212271
both side are pinging and name resolution is ok
all ports are open
The Virtual Machine Replication is ok
The Planned Failover cannot complete and show me this simple error
"failed"
i have no message on event Viewer
Error:
https://onedrive.live.com/redir?resid=45C59B28F67FC71C%212270
Planned Failover from Cluster (Primary site) to another Cluster (Replica site) with Replica
Start Hyper-V Manager pr failover cluster console on the primary server and choose a virtual machine to fail over.
1. Turn off the virtual machine that you want to fail over.
2. Right-click the virtual machine, point to Replication, and then point to
Planned Failover.
3. Click Fail Over to actually transfer operations to the virtual machine on the Replica server.

Hi Samuel,
In the original post :
Tests: 1 -
Planned Failover from Cluster to StandAlone Hyper-v is ok
Test: 2
Planned Failover from Standalone hyper-v to Cluster is ok
Test:3
Planned Failover from Cluster (Primary site) to another Cluster (Replica site) with Replica
There is no standalone hyper-v to standalone hyper-v between two sites .
After the last test , if they still can not do planned failover , maybe you can focus on network configuration .
Best Regads
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Replica Planned Failover - Reverse Replication Fails

Replication was created successfully from server HV1 to HV2. Both HV servers are domain members, with valid DNS. I can add HV2 to the Hyper-V management console on HV1, and vice versa, so I can manage both servers from either console. (i.e.,
they talk nicely to each other)
When I run a Planned Failover test, the message shown below pops up saying "Hyper-V failed to enable reverse replication", along with additional info.
Before I needlessly get too wordy in this post, any ideas on what the problem is?
NOTE: NO firewall is running on either machine.

Both servers answer on port 80 with telnet. When any character is typed in, an HTTP response is given which demonstrates the service is listening and responding. (BOTH servers give an identical response.)
HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=us-ascii
Server: Microsoft-HTTPAPI/2.0
Date: Fri, 25 Apr 2014 16:03:31 GMT
Connection: close
Content-Length: 326
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Verb</h2>
<hr><p>HTTP Error 400. The request verb is invalid.</p>
</BODY></HTML>
Connection to host lost.
Next comes the powershell test. Running the powershell test on HV1 where the original VM is (looking toward HV2 where the replica is) a success resonse is given. However, when running the same test on HV2, it errors with
the response:
Test-VMReplicationConnection : Hyper-V failed to test replication settings for specified Replica server
'hv1.(domain).net'. Error: The connection with the server was terminated abnormally (0x00002EFE).
Hyper-V failed to establish a connection with the Replica server 'hv1.(domain).net' on port '80'. Error: The connection
with the server was terminated abnormally (0x00002EFE).
At line:1 char:1
+ Test-VMReplicationConnection hv1.(domain).net 80 kerberos
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Test-VMReplicationConnection]
, VirtualizationOperationFailedException
+ FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.TestVMReplicationConnectionCommand
In the event log tree you specified is the error:
EVENT ID: 29288Hyper-V failed to test replication settings for specified Replica server 'hv1.(domain).net'. Error: The connection with the server was terminated abnormally (0x00002EFE).
So the event logs show the same error (connection was terminated abnormally) as was shown in the screenshot in my original post. It makes sense that reverse-replication cannot be established when HV1 abruptly terminates the connection from HV2.
The question is WHY it's happening. To reiterate, both machines are configured for replication from any authenticated server, both are members of the same domain, and all administration is done using the domain (not local) admin account.
Any ideas?

Cannot apply Hyper v Replica ip failover. [RESOLVED]

Hello,
I'm using Hyper with replica server. I have two hosts in Windows Server 2012 with hyper v installed and last integration installed both sides on each VM.
I have set up the failover ip on each side, and when I try to failoer a machine evryhting work good execpt the ip failover... I have this error :
« xxxx» n’a pas pu appliquer les paramètres IP à l’adaptateur « {6f71b925-f7d3-4f7a-b987-ca787eca5643} » : Erreur non spécifiée (0x80004005). (ID d’ordinateur virtuel 3B423647-943C-444C-9E2A-E8C24973B643)
English : « xxxx»cannot apply ip settings to the adaptor« {6f71b925-f7d3-4f7a-b987-ca787eca5643} » : non specified error (0x80004005). (ID d’ordinateur virtuel 3B423647-943C-444C-9E2A-E8C24973B643)...
+
System
Provider
[ Name]
Microsoft-Windows-Hyper-V-Integration-KvpExchange
[ Guid]
{82D60869-5ADA-4D49-B76A-309B09666584}
EventID
4132
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x8000000000000000
TimeCreated
[ SystemTime]
2013-12-14T15:02:24.884325200Z
EventRecordID
359
Correlation
Execution
[ ProcessID]
4192
[ ThreadID]
1368
Channel
Microsoft-Windows-Hyper-V-Integration-Admin
Computer
xxxx
Security
[ UserID]
S-1-5-83-1-994195015-1145869372-3269995166-1136030537
UserData
VmlEventLog
VmName
xxxServer
VmId
3B423647-943C-444C-9E2A-E8C24973B643
String
{6f71b925-f7d3-4f7a-b987-ca787eca5643}
ErrorCodeString
%%2147500037
ErrorCode
0x80004005
Is someone can help me, I'm stucked for one week now and cannot find any solutions... Thank you very much...

Hi,
I am glad that this issue is solved. Thank you very much for your sharing.
This solution you provided will help lots of people who have similar issues.
Please feel free to ask us if there are any issues in the future.
Best Regards,
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Manual IP failover from one to another host

Hi *,
I needed a script which enables root on "host 2" to configure another IP to a virtual network interface. This is used in case of unavailability of the origin IP owner (host 1).
I tested the following which works fine in my network:
on host 2:
(activate IP)
ifconfig $NEW_NIC plumb
ifconfig $NEW_NIC $H1_IP netmask $NEW_MASK broadcast $NEW_BROADCAST up
(deactivate)
ifconfig $NEW_NIC unplumb
while activated, host 1 is unreachable via "$H1_IP" but host 2 is. After deactivation it takes only a few seconds to "normalize" routing..
My question is: Under which circumstances this scenario wont work and what can I do to circumvent problems?
Many thanks in advance.
Cheers,
Chris

Did you see the response you received on this question when you posted it to comp.unix.solaris?
actually it sounds to me like you need something like Sun Cluster.

Hyper-V Live Migration Compatibility with Hyper-V Replica/Hyper-V Recovery Manager

Hi,
Is Hyper-V Live Migration compatible with Hyper-V Replica/Hyper-V Recovery
Manager?
I have 2 Hyper-V clusters in my datacenter - both using CSVs on Fibre Channel arrays. These clusters where created and are managed using the same "System Center 2012 R2 VMM" installation. My goal it to eventually move one of these clusters to a remote
DR site. Both sites are connected/will be connected to each other through dark fibre.
I manually configured Hyper-V Replica in the Fail Over Cluster Manager on both clusters and started replicating some VMs using Hyper-V
Replica.
Now every time I attempt to use SCVMM to do a Live Migration of a VM that is protected using Hyper-V Replica to
another host within the same cluster,
the Migration VM Wizard gives me the following "Rating Explanation" error:
"The virtual machine virtual machine name which
requires Hyper-V Recovery Manager protection is going to be moved using the type "Live". This could break the recovery protection status of the virtual machine.
When I ignore the error and do the Live Migration anyway, the Live migration completes successfully with the info above. There doesn't seem to be any impact on the VM or it's replication.
When a Host Shuts-down or is put into maintenance, the VM Migrates successfully, again, with no noticeable impact on users or replication.
When I stop replication of the VM, the error goes away.
Initially, I thought this error was because I attempted to manually configure
the replication between both clusters using Hyper-V Replica in Failover Cluster Manager (instead of using Hyper-V Recovery Manager).
However, even after configuring and using Hyper-V Recovery Manager, I still get the same error. This error does not seem to have any impact on the high-availability of
my VM or on Replication of this VM. Live migrations still occur successfully and replication seems to carry on without any issues.
However, it now has me concern that Live Migration may one day occur and break replication of my VMs between both clusters.
I have searched, and searched and searched, and I cannot find any mention in official or un-official Microsoft channels, on the compatibility of these two features.
I know vMware vSphere replication and vMotion are compatible with each otherhttp://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.replication_admin.doc%2FGUID-8006BF58-6FA8-4F02-AFB9-A6AC5CD73021.html.
Please confirm to me: Are Hyper-V Live Migration and Hyper-V Replica compatible
with each other?
If they are, any link to further documentation on configuring these services so that they work in a fully supported manner will be highly appreciated.
D

This can be considered as a minor GUI bug.
Let me explain. Live Migration and Hyper-V Replica is supported on both Windows Server 2012 and 2012 R2 Hyper-V.
This is because we have the Hyper-V Replica Broker Role (in a cluster) that is able to detect, receive and keep track of the VMs and the synchronizations. The configuration related to VMs enabled with replications follows the VMs itself.
If you try to live migrate a VM within Failover Cluster Manager, you will not get any message at all. But VMM will (as you can see), give you an
error but it should rather be an informative message instead.
Intelligent placement (in VMM) is responsible for putting everything in your environment together to give you tips about where the VM best possible can run, and that is why we are seeing this message here.
I have personally reported this as a bug. I will check on this one and get back to this thread.
Update: just spoke to one of the PMs of HRM and they can confirm that live migration is supported - and should work in this context.
Please see this thread as well: http://social.msdn.microsoft.com/Forums/windowsazure/en-US/29163570-22a6-4da4-b309-21878aeb8ff8/hyperv-live-migration-compatibility-with-hyperv-replicahyperv-recovery-manager?forum=hypervrecovmgr
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Unplanned automatic failover using Hyper-v Replica , why don't the VMs start up automatically on the replica server?

Hi,
We have cluster with two hosts (Host01 , host02) replicated to another server (Replica01)
in order to test automatic failover to the replica server (Replica01) We unplugged the power cables from Host01 and Host 02
now the VMs on the replica server is still off , why don't the VMs start up automatically on the replica server?
Ramy Shaker

overall there is no automatic failover in Hyper-V
Of course there is. It's enabled by Failover Clustering. This is a totally separate technology from Hyper-V Replica.
There is no automatic start up in Hyper-V Replica because it is not designed to detect a split-brain condition where the same virtual machine is running in multiple locations simultaneously. The replica site has no way to know why it can't reach the primary
system anymore. It might just be because someone unplugged a network cable. If the primary's virtual machines are still running and the replica decides to spin up its copies, you will have many troubles.
Eric Siron Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
"Every relationship you have is in worse shape than you think."

2 Hyper-V Servers with Failover Cluster and a single File Server and .VHDs stored on a SMB 3 Share

I have 2 X M600 Dell Blades (100 GB local storage and 2 NICs) and a Single R720 File Server (2.5 TB local SAS storage and 6 NICs). I´m planning a Lab/developer enrironment using 2 Hyper-V Servers with Failover Cluster and a single File Server putting
all .VHDs stored on a SMB 3 Share on the File Server.
The ideia is to have a HA solution, live migration, etc, storing the .VHDs onm a SMB 3 share
\\fileserver\shareforVHDs
It is possible? How Cluster will understand the
\\fileserver\shareforVHDs as a cluster disk and offer HA on it?
Or i´ll have to "re-think" and forget about VHDs on SMb 3 Share and deploy using iSCSI?
Storage Spaces makes difference in this case?
All based on wind2012 R2 STD English version

I have 2 X M600 Dell Blades (100 GB local storage and 2 NICs) and a Single R720 File Server (2.5 TB local SAS storage and 6 NICs). I´m planning a Lab/developer enrironment using 2 Hyper-V Servers with Failover Cluster and a single File Server putting
all .VHDs stored on a SMB 3 Share on the File Server.
The ideia is to have a HA solution, live migration, etc, storing the .VHDs onm a SMB 3 share
\\fileserver\shareforVHDs
It is possible? How Cluster will understand the
\\fileserver\shareforVHDs as a cluster disk and offer HA on it?
Or i´ll have to "re-think" and forget about VHDs on SMb 3 Share and deploy using iSCSI?
Storage Spaces makes difference in this case?
All based on wind2012 R2 STD English version
You can do what you want to do just fine. Hyper-V / Windows Server 2012 R2 can use SMB 3.0 share instead of a block storage (iSCSI/FC/etc). See:
Deploy Hyper-V over SMB
http://technet.microsoft.com/en-us/library/jj134187.aspx
There would be no shared disk and no CSV just SMB 3.0 folder both hypervisor hosts would have access to. Much simplier to use. See:
Hyper-V recommends SMB or CSV ?
http://social.technet.microsoft.com/Forums/en-US/d6e06d59-bef3-42ba-82f1-5043713b5552/hyperv-recommends-smb-or-csv-
You'll have however a limited solution as your single physical server being a file server would be a single point of failure.
You can use Storage Spaces just fine but you cannot use Clustered Storage Spaces as in this case you'll have to take away your SAS spindles from your R720 box and mount them into SAS JBOD (make sure it's certified). So you get rid of an active components
(CPU, RAM) and keep more robust all-passive SAS JBOD as your physical shared storage. Better then a single Windows-running server but for a true fault tolerance you'll have to have 3 SAS JBODs. Not exactly cheap :) See:
Deploy Clustered Storage Spaces
http://technet.microsoft.com/en-us/library/jj822937.aspx
Storage Spaces,
JBODs, and Failover Clustering – A Recipe for Cost-Effective, Highly Available Storage
http://blogs.technet.com/b/storageserver/archive/2013/10/19/storage-spaces-jbods-and-failover-clustering-a-recipe-for-cost-effective-highly-available-storage.aspx
Using
Storage Spaces for Storage Subsystem Performance
http://msdn.microsoft.com/en-us/library/windows/hardware/dn567634.aspx#enclosure
Storage
Spaces FAQ
https://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx
Alternative way would be using Virtual SAN similar to VMware VSAN in this case you can get rid of a physical shared storage @ all and use cheap high capacity SATA spindles (and SATA SSDs!) instead of an expensive SAS.
Hope this helped :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Change Hyper-V 2012 R2 failover cluster management subnet

Hi,
We have an existing Hyper-V 2012 R2 Failover cluster. Virtual machines are live on this cluster. The networking team has decided to reorganise the network subnets. As a consequence we need to change the management IPs of our Hyper-V failover
clusters.
What are the possibilities?
Evect 1 node from the cluster, set correct management IP on the evicted cluster. Create a single-node cluster. Mask a new LUN to the single-host cluster. Execute a shared nothing live migration of the VMs which are hosted on old cluster.
Kr,

Hi Kr,
You can refer the following similar scenario article:
Changing Hyper-V Cluster Virtual IP Address (VIP) After Layer 3 Changes
http://blogs.technet.com/b/chrad/archive/2011/09/16/changing-hyper-v-cluster-virtual-ip-address-vip-after-layer-3-changes.aspx
Change IP address Hyper-V Cluster
http://bartvanvugt.blogspot.com/2012/01/change-ip-address-hyper-v-cluster.html
More related third party article:
Change IP address Hyper-V Cluster
http://bartvanvugt.blogspot.com/2012/01/change-ip-address-hyper-v-cluster.html
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V replica vs Shared Nothing Live Migration

Shared Nothing Live Migration allows to transport your VM over the WAN without shutting it down (how much time it takes on io intensive vm is another story)
  Hyper-V replica does not allow to perform the DR switch without shutdown operation on primary site VM !
why can't it take the VM live to the DR ?
that's because if we use Shared Nothing across the WAN, we don't use the data that Hyper-V replica can and then it also breaks everything hyper-V replica does.
Point is: how to take the VM to DR in running state, what is the best way to do that ?
Shahid Roofi

Hi Shahid,
Hyper-V Replica is designed as a DR technology, not as a technique to move VMs. It assumes that should you require it, the source VM would probably be offline and therefore you would be powering up the passive copy from a previous point in time
as its not a true synchronous replica copy. It does give you the added benefit to be able to run a planned failover which as you say, powers of the VM first, runs a final Sync then powers the new VM up. Obviously you cant have the duplicate copy of this VM
running all the time at the remote site, otherwise you would have a split brain situation for network traffic.
Like the live migration the shared nothing live migration is a technology aimed at moving a VM, but as you know offers the ability to do this without having shared storage and only requires a network connection. When initiated moves the whole
VM, well copies the virtual drive and memory before sending machine writes to both, then only to the new VM when they both match. With regards to the speed, I assume you have the SNLM setup to compress data before sending across the wire?
If you want a true live migration between remote sites, one way would be to have a SAN array between both sites synchronously replicating data, then stretch the Hyper-V cluster across both sites. Obviously this is a very expensive solution but perhaps
the perfect scenario.
Kind Regards
Michael Coutanche
Blog:
Twitter:   LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Hyper-V Replica Broker to multiple CSVs

With some help from the TechNet community and a whole lot of trial and error, I have successful configured my failover cluster and performed a couple of planned failovers. Hooray! However, I have 3 CSVs on my DR cluster and would like to utilize the entire
disk space for replication. I have a replica broker on the primary side (not configured) and one on the DR side that points to the primary broker and points to 1 volume on the DR cluster for storage. I just found out that I cannot add additional volumes in
the specified servers section by pointing to the same primary server. So do I (A) make multiple brokers on the primary side with unique names and point them each to a CSV. (B) Delete my volumes and make one big one to facilitate all the replicas? Is
there a third or even fourth option I haven't contemplated. Obviously, I would like to keep the setup as simple and efficient as possible. Thank you in advance for any help.
Brian Gilmore Lead IT Technician Don-Nan Pump & Supply

Hi Brian,
It is only possible to create a single Replica Broker per cluster. The cluster will not allow you to create a second or third role. The normal way would be to create a larger CSV for VM replicas and leave normal running VMs on the other CSVs.
The only other way would be to use multiple standalone hosts on the primary site and split the incoming data up by host name but then you lose the whole point of a fail over cluster without the cluster.
Hope that helps a little, regards Michael

Server 2012: Enabling Hyper-V Replica Site to Site Failure

We recently installed Server 2012 Data Center with Hyper-V on a two servers at two different sites: Main Site and DR Site.
Hyper-V is enabled and working great at both sites on these servers and now trying to configure Hyper-V replica gets us this result:
Some of the items we made sure to verify:
Enabled Firewall rules for inbound rules on Port 80. (Hyper-V Replica HTTP Listener) (Both Sites)
Modified ASA Firewall for HTTP port 80 and can run a packet trace from site to site.
Ping works fine in communication between servers
Both are in the same domain
Within the same Trust Group
Same default storage location and can view the folder from each location
So I am not sure what we are missing, but is there another port that needs to be open if we are going through HTTP because after starting to configuring the replica another message shows that "Could not get the configuration details of the specified server."
Searching around on TechNet didn't show any resolution for this, but if anyone would have some additional tips to try to troubleshoot that would be greatly appreciated!
Thank you!
-Jeff

Hi All,
I am facing the same issue, Please let me the solution... I have given permission to user account at Local Groups in both nodes of Primary Site and DR Site.. and Windows Firewall is also off, IP Subnet is Different at both End...
Brief Description of Infrastructure.
We have Setup Windows Cluster 2012 Failover Cluster in Both Sites ( primary and DR) with the help of mentioned links.
http://www.thomasmaurer.ch/2012/07/hyper-v-replica-the-game-changer/
http://kristiannese.blogspot.in/2012/03/hyper-v-replica-by-example-part-one.html
Now, We want to cross-check Hyper-V Replica functionality but it is saying that Port 80 is not opened, Need Suggestion on same.
Windows Firewall inbound rules is already set as per above links.
Question: From where to where we need to open port 80 means which nodes/cluster/Hyper-V Broker ? As per mentioned cases.
Like,
Case 1. From Hyper-V broker of Primary Site to Hyper-V Broker of DR Site
Case 2: From Physical IP Address of Both Servers at Primary Site to Physical IP of Both Server at DR Site.
Case 3: From Cluster IP Address of Primary Site to Cluster IP of DR Site.
Case 4. From Physical IP Address of Primary Site to Hyper-v Replica Broker of DR Site.
Case 5. Port 80 need to open between Both End for Physical IP’s, Hyper-V Replica Broker and Cluster IP.
Kindly suggest on urgent basis.
Note: It is working fine in same IP Subnet, only change with different Subnet.
Please suggest from which IP to which IP , port 80 Need to be open in Mentioned scenerio.
Primary Site.
Host 1 IP address : 10.25.135.25
Host 2 IP address : 10.25.135.26
Cluster IP Address : 10.25.135.27
Hyper-V Replica Broker Role : 10.25.135.28
DR Site
Host 1 IP Address : 10.103.48.100
Host 2 IP Address : 10.103.48.101
Cluster IP address : 10.103.48.27
Hyper-V Replica Broker Role: 10.103.48.28
I hope , now you can help me.
Thanks
Kirpal Singh

Hyper-V Replica Capacity Planner stuck getting VM information

I'm trying to use the Capacity Planner for Hyper-V replica tool to estimate requirements for a replica site.
It keeps getting stuck "Getting the VM and VHD from primary site, this can take upto several minutes...". I've waited over an hour, and it still sits there.
The primary site is a 3 node Hyper-V 2012R2 cluster. I have installed and configured the Hyper-V Replication Broker role on the cluster. For now, it's set to use HTTP without any certificates.
I don't have a replica site yet, so I've selected "Skip tests involving Replica site". For the primary site, I've tried pointing it at both the replication broker, and at one of the individual nodes. It gets stuck in the same place.
Other things I've tried:
Disabled windows firewall on all 3 nodes
Running the tool from one of the nodes, logged in as a domain admin account
Moving all the VMs off of one node, and pointing the tool at that now empty node
Let it run for longer - left it alone overnight.
Downloaded the tool again in case it was corrupt
Rebooted my computer
In all cases, it gets stuck at the exact same spot.
Any idea how to figure out why it is freezing? Have I missed configuring something important for the tool to run?

Hi Grant,
Thanks for your reply.
The tool and documentation have been updated for Windows Server 2012 R2
and can be download from here:
http://www.microsoft.com/en-us/download/details.aspx?id=39057
Would you please update it and see if it helps.
Best Regrds,
Susie
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hyper-V Replica Broker resource not coming online

I was trying to create a cluster broker on a cluster using WMI. I am creating the required IPv4, IPv6 network resources and adding them as a dependency on the Hyper-V replica broker resource. When trying to bring the broker online, the Hyper-V Replica Broker
resource is failing to come online with the below errors.
INFO [NM] Received request from client address HRM-08-007.
ERR [RES] Virtual Machine Replication Broker <Hyper-V Replica Broker C10022014XXXX>: 'Hyper-V Replica Broker C10022014XXXX' failed to start the network listener on destination node 'MachineName': No such host is known. (0x80072AF9). Please
look at the event log on destination node for more details.
WARN [RES] Virtual Machine Replication Broker <Hyper-V Replica Broker C10022014XXXX>: 'Hyper-V Replica Broker C10022014XXXX' failed to start the network listener for the Hyper-V Replica Broker resource: Unspecified error (0x80004005).
The node 'MachineName' does exist.
What might be the issue? How to debug this.

Would be helpful to post your WMI script. Pretty hard to guess at the commands you are trying to use to accomplish this.
And what did the event log say in the destination node?
.:|:.:|:. tim

Does Lync Server 2013 support Hyper-V Replica

I can’t find a definitive answer on this. I plan on either having 2 Standard Edition Lync 2013 Servers, or use Hyper-V replica for disaster recovery.
I’m expecting some down time during the failover. Looking for the simplest and most cost effective solution.

Hi,
It is not supported. Here are similar cases:
http://social.technet.microsoft.com/Forums/windows/en-US/ce08024b-6516-44b6-9fb0-76e9c02b1da2/does-lync-2013-support-hyperv-replica?forum=lyncdeploy
http://social.technet.microsoft.com/Forums/windows/en-US/d5882edc-e25c-4d09-9079-d6f8e90d4035/does-lync-2013-support-hyperv-replica?forum=winserverhyperv
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V Replica Trust Group...

Hi all;
As you know, when configuring Hyper-V Replica on a Replica Server, it able use to specify multiple primary servers. Right?
As I can specify which servers are trusted to replicate to replica server, why bother me to create a Trust Group and join that primary servers to it? What is the primary purpose of creating Trust Group?
Thanks
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Hi Sir,
>> What is the primary purpose of creating Trust Group?
"How is this useful? Hyper-V Replica allows replication to continue seamlessly when virtual machines are migrated either on the primary server/cluster or Replica server/cluster. Hence the
replication traffic for a given Replica virtual machine cannot be tied only
to the server that enabled replication of the virtual machine. "
"Tag to group a set of such allowed primary servers into a trust zone (Security Tag).
http://blogs.technet.com/b/virtualization/archive/2012/04/09/configure-your-replica-server-to-receive-replication-traffic-from-specific-primary-server-s.aspx
Best Regards,
Elton JI
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Hyper-v Replica: Planned Failover from Cluster to another Cluster Failed

Similar Messages

Maybe you are looking for