NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 234

Robotic status code 234
HOWTO91234 | 2013-10-02
How To | CMS-XML

NetBackup status code: 234

NetBackup status code : 234
HOWTO90646 | 2013-10-02
How To | CMS-XML

NetBackup status code: 234

NetBackup status code : 234
HOWTO50994 | 2012-11-19
How To | CMS-XML

Robotic status code 234

Robotic status code 234
HOWTO51584 | 2012-11-19
How To | CMS-XML

NetBackup status code: 234

NetBackup status code : 234
HOWTO35105 | 2010-10-29
How To | CMS-XML

Robotic status code: 234

Robotic status code : 234
HOWTO35694 | 2010-10-29
How To | CMS-XML

Duplications using Quantum DXi NDMP DirectCopy may intermittently fail with a status 85

13:07:47.074 [11544] 2 read_data: sent at least one KeepAlive to bpduplicate per fragment 13:07:47.092 [11544] 32 read_backup: Amount of data read (17908352) does not match the fragment kbytes (11779840) for backup id ab_master_1350946816, copy 1, fragment 16 13:08:17. 234 [11544] 2 bptm: EXITING with status 85 ----------
TECH200976 | 2014-01-17
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_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 22:42:36.171 [1640.2132] 2 vnet_pop_status: vnet.c.324: 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

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

user-directed backup, restore, and image list operations fail with status 133 if the client database exits.

12:01:10.752 [25116] 2 logconnections: BPRD ACCEPT FROM 10.82.105. 234 .38361 TO 10.82.105.15.13724
TECH67669 | 2013-03-21
Technical Solutions | CMS-XML

Catalog backup job failed with status code 2 in NetBackup 7.1 on Windows 2003 x86 Chinese version platform

13:52:50. 234 [3940.2128] 16 executeSql: Error executing UPDATE dbm_main.dbm_imagechangelog SET CreatedDateTime = current utc timestamp WHERE (MasterServerKey = 1000002) AND (BackupID = masterserver_1326261143 ) AND (ClientType = 35) AND (OperationID = 1) (rc=100) ErrMsg , ErrCode 0, SqlState
TECH178673 | 2012-07-28
Technical Solutions | CMS-XML

GENERAL ERROR: Getting Status 191, 800, 150, 50 while trying to duplicate images

06:23:34.218 [1476.8080] 2 check_serial_num: serial number match for drive with SCSI coordinates {3,0,4,0}, dos_path \\.\tape0, drive serial number hu10729mgg, expected serial number hu10729mgg 06:23:34. 234 [1476.8080] 2 init_tape: \\.\tape0 (SCSI coordinates {3,0,4,0}) configured with blocksize 0
TECH146711 | 2011-03-28
Technical Solutions | CMS-XML

Unable to login to NetBackup Java console (jnbSA) or BAR GUI (jbpSA) local or remote. Status code 505. Cannot connect to the nb-java authentication service on <master_server> on the configured port - 13722. Exception:java.lang.Null.Pointer.Exception Exception message: null

root 234 1 0 Dec 10 ? 0:01 /usr/sbin/inetd -s
TECH66075 | 2010-01-24
Technical Solutions | CMS-XML

BUG REPORT: False status 0 on jobs

use_ofb -use_otm -wofb_enabled 1 -nbu -secure 1 -kl 3 -rg root -fso -ckpt_time 1800 -connect_options 16974338 22:50:09. 234 [22368] 32 bpbrm handle_backup: from client client_b: FTL - tar file write error (40) 22:50:10.400 [22368] 2 bpbrm handle_backup: client client_b EXIT STATUS = 14: file write failed
TECH61447 | 2010-01-23
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?