1.      Cbengine logs:  C:\Program Files\Microsoft Azure Recovery Services Agent\Temp

Transformer not found for the exception, using unknown exception transformer | Params: {Exception = System.AggregateException: One or more errors occurred. ---> Microsoft.Identity.Client.MsalServiceException: A configuration issue is preventing authentication - check the error message from the server for details. You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details.  Original exception: AADSTS700027: The certificate with identifier used to sign the client assertion is expired on application. [Reason - The key used is expired., Thumbprint of key used by client: 'xxxxxxxxxxxx', Found key 'Start=11/15/2021 13:54:55, End=11/16/2024 13:54:55', Please visit the Azure Portal, Graph Explorer or directly use MS Graph to see configured keys for app Id 'xxxxxxxxx'. Review the documentation at https://docs.microsoft.com/en-us/graph/deployments to determine the corresponding service endpoint and https://docs.microsoft.com/en-us/graph/api/application-get?view=graph-rest-1.0&tabs=http to build a query request URL.

 

Enable replication failed for virtual machine 'XXXXXX'. Service returned an error. (Error Code '8079ffff'). (Virtual Machine ID XXXXX, Data Source ID XXXXX, Task ID XXXXX)

Fix

I am afraid we may not have an alert for the certificate. If you encounter the same issue where all replication jobs associated with one Hyper-V host suddenly pause, you can directly renew the certificate as you did today without re-installing and re-registering.

FYI, the certificate details can be reviewed by running the following command on PowerShell:

Get-ChildItem Cert:\LocalMachine\My | where{$_.Subject -like “*”} |fl