NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


Show Me
Status
Information Resources
Product(s)
Most Popular Subjects
Downloads
   

Symantec Suggests

  Next 

Media Manager status code 9

Media Manager status code 9
HOWTO104397 | 2014-11-20
How To | CMS-XML

Device configuration status code 9

Device configuration status code 9
HOWTO104556 | 2014-11-20
How To | CMS-XML

Robot Error status code 9

Message: Error in SEMAPHORE operation Explanation:
HOWTO104771 | 2014-11-20
How To | CMS-XML

NetBackup status code: 9

Verify that the required extension product is installed and configured. Click here to view technical notes and other information in the Symantec Knowledge Base about this status code .
HOWTO103939 | 2014-11-20
How To | CMS-XML

Backup using client-side encryption fails with Status 9

Backup using client-side encryption fails with Status 9
TECH62487 | 2013-10-24
Technical Solutions | CMS-XML

When the Encryption option is selected, file system backups may fail with VERITAS NetBackup (tm) Status Code 9: an extension package is needed, but was not installed.

Error Code
TECH43871 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE 0: INCREMENTAL backups run as a FULL backup despite the last FULL having backed up all files with Status 0. The bpbkar log reports "folder <folder_name> has been created recently (since 11/9/02 11:35:32 AM). It will be backed up in full."

4 dos_backup::tfs_include: INF - folder has been created recently (since 11/ 9 /04 11:35:32 AM). It will be backed up in full.
TECH23000 | 2012-02-23
Technical Solutions | CMS-XML

Microsoft Information store backup fails with status code 9 when Java Console version is lower than Netbackup Master Server version.

Upgrade the java console to the latest version(NBU 6.5.4) to match with the NetBackup Master Server and then try selecting the Information Store Directives, it should show us the correct directives selections and run the job again. Job should run without any error .
TECH87989 | 2010-09-04
Technical Solutions | CMS-XML

GENERAL ERROR: The error "<32> wimageproblem: fprintf(" ") failed: Bad file descriptor (9) - <backup_image>" occurs in the NetBackup Problems report and log files

32 wimageproblem: fprintf( ) failed: Bad file descriptor ( 9 ) -
TECH48946 | 2007-01-09
Technical Solutions | CMS-XML

BUG REPORT: After upgrading Oracle 9i to Oracle 10.1.0.5 (64-bit) on an AIX, the NetBackup wizard fails to connection to the instance with the error message, "ERR - Unable to connect to <instance name>"

Bug ID(s) ETracks 831398, 831403, and 831404: jnbSA GUI fails to connect to Oracle instance after upgrade of Oracle from 9 i to 10g Symptom(s)
TECH49884 | 2007-01-25
Technical Solutions | CMS-XML

"onbar -l" logical log backup syntax no longer works in Informix version 9.40, returning an onbar syntax error 149, NetBackup error 6

The syntax of the logical log backup command has changed starting in Informix version 9 .40. Previous versions of Informix allowed you to back up logical logs with the following command:
TECH29536 | 2005-01-21
Technical Solutions | CMS-XML

How to troubleshoot NDMP Backups failures when status code 99 (or other NDMP backup failure) is reported. Includes logging instructions.

The following troubleshooting steps may help isolate the root cause of NDMP backup issues. If they do not, proceed with logging instructions in Step 9 .
TECH56492 | 2015-02-23
Technical Solutions | CMS-XML

Backup fails with status 24 after the network stops delivering data to the media server.

-------------------- -------------------- ----- ------ ----- ------ ------- Friday October 9 05:14:08 GMT 2009 (The socket does not exist until the backup starts.)
TECH76201 | 2014-10-16
Technical Solutions | CMS-XML

NetBackup restore and backup status codes

NetBackup restore and backup status codes The status codes and their meanings are as follows: Status Code 9 . An extension package is needed but was not installed.
HOWTO89629 | 2013-10-02
How To | CMS-XML

GENERAL ERROR: How to troubleshoot robot communication issues in Windows

System log: 9 /23/03 12:43:24 AM lp6nds35 Error None 9 N/A INVERS The device, \Device\scsiport3, did not respond within the timeout period. 5/14/04 11:31:20 PM adpu160m Error None 9 N/A DENTON The device, \Device\Scsi\adpu160m2, did not respond within the timeout period.
TECH38829 | 2010-09-07
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?