Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,635 questions
Stretch Hyper-V cluster, storage replica - Set-SRNetworkConstraint
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 72%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPZ%3C/text%3E%3C/svg%3E)
Piotr Ziemiański
0
Reputation points
Hi,
I have a stretch Hyper-V cluster, configured on Windows Server 2022 Data Center.
I use the Storage Replica functionality. I have limited network interfaces for a replica (Set-SRNetworkConstraint), for one cluster network.
When I testing this configuration, I receive incorrect behavior after disconnecting the network defined in SRNetworkConstraint in all cluster nodes. Replication alternates between disconnections and connections in other available cluster networks. The logs in this situation show:
04.10.2023 17:33:27 5015 Information Successfully established a connection to a partner replica....
04.10.2023 17:33:27 5014 Error Connection lost to the share hosting the partner replica....
04.10.2023 17:33:26 5015 Information Successfully established a connection to a partner replica....
04.10.2023 17:33:26 5014 Error Connection lost to the share hosting the partner replica....
04.10.2023 17:33:16 5015 Information Successfully established a connection to a partner replica....
04.10.2023 17:33:16 5014 Error Connection lost to the share hosting the partner replica....
04.10.2023 17:33:15 5015 Information Successfully established a connection to a partner replica....
04.10.2023 17:33:15 5014 Error Connection lost to the share hosting the partner replica....
04.10.2023 17:33:14 5015 Information Successfully established a connection to a partner replica...
In Performance counter I can also see that the status of the replica changes over and over again from correct to incorrect.
If I do not have SRNetworkConstraint defined, after disconnecting one of the cluster networks, the replica works correctly - its disconnects and connects to other available cluster networks.