Non protected virtual machines get replicated on LUN which is replicated creating a piggyback virtual machine
search cancel

Non protected virtual machines get replicated on LUN which is replicated creating a piggyback virtual machine

book

Article ID: 324748

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:
  • Non protected virtual machines get replicated on replicated LUN creating a piggyback virtual machine which is an illegal operation as per the license requirements
  • In the vmware-dr-xx log file, located at C:\ProgramData\VMware\VMware vCenter Site Recovery Manger\Logs, you see entries similar to:
<YYYY-MM-DD><time> [03328 error 'StorageProvider'] Failed to fetch 'vim.VirtualMachine.config.ftInfo' property of 'vm-1170'</time>
<YYYY-MM-DD><time></time> [03328 warning 'StorageProvider'] Cannot fetch FT info for VM 'vm-1170': (dr.fault.CannotFetchVcObjectProperty) {
--> dynamicType = <unset>,
--> faultCause = (vmodl.MethodFault) null,
--> object = 'vim.VirtualMachine:vm-1170',
--> path = "config.ftInfo",
--> msg = "",
--> }
<YYYY-MM-DD><time></time> [03328 verbose 'StorageProvider'] Found 1 piggyback VMs on datastore 'datastore-1166:DS_FC_BUS1_C2PMQ_CLU_01' in protection group 'protection-group-114114'


Cause

This issue occurs if the virtual machines are not in the protection group.

Resolution

When planning replication, it is necessary to separate the protected virtual machines and replicated LUNs from the non protected virtual machinesĀ and non replicated LUNs.