NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 65

Media Manager status code 65
HOWTO104446 | 2014-11-20
How To | CMS-XML

Device management status code 65

Device management status code 65
HOWTO104688 | 2014-11-20
How To | CMS-XML

Device configuration status code 65

Device configuration status code 65
HOWTO104601 | 2014-11-20
How To | CMS-XML

NetBackup status code: 65

NetBackup status code : 65
HOWTO103993 | 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

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

03:30:31.891 [Debug] 51216 137 PID:25000 TID:3 File ID:117 [No context] 3 [parseData] not enough data to parse: dataAvail = (37)64 6f 5f 79 70 63 61 6c 6c 3a 20 63 6c 6e 74 5f 63 61 6c 6c 3a 20 52 50 43 3a 20 54 69 6d 65 64 20 6f 75 74 a ...snip...
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

Netbackup Administration Console crashes with Application error 1000 and 1004

0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 4e 42 43 ure NBC 0018: 6f 6e 73 6f 6c 65 2e 45 onsole.E
TECH144245 | 2013-11-15
Technical Solutions | CMS-XML

Device Monitor or vmoprcmd output shows that the drive is in PEND status.

Caution: You can use this command after a PEND status has been displayed in Device Monitor in the NetBackup Administration Console, but do not issue this command during backups. See Drive Status List of the Device Monitor on page 65 of the NetBackup 4.5 Shared Storage Option System Administrator s Guide for UNIX and Windows .
TECH23205 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: ltid hangs on media server. Many oprd processes found running on media server.

19:55:04.080 [15163] 2 WaitSocketReady: Processing HOT cmd, Type=100 19:55:04.081 [15163] 4 LtidProcCmd: Pid=4255, Data.Pid=4255, Type=100, param1=0, param2=7, LongParam=300 19:55:04.110 [15163] 4 QueueMsg: Data.Pid=4239, Type=101, param1=- 65 , param2=-3504, LongParam=1
TECH56642 | 2013-08-29
Technical Solutions | CMS-XML

SQL database backup failing with Flush or Write failure on backup device, Operating system error 995 (failed to retrieve text for this error. Reason: 15105)

0018: 00 00 09 00 00 00 64 00 ......d. 0020: 65 00 6c 00 74 00 65 00 a.t.a.b. 0028: 6b 00 74 00 65 00 00 00 a.s.e...
TECH207801 | 2013-07-02
Technical Solutions | CMS-XML

A backup attempting to use fiber transport may fail with a status 83: could not open FT Server pipe: pipe open failed.

05/28/13 14:23:53.022 [DMABuffLock] SGRVpool max pages initialized too small, mapvectlen (66) = maxvectlen ( 65 )
TECH206660 | 2013-05-28
Technical Solutions | CMS-XML

NetBackup status code 811: failed to communicate with resource requester

2. Verify Private Branch Exchange (PBX) configuration and permissions. For information on PBX, see “Resolving PBX problems” on page 65 of the troubleshooting guide.
TECH59210 | 2013-03-26
Technical Solutions | CMS-XML

Backups of Symantec Enterprise Vault (EV) using NetBackup through Fibre Transport fails with status code 10: "allocation failed"

Page 65 , SAN Media Server/SAN Client/FT Media Server- Symantec NetBackup ™ Enterprise Server and Server 7.x OS Software Compatibility List http://www.symantec.com/docs/TECH76648
TECH174925 | 2012-08-20
Technical Solutions | CMS-XML

Oracle RMAN backup fails with status 6 due to socket reset during data transfer

... The client host appears to retransmit the frame. 65 0.00000 3.3.3.3 - 2.2.2.2 TCP D=34753 S=1556 Ack=3262278469 Seq=971234913 Len=1460 Win=65535
TECH163595 | 2011-06-29
Technical Solutions | CMS-XML

BUG REPORT: The vault hot catalog backup fails, reporting status code 42 (network read failed), when using a remote media server.

The error log will show status code 42: 1221555908 1 4 4 media 65 62 0 master nbjm started backup job for client master , policy vaultcatalogbackup, schedule vaultcatalog_full on storage unit media -dlt2-robot-tld-0 1221555947 1 68 4 media 65 62 0 master nbpem CLIENT master POLICY vaultcatalogbackup SCHED vaultcatalog_full EXIT STATUS 42 (network read failed)
TECH63565 | 2009-01-30
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?