[VMC on AWS] HCX-Unable to stop DR protection
search cancel

[VMC on AWS] HCX-Unable to stop DR protection

book

Article ID: 328974

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

To remove DR protection from a VM which is stuck and not actionable.

Symptoms:
HCX DR task is stuck at 60% :-

Environment

VMware HCX

Resolution

Procedure 1. Restart App Engine Service
The first step, if possible, is to restart the application engine service on the HCX Manager on both source and target sides and then retry removing DR protections from the UI. Do this when no active migrations or network extensions are happening, scheduled migrations that are waiting for cutover will not be affected. For more details on restarting services go to HCX User guide
1. SSH or console into the HCX Manager as admin and switch user to root.
2. Issue the command to restart the service: 
                hcx-manager# systemctl restart app-engine
3. Issue the command to view the status of the service: 
                hcx-manager# systemctl status app-engine
4. Once the app-engine service is back, try removing the DR protections. If this does not help, move on to the next step.
 
Procedure 2. Verify Replication Status on the ESXi hosts:
1. Connect to the console of the ESXi host which is hosting the virtual machine you want to modify is running. 
2. Run this command to get the virtual machine (VM) ID:
                # vim-cmd vmsvc/getallvms
3. Run this command on the same host to get the replication state of that virtual machine. Run this command a few times to see if replication is still happening, every time you run it if the replication is ongoing you will see the transferred MBs increment. 
# vim-cmd hbrsvc/vmreplica.getState <VM_ID>
4. Run this command to disable replication services for that virtual machine if necessary:
# vim-cmd hbrsvc/vmreplica.disable <VM_ID>
    Where <VM_ID> is the virtual machine ID noted in Step 2.
5. Try removing the DR protections from the HCX UI. If this does not help, move on to the next step.
 

 If the above 2 procedures do not resolve your issue, please gather and provide the below information when opening a ticket with Broadcom

1- <VM name>

2- VMware HCX Version

3- Obtain the replicationID from the UI