NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

in-depth Troubleshooting Guide for Exit Status Code 219 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 5.0 / 5.1

219
TECH39445 | 2005-01-27
Technical Solutions | CMS-XML

Robotic status code 219

Robotic status code 219
HOWTO104724 | 2014-11-20
How To | CMS-XML

NetBackup status code: 219

NetBackup status code : 219
HOWTO104134 | 2014-11-20
How To | CMS-XML

STATUS CODE: 219 A Status 219 is received for a specific media server, even though network connectivity is good and drives are available.

STATUS CODE : 219 A Status 219 is received for a specific media server, even though network connectivity is good and drives are available.
TECH90445 | 2013-10-23
Technical Solutions | CMS-XML

status code 219:Storage unit is not defined in EMM.

status code 219 :Storage unit is not defined in EMM.
TECH163908 | 2011-07-04
Technical Solutions | CMS-XML

BUG REPORT: After attempting to change a Storage Lifecycle Policy destination by selecting "Override policy storage selection" in the Java admin console, a status code 219 is reported.

219
TECH124388 | 2011-05-26
Technical Solutions | CMS-XML

Jobs fail with Status 219 on Linux Media Server

Jobs fail with Status 219 on Linux Media Server
TECH56462 | 2008-01-28
Technical Solutions | CMS-XML

STATUS CODE: 219: Required Storage Unit is unavailable

STATUS CODE : 219 : Required Storage Unit is unavailable
TECH37270 | 2005-01-14
Technical Solutions | CMS-XML

Backup fails with a Status Code 219

The required storage unit is unavailable( 219 )
TECH29468 | 2005-01-09
Technical Solutions | CMS-XML

Status Code 219 - Storage unit is not defined in EMM | Symantec Connect

Status Code 219 - Storage unit is not defined in EMM 5/23/2012 6:10:00 PM - requesting resource puck1.nbu_policy.MAXJOBS.Belinda 5/23/2012 6:10:00 PM - Error nbjm(pid=33196) NBU status: 219, EMM status: Storage unit is not defined in EMM the required storage unit is unavailable( 219 )
Connect Forums | HTML

VMware backups failing with Status 23 and Status 6

09:13:10.439 [9028.8948] 2 onlfi_vfms_logf: INF - lockVM: vixdisklib_prepareforaccess returned:3014 [Insufficient permissions in the host operating system] 09:14:00. 219 [9028.8020] 2 send_keep_alive: INF - sending keep alive 09:14:10.453 [9028.8948] 2 onlfi_vfms_logf: INF - lockVM: Calling vixdisklib_prepareforaccess
TECH227160 | 2014-12-17
Technical Solutions | CMS-XML

How to configure email notification and the different methods to email backup exit statuses from a UNIX master in NetBackup

The Global Attributes for the master server in the GUI can be configured to send email for any non-zero backup status. The exceptions to this are status 96, 219 , or any exit status where the bpbrm
TECH32539 | 2014-07-08
Technical Solutions | CMS-XML

After upgrade to NetBackup 7.x, VMWare clients with multiple IP addresses are failing with status 156

13:58:11.507 [6300.6616] 2 vnet_connect_to_vnetd_extra: ../../libvlibs/vnet_vnetd.c.188: msg: VNETD CONNECT FROM 172.30. 219 .100.1441 TO 172.30.217.195.13724 fd = 1408
TECH130452 | 2011-05-20
Technical Solutions | CMS-XML

GENERAL ERROR: Media servers bounce between "Active for Disk" and "Active for Disk and Tape."

evaluates when the last time a heartbeat was received from a Media Server: Logged in OID 111 (nbemm), with internal OIDs 219 (resource event manager) and 144 (device allocator) all at verbose 6: 4/28/2009 11:52:07
TECH70827 | 2010-01-29
Technical Solutions | CMS-XML

The status code 58 Can’t connect to client | Symantec Connect

The status code 58 Can’t connect to client 01:55:02.145 [24252] <2> bptestbpcd: VERBOSE = 1 01:55:02. 219 [24252] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: vn_request_service_socket: 6 0x00000006 01:55:02.219 [24252] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062: service: bpdbm
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?