Trying to get Azure Site Recovery working and running into issues.  Any ideas would be greatly appreciated.

Environment:
host server: Windows Server 2012 R2
one VM: also Windows Server 2012 R2
427 GB of total data
T1 internet connection

We started the initial replication on 8/7.  It ran for about a week, then seemed to indicate that it completed successfully.  It shows some errors, but they seem to be related to the missed replication cycles while the initial replication was running.  Here's what I see on 8/14:

• In Hyper-V server event log "MicrosoftAzureRecoveryServices-Replication" it shows Information Event ID 2 logged at 8/14/2015 3:57:41 AM: "Successfully completed initial replication over the network for virtual machine 'xxx'".
• In Hyper-V, it shows:
          -Replication Health: Critical
          -Successful replication cycles: 1 out of 22
          -Size of data yet to be replicated: 21.37 GB
          -Last synchronized at: 8/7/15  2:55:51 PM
• In Azure Site Recovery portal, it shows:
          -Health: Critical
          -Status: Protected
          -Error ID    68514
          Possible causes    The last successful replication for virtual machine 'xxx' in cloud/site 'xxx' was more than two hours ago. Replication couldn't complete because of issues with connectivity to the Azure storage account.
          Recommendation    Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host server and if required resume the replication.

Replication then appeared to be paused on the Hyper-V host.  If I click "Resume Replication", it runs for a few hours, then fails.  I see the following errors in Windows event log and Azure Site Recovery portal:

Log Name:      MicrosoftAzureRecoveryServices-Replication
Source:        MicrosoftAzureRecoveryServices
Date:          8/14/2015 7:27:39 PM
Event ID:      63
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      xxx.xxx.local
Description:
Replication failed for virtual machine 'xxx' with an unexpected error while trying to update progress of the operation. This could happen because the operation was cancelled or because a time out was encountered during the operation. Please ensure that the Hyper-V Virtual Machine Management service is running and then try again.

        The virtual machine couldn't be replicated.
        Error ID    68518
        Possible causes    More than 20% of the replication cycles for virtual machine 'xxx' in cloud/site 'xxx-HyperVSite' have been missed. Replication couldn't complete because of issues with connectivity to the Azure storage account.
        Recommendation    Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host server and if required resume the replication.

        The virtual machine couldn't be replicated.
        Error ID    68502
        Possible causes    Replication was paused either manually, or due to problems with virtual machine 'xxx' in cloud/site 'xxx-HyperVSite'.
        Recommendation    Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host server and resume the replication.

        The virtual machine couldn't be replicated.
        Error ID    68523
        Provider error    Replication failed for virtual machine 'xxx' with an unexpected error while trying to update progress of the operation. This could happen because the operation was cancelled or because a time out was encountered during the operation. Please ensure that the Hyper-V Virtual Machine Management service is running and then try again.
        Possible causes    Check the Provider error messages.
        Recommendation    Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host server and if required resume the replication.

Please note that I've tried to "Resume Replication" multiple times and tried rebooting the Hyper-V server, but still get the same results/errors when I try to run subsequent replications.  Also note that this is the second time that I've tried to setup Azure Site Recovery for this Hyper-V server.  The first time I ran into exactly the same problem.  At that time, I uninstalled Azure Recovery Services Agent and Azure Site Recovery Provider from Hyper-V server, deleted the VM and the Protection Group from Azure console, then set everything up again from scratch.

Thanks for any help that anyone can provide.

Hi Brendon-MSDN,

We are researching on the query and would get back to you soon on this. I apologize for the inconvenience and appreciate your time and patience in this matter.

Girish Prajwal

Hi Brendon,

Sincere apologies for the delay in responding.

We need to deep dive into the issue to analyse where it is going wrong. I suggest you to open a support case with our technical team (ASR).

http://azure.microsoft.com/en-us/support/options/

Girish Prajwal

Hi Brendon, could you check with this resolution below?

http://blogs.msdn.com/b/nitinsingh/archive/2015/08/31/virtual-machine-protected-using-azure-site-recovery-keeps-on-going-to-resynchronization-state-randomly-and-then-resynch-will-also-fail.aspx

Thank you,

Ruturaj

Hi Girish and Ruturaj,

Thank you for the replies.

We don't have a support contract to open a case.

I checked the article, but we don't have any disks larger than 1 TB.  There are 3 disks in the VM and the largest is 350 GB.

We have given up on using Azure Site Recovery on this server. We might try it again at a later time if we end up getting a faster internet connection.

Brendon