Recovering from the configured recovery point objective (RPO) is lower than what the host can support error.
search cancel

Recovering from the configured recovery point objective (RPO) is lower than what the host can support error.

book

Article ID: 344130

calendar_today

Updated On:

Products

VMware Live Recovery VMware vSphere ESXi

Issue/Introduction



Symptoms:

After vSphere Replication has been removed from an environment, VM's that were formally protected by replication fail vMotion, Powering on and other functions on hosts with an error message of the form "<hostname> is not compatible with the vSphere Replication configuration supported by the virtual machine '<VM Name>': the configured RPO is lower than what the host can support.


Environment

VMware vSphere Replication 5.8.x
VMware vSphere Replication 5.1.x
VMware vSphere Replication 5.5.x
VMware vSphere Replication 5.6.x
VMware vSphere Replication 6.0.x

Cause

vSphere Replication was not correctly removed from the environment, replication was not stopped on the virtual machine, prior to the replication appliance being deleted.

Resolution

To recover an existing virtual machine exhibiting this error:

  1. Shut down the virtual machine.
  2. ssh to the host where the Virtual machine is located (look at the vm summary tab in the general section)
  3. Locate the virtual machine's files in the datastore.
  4. Backup the virtual machine's configuration file (.vmx) If your edits break the virtual machine, you can roll back to the original version of the file.
  5. Edit the virtual machine's configuration file (.vmx) to comment out the following lines; prefixing them with a '#' character.
    Please see Tips for editing a .vmx file (1714) and Editing files on an ESX host using vi or nano (1020302).

    hbr_filter.configGen = ""
    hbr_filter.rpo = ""
    hbr_filter.destination = ""
    hbr_filter.port = "0"
    hbr_filter.gid = ""
    hbr_filter.protocol = ""
    hbr_filter.quiesce = "true"
    hbr_filter.opp = "true"
    hbr_filter.pause = "true"
    scsi0:0.hbr_filter.rdid = ""
    scsi0:0.hbr_filter.persistent = ""

  6. Save the file
  7. Run vim-cmd vmsvc/getallvms | grep -i <VM Name> to find the vmid.
  8. Then Run vim-cmd vmsvc/reload <vmid found above> to reload the virtual machine into inventory.
    See Reloading a vmx file without removing the virtual machine from inventory (1026043) for more details.
  9. Power on the virtual machine


Additional Information


構成された目標復旧時点 (RPO) からのリカバリが、ホストがサポートできるエラーを下回る

Impact/Risks:
corruption of the virtual machine's configuration file (.vmx)