This post is more than 5 years old
25 Posts
0
3549
November 11th, 2014 07:00
Networker EBR: The VM could not be located on the datastore
Hello. Our backup group covers around 120 VM's. Around 105 back up with no issue, with great performance. Around 15 or so, which have no noticeable differences fail to back up, they all have the same error. I have tried VMotioning the storage and hosts for the VM's. Here is one VM's output.
Extracted Lines:
2014-11-11T15:14:26.306Z avnwcomm Error: Plugin returned non-zero exit code (10007). Aborting NetWorker connection.
2014-11-11 15:14:20 avvcbimage Warning: [IMG0014] Problem logging into URL 'https://[redacted]:443/sdk' with session cookie.
2014-11-11 15:14:26 avvcbimage Warning: The datastore 'WINDOWS12VM' could not be located on the datacenter
2014-11-11 15:14:26 avvcbimage Warning: The VM 'WINDOWS12VM./' could not be located on the datastore
2014-11-11 15:14:26 avvcbimage Warning: DataStore/File Metadata download failed.
2014-11-11 15:14:26 avvcbimage Warning: [IMG0016] The datastore from VMX '[silver06] WINDOWS12VM/WINDOWS12VM..vmx' could not be fully inspected.
2014-11-11 15:14:26 avvcbimage Error: The file with extension '.vmx' could not be located on the VM
2014-11-11 15:14:26 avvcbimage Warning: Download VM .vmx file failed.
2014-11-11 15:14:26 avvcbimage Error: failed to download vm metadata, try later
2014-11-11 15:14:26 avvcbimage Error: [IMG0009] createSnapshot: snapshot creation or pre/post snapshot script failed
0 events found
jussik1
3 Posts
0
November 14th, 2014 05:00
I had the same issue and not backed up vms had inconsistent names between vm and vdmks.
Fix was to put enable rename flag on on vcenter and storage vmotion failed vms.
kb.vmware.com/kb/2008877
kgthomson
25 Posts
0
November 12th, 2014 03:00
Correct, multiple datastores. Failed VM's are on different ones to each other - but on the same ones as successful VM's.
crazyrov
6 Operator
•
1.3K Posts
0
November 12th, 2014 03:00
Hi,
Are you using multiple data stores to store the VMDK's ? If yes, are the affected VM on a common datastore ?
beornwulf
1 Rookie
•
9 Posts
0
November 17th, 2014 05:00
We had the exact error in our environment as well. We worked with support for a long time trying to figure it out, it ended up being a compatibility issue as we had migrated to 8.2 VBA appliances and were running VCenter 5.1 (only 5.5 vCenter is supported). Once we downgraded back to 8.1 vba's, all vm's that had an error previously starting backing up fine. I believe the "gut" feeling from support was it being due to an api issue..........in other words new code looking for hooks into vcenter that did not exist.
jussik1
3 Posts
0
November 17th, 2014 05:00
We upgraded from 8.1 to 8.2 and problems were with 8.2 and 5.1 vpshere.
Enable rename and vmotion did the trick. So we’re now running NW 8.2 (and it’s version of EBR) and 5.1 vpshere.
There were no problems with 8.1 NW’s version of EBR.
jussik1
3 Posts
0
November 17th, 2014 06:00
Yep. We upgraded from 8.1 to 8.2 and problems were with 8.2 and 5.1 vpshere.
Enable rename and vmotion did the trick. So we’re now running NW 8.2 (and it’s version of EBR) and 5.1 vpshere.
There were no problems with 8.1 NW’s version of EBR.
--
Jussi
beornwulf
1 Rookie
•
9 Posts
0
November 17th, 2014 08:00
We tried the rename of a vm and vmotion but did not work in our environment. Since it is not a supported config, it was decided to just revert back so it was not an issue each time calling for support........
kgthomson
25 Posts
0
November 18th, 2014 00:00
At this point we have removed the EBR appliance and have moved straight to VDP (as it does not require us to purchase a Diskbackup enabler) and is far more stable. I however believe that jussik's reply would have solved our issue. We are running 5.5 just as a reference.