NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 189

NetBackup status code : 189
HOWTO104107 | 2014-11-20
How To | CMS-XML

Media Manager status code 189

Media Manager status code 189
HOWTO104540 | 2014-11-20
How To | CMS-XML

NetBackup status code 189: the server is not allowed to write to the client's file systems

189
TECH58654 | 2012-05-14
Technical Solutions | CMS-XML

Phase 2 import failed with status 40

11:49:03.792 [2268.3132] 2 bpbrm kill_child_process_ex: start 11:49:04. 189 [2268.3132] 2 bpbrm wait_for_child: start 11:49:04.189 [2268.3132] 2 bpbrm wait_for_child: child exit_status = 150
TECH209447 | 2014-01-14
Technical Solutions | CMS-XML

GENERAL ERROR: If static Network Address Translation (NAT) is configured on the firewall binding the firewall's external IP with the NetBackup master/media server ports, then the DMZ client must be able to perform reverse name lookups of the firewall's public IP address to the name of the NetBackup master/media server.

22:42:36.171 [1640.2132] 2 vnet_pop_byte: vnet.c.111: Function failed: 9 0x00000009 22:42:36.171 [1640.2132] 2 vnet_pop_string: vnet.c. 189 : Function failed: 9 0x00000009 22:42:36.171 [1640.2132] 2 vnet_pop_signed: vnet.c.234: Function failed: 9 0x00000009
TECH39431 | 2013-10-29
Technical Solutions | CMS-XML

Backup jobs do not get scheduled, existing backups hang on very busy systems when a large number of messages are written to the netbackup/db/error log files.

07:59:05. 189 [8691] 2 vnet_pbxconnect: pbxConnectEx Succeeded When these delays writting to the error log occur, the nbpem log at the default logging levels (DebugLevel=1
TECH199637 | 2013-03-11
Technical Solutions | CMS-XML

BUG REPORT: The bptm write process may attempt to access a non existent shared memory file if job database cleanup runs longer then 5 minutes resulting in a status 12

start: 10:11:01.353 [20603] 2 write_backup: got from bpdup (START BACKUP -jobid 2000392 -c clientA -b clienta_1202256093 -cl POLICY - shm -blksize 1048576 -bt 1202256093 -st 2 -rl 3 -date 1204934493 -ct 4 -cn 2 - use_vnetd -mtd), len = 189 , err = 0 The bpdm
TECH66236 | 2013-03-02
Technical Solutions | CMS-XML

All backups via media servers exited with status 811 (failed to communicate with resource requester)

Then the job will terminate: 09:41:28. 189 [31329] 2 media_signal_poll: 1:Terminate detected (MultiResReq.cpp:2319) 09:41:28.189 [31329] 2 RequestInitialResources: Cancellation requested
TECH163911 | 2012-06-25
Technical Solutions | CMS-XML

Backups to Media Server fail with Status 806 & Status 811 after upgrading to NBU 7.x

21:08:50.188 [8355] 2 vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1371: 0: found in cache service: NULL 21:08:50. 189 [8355] 16 RequestInitialResources: MultiResReq.cpp:2395 resource request failed [150] 21:08:50.189 [8355] 2 RequestInitialResources: Requesting cancellation from jobmgr
TECH167641 | 2012-06-25
Technical Solutions | CMS-XML

ltid and vmd services are not running on all Windows media servers - receive error "Failed to validate this host with the EMM"

06/17/10 11:48:33. 189 [Diagnostic] NB 51216 nbemm 111 PID:1298486 TID:1286 File ID:111 [No context] 1 v-111-1061 [MachineImpl::addMachineAlias] Client signature HOST= MEDIASERVER VER= 650000 APP= vmd PID= 5588
TECH136104 | 2011-08-17
Technical Solutions | CMS-XML

BUG REPORT: Status Code 196 received when new_stream is not listed first in the policy file selection list

directive exists in a policy file selection list, but is not listed in the first line. The requirement that the new_stream be the first item in the listing is detailed on page 185 of the NetBackup 6.5 System Administrator s Guide for Windows, Volume I and page 189 of the NetBackup 6.5 System Administrator s Guide for UNIX and Linux where it states:
TECH69001 | 2009-01-11
Technical Solutions | CMS-XML

Media Error (84) and (41) | Symantec Connect

189 :18:38:54.00x36 0x70 0x67 0x00 0xb4 189:18:38:48.00x36 0x70 0x67 0x00 0xb4 187:08:58:01.00x36 0x70 0x35 0x1f 0x6e
Connect Forums | HTML

STATUS CODE 25: Troubleshooting procedures for client Status 25 errors.

16:49:39. 189 [3336.4360] 16 bpcd main: read failed: The operation completed successfully.
TECH141839 | 2015-02-12
Technical Solutions | CMS-XML

STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 errors.

16:49:39. 189 [3336.4360] 16 bpcd main: read failed: The operation completed successfully.
TECH68832 | 2015-01-12
Technical Solutions | CMS-XML

Status Code Chart

188 189 190
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?