搜尋結果
I am facing the issue Unable to find the virtual machine(4239), Even I am trying to select the machine manually machine is not visible, But machine is in VC only. Please find the logs. 9/2/2015 9:51:18 AM - Info nbjm(pid=8708) starting backup job (jobid=920792) for client flmlbsn01, policy USMEL_VIRT_OTHERS, schedule Daily_Incr
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.
would like to see an answer to this , as we are seeing similar issues with snapshot files as well. my guess is NBU tries to remove it, but there's a lock within vCenter that prevents it, since it sees it still as an 'active' snapshot and therefore, cannot be removed.
10/28/2014 18:02:37 - Critical bpbrm (pid=11092) from client dalcdctest: FTL - snapshot processing failed, status 4239 10/28/2014 18:02:37 - Critical bpbrm (pid=11092) from client dalcdctest: FTL - snapshot creation failed, status 4239
If the policy uses VM host name or VM DNS name as the Primary VM identifier, NetBackup may not find the virtual machine. The backup fails. If the policy uses VM display name or VM UUID as the Primary VM identifier, NetBackup can identify the virtual machine. The backup succeeds. The problem with tagging onto another post is that we don't get to ...
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 ...
2014年8月8日 · I am also facing Status Code 4239 in my environment and it seems to me Status code 4239 is intermittent issue. If you can check telnet from VMware Backup Host(Media Server) to the VCenter server at port 443 TCP/IP port is working or not ?
After the migration I get the error: Unable to find the virtual machine (4239), in the details staus is the following: 21/08/2014 21:28:51 - Info bpfis (pid=2448) done. status: 4207: Could not fetch snapshot metadata or state files. I have migrated 2 VM's and both are having the same issue. I have added the new VC server to the config in ...
The two errors are unrelated and need troubleshooting separately. Status 2009 (all drives are down) means that you have a hardware problem - tape library, tape drives or bad media. Status 4239 (unable to find the virtual machine) has to do with a problem with VMware backup configuration. Let us go back to your opening line:
Hi Folks, Why am i receiving that message every time i add a VM to my policy ? I dont support vmware, is there a problem with the vmware tools ? they are installed, a snapshot can be created from vmware console.... Do you have an idea ? Policy: VMWARE_DISQUE_SAN -- client: XX-XXXX-XXXXXX (virtual machine proxy: YY-YYYY-YYYYY.YY-YYYY.YYYYY ...
