Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
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/vsan:xxxxxxxx9f4a44ae-9bc4c4ac3d69fc99/2da10b61-xxxx-8072-xxxx-xxxxxx49fca8/vm_name.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: You can also verify if the virtual machine has LWD filter by going to vcenter mob VM-> Config->Hardware->Device->VirtualDisk->independentFilters
To explain how to identify the issue and provide a workaround
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).
Customers will not be able to replicate the affected virtual machine.
SDDC version 1.20 and above supports protecting same virtual machine by VCDR and HBR with certain limitations: https://docs.vmware.com/en/Site-Recovery-Manager/8.7/com.vmware.srm.admin.doc/GUID-F653CFF1-398B-44E7-A939-D6A11664DF16.html
Use either HBR or VCDRCoexistence 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 https://kb.vmware.com/s/article/90283 (lwd-cleanup-util.py) should be used to remove the vmwarelwd filter from the affected VMs.
https://docs.vmware.com/en/VMware-Cloud-Disaster-Recovery/services/vmware-cloud-disaster-recovery/GUID-C3D21347-9DA3-469A-9F06-69A9A6632F04.html#:~:text=High%2Dfrequency%20snapshots%20use%20a,confidentiality%20of%20captured%20disk%20blocks.https://docs.vmware.com/en/Site-Recovery-Manager/8.6/com.vmware.srm.admin.doc/GUID-F653CFF1-398B-44E7-A939-D6A11664DF16.htmlhttps://docs.vmware.com/en/Site-Recovery-Manager/8.5/com.vmware.srm.admin.doc/GUID-F653CFF1-398B-44E7-A939-D6A11664DF16.html