NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 199

NetBackup status code : 199
HOWTO104117 | 2014-11-20
How To | CMS-XML

Media Manager status code 199

Media Manager status code 199
HOWTO104549 | 2014-11-20
How To | CMS-XML

NetBackup for Microsoft SQL Server database agent backup failed with Status Code 199

NetBackup for Microsoft SQL Server database agent backup failed with Status Code 199
TECH66372 | 2013-10-24
Technical Solutions | CMS-XML

Media Manager status code 199

Media Manager status code 199
HOWTO91046 | 2013-10-02
How To | CMS-XML

NetBackup status code: 199

NetBackup status code : 199
HOWTO90614 | 2013-10-02
How To | CMS-XML

Media Manager status code 199

Media Manager status code 199
HOWTO51395 | 2012-11-19
How To | CMS-XML

NetBackup status code: 199

NetBackup status code : 199
HOWTO50962 | 2012-11-19
How To | CMS-XML

STATUS CODE 199: could not deassign media due to Media Manager error when performing bpsyncinfo -delete <media_id>

premature eof encountered could not deassign offline catalog backup media in Media Manager volume database Media Manager error 199 , the media is allocated for use, host = server1
TECH58316 | 2012-08-18
Technical Solutions | CMS-XML

NetBackup status code: 199

NetBackup status code : 199
HOWTO35073 | 2010-10-29
How To | CMS-XML

Media Manager status code: 199

Media Manager status code : 199
HOWTO35505 | 2010-10-29
How To | CMS-XML

Unable to do a Vault catalog backup. Vault fails with status 294. Catalog backup within vault fails with status 199: operation not allowed during this time period

Unable to do a Vault catalog backup. Vault fails with status 294. Catalog backup within vault fails with status 199 : operation not allowed during this time period
TECH64697 | 2010-08-28
Technical Solutions | CMS-XML

STATUS CODE 199: Oracle Proxy Copy fails with a NetBackup Status Code 199 (operation not allowed during this time period).

199
TECH51091 | 2008-01-04
Technical Solutions | CMS-XML

Status code 6 and 199 (DESPERATE HELP NEEDED!) | Symantec Connect

Status code 6 and 199 (DESPERATE HELP NEEDED!) Guys, I've been battling for serveral months now a pesky problem related to SC 6 and 199 for two schedules of the same policy. Basically, every Saturday at around 5:30am, one of my schedules fails invariably with SC 199, while the other completes successfully the first time, but fails about 12 min later with SC 6. I'm running 6.5.3.1 on my master, and the client is Solaris 9.
Connect Forums | HTML

Instant Recovery of a Virtual Machine failing with a Status 5.

Application Event logs: Windows(R) failed a request to initialize the Network File System (NFS) redirector [d:\w7rtm\base\fs\remotefs\nfs\client\nfsclient\service.c: 199 ] : 0: The operation completed successfully. Client for NFS cannot start.
TECH218051 | 2014-06-05
Technical Solutions | CMS-XML

SAN Client backups failing intermittently with STATUS 174 and nbftsrvr buffer processing failures in [ProcessReadWrite]

11:44:35.144 [5167] 32 write_data: data buffers out of sequence, expected number 17, received 20 11:44:35.144 [5167] 2 write_backup: write_data() returned, exit_status = 174, CINDEX = 0, twin_index = 0, backup_status = -8 NBFTSRVR (OID: 199 ) log
TECH147561 | 2014-05-26
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?