Highlighted

Error code 4239 -

Hi All,

NB Version 7.6.0.2

Windows Master server.

VM BKP - Client less(Through VC)

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  
9/2/2015 9:51:18 AM - Info nbjm(pid=8708) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=920792, request id:{A7C3F97F-96C7-4F0D-93E3-E42AA8209655})  
9/2/2015 9:51:18 AM - requesting resource usmelnb01-SUG
9/2/2015 9:51:18 AM - requesting resource usmelnb01.NBU_CLIENT.MAXJOBS.flmlbsn01
9/2/2015 9:51:18 AM - requesting resource usmelnb01.NBU_POLICY.MAXJOBS.USMEL_VIRT_OTHERS
9/2/2015 9:51:18 AM - granted resource usmelnb01.NBU_CLIENT.MAXJOBS.flmlbsn01
9/2/2015 9:51:18 AM - granted resource usmelnb01.NBU_POLICY.MAXJOBS.USMEL_VIRT_OTHERS
9/2/2015 9:51:18 AM - granted resource 5695L5
9/2/2015 9:51:18 AM - granted resource HP.ULTRIUM5-SCSI.001
9/2/2015 9:51:18 AM - granted resource usmelnb01-hcart2-robot-tld-0
9/2/2015 9:51:18 AM - estimated 0 Kbytes needed
9/2/2015 9:51:18 AM - begin Parent Job
9/2/2015 9:51:18 AM - begin VMware, Start Notify Script
9/2/2015 9:51:18 AM - started
9/2/2015 9:51:19 AM - Info RUNCMD(pid=44716) started            
9/2/2015 9:51:19 AM - Info bpbrm(pid=39148) flmlbsn01 is the host to backup data from     
9/2/2015 9:51:19 AM - Info bpbrm(pid=39148) reading file list for client        
9/2/2015 9:51:19 AM - Info bpbrm(pid=39148) start bpfis on client         
9/2/2015 9:51:19 AM - Info bpbrm(pid=39148) Starting create snapshot processing         
9/2/2015 9:51:19 AM - Info RUNCMD(pid=44716) exiting with status: 0         
Status 0
9/2/2015 9:51:19 AM - end VMware, Start Notify Script; elapsed time: 0:00:01
9/2/2015 9:51:19 AM - begin VMware, Step By Condition
Status 0
9/2/2015 9:51:19 AM - end VMware, Step By Condition; elapsed time: 0:00:00
9/2/2015 9:51:19 AM - begin VMware, Read File List
Status 0
9/2/2015 9:51:19 AM - end VMware, Read File List; elapsed time: 0:00:00
9/2/2015 9:51:19 AM - begin VMware, Create Snapshot
9/2/2015 9:51:19 AM - started process bpbrm (39148)
9/2/2015 9:51:20 AM - Info bpfis(pid=44660) Backup started           
9/2/2015 9:51:21 AM - snapshot backup of client flmlbsn01 using method VMware_v2
9/2/2015 9:51:38 AM - Critical bpbrm(pid=39148) from client flmlbsn01: FTL - VMware_freeze: Unable to locate VM flmlbsn01 using VM display name
9/2/2015 9:51:38 AM - Critical bpbrm(pid=39148) from client flmlbsn01: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 
9/2/2015 9:51:38 AM - Critical bpbrm(pid=39148) from client flmlbsn01: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 
9/2/2015 9:51:38 AM - Critical bpbrm(pid=39148) from client flmlbsn01: FTL - snapshot processing failed, status 4239   
9/2/2015 9:51:38 AM - Critical bpbrm(pid=39148) from client flmlbsn01: FTL - snapshot creation failed, status 4239   
9/2/2015 9:51:38 AM - Warning bpbrm(pid=39148) from client flmlbsn01: WRN - ALL_LOCAL_DRIVES is not frozen    
9/2/2015 9:51:38 AM - Info bpfis(pid=44660) done. status: 4239          
9/2/2015 9:51:38 AM - end VMware, Create Snapshot; elapsed time: 0:00:19
9/2/2015 9:51:38 AM - Info bpfis(pid=44660) done. status: 4239: Unable to find the virtual machine    
9/2/2015 9:51:38 AM - end writing
Status 4239
9/2/2015 9:51:38 AM - end Parent Job; elapsed time: 0:00:20
9/2/2015 9:51:38 AM - begin VMware, Stop On Error
Status 0
9/2/2015 9:51:38 AM - end VMware, Stop On Error; elapsed time: 0:00:00
9/2/2015 9:51:38 AM - begin VMware, Delete Snapshot
9/2/2015 9:51:38 AM - started process bpbrm (45548)
9/2/2015 9:51:39 AM - Info bpbrm(pid=45548) Starting delete snapshot processing         
9/2/2015 9:51:40 AM - Info bpfis(pid=24616) Backup started           
9/2/2015 9:51:40 AM - Critical bpbrm(pid=45548) from client flmlbsn01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.flmlbsn01_1441201878.1.0      
9/2/2015 9:51:40 AM - Info bpfis(pid=24616) done. status: 4207          
9/2/2015 9:51:40 AM - end VMware, Delete Snapshot; elapsed time: 0:00:02
9/2/2015 9:51:40 AM - Info bpfis(pid=24616) done. status: 4207: Could not fetch snapshot metadata or state files  
9/2/2015 9:51:40 AM - end writing
Status 4207
9/2/2015 9:51:40 AM - end Parent Job; elapsed time: 0:00:22
Status 4239
9/2/2015 9:51:40 AM - end operation
Unable to find the virtual machine(4239)

 

 

 

 

