1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

Random VM backup errors

Discussion in 'Backup / Archive Discussion' started by DanGiles, Jun 30, 2017.

  1. DanGiles

    DanGiles ADSM.ORG Senior Member

    Joined:
    Oct 25, 2002
    Messages:
    611
    Likes Received:
    15
    Occupation:
    Sr. Storage Admin
    Location:
    Toronto, Ont. Canada
    I have VM backups running fairly smoothly, but there are a couple of clusters that consistently gives me backup errors. There are usually just a couple failing, but which ones fail are pretty random, so getting a VM trace is nearly impossible.
    The errors are one of the following:
    06/29/2017 20:41:44 ANS9365E VMware vStorage API error for virtual machine 'XXXX'.
    IBM Spectrum Protect function name : VixDiskLib_Cleanup
    IBM Spectrum Protect file : ..\..\common\vm\vmvddksdk.cpp (1817)
    API return code : 26
    API error message : Unable to connect to the host

    06/28/2017 20:54:46 ANS0361I DIAG: miniThreadManagerThread:VmThreadReadTop(): thread queue error: rc=107.
    06/28/2017 20:54:53 ANS4174E Full VM backup of VMware Virtual Machine 'YYYY' failed with RC=-1 mode=Incremental Forever - Incremental, target node name='VEBU_BURLINGTON', data mover node name='VEBU_BURLINGTON_DMM4'

    06/28/2017 20:46:45 ANS9365E VMware vStorage API error for virtual machine 'BUPNVRINav1'.
    IBM Spectrum Protect function name : VixDiskLib_Open
    IBM Spectrum Protect file : ..\..\common\vm\vmvddksdk.cpp (1868)
    API return code : 3014
    API error message : Insufficient permissions in the host operating system

    No errors in vSphere or on the guest machine itself. And no, this has NOTHING to do with permissions!

    Anyone else see behaviour like this?
     
  2.  

Share This Page