Loading...
Loading...
A Storage vMotion operation was performed on virtual machine (VM) VM-PROD-01, migrating it from datastore VNX-DS-01 to VNX-DS-02. After the migration, a backup was initiated, but it failed with the following messages recorded in the log file: 2026-01-27 05:41:35 avvcbimage Info <42665>: setParent(): sGuestName= sProxyHostName=avmrpxy01 svCentername=vcenter01.lab.com sGuestVmName=vm-prod-01 sVmxPath=[VNX-DS-01] vm-prod-01/vm-prod-01.vmx 2026-01-27 05:41:35 avvcbimage Info <43574>: vcApiVersion 6.5 2026-01-27 05:41:35 avvcbimage Info <43575>: VSphereHTTP::vcVersion65 will be true 2026-01-27 05:41:35 avvcbimage Info <42137>: job type = 4 2026-01-27 05:41:35 avvcbimage Info <18664>: Login( https://vcenter01.lab.com:443/sdk) Datacenter: 'Primary' 2026-01-27 05:41:35 avvcbimage Info <19728>: - connected to 'VirtualCenter' - version: 'VMware vCenter Server 8.0.3 build-24853646', apiVersion:'8.0.3.0' 2026-01-27 05:41:35 avvcbimage Warning <16004>: Soap fault detected, Find VM - NOT ok, Msg:'' 2026-01-27 05:41:35 avvcbimage Error <0000>: [IMG0014] Problem opening vCenter:'Primary', path:'[VNX-DS-01] vm-prod-01/vm-prod-01.vmx'. 2026-01-27 05:41:35 avvcbimage Info <9772>: Starting graceful (staged) termination, Failed to log into web service. (wrap-up stage) 2026-01-27 05:41:35 avvcbimage Warning <40657>: Login failed 2026-01-27 05:41:35 avvcbimage Info <40654>: isExitOK()=208 2026-01-27 05:41:35 avvcbimage Info <17823>: Body- abortrecommended(t) 2026-01-27 05:41:35 avvcbimage Info <40658>: vmparams (vcenter01.lab.com) 2026-01-27 05:41:35 avvcbimage Info <40654>: isExitOK()=208 2026-01-27 05:41:35 avvcbimage Info <42660>: Value of runflags.m_allDisksIncluded is true 2026-01-27 05:41:35 avvcbimage Error <0000>: [IMG0009] Create Snapshot: snapshot creation/pre-script/post-script failed. 2026-01-27 05:41:35 avvcbimage Info <40654>: isExitOK()=208 2026-01-27 05:41:35 avvcbimage Info <40659>: snapshot created:false NOMC:false ChangeBlTrackingAvail:false UsingChBl:true, ExitOK:false, cancelled:false, fatal: true 2026-01-27 05:41:35 avvcbimage Info <18664>: Login( https://vcenter01.lab.com:443/sdk) Datacenter: 'Primary' 2026-01-27 05:41:35 avvcbimage Info <19728>: - connected to 'VirtualCenter' - version: 'VMware vCenter Server 8.0.3 build-24853646', apiVersion:'8.0.3.0' 2026-01-27 05:41:35 avvcbimage Warning <16004>: Soap fault detected, Find VM - NOT ok, Msg:'' 2026-01-27 05:41:35 avvcbimage Error <0000>: [IMG0014] Problem opening vCenter:'Primary', path:'[VNX-DS-01] vm-prod-01/vm-prod-01.vmx'. The log file shows old datastore (VNX-DS-01) instead of the current datastore (VNX-DS-02): 2026-01-27 05:41:35 avvcbimage Info <42665>: setParent(): sGuestName= sProxyHostName=avmrpxy01 svCentername=vcenter01.lab.com sGuestVmName=vm-prod-01 sVmxPath=[ VNX-DS-01 ] vm-prod-01/vm-prod-01.vmx ... 2026-01-27 05:41:35 avvcbimage Warning <16004>: Soap fault detected, Find VM - NOT ok, Msg:'' 2026-01-27 05:41:35 avvcbimage Error <0000>: [IMG0014] Problem opening vCenter:'Primary', path:'[ VNX-DS-01 ] vm-prod-01/vm-prod-01.vmx'. 2026-01-27 05:41:35 avvcbimage Info <9772>: Starting graceful (staged) termination, Failed to log into web service. (wrap-up stage) 2026-01-27 05:41:35 avvcbimage Warning <40657>: Login failed
This is a product limitation. Sometimes vCenter publishes events such as a Storage vMotion before the actual migration job has fully completed. When this happens, the Avamar Management Console Service (MCS) service looks up the VM, captures its current configuration, and updates the VM cache accordingly. As a result, the cached configuration becomes outdated within a few seconds.
Perform the below options for a short-term solution: NOTE: vCenter sync requires no image backup to be running. By default, Avamar runs auto update the 'vm cache' 1 hour before backup window starts. This means that this issue should be fixed automatically during the next day. In Avamar, the user can right click the vCenter domain and choose "sync with vCenter" option to force a cache update with the same limitation that no image backups be running. Use goav to synch with vCenter following article Avamar: GoAV Product Tool for Management and Troubleshooting ./goav vcenter sync
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.