OSAM migration tasks fails at Initial Sync. "SDR at full capacity"

Products

• VMware HCX

Issue/Introduction

 

• During OSAM migration, the initial sync does not progress beyond 0%.
• The replication job displays "Selected Datastore" but does not reach the Sentinel Gateway event stage.
• HCX logs may show entries similar to:

/common/logs/admin/app.log

[OsAssistedReplicationService_SvcThread-####, Ent: HybridityAdmin, , TxId: ######-####-####-####-######] INFO  c.v.v.h.s.o.jobs.StartReplicationJob- [transferId:'######-####-####-####-######' sid:'######-####-####-####-######' jobId:'######-####-####-####-######' hostname:'Test####'] Parking Transfer: SDR at full capacity

 

Environment

HCX 4.11

Cause

• This behavior occurs when the Service Data Replicator (SDR) reaches its configuration limit.
• In VMware HCX 4.11 , each Service Mesh SDR supports a maximum of 50 disks.
• Once this limit is reached, additional replication jobs cannot progress.

 

Resolution

To resolve this issue:

1. Create a new Service Mesh within the same environment to distribute OSAM disk replication jobs across multiple SDR instances.

For the affected VMs:

• Uninstall the existing Sentinel Agent.
• Reinstall the Sentinel Agent using the installer from the new Service Mesh.
• This ensures the VM is registered with the new Service Mesh and can utilize its SDR capacity.

Configuration Limit: https://configmax.broadcom.com/guest?vmwareproduct=VMware%20HCX&release=VMware%20HCX%204.11.0&categories=42-0

Additional Information

 

• Ensure future replication planning considers the 50-disk-per-SDR limit to avoid saturation.
• For large-scale migrations, proactively distribute workloads across multiple Service Meshes.