NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 76

Media Manager status code 76
HOWTO104456 | 2014-11-20
How To | CMS-XML

Device management status code 76

Device management status code 76
HOWTO104697 | 2014-11-20
How To | CMS-XML

Device configuration status code 76

Device configuration status code 76
HOWTO104612 | 2014-11-20
How To | CMS-XML

NetBackup status code: 76

NetBackup status code : 76
HOWTO104004 | 2014-11-20
How To | CMS-XML

DOCUMENTATION: How to troubleshoot and correct problems with media servers when the status changes in the Media Servers area of the NetBackup Administration GUI.

47 49 4f 50 01 00 00 01 00 00 02 04 00 00 00 00 GIOP............ 00 00 00 01 00 00 00 03 00 00 00 1b 49 44 4c 3a ............IDL: 56 65 72 69 74 61 73 2f 45 4d 4d 2f 53 65 72 76 Veritas/EMM/Serv
TECH69625 | 2009-01-15
Technical Solutions | CMS-XML

Upgrade to 7.6.0.1 failing with: SQL Anywhere Error -195: Column 'displayOrder' in table 'report_tablecolumn' cannot be NULL

End of applying SQL queries in file : 76 /data_changes/DataChanges.xml Exit Code is : 1
TECH216541 | 2014-07-15
Technical Solutions | CMS-XML

rman-10038 error when attempting to backup Oracle version 11.2 using NetBackup 6.x.

strcpy()+16 signal __restore_rt() 3720393931393233 ? put_string()+ 76 call strcpy() 3720393931393233 ?
TECH77071 | 2014-03-14
Technical Solutions | CMS-XML

Netbackup Administration Console crashes with Application error 1000 and 1004

0028: 30 31 30 2e 37 30 37 20 010.707 0030: 69 6e 20 6d 73 76 63 72 in msvcr 0038: 38 30 2e 64 6c 6c 20 38 80.dll 8
TECH144245 | 2013-11-15
Technical Solutions | CMS-XML

GENERAL ERROR: When using Veritas NetBackup (tm) what does the "unable to lock media at offset ##" message mean?

log file, messages similar to the following appear, db_lock_media: unable to lock media at offset 76 (560010) . Are these messages important and can they be the cause of backup failures?
TECH7640 | 2013-10-24
Technical Solutions | CMS-XML

System state backup fails with status 156 snapshot error encountered and application log reports VDS faulting errors.

12:26:55.480 PM: [5724.5316] 16 dtcp_write: TCP - failure: attempted to send 76 bytes
TECH180005 | 2012-03-27
Technical Solutions | CMS-XML

NetBackup 7 Media Server installation hangs and the error "Could not set globalDB hostname" is displayed

Could not set globalDB hostname to master-server-name : cannot get host name ( 76 ) Set Enterprise Media Manager server failed.
TECH157235 | 2011-08-19
Technical Solutions | CMS-XML

BUG REPORT: After upgrading to 6.5.4, backup fails with status 130 if an ACL is present.

\x00\x04\x00\x07\x00\xb06\x00\x00\x10\x00\x07\x00\x00\x00\x00\x00 \x00\x00\x00 \x00\x00\x00 , 132) = 76 ...snip...
TECH136352 | 2010-11-12
Technical Solutions | CMS-XML

Catalog Recovery on a Clustered Master Server partially completes with a Status 5

23:48:29 (76.001) INF - TAR EXITING WITH STATUS = 0 23:48:29 ( 76 .001) INF - TAR RESTORED 28805 OF 28806
TECH66145 | 2010-01-24
Technical Solutions | CMS-XML

Catalog searches in the console fail with error message: INF - unexpected return value from db_imagereceive: file read failed 13

16:14:01.468 [5044.3820] 2 list_client_images: backups matching criteria = 7 16:14:01.468 [5044.3820] 2 process_request: request complete: exit status 13 file read failed; query type: 76 Note:
TECH77510 | 2010-01-23
Technical Solutions | CMS-XML

Backup job on Novell client failing - Status 41 | Symantec Connect

Backup job on Novell client failing - Status 41 It's not a tape issue, as different tapes are being used each night. The backup fails at almost exactly the same time each night (1:10 am). The job has backed up almost the same exact amount of data each time at failure point ( 76 .6 GB).
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?