1 Solution

Accepted Solutions
Accepted Solution!

This error means Netbackup is

This error means Netbackup is not able find a VM by that name, and you have confirmed that the VM is not there when you do a browse from netbackup. 

At this point if you have access to the VMWare infrastructure i would say log into vcenter and make sure the VM exists and still has the same name. If another group manages it, talk to them. 

If quiesce option is enabled in the policy you should also make sure that VMWare tools are installed, running and up-to-date on the VM, missing tools can result in this error. 

 

View solution in original post

11 Replies

Please upload following logs

Please upload following logs from VMware backup host

install_path\NetBackup\logs\bpVMutil

install_path\NetBackup\logs\bpfis

I assume that you have already tried to create a new policy and mentioned the VM name manually in the policy. Also once you finish the policy configuration, the validation of the policy completes successfully.

Accepted Solution!

This error means Netbackup is

This error means Netbackup is not able find a VM by that name, and you have confirmed that the VM is not there when you do a browse from netbackup. 

At this point if you have access to the VMWare infrastructure i would say log into vcenter and make sure the VM exists and still has the same name. If another group manages it, talk to them. 

If quiesce option is enabled in the policy you should also make sure that VMWare tools are installed, running and up-to-date on the VM, missing tools can result in this error. 

 

View solution in original post

I see the following in your

I see the following in your post:

Even I am trying to select the machine manually machine is not visible,

Have you checked and verified that the user account used for VM backups have all the necessary permissions?

What is selected in VMware tab for 'Primary VM identifier'?

 

Hi Marianne, Primary VM

Hi Marianne,

Primary VM identifier --> VM display name is selected.

 

 

Hi Areznik, Vm is exist in

Hi Areznik,

Vm is exist in Vcenter and having same name also quiesce option is enabled already and Vmware too also installed as well.

Same issue I am facing on

Same issue I am facing on diff server right now..Host is different...

Is there any error in vSphere

Is there any error in vSphere when netbackup attempts to take a snapshot?

Hi Areznik, there is no error

Hi Areznik,

there is no error in task and event of Vsphere.Actually Netbackup unable to find the VM even I configured the policy by adding the VM manually.

 

Re: Error code 4239 -

any one have any suggestion ? i am faceing the same problem

i have a number of turend off VM and need to backup them

when i Changing the Primary VM identifier from that to "VM display name" an error 4239 appear and massage unable to find Virtual machine and  if i ignore it and run the policy backup did't start snapshot

Re: Error code 4239 -

Same problem here, 4239 appears when vm is offline. VM display name is selected

Re: Error code 4239 -

It seems that the hostname is still used instead of display name after the change.
Recreated new policy with display name and now it works.