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

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

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

Duplications of Granular (GRT) Backups from disk to tape fail with status 191.

bpdbm log: 06:35:29. 199 [11420.7532] 2 local_bpcr_connect: expected reserved port, got 1556 06:35:29.386 [11420.7532] 2 dbm_open_client_connection: client socket from bpcr = 936
TECH166508 | 2013-11-22
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

11/10/10 11:13:15.759 [Debug] NB 51216 nbftsrvr 199 PID:20703 TID:3 File ID: 199 [No context] 0 [initializesdc24xx] isp-2432 instance 2 PN 3 (Subsystem Device ID 0x143) Not in Target Mode
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

VMware Backups may fail with Status code 11 and Status code 13 due to NetBackup I/O related issues

11/25/2011 17:13:38.0757 : read:h:\7101\src\vxms\plugin\common\map\vix\VixFile.h: 199 ERROR [Sys Error: Invalid argument] : g_vdinterface- vdRead returned error 1
TECH175713 | 2013-10-14
Technical Solutions | CMS-XML

VMware Full Mapped backup failing with status 13 and bpbkar exiting with status 11 system call failed

07/28/2011 13:32:54.0563 : read:h:\7101\src\vxms\plugin\common\map\vix\VixFile.h: 199 ERROR [Sys Error: Invalid argument] : g_vdinterface- vdRead returned error 16000, offset 0x0000001ac8717a00, length 0x0000000000040000 07/28/2011 13:32:54.0563
TECH167193 | 2013-10-03
Technical Solutions | CMS-XML

VMWare backups are hanging or failing with status 41 due to WMI hanging on IsSystemBootedUsingEFIFirmware()

log you will see a delay in between the EFI call: 11:05:46. 199 PM: [4000.6600] 2 ov_log::v_globallog: INF -IsSystemBootedUsingEFIFirmware() - Enter 11:15:51.557 PM: [4000.6600] 2 ov_log::v_globallog: INF - Boot Manager Path: \EFI\Microsoft\Boot\bootmgfw.efi
TECH199036 | 2013-07-01
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.

The job details indicate that the bptm process returns the error could not open FT server pipe. This suggests the error occurred with the FT process on the media server. Reviewing VxUL logging for OID 199 (nbftsrvr) will show additional information about the memory allocation failure.
TECH206660 | 2013-05-28
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?