Forum Discussion

smrutirekhadash's avatar
smrutirekhadash
Level 0
5 years ago

Re: Operation Status: 4239 Unable to find the virtual machine

Hi , I m facing the same issue as https://vox.veritas.com/t5/NetBackup/Operation-Status-4239-Unable-to-find-the-virtual-machine/m-p/877041 with Vms, 

Below are the steps followed as per your suggestion, but the backup failing.

rebooted the VC, re-added the Vm to Vc inventory.

Checked the UUID instance and DNS name it is same in Netbackup and Vcenter.

03/19/2020 03:07:36 - Critical bpbrm (pid=11920) from client US9-sv00120: FTL - VMware_freeze: Unable to locate virtual machine sec9-sv00120
03/19/2020 03:07:37 - Critical bpbrm (pid=11920) from client US9-sv00120: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
03/19/2020 03:07:37 - Critical bpbrm (pid=11920) from client US9-sv00120: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
03/19/2020 03:07:37 - Critical bpbrm (pid=11920) from client US9-sv00120: FTL - snapshot processing failed, status 4239
03/19/2020 03:07:37 - Critical bpbrm (pid=11920) from client US9-sv00120: FTL - snapshot creation failed, status 4239

 

 

 

  • iVaibhav's avatar
    iVaibhav
    Level 4
    5 years ago

    Is there another VM by same name /different name but cloned . 

    It also happens when someone from Server Team performs maintainance on server and clones the machine manually . In this case, there are machines may be with different name but 2 UUIDs on Vcenter  which causes backup code 4239. 

    Check with Server Team for any known maintainance history on this server.

  • EthanH's avatar
    EthanH
    Level 4
    5 years ago

    Is this a VMWare Intelligent Policy, or are these VMs manually added to backups? Is this for all VMs in the policy, or just one? If it's for all VMs, the issue most likely lies within the vCenter/ESX host.

    What is the primary identifier used in the policy? I would either try changing to to "Hostname" (if it's using Display name, or vice versa if it's using Hostname) and see what that returns. 

    If you're using VIP, try creating a test policy and manually adding the problematic VM. From the policy, go to the Clients tab, then click the folder icon to browse the vCenter for the client. Make sure that the Display name, Hostname, and DNS name are all accurate, and do not contain any unexpected characters (spaces, periods, symbols, etc).

    Check connectivity from the backup host (the media server used to query the vCenter) to the vCenter and/or ESX host(s) that are giving you issues. Use traceroute (or tracert on Windows), nslookup, and ping are all successful.

  • Bessam's avatar
    Bessam
    Level 4
    5 years ago

    Hello,

    you can refer to technote:

    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

  • Sandeep_Backup6's avatar
    Sandeep_Backup6
    Level 0
    3 years ago

    Hi smrutirekhadash,

    Please check with the Virtual machine servers in under Credentials section , or update/reset the virtual macine credentials. As in it 90 days password expiration policy works.

    Hope the issue has been resolved.