Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Configuring a replication for a VM fails stating an active replication is already enabled in Cloud Director Availability (67396)

Last Updated: 5/16/2023Categories: TroubleshootingTotal Views: 8857Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

When you configure a replication for a VM that was previously replicated with Cloud Director Availability, the action fails with the error:

The operation could not be completed, because the virtual machine has an active replication enabled.

In /opt/vmware/h4/cloud/log/cloud.log on the target Cloud Director Replication Management Appliance, you see a similar message:

2019-02-22 10:41:23.219 ERROR - [UI_/portal/outgoing-replications/SPB_RepMgr/vm_20076990-0142-44b1-b1f6-5e4f72c6b263_q6_bi] [c4-scheduler-2] com.vmware.h4.jobengine.JobExecution : Task 8de22f51-b550-46e3-bf7a-64bb25004566 (WorkflowInfo{type='start', resourceType='vmReplication', resourceId='C4-c80537bd-da3d-4192-9e41-f9a2d19227c9', isPrivate=false, resourceName='null'}) has failed

com.vmware.h4.replicator.api.exceptions.ReplicationAlreadyEnabledException: The operation could not be completed, because the virtual machine has an active replication enabled.

In /opt/vmware/h4/manager/log/manager.log on the target Cloud Director Replication Management Appliance, you see a similar message:

2019-02-22 10:41:23.200 ERROR - [UI_/portal/outgoing-replications/SPB_RepMgr/vm_20076990-0142-44b1-b1f6-5e4f72c6b263_q6_bi_al] [health-check-5] com.vmware.h4.jobengine.JobExecution : Task 92dff365-de26-40bd-9f2a-08fa67eddb17 (WorkflowInfo{type='start', resourceType='replication', resourceId='H4-829379bc-6db9-44ee-85d8-310fc1353103', isPrivate=false, resourceName='null'}) has failed

com.vmware.h4.replicator.api.exceptions.ReplicationAlreadyEnabledException: The operation could not be completed, because the virtual machine has an active replication enabled.

In /opt/vmware/h4/replicator/log/replicator.log on the source Replicator Appliance, you see a similar message:

2019-02-22 10:41:23.132 ERROR - [UI_/portal/outgoing-replications/SPB_RepMgr/vm_20076990-0142-44b1-b1f6-5e4f72c6b263_q6_bi_al_Zf] [pc-task-monitor-4] c.v.h.r.monitoring.JobTaskUpdateHandler : Task 918a8f3f-3624-45a7-bbde-e4e6347f3be7 has failed.

com.vmware.vim.binding.vim.fault.ReplicationVmConfigFault: The vSphere Replication configuration of the virtual machine has an issue: Replication is already enabled.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs because the replication filter was not disabled on the ESXi host the source VM resides on when the replication was deleted in Cloud Director Availability.

Resolution

To resolve this issue, you need to disable the replication filter on the source ESXi host before you can configure the replication again in Cloud Director Availability.

To disable the replication on an ESXi host, perform the following steps:

SSH to the ESXi host the source VM resides on.

Determine the VM ID of the source VM by running the command:

vim-cmd vmsvc/getallvms | grep vm_name

Validate that a replication is still enabled for the VM with the command:

vim-cmd hbrsvc/vmreplica.getConfig vm_id

Confirming that the replication is still active, you can disable with:

vim-cmd hbrsvc/vmreplica.disable vm_id

Run the getConfig command again to confirm the replication is now disabled.

Navigate back to the Cloud Director Availability Portal and configure the replication anew.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware vCloud Availability for Cloud-to-Cloud DR 1.x

VMware vCloud Availability 3.0.x

VMware Cloud Director Availability 4.x

Take Our Survey

Support Assistant