[VMC ON AWS ] Virtual machine shows RPO warning due to lwd filter
search cancel

[VMC ON AWS ] Virtual machine shows RPO warning due to lwd filter

book

Article ID: 325147

calendar_today

Updated On:

Products

VMware Cloud on AWS

Issue/Introduction

  • To explain how to identify the issue and provide a workaround
  • Trying to protect a VM in vLSR, which was already protected by vLCR using high-frequency snapshot.
  • Virtual machine shows RPO warning.
  • Hostd.log shows below error

    --------

    <DATE>T<TIME>Z info hostd[2112365] [Originator@6876 sub=Hbrsvc] Replicator: ReconfigListener triggered forconfig VM 20

    <DATE>T<TIME>Z error hostd[2112365] [Originator@6876 sub=Hbrsvc] VM is LWD protected- can't replicate

    <DATE>T<TIME>Z error hostd[2112365] [Originator@6876 sub=Hbrsvc] VM is LWD protected- can't replicate

    <DATE>T<TIME>Z error hostd[2112365] [Originator@6876 sub=Hbrsvc] VM is LWD protected- can't replicate

    <DATE>T<TIME>Z error hostd[2112365] [Originator@6876 sub=Hbrsvc] VM is LWD protected- can't replicate

    <DATE>T<TIME>Z info hostd[2129832] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/<vsandatastore>/examplevm.vmx] Updated active set of monitored objects forVM '20'. total: 9, added: 4, removed: 0

    <DATE>T<TIME>Z info hostd[2129832] [Originator@6876 sub=Vimsvc.TaskManager] Task Completed : haTask-20-vim.VirtualMachine.createSnapshot-100972 Status success

    <DATE>T<TIME>Z info hostd[2112366] [Originator@6876 sub=Hbrsvc] Replicator: powerstate change VM: 20 Old: 1 New: 1

    <DATE>T<TIME>Z info hostd[2112366] [Originator@6876 sub=Hbrsvc] Replicator: PowerOn -> PowerOn transition forVM: (id=20) vm_name

    <DATE>T<TIME>Z info hostd[2112366] [Originator@6876 sub=Hbrsvc] Replicator: Poweron forVM: (id=20) vm_name

    <DATE>T<TIME>Z error hostd[2112366] [Originator@6876 sub=Hbrsvc] VM is LWD protected- can't replicate

    <DATE>T<TIME>Z error hostd[2112366] [Originator@6876 sub=Hbrsvc] Failed to configure replication forVM (id=20): Disk with replication-incompatible type specified (devKey=2000)

    <DATE>T<TIME>Z error hostd[2112366] [Originator@6876 sub=Hbrsvc] Invalid Disk config forVM: 20: 

  • When trying to protect the VM with VMware Live Site recovery you may see error

"Operation Failed Operation Error: Unable to protect VM 'VM Name' with unsupported IO filter 'vmwarelwd' for device with key '2000'."

 

 


Cause

You cannot protect same virtual machine by HBR and VCDR in 1.16 and 1.18. It is unsupported. LWD IO filter is used by VCDR (High-Frequency Snapshots) and also by Dell PowerProtect (transparent snapshots).

Impact/Risks:

Customers will not be able to replicate the affected virtual machine.

You can also verify if the virtual machine has LWD filter by going to vcenter mob

VM-> Config->Hardware->Device->VirtualDisk->independentFilters

 

Resolution

SDDC version 1.20 and above supports protecting same virtual machine by VCDR and HBR with certain limitations: Protect same VM with both VMware Live Cyber Recovery and VMware Live Site Recovery 


Workaround:

Use either HBR or VCDR
Coexistence is not supported before SDDC 1.20/vSphere 8.0.
As such, VCDR protection should be disabled on the VMs in question. If this has been done, and there are multiple instances, then the script referenced in KB90283 (lwd-cleanup-util.py) should be used to remove the vmwarelwd filter from the affected VMs.

Additional Information

Powered by Wolken Software