ASR Error - Replication for the virtual machine failed due to a failure in exporting the virtual machine configuration RRS feed

  • Question

  • Hello all,

    We have enabled the on-prem Hyper-V VM replication through ASR and its works fine for 3 Hyper-V VM However, we are getting below error for one Hyper-V VM.  

    Error Message
    Replication for the virtual machine ABC failed due to a failure in exporting the virtual machine configuration 

    Provider error
    Export System Definition for virtual machine 'ABC' failed.

    Provider error
    Replication for virtual machine 'ABC' is in error. Fix the error(s) and resume replication.

    Possible causes
    Replication errors occurred for virtual machine 'ABC' in cloud/site 'BIM' because of issues with connectivity to Azure storage.

    Error Message
    Replication for the virtual machine ABC failed (ErrorCode: 8079002c Timestamp).

    Provider error
    The configuration file for virtual machine 'ABC' could not be sent to the Azure Site Recovery. You may not be able to failover back your virtual machine on your host if it gets deleted from the host. (Virtual Machine ID 3dd0de15-4c26-4d80-b575, Data Source ID 175976331, Task ID 6013-e21b-a9a9-c631261e91f1)

    Possible causes
    Failure while replicating the virtual machine to Azure.


    • Edited by Suhag Desai Thursday, October 17, 2019 12:05 AM subject change
    Thursday, October 17, 2019 12:05 AM

All replies

    1. From an elevated PowerShell session on the Hyper-V host run command Get-VMIntegrationService -VMName<VMName> check if any service is in failed state.
    2. Check if the integration service on the VM is up to date “using the Hyper-V console”.
    3. Login to the VM, run CMD as admin and run the command VSSadmin list writers “ and make sure all the services are stable
    4. If everything looks good, disable and re-enable replication for this VM.
    Thursday, October 17, 2019 12:41 PM
  • Thank you.

    Have checked the above but all looks good. We can see healthy replication from Hyper-V, However, on portal it is still showing critical warning but updating the %. Any clue on this?



    Thursday, October 17, 2019 6:40 PM
  • Is this a production environment VM? 
    If yes, I suggest reaching out to Azure technical support team for further investigation into this issue.

    If this is not a prod VM, you can try the following:

    1. The issue should be related to creating checkpoint for the VM, can you create checkpoint manually for the VM from the Hyper-V console? or 

    2. Try below reg key change: Please backup the reg key before making any change.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Backup\Replication Azure
    Name : MaxUploadConfigSizeInMB
    Type: REG_DWORD
    Value : 100

    If this doesn't work

    3. Try changing the default installation location of MARS agent using below command

    reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Replication" /v ConfigExportLocation /t Reg_Sz /d <TargetFolderPath>

    Friday, October 18, 2019 12:09 PM
  • Thanks, i will open the ticket with MS


    Friday, October 18, 2019 2:05 PM
  • @Suhag Please let us now the status of your issue. Appreciate if you could share the support request number for internal tracking. 

    Monday, October 21, 2019 6:30 AM
  • Hi - We decided to migrate the VM manually by uploading the VHD as Azure ASR not working as expected. 


    Monday, October 21, 2019 6:37 PM
  • Let us know how it goes.
    Tuesday, October 22, 2019 7:42 AM