none
Hyper-V VM replication to Azure stopped CBEngine Logs reports RRS feed

  • Question

  • We see this error in the CBEngine Logs reports Reason - The key used is expired., Thumbprint of key used by client. Agent is updated to run the latest. How to fix this.

    Additionally see this Exception in GetAADToken | Params: {Data = }{Message = AADSTS700027: Client assertion contains an invalid signature

    Thanks


    NJ



    • Edited by navinjk11 Thursday, September 5, 2019 4:21 AM
    Thursday, September 5, 2019 4:15 AM

Answers

  • Got it resolved. 

    1- First updated the Azure Site Recovery Provider to the latest version.

    2- Checked the CBENGINE Logs and found the errors as above. Identified that the Hyper-V Replication certificates had expired.

    3- On Azure -Recovery Vault -Site Recovery Infrastructure -Hyper-V Hosts Selected the Hosts and Selected Option Renew Certificates. After a few minutes verified that the Certificate was updated and the Replication Resumed.

    Thanks for the response.


    NJ

    Thursday, September 5, 2019 2:27 PM

All replies

  • Was the replication working fine before?

    Are you using an authenticated proxy to control network connectivity? If so, Azure Site Recovery doesn't support it.

    Thursday, September 5, 2019 12:00 PM
    Moderator
  • Got it resolved. 

    1- First updated the Azure Site Recovery Provider to the latest version.

    2- Checked the CBENGINE Logs and found the errors as above. Identified that the Hyper-V Replication certificates had expired.

    3- On Azure -Recovery Vault -Site Recovery Infrastructure -Hyper-V Hosts Selected the Hosts and Selected Option Renew Certificates. After a few minutes verified that the Certificate was updated and the Replication Resumed.

    Thanks for the response.


    NJ

    Thursday, September 5, 2019 2:27 PM
  • Thanks for the update! Glad to hear it is resolved :)
    Tuesday, September 10, 2019 8:46 AM
    Moderator