Hyper-V Replication Timed Out Error Troubleshooting

hyper-vwindows-server-2012-r2

Due to a HDD space issue, I paused replication from our main server to replication/backup server. Both are running Win 2012R2.

I have now resolved the space issue on the destination server and Hyper-V is requiring me to 'resynchronize' a few VM's.

I have tried this, but on two of the VM's it is giving me a Hyper-V failed to resynchronize changes for virtual machine '<VM NAME>': The operation timed out (0x00002EE2) error in Event Viewer.

It then stops and starts from the beginning again and throws up this error again, and it just does this over and over…

Now I understand the 'timed out' error, but this is between two hosts that have a 1Gbps internet connection so I cannot see how that can be possible, certainly not if it is trying to say that the source/destination servers do not have enough bandwidth. I would accept that it times out for a different reason, but what could that be? The errors give no more info.

Is it possible to give the operation more time to try and complete? I assume that it is trying to resync the whole thing as it was disabled for around 2 weeks and cannot perform a simply 'replicate changes' and needs to do the whole thing.

It seems to get to 45% then throws that error, stops and tries again from 0%.

Any pointers on how to resolve would be great.

Thanks.

Best Answer

It might be DNS or TCP/IP related error. Make sure that replica and source host can ping each other using ping or nslookup by DNS name, FQDN and IP. Here is some info (#3) - https://www.altaro.com/hyper-v/advanced-troubleshooting-of-hyper-v-replica-part-1/

Related Solutions

Sql-server – “The wait operation timed out” when running SQL Server in Hyper-V

Try to execute this command:

exec sp_updatestats

It, incredibly, resolved the problem.

The code above its the error before the command has been executed.

[Win32Exception (0x80004005): The wait operation timed out]

[SqlException (0x80131904): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +1742110
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +5279619
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +242
   System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) +1434
   System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() +61
   System.Data.SqlClient.SqlDataReader.get_MetaData() +90
   System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +365
   System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite) +1355
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) +175
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +53
   System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +134
   System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) +41
   System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) +10
   System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +140
   System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +316
   System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +86
   System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1482
   System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +21
   System.Web.UI.WebControls.DataBoundControl.PerformSelect() +138
   System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +30
   System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +79
   System.Web.UI.WebControls.BaseDataBoundControl.OnPreRender(EventArgs e) +22
   System.Web.UI.Control.PreRenderRecursiveInternal() +83
   System.Web.UI.Control.PreRenderRecursiveInternal() +155
   System.Web.UI.Control.PreRenderRecursiveInternal() +155
   System.Web.UI.Control.PreRenderRecursiveInternal() +155
   System.Web.UI.Control.PreRenderRecursiveInternal() +155
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +974

Replication establishing error between Hyper-V 2012R2 and 2016 (0x00002EFE)

I have found the answer: HTTP communication in replication protocol is crafted proprietarily. So it is not the standard one. In my Kerio Control, there is a IPS protection what kills the connection silently. I was created special firewall rule that is only for that commnunication and this rule is not using HTTP inspection module. From that point the replication starts working smoothly.

Related Topic