NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

All virtual machine backups failing with Status 4239

NetBackup VMware agent backups that were working suddenly started failing with Status 4239 - Unable to find the virtual machine( 4239 )
TECH226472 | 2014-11-19
Technical Solutions | CMS-XML

NetBackup status code: 4239

NetBackup status code : 4239
HOWTO105298 | 2014-11-20
How To | CMS-XML

4239 error code | Symantec Connect

4239 error code
Connect Forums | HTML

GENERAL ERROR: ltid hangs on media server. Many oprd processes found running on media server.

19:55:04.080 [15163] 2 WaitSocketReady: Processing HOT cmd, Type=100 19:55:04.081 [15163] 4 LtidProcCmd: Pid=4255, Data.Pid=4255, Type=100, param1=0, param2=7, LongParam=300 19:55:04.110 [15163] 4 QueueMsg: Data.Pid= 4239 , Type=101, param1=-65, param2=-3504, LongParam=1
TECH56642 | 2013-08-29
Technical Solutions | CMS-XML

Status Code Chart

4238 4239 4240
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

NetBackup messages

unable to find the virtual machine See NetBackup status code : 4239 unable to get the address of the local listen socket
HOWTO103773 | 2014-11-20
How To | CMS-XML

FTL - vmware_freeze: VIXAPI freeze failed unknown client xxxxxx: sym_vmc_failed_to_get_mor_by_name

Snapshot job fails with: /09/2014 9:16:26 AM - Critical bpbrm(pid=3688) from client xxxxxx: FTL - snapshot processing failed, status 4239
TECH224317 | 2014-09-03
Technical Solutions | CMS-XML

NetBackup is reusing VM selection query results for longer than configured.

After restoring VM, backup of that same VM is failing with status 4239
TECH212564 | 2013-12-17
Technical Solutions | CMS-XML

Unable to find virtual machine | Symantec Connect

Unable to find virtual machine Dear All, Any body facing such issue error code 4239 if yes what is the solution to resolved the issue. Operating Systems:
Connect Forums | HTML

Backing up / restoring VM's - 7.6.0.3 | Symantec Connect

Backing up / restoring VM's - 7.6.0.3 11/17/2014 11:24:34 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - vfm_freeze: method: vmware_v2, type: FIM, function: vmware_v2_freeze 11/17/2014 11:24:34 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - snapshot processing failed, status 4239 11/17/2014 11:24:34 AM - Critical bpbrm(pid=1788) from client OWLOGGING: FTL - snapshot creation failed, status 4239
Connect Forums | HTML

VMware backups - next step after zoning datastore to backup host | Symantec Connect

From the Clients tab I was able to browse into Vmware for a list of clients to select so that is working OK. However - when I run the policy it always ends status 4239 : 11/24/2014 1:44:16 PM - Info nbjm(pid=6660) starting backup job (jobid=133505) for client test101.mycompany.com, policy std_myvm, schedule Full
Connect Forums | HTML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?