Replication server name does not report correct name in UI after VM display name has been updated.

Products

• VMware Live Recovery

Issue/Introduction

• We have changed VRMS Appliance Management hostname. Hostname is updated but when configure a new replication is still showing old VRMS Appliance Management hostname under Replication Server.
  
  
• We have changed the VRMS Appliance Management friendly display name in Inventory, and it does not match the Replication Server label in UI.
  
  
• The vSphere Replication appliances has been reregistered in VC and taskbar shows "The object 'vim.VirtualMachine:vm-###' has already been deleted or has not been completely created"
  
  
• In Replication Server label in showing as ''127.0.0.1" in the  Incoming tab of the vSphere Replication UI.
  
       

    

  

Environment

vSphere Replication 8.x, 9.x

Cause

• When a VR VM hostname is changed, it does not affect or propagate to the VR server name in the VR Db.
  
  
• If the VR VM 'friendly' display name is changed while VRs are in a disconnected state , it may not always propagate the change to the relevant VR Db tables.
  
  
• If a VR VM is reregistered ,it will change the VC moRef, and NOT propagate to the VR Db.
  
  
  There are VR 2 tables that hold VR server naming info.
    - hbrserverentity  .. ..... for LOCAL VR naming  
   -  hbrserverinfoentity ...for REMOTE VR naming   
  
  

Resolution

• Snapshot the vSphere Replication, as a formality, prior to attempting database edits.
  
  
• Extract the present info. from the 2 VR Db tables
  
  •  # select vmmoid, vsrv_address,  hbrservername, replicationtrafficaddress from hbrserverentity;
  •  # select uuid,configurationurl,name,sitename from hbrserverinfoentity
    
    
• Collect the correct VR info.  moRef and sitename, FQDN etc
  
  
  
• Edit the VR DB hbrserverentity table with new vmmoid  and hbrservername 
  
  /opt/vmware/hms/bin/embedded_db_connect.sh
  # select vmmoid, hbrservername, vsrv_address from hbrserverentity;
  # update hbrserverentity set vmmoid = 'vm-xxxxx' where vsrv_address='127.0.0.1';
  # update hbrserverentity set hbrservername = 'newName' where vsrv_address='127.0.0.1';
  # select vmmoid, hbrservername, vsrv_address from hbrserverentity;
  # systemctl restart hms.service 
  
  
• Edit the VR Dd hbrserverinfoentity table  with new name, sitename and configurationurl 
  

  /opt/vmware/hms/bin/embedded_db_connect.sh
  \x

  # select uuid,configurationurl,name,sitename from hbrserverinfoentity;
  # update hbrserverinfoentity set configurationurl='xxxxxxxxxxxxxx';
  # update hbrserverinfoentity set name='newVRName';
  # update hbrserverinfoentity set sitename ='yyyyyyyyyy';
  # select uuid,configurationurl,name,sitename from hbrserverinfoentity;

  
  Repeat on opposite VR paired appliance.

Additional Information

Error : "The object has already been deleted or has not been completely created" observed on reconnecting VR server