Détails de l'erreur
XXXXXXXXXXXXXXXXXXX
ID de l'erreur
324520
Message d'erreur
Resynchronization is in progress for disk(s) \\.\PHYSICALDRIVE0 of the source machine XXXXXXXXXXXXXXXXXXX
Causes possibles
The disk(s) - \\.\PHYSICALDRIVE0 were inconsistent with the target volume in Azure, due to data missed in transit or due to an intermittent server failure. This issue has now been resolved and to achieve data consistency and avoid data corruption, following disk(s) required resynchronization - \\.\PHYSICALDRIVE0. 
Recommandation
Resynchronization is already in progress for the source machine. Please wait for some time for the operation to complete.
Vu la première fois à
25/04/2025 09:48:34
ID de l'erreur
323500
Message d'erreur

      Replication for XXXXXXXXXXXXXXXXXXX (\\.\PHYSICALDRIVE0) hasn't progressed in the last 60 minutes.
    
Causes possibles

      Replication may not be progressing due to​
      1. Network connectivity issues between the process server and the log/target Azure storage account (or Re-protection server if replicating back to an on-premises site)​
      2. The Azure subscription of the target storage account has been disabled.​
    
Recommandation

      1. Ensure that there is network connectivity between the process server and the log/target Azure storage account (or Re-protection server if replicating back to an on-premises site.)​
      2. If Identity is enabled on the Recovery Services Vault, please make sure the log/target Azure storage account has the necessary permissions to access the storage account.
      a) Go to your Storage account -> Access Control (IAM).
      b) Add the below role-assignments (for ARM based storage account) to the Recovery services vault.
      1) "Contributor" and,
      2) "Storage Blob Data Contributor" for Standard storage or "Storage Blob Data Owner" for Premium storage
      3. Ensure that the "Microsoft Azure Recovery Services Agent", and "InMage Scout Vx Agent - Sentinel/Outpost" services are running on the process server machine. Try restarting these services on the process server.​

      Refer to the article https://aka.ms/asr-v2a-replication-not-progressing , to learn how to troubleshoot replication issues.​
      If the issue persists, contact support.​
    
Liens connexes
https://aka.ms/asr-v2a-replication-not-progressing
Vu la première fois à
25/04/2025 09:48:34