sirclesadmin
3 years ago
Hyper-V Replication error issue on SQL server VM:

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 16/03/2020 11:37:28
Event ID: 32022
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: %computername%.domain.local
Description:
Hyper-V could not replicate changes for virtual machine 'DB VM': The operation timed out (0x00002EE2). (Virtual machine ID 106925A8-DA68-4D41-8293-0014FE5A27AD)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>32022</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-03-16T11:37:28.556143900Z" />
<EventRecordID>119513</EventRecordID>
<Correlation />
<Execution ProcessID="3044" ThreadID="4280" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>%computername%.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>DB VM</VmName>
<VmId>106925A8-DA68-4D41-8293-0014FE5A27AD</VmId>
<ErrorMessage>%%12002</ErrorMessage>
<ErrorCode>0x00002EE2</ErrorCode>
</VmlEventLog>
</UserData>
</Event>

Coincides with:

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 16/03/2020 11:37:28
Event ID: 29312
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: %computername%.domain.local
Description:
Connection to the Replica server '%computername%.domain.local' timed out while waiting to receive a response for virtual machine DB VM: The operation timed out(0x00002EE2). The total size of replication data being transferred is 332 KByte(s). (Virtual machine ID 106925A8-DA68-4D41-8293-0014FE5A27AD)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>29312</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-03-16T11:37:28.547782000Z" />
<EventRecordID>119512</EventRecordID>
<Correlation />
<Execution ProcessID="3044" ThreadID="4280" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>%computername%.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>DB VM</VmName>
<VmId>106925A8-DA68-4D41-8293-0014FE5A27AD</VmId>
<ErrorMessage>%%12002</ErrorMessage>
<ErrorCode>0x00002EE2</ErrorCode>
<Parameter0>%computername%.domain.local</Parameter0>
<Parameter1>332</Parameter1>
</VmlEventLog>
</UserData>
</Event>

And:

Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 16/03/2020 11:37:28
Event ID: 32315
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: %computername%.domain.local
Description:
Hyper-V failed to replicate changes for virtual machine 'DB VM' (Virtual machine ID 106925A8-DA68-4D41-8293-0014FE5A27AD). Hyper-V will retry replication after 1 minute(s).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>32315</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-03-16T11:37:28.556335000Z" />
<EventRecordID>119514</EventRecordID>
<Correlation />
<Execution ProcessID="3044" ThreadID="4280" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>%computername%.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>DB VM</VmName>
<VmId>106925A8-DA68-4D41-8293-0014FE5A27AD</VmId>
<Parameter0>1</Parameter0>
</VmlEventLog>
</UserData>
</Event>

Is this because the SQL server has too great a disk usage to replicate reliably?
Sponsor

Want to thank us? Use: Patreon or PayPal or Bitcoins: 3GJia7gLLY8V8eYBf5Q3RjCrNV8kZC3aNn

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.


sirclesadmin
7 months ago
It is worth removing the replication partner and re-adding it as we have solved this error in the past that way.
You will want to look at how many VMs are on that drive and what the throughput it. Have a look at performance monitor on disks and NICs for the servers on each side of the replication.
You will also want to check how much data is being replicated but in the above it only appears to be 332Kbytes but if it is an SQL server there may be issues replicating the whole DB? instead of just part of the file.
It may be worth considering replicating the DB rather than the db drive but it might not suit your needs.
In general, a dedicated disk for the DBs and logs is bets so VMs aren't usually the best idea for SQL.