Initial Replication error

Hello Argus Admin User

Thank you for reaching out to the Microsoft Q&A forum.

It looks like your DCC-Fileserver VM’s replication cycle is failing with an AzureStorageException and a 412 ConditionNotMet error during the “WaitingForExportCompletion” phase. That HTTP 412 means a storage‐side ETag or conditional header didn’t match—most often a transient quirk in snapshot export—but repeated failures mean we should dig deeper. Here’s a set of things you can try, plus some follow-up questions if it keeps happening:

What you can try

Review the VM’s replication events

• In the Azure portal go to your Azure Migrate project → Server migration → DCC-Fileserver → Events.

• Look at the full chain of “Replication cycle failed” messages to see if anything else is failing earlier.

Run the built-in replication diagnostics

• Still in Server migration, click “Run diagnostics” (this triggers the GatewayAgentlessVMwareReplicationCycleIssues checks).

• If any insights show up, follow the remediation steps there.

Restart the gateway/appliance services

• RDP into your Azure Migrate appliance VM. • Open services.msc → find “Microsoft Azure Gateway Service” (and “cxpsprocessserver” or “InMage Scout VX Agent Sentinel/Outpost” on the process server if used) → Stop and then Start.

• This clears out any hung VDDK or snapshot process.

Verify network and storage configuration

• Ensure TCP port 443 and 9443 from your process/configuration server to Azure aren’t being blocked by a firewall.

• Confirm that no storage vMotion or disk detach happened recently on the on-prem VM—agentless replication can fail if disks move or snapshots change outside of the Migrate tool.

Disable & re-enable replication (fresh initial sync)

• In the portal go to Recovery Services vault → Replicated items → select DCC-Fileserver → Disable replication.

• After it cleans up, re-enable replication. This kicks off a brand-new initial sync.

Keep your appliance up to date

• Make sure you’re running the latest Azure Migrate appliance bits—each update fixes edge-case snapshot or VDDK issues.

Follow-up questions

• Has this VM ever completed an initial replication successfully, or is this the first cycle?

• Did you see any storage-vMotion, datastore changes, or manual snapshot operations on the VMware host right before the error?

• Are other VMs on the same appliance/project replicating fine, or are they failing with similar errors?

• Which version of the Azure Migrate appliance and VDDK are you running?

• After you run the replication diagnostics, do you get any specific insights flagged?

Reference documentation

• Resolve server migration replication issues in Azure Migrate – https://aka.ms/AzureMigrateReplicationTroubleshoot

• Troubleshoot replication in agentless VMware VM migration – https://aka.ms/AgentlessVMwareReplicationTroubleshoot

• Control bandwidth throttling & common replication-cycle errors – https://aka.ms/AzureMigrateCommonReplicationIssues

Hope this helps track down the root cause—let me know what you find!

The error indicates that the current replication cycle for the VM failed inside the snapshot export/upload phase to Azure Storage and was aborted with an AzureStorageException (HTTP 412 ConditionNotMet). This is treated as a transient storage-side failure during initial or ongoing replication.

To handle it:

1. In the Azure portal, go to Azure Migrate → Servers, databases and web apps.
2. Under Migration and modernization, in the Replications area, select the number next to Azure VM to open the list of replicating machines.
3. Locate VM DCC-Fileserver and check the Replication health column. If it shows Critical or Warning, right‑click the VM and select Health error Details.
4. On the Error Details page, review the error and then select Recent Events. Look for the most recent event of type Replication cycle failed for this VM and confirm whether the same AzureStorageException/ConditionNotMet appears repeatedly.
5. If the error appears only once or intermittently, allow the next replication cycle to run. Transient storage or network issues are expected to self‑heal and the next cycle should succeed.
6. If the error recurs in multiple consecutive cycles (continuous failures), follow the guidance in the events pane to resolve any listed issues, then:
   • If Automatically repair replication was enabled when replication was configured, let Azure Migrate attempt the repair.
   • If automatic repair was not enabled or does not fix the issue, select the VM and choose Repair Replication.
7. If the VM status moves to Repair pending and repair does not complete successfully, stop replication for this VM, reset Changed Block Tracking (CBT) on the VMware VM, and then reconfigure replication for DCC-Fileserver.
8. After errors are resolved and replication is reconfigured or repaired, monitor the next replication cycles from the same Replications view and Recent Events to confirm that cycles complete successfully.
9. If replication cycle failures continue after these steps, open a support case as recommended in the event details.

References:

• Troubleshooting replication issues in agentless VMware VM migration
• Agentless migration architecture