NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 189

Media Manager status code 189
HOWTO91037 | 2013-10-02
How To | CMS-XML

NetBackup status code: 189

NetBackup status code : 189
HOWTO90604 | 2013-10-02
How To | CMS-XML

Media Manager status code 189

Media Manager status code 189
HOWTO51386 | 2012-11-19
How To | CMS-XML

NetBackup status code: 189

NetBackup status code : 189
HOWTO50952 | 2012-11-19
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

NetBackup status code: 189

NetBackup status code : 189
HOWTO35063 | 2010-10-29
How To | CMS-XML

Media Manager status code: 189

Media Manager status code : 189
HOWTO35496 | 2010-10-29
How To | 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

Tapes are failing with a Status Code 85 (media read error) on Phase 2 of the import process.

08:54:07. 189 [5532.560] 2 read_data: ReadFile returned FALSE, More data is available. (234);bytes = 122880
TECH43569 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: When attempting to inventory a robot with more than one media type, the following error message will occur on the first non-similar tape found: Media type and volume group mismatch (101)

4 vdb_lock: locking volDB 4 vdb_write: writing volDB record for media_id 000304 at offset 189 2 pooldb_num_to_name: PoolNamePtr for 1 is NetBackup
TECH36304 | 2013-10-23
Technical Solutions | CMS-XML

Phase 2 import fails with a media read error, Status Code 85.

08:54:07. 189 [5532.560] 2 read_data: ReadFile returned FALSE, More data is available. (234);bytes = 122880
TECH33762 | 2013-04-25
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
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?