NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 126

Media Manager status code 126
HOWTO104492 | 2014-11-20
How To | CMS-XML

NetBackup status code: 126

NetBackup status code : 126
HOWTO104048 | 2014-11-20
How To | CMS-XML

Unable to restore sybase database,show error information:"Backup Server Internal Error: 4.126.3.1: Unable to get current date and time. Internal error."

Backup Server Internal Error : 4. 126 .3.1: Unable to get current date and time.
TECH209125 | 2013-10-22
Technical Solutions | CMS-XML

STATUS CODE 126: A hot catalog backup fails with status 126 (NB database backup header is too large, too many paths specified) reported.

STATUS CODE 126 : A hot catalog backup fails with status 126 (NB database backup header is too large, too many paths specified) reported.
TECH59998 | 2010-01-03
Technical Solutions | CMS-XML

NetBackup status code 126: NB database backup header is too large, too many paths specified

126
TECH58615 | 2009-01-12
Technical Solutions | CMS-XML

Error message "not authorized to connect to vmd (126)" while trying to run vmglob command.

Question: What does the error not authorized to connect to vmd ( 126 ) mean? Condition: Running: vmglob -set_gdbhost global_device_database_hostname -h volume_database_hostname
TECH53802 | 2008-01-21
Technical Solutions | CMS-XML

Media Manager status code 181

Determine whether authorization fails on vmd Examine the debug log files for Media Manager status code 126 occurrences (not authorized to connect to vmd ).
HOWTO104534 | 2014-11-20
How To | CMS-XML

NetBackup backups are failing with Status 24 due to network issue in the environment

12:11:52.830 PM: [6552.6976] 2 TransporterRemote::write[2](): DBG - | An Exception of type [SocketWriteException] has occured at: | Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.54. 126 .1
TECH217961 | 2014-05-30
Technical Solutions | CMS-XML

GENERAL ERROR: The services called NetBackup Enterprise Media Manager and NetBackup Resource Broker don't error, but won't remain started and the NetBackup Device Manager service generates event log error, "EMM interface initialization failed, status = 334"

14:03:37.687 [3612.540] 16 nbdb_ping: ErrMsg Specified driver could not be loaded due to system error 126 (VERITAS NB Adaptive Server Anywhere 9.0.1)., ErrCode -1, Sqlstate im003
TECH46255 | 2014-04-09
Technical Solutions | CMS-XML

Job fails with status 232 after going active on RHEL media server using NIS/YP

...snip... 07:01:01. 126 [7878] 2 bpbrm main: wrote CONTINUE on comm_sock 07:01:01.126 [7878] 2 bpbrm main: closing data_sock
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

GENERAL ERROR: oprd returned abnormal status (96) - volume pools missing

18:41:41. 126 [6120.720] 16 InitLtidDeviceInfo: Drive HP.ultrium3-scsi.036 is ACTIVE
TECH70502 | 2014-03-27
Technical Solutions | CMS-XML

Microsoft Exchange DAG backup failing with error code "socket write failed(24) "

An Exception of type [SocketWriteException] has occured at: Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.54. 126 .1 $ , Function: TransporterRemote::write[2](), Line: 338
TECH193354 | 2013-11-11
Technical Solutions | CMS-XML

NetBackup for Informix restore is failing with status 227 even though the bplist output shows that the backup of the Informix dbspace exists.

19:55:31.490 [5012.9684] 2 logconnections: BPRD ACCEPT FROM 10.2.113.82.3086 TO 10.2.97.50.13724 19:55:31.661 [5012.9684] 2 process_request: command c_bprestore_6_5_2_2 ( 126 ) received 19:55:32.193 [5012.9684] 2 adjust_clientname: adjusted clientname = nodo6, client_bp_conf_name = exito6
TECH154564 | 2013-10-30
Technical Solutions | CMS-XML

VM Restore fails with "file write failed" status 2820 error

11:42:40.855 [7060.6972] 2 set_job_details: Tfile (293754): LOG 1374457360 32 bpbrm 7060 from client nbexxxxxxxx: FTL - Virtual machine restore: file write failed 11:42:40.855 [7060.6972] 2 send_job_file: job ID 293754, ftype = 3 msg len = 126 , msg = LOG 1374457360 32 bpbrm 7060 from client nbexxxxxxxx: FTL - Virtual machine restore: file write failed VxMS
TECH209445 | 2013-08-26
Technical Solutions | CMS-XML

A Catalog child job backup fails with STATUS 50

Activity monitor shows: 11/07/2011 14:22:09 - begin writing 11/07/2011 14:22:12 - Info bphdb (pid=9545) bpbkar waited 126 times for empty buffer, delayed 126 times
TECH176379 | 2013-04-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?