NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Catalog backup fails with status 29 and 71 after NBAC is enabled

Catalog backup fails with status 29 and 71 after NBAC is enabled
TECH158862 | 2014-06-19
Technical Solutions | CMS-XML

Oracle automatic backup job fails with status 6 or status 29 after the application job fails with status 12.

Oracle automatic backup job fails with status 6 or status 29 after the application job fails with status 12.
TECH60963 | 2013-11-07
Technical Solutions | CMS-XML

Microsoft Exchange Granular Recovery Technology (GRT) restores fail with an error 29

Microsoft Exchange Granular Recovery Technology (GRT) restores fail with an error 29
TECH137478 | 2013-10-24
Technical Solutions | CMS-XML

STATUS CODE 29: Oracle backups using the Veritas NetBackup (tm) for Oracle Agent fail with a status 29 when run from the NetBackup master server, but run successfully from the client.

STATUS CODE 29 : Oracle backups using the Veritas NetBackup (tm) for Oracle Agent fail with a status 29 when run from the NetBackup master server, but run successfully from the client.
TECH32290 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE 29: Scheduled Oracle backups fail with status code 29 when the template resides in the master server and Veritas NetBackup (tm) 4.5 Feature Pack 6 (45_fp6) is installed in the Oracle client.

The bprd log on the master server shows the following errors : 17:21:13.328 [4140.512] 2 spawn_child: D:\Program Files\VERITAS\NetBackup\bin\bpsched.exe -ru root -rg other -ct 13 -ppid 4140 -class zz -sched Daily -IB
TECH32721 | 2013-10-23
Technical Solutions | CMS-XML

Device configuration status code 29

Device configuration status code 29
HOWTO91069 | 2013-10-02
How To | CMS-XML

NetBackup status code: 29

A command was not run. This error can occur because the permissions of the command do not allow it to be run. Or it occurs due to a lack of system resources such as memory and swap space.
HOWTO90458 | 2013-10-02
How To | CMS-XML

STATUS CODE: 29 Oracle full backups are successful, but attempts to run incremental backups fail with a NetBackup Status Code 29 (failed trying to exec a command)

STATUS CODE : 29 : Oracle full backups are successful, but attempts to run incremental backups fail with a NetBackup Status 29 (failed trying to exec a command)
TECH50982 | 2013-04-25
Technical Solutions | CMS-XML

Unix client backup fails with status 29: failed trying to exec a command, and finally with afs/dfs command failed(78)

Unix client backup fails with status 29 : failed trying to exec a command, and finally with afs/dfs command failed(78)
TECH204986 | 2013-04-11
Technical Solutions | CMS-XML

Device configuration status code 29

Device configuration status code 29
HOWTO51418 | 2012-11-19
How To | CMS-XML

NetBackup status code: 29

A command was not run. This error can occur because the permissions of the command do not allow it to be run. Or it occurs due to a lack of system resources such as memory and swap space.
HOWTO50806 | 2012-11-19
How To | CMS-XML

Catalog backups failing with status code 29 and 36

Error in the detailed status of the activity monitor Parent Job fails with the following error: 08/02/2011 10:20:26 - requesting resource xxxxx_catalog.MAXJOBS
TECH153150 | 2012-01-25
Technical Solutions | CMS-XML

The catalog backups fail with status 29

The catalog backups fail with status 29
TECH167212 | 2011-11-30
Technical Solutions | CMS-XML

Device configuration status code: 29

Device configuration status code : 29
HOWTO35528 | 2010-10-29
How To | CMS-XML

NetBackup status code: 29

A command was not run. This error can occur because the permissions of the command do not allow it to be run. Or it occurs due to a lack of system resources such as memory and swap space.
HOWTO34915 | 2010-10-29
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?