NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

in-depth Troubleshooting Guide for Exit Status Code 134 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 6.0

134
TECH43250 | 2006-01-13
Technical Solutions | CMS-XML

in-depth Troubleshooting Guide for Exit Status Code 134 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 5.0 / 5.1

134
TECH42410 | 2005-01-31
Technical Solutions | CMS-XML

Media Manager status code 134

Media Manager status code 134
HOWTO104499 | 2014-11-20
How To | CMS-XML

NetBackup status code: 134

A status 134 is not logged in the error logs. A 134 status causes a new try to appear in the Activity Monitor. It does not increase the retry count that is associated with the allowed number of retries.
HOWTO104056 | 2014-11-20
How To | CMS-XML

Trying to activate SLP getting error "Lifecycle manager operation active: Unable to process. Duplication session in progress. return value = [134]"

Lifecycle manager operation active: Unable to process. Duplication session in progress. return value = [ 134 ]
TECH182757 | 2013-12-10
Technical Solutions | CMS-XML

DOCUMENTATION: Why don't tapes get unmounted when running many user (database) backups in a shared storage option environment? Backup jobs receive a status code 134.

Because of these timing interactions of the VERITAS NetBackup (tm) scheduler with media manager components, there could be occasions when the scheduler might make a job active but the drive would have been taken by another job. On such occasions, the job will be re-queued with status 134 : server resources are busy. For example, when the scheduler needs to use all the drives and at the same time restore jobs were initiated by a user, some of the jobs will be re-queued.
TECH28727 | 2013-10-23
Technical Solutions | CMS-XML

Bug Report: Attempts to back up SAP exit with Status Code 6 after the media server fails with Status Code 134.

log shows the following error message: EXITING with status 134 ---------- The bpbrm log contains the following error:
TECH44423 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE: 54, 24, 134, and 6 are all received while performing a backup. The final exit status is 6 indicates the backup has failed.

log. It will finally exit with status code 54. The abundance of server status 134 messages written to the client progress logs causes the SQL agent to get out of sync with the connections to the media server.
TECH37196 | 2013-10-23
Technical Solutions | CMS-XML

BUG REPORT: FlashBackups may occasionally exit with a status 134, resulting in rogue snaps left on the client that are not cleaned up.

BUG REPORT: FlashBackups may occasionally exit with a status 134 , resulting in rogue snaps left on the client that are not cleaned up.
TECH56748 | 2008-01-23
Technical Solutions | CMS-XML

STATUS CODE: 191 - Duplications from tape, disk or from a Disk Staging Storage Unit (DSSU) will fail with a status 191 if a status 134 occurs during the relocation of images to tape.

STATUS CODE : 191 - Duplications from tape, disk or from a Disk Staging Storage Unit (DSSU) will fail with a status 191 if a status 134 occurs during the relocation of images to tape.
TECH44400 | 2007-01-25
Technical Solutions | CMS-XML

The VERITAS NetBackup (tm) scheduler receives a Status Code 134, but VERITAS Snapshot Provider (VSP) still takes the snapshot. In this instance, VSP cache files are left behind.

Etrack (NetBackup) 384759: Scheduler gets 134 , but snap taken. VSP Cache files being left behind.
TECH43330 | 2006-01-20
Technical Solutions | CMS-XML

BUG REPORT: When using VERITAS NetBackup (tm) 5.1, attempts to backup Oracle on hp-ux 11.11 either aborts with a status 134, or core dumps upon execution.

BUG REPORT: When using VERITAS NetBackup (tm) 5.1, attempts to backup Oracle on hp-ux 11.11 either aborts with a status 134 , or core dumps upon execution.
TECH44379 | 2006-01-04
Technical Solutions | CMS-XML

STATUS CODE: A Status 134 "unable to process request because the server resources are busy" error occurs and jobs requeue. The client's bpbkar process unexpectedly runs up to hundreds of times within an hour.

STATUS CODE : A Status 134 "unable to process request because the server resources are busy" error occurs and jobs requeue. The client's bpbkar process unexpectedly runs up to hundreds of times within an hour.
TECH38198 | 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.

For Windows media server: install path \NetBackup\bin\vxlogcfg -a -p 51216 -o 134 -s DebugLevel=6 -s DiagnosticLevel=6 install path \NetBackup\bin\vxlogcfg -a -p 51216 -o 151 -s DebugLevel=6 -s DiagnosticLevel=6
TECH56492 | 2014-10-01
Technical Solutions | CMS-XML

NetBackup status code: 23 - How to troubleshoot backups that fail with status 23 "socket read failed".

12:44:38.619 [4804.5184] 2 bpcd main: setup_sockopts complete 12:44:43. 134 [4804.5184] 8 bpcd peer_hostname: gethostbyaddr failed : The requested name is valid, but no data of the requested type was found. (0)
TECH56079 | 2013-04-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?