Close

VMware Cloud Director Availability sync stuck at 0%

In this article, I am going to guide you how to fix outgoing replication stuck at 0% in VMware Cloud Director Availability.

Symptoms

Replication sync status stuck at 0%

Errors in log file /opt/vmware/h4/replicator/log/replicator.log

82a5bc4fd3a
2024-07-16 07:29:05.763 ERROR - [UI-71721a1a-bd09-4afe-be66-a3e2438cd305-r432-lc-Nj-tq] [job-62] com.vmware.h4.jobengine.JobExecution : Task 04289ba5-f8c9-4354-af7c-3f6b0e60cb3f (WorkflowInfo{
type='destroySource', resourceType='replication', resourceId='H4-ad91f083-b5dc-4d3a-a263-d82a5bc4fd3a', isPrivate=false, resourceName='null'}) has failed

com.vmware.h4.manager.api.exceptions.ReplicationNotFoundException: Replication with id 'H4-ad91f083-b5dc-4d3a-a263-d82a5bc4fd3a' was not found.
at com.vmware.h4.replicator.repo.SourceReplicationRepo.lambda$getSourceReplicationEntity$2(SourceReplicationRepo.java:117)
at java.base/java.util.Optional.orElseThrow(Optional.java:403)
at com.vmware.h4.replicator.repo.SourceReplicationRepo.getSourceReplicationEntity(SourceReplicationRepo.java:116)
at com.vmware.h4.replicator.repo.SourceReplicationRepo.getReplicatedVm(SourceReplicationRepo.java:109)
at com.vmware.h4.replicator.repo.SourceReplicationRepo$$FastClassBySpringCGLIB$$d5dc8cc1.invoke(<generated>)
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:792)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:762)
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:388)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:762)
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:707)
at com.vmware.h4.replicator.repo.SourceReplicationRepo$$EnhancerBySpringCGLIB$$3b509bdf.getReplicatedVm(<generated>)
at com.vmware.h4.replicator.replication.DestroySourceJob.execute(DestroySourceJob.java:80)
at com.vmware.h4.replicator.replication.DestroySourceJob.execute(DestroySourceJob.java:46)
at com.vmware.h4.jobengine.JobEngine.execute(JobEngine.java:238)
at com.vmware.h4.jobengine.JobEngine.lambda$resumeQueuedJob$1(JobEngine.java:174)
at com.vmware.h4.jobengine.ThrottledExecutorService$1.run(ThrottledExecutorService.java:132)
at com.vmware.h4.common.mdc.MDCRunnableWrapper.run(MDCRunnableWrapper.java:32)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)

Cause

This issue occurs replication of VMS which does have vtpm device or encrypted core files.


Solution

we need to install hbr-agent.vib on source and destination ESXi host to replicate data.

log in to the ESXi host and run the following command


esxcli software vib install -v "https://Replicator-applaince.FQDN/hbr-agent.vib"

Once VIB is installed sync with start automatically after a few minutes.

I hope this article has been informative. thank you for reading.