NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

NetBackup status code: 5820

NetBackup status code : 5820
HOWTO105395 | 2014-11-20
How To | CMS-XML

Netbackup 7.1 Status Code 156 | Symantec Connect

Netbackup 7.1 Status Code 156 5/31/2012 6:33:57 PM - Info bptm(pid=7348) start backup 5/31/2012 6:34:05 PM - Info bptm(pid=7348) backup child process is pid 11288. 5820 5/31/2012 6:34:05 PM - Info bptm(pid=11288) start
Connect Forums | HTML

Netbackup flashbackup-windows Failed with Error 13 and Error 11 | Symantec Connect

11:52:09.467 [ 5820 .7688] <32> bpfis: FTL - VfMS error 11; see following messages: 11:52:09.467 [5820.7688]
Connect Forums | HTML

Status Code Chart

5819 5820 5821
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

STATUS CODE 156: VM (Virtual Machine) clients are failing to backup with status 156 (snapshot error encountered) reported in the Activity Monitor.

14:01:14.588 [5952.2212] 2 onlfi_vfms_logf: [2008-07-08 14:00:34.726 vcbMounter 5820 error ] Error : Failed to open the disk: Cannot access a SAN/iSCSI LUN backing this virtual disk.
TECH61552 | 2009-01-10
Technical Solutions | CMS-XML

STATUS CODE 150: Backups fail with a NetBackup Status Code 150 (termination requested by administrator), despite no administrator intervention, after a client is moved from an old master server to a new master server.

exits with a status 14. 4:14:26.101 PM: [2608. 5820 ] 4 bpio::read_string: INF - read non-blocking message of length 1 4:14:27.148 PM: [2608.5820] 4 ov_log::OVLoop: Timestamp
TECH50484 | 2009-01-04
Technical Solutions | CMS-XML

error 84 (Status = media write error.) | Symantec Connect

8/25/2009 8:42:24 AM - begin writing 8/25/2009 8:43:59 AM - Error bptm(pid= 5820 ) write error on media id 2773L3, drive index 3, writing header block, 21 8/25/2009 8:44:01 AM - end writing; write time: 00:01:37
Connect Forums | HTML

NetBackup messages

not a valid Logging Assistant temporary directory for clean-up See NetBackup status code : 5820 not all requested files were restored
HOWTO103773 | 2014-11-20
How To | CMS-XML

Cannot connect on socket(25) | Symantec Connect

Cannot connect on socket(25) 2/28/2013 9:48:20 AM - Error bpbrm(pid= 5820 ) bpcd on lon-ishare-01a.group.shlroot.local exited with status 48: client hostname could not be found
Connect Forums | HTML

authentication failed(160) | Symantec Connect

authentication failed(160) 22/02/2010 16:32:56 - begin Catalog Backup, Start Notify Script 22/02/2010 16:32:56 - started process RUNCMD ( 5820 ) 22/02/2010 16:32:56 - ended process 0 (5820)
Connect Forums | HTML

Tape Drive cleaning.. Library or Netbackup | Symantec Connect

14:35:44.285 [6144] <2> drivename_close: Called for file p_media_server_lto4_drive4 14:35:45.220 [ 5820 ] <2> drivename_open: Called with Create 1, file p_media_server_lto4_drive13 14:35:45.220 [5820] <2> drivename_lock: lock failed
Connect Forums | HTML

NetBackup Services | Symantec Connect

12:25:38.085 [5472. 5820 ] <2> logconnections: BPRD ACCEPT FROM 10.1.9.195.49662 TO 10.1.9.195.13724
Connect Forums | HTML

Critical bpbrm(pid=10476) from client M***: FTL - cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.*** | Symantec Connect

11:13:41.455 AM: [5844. 5820 ] <4> ov_log::OVInit: INF - Starting log file: C:\Program Files\Veritas\NetBackup\logs\BPBKAR\040412.LOG
Connect Forums | HTML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?