NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 80

Message: cannot update database due to existing errors vmphyinv
HOWTO90956 | 2013-10-02
How To | CMS-XML

Device management status code 80

Message: Job Manager returned error : see activity monitor Explanation:
HOWTO91198 | 2013-10-02
How To | CMS-XML

NetBackup status code: 80

, and on Windows systems, the NetBackup Device Manager service, is used only if devices are attached to the system. Click here to view technical notes and other information in the Symantec knowledge base about this status code .
HOWTO90507 | 2013-10-02
How To | CMS-XML

NetBackup status code: 80

NetBackup status code : 80
HOWTO50855 | 2012-11-19
How To | CMS-XML

Media Manager status code 80

Message: cannot update database due to existing errors vmphyinv
HOWTO51305 | 2012-11-19
How To | CMS-XML

Device management status code 80

Message: Job Manager returned error : see activity monitor Explanation:
HOWTO51548 | 2012-11-19
How To | CMS-XML

NetBackup status code: 80

NetBackup status code : 80
HOWTO34964 | 2010-10-29
How To | CMS-XML

Media Manager status code: 80

Message: cannot update database due to existing errors vmphyinv
HOWTO35415 | 2010-10-29
How To | CMS-XML

Device management status code: 80

Message: Job Manager returned error : see activity monitor Explanation:
HOWTO35658 | 2010-10-29
How To | CMS-XML

Status Code 80: Media Manager device daemon (ltid) is not active

Overview: Catalog backup fails with error : bpbackupdb(pid=XXX) load of media id XXXXX failed, Media Manager device daemon (ltid) is not active.
TECH32729 | 2006-01-03
Technical Solutions | CMS-XML

After upgrading to 7.6.0.1/2.6.0.1, VMware backups via SAN may fail with Status 130 due to bpbkar core dump

kernel: [511349.964163] sd 3:0:1:45: [sds] CDB: Read(10): 28 00 d7 9b a5 80 00 01 00 00
TECH214512 | 2014-08-12
Technical Solutions | CMS-XML

SharePoint backup fails with status code 13 due to conflicting streams backup.

6/20/2014 2:12:56 AM - Warning bpbrm(pid=7668) from client client1: WRN - can t open object: Microsoft SharePoint Resources:\Microsoft SharePoint Foundation Web Application\SharePoint - 80 \content-db 1 (client01/wss_content)\wss_content (BEDS 0xe000035f: The SQL Server backup interface has reported a problem. Further details can be found in the job log. Restarting the SQL Server service or the server may correct the problem.)
TECH222208 | 2014-08-06
Technical Solutions | CMS-XML

Netbackup Administration Console crashes with Application error 1000 and 1004

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

SQL restore fails with error 'RESTORE detected an error on page (xxxxx:xxxxxxxxx) in database "DatabaseToRestore" as read from the backup set.'

INF - ODBC return code 2 , SQL State 01000 , SQL Message 3211 [Microsoft][SQL Native Client][SQL Server]70 percent processed. INF - ODBC return code 2 , SQL State 01000 , SQL Message 3211 [Microsoft][SQL Native Client][SQL Server] 80 percent processed. INF - ODBC return code 2 , SQL State 01000 , SQL Message 3211 [Microsoft][SQL Native Client][SQL Server]90 percent processed.
TECH68315 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup for SQL Server backup fails with Status Code 2 or Status Code 41 for a specific database using full text index

INF - SQL Message 3211 [Microsoft][SQL Native Client][SQL Server]70 percent processed. INF - SQL Message 3211 [Microsoft][SQL Native Client][SQL Server] 80 percent processed. INF - SQL Message 3211 [Microsoft][SQL Native Client][SQL Server]90 percent processed.
TECH58493 | 2013-10-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?