Forum Discussion

prototype_1's avatar
6 years ago

Operation Status: 4239 Unable to find the virtual machine

 asdasdasdasd

  • prototype_1's avatar
    prototype_1
    6 years ago

    Hi ALL

    Solution provided by Tech. Engineer;

     

    1) Power Off the VM

    2) Remove the Virtual Machine from the VMware vCenter Inventory. (We are NOT deleting it, just removing it from the inventory)

    3) Add it back to the Inventory

    4) Remove the VM from the Policy Selection

    5) Add it back again and then retry backup.

  • prototype_1 

    How is client name selected in the policy? Manually or through VIP? 

    We see the following in Job Details:
    vCenter server vcenter.ahs.local, ESX host 10.70.0.70, BIOS UUID 4212fbc4-0b72-6bc0-6654-1abf1cf4f207, Instance UUID 502e0fc8-2d42-8bcf-2992-9646d7a93f3d, Display Name IIS24, Hostname INSURA24.ahs.local

    Have you verified that this VM with details as per above info is indeed visible on that particular ESX server?

    https://www.veritas.com/support/en_US/doc/44037985-127664609-0/v82342413-127664609

    NetBackup status code: 4239

    Message: Unable to find the virtual machine

    Explanation: Possible causes of this error:

    • The virtual machine name is not entered correctly (for example, the name is misspelled).

    • The virtual machine identifier type is not selected correctly for the policy. For example, the virtual machine display name is entered, but the virtual machine identifier for the policy indicates virtual machine host name.

    • The virtual machine is renamed, deleted, or moved.

    Recommended Action: Verify the following:

    • The virtual machine identifier configured for the policy and the name (display name, host name, UUID) entered for the virtual machine on the policy agree.

    • You can view the virtual machine in the VMware user interface.

     

    • Krutons's avatar
      Krutons
      Moderator

      If the VM's were deleted, maybe review how often your VMware policies query vCenter.

      • prototype_1's avatar
        prototype_1
        Level 3

        Hi we applied all these steps, but we didnt get success

        I opened a case to veritas support.

    • These replies have been moved.