NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

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

41
TECH43122 | 2014-07-01
Technical Solutions | CMS-XML

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

41
TECH42466 | 2013-10-23
Technical Solutions | CMS-XML

NetBackup SAP HANA backup jobs fail with error 41 and 25

NetBackup SAP HANA backup jobs fail with error 41 and 25
HOWTO88624 | 2013-09-30
How To | CMS-XML

NetBackup status code: 41

If the bpbrm log has entries similar to the following, the problem is in the routing configuration on the server: bpbrm hookup_timeout: timed out waiting during the client hookup bpbrm Exit: client backup EXIT STATUS 41 : network connection timed out
HOWTO103971 | 2015-01-20
How To | CMS-XML

Media Manager status code 41

Media Manager status code 41
HOWTO104422 | 2014-11-20
How To | CMS-XML

Device management status code 41

Device management status code 41
HOWTO104669 | 2014-11-20
How To | CMS-XML

Device configuration status code 41

Device configuration status code 41
HOWTO104583 | 2014-11-20
How To | CMS-XML

BUG REPORT: NetBackup SQL or Oracle database agents, or user initiated backups are failing with Status Code 41 after upgrading to NetBackup 6.5 or 7.0.

10:40: 41 .435 [2040.4076] 2 logconnections: BPRD CONNECT FROM client.4627 TO master.13724
TECH58164 | 2014-10-20
Technical Solutions | CMS-XML

Sharepoint 2013 backup fails with error 41

Sharepoint 2013 backup fails with error 41
TECH214884 | 2014-02-12
Technical Solutions | CMS-XML

SAP application backup job hangs, may eventually failing with status 41

SAP application backup job hangs, may eventually failing with status 41
TECH207045 | 2013-10-29
Technical Solutions | CMS-XML

STATUS CODE 41: Possible causes of exit status 41 (network connection timed out) on NetBackup for Lotus Notes Agent backups

Troubleshooting: Typical situations where Lotus Notes backups will fail with status 41 include: 1. Client Read Timeout value set too low to allow backup processes to complete
TECH31305 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: Network errors during Oracle RMAN backups when using xinetd resulting in status 6, status 23, status 25, status 41, or status 58

GENERAL ERROR : Network errors during Oracle RMAN backups when using xinetd resulting in status 6, status 23, status 25, status 41 , or status 58
TECH58196 | 2013-10-24
Technical Solutions | CMS-XML

Status 41 occurring on root partition backup of UNIX OS platforms, bpbkar hangs on "/," but other partitions and directories on the client back up without hanging.

Status 41 occurring on root partition backup of UNIX OS platforms, bpbkar hangs on "/," but other partitions and directories on the client back up without hanging.
TECH29421 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE 41: NetBackup Exchange mailbox backups fail with a Status Code 41.

41
TECH28396 | 2013-10-23
Technical Solutions | CMS-XML

Lotus Domino server crashed due to low memory condition during NetBackup for Lotus Notes database agent backup. The NetBackup job may fail with Status Code 41.

Lotus Domino server crashed due to low memory condition during NetBackup for Lotus Notes database agent backup. The NetBackup job may fail with Status Code 41 .
TECH58238 | 2013-10-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?