NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Device management status code 40

Device management status code 40
HOWTO104668 | 2014-11-20
How To | CMS-XML

Device configuration status code 40

Device configuration status code 40
HOWTO104582 | 2014-11-20
How To | CMS-XML

NetBackup status code: 40

The connection between the client and the server was broken. This status code can also appear if the connection is broken between the master and the media server during a backup.
HOWTO103970 | 2014-11-20
How To | CMS-XML

Media Manager status code 40

Examine command output (if available) and the daemon and reqlib debug logs for a more detailed message on the protocol error . See Setting debug logging to a higher level in the Troubleshooting Guide
HOWTO104421 | 2014-11-20
How To | CMS-XML

Subsequent backup or restore jobs with WAN resiliency, MSDP client direct, and accelerator enabled, fail with status code 40

2nd accl backup fail with state 40 while accl+cd+wan are enabled at the same time
TECH218268 | 2014-06-17
Technical Solutions | CMS-XML

Status 87 and Status 40 on long running Client side deduplication jobs across a slow connection

Client side deduplication backup are failing with Status 87 and/or Status 40 for remote clients across the WAN/firewall. The error occured at either the end of a storage unit fragment or at the end of a backup when the last [or only] fragment is closed.
TECH206337 | 2014-04-14
Technical Solutions | CMS-XML

STATUS CODE 43: Backup jobs using the FlashBackup policy type are failing with status code 43 (unexpected message received) reported. This can also manifest itself as a Status Code 40 (network connection broken), with VMWare policy Type.

STATUS CODE 43: Backup jobs using the FlashBackup policy type are failing with status code 43 (unexpected message received) reported. This can also manifest itself as a Status Code 40 (network connection broken), with VMWare policy Type.
TECH55906 | 2014-03-11
Technical Solutions | CMS-XML

Oracle Clients fails when taking large backups producing a status 23,24 or 40 errors

Oracle Clients fails when taking large backups producing a status 23,24 or 40 errors
TECH215286 | 2014-02-25
Technical Solutions | CMS-XML

Status 0 on Application backups, but parent job fails with status 40 before or after

Status 0 on Application backups, but parent job fails with status 40 before or after
TECH66444 | 2014-02-24
Technical Solutions | CMS-XML

Phase 2 import failed with status 40

Phase 2 import failed with status 40
TECH209447 | 2014-01-14
Technical Solutions | CMS-XML

Getting Status 40 when backing up Windows 2008 clients

Installed a media server at a remote location to backup remote clients. All systems are Windows 2008 R2. Getting status 40 on backups.
TECH183711 | 2014-01-09
Technical Solutions | CMS-XML

STATUS CODE 13: Backup of SuSe Linux clients failing with status: 13 file read failed and exit status = 40: network connection broken reported

10:49:20.497 [6346] 2 bpbkar Exit: INF - Close of stdout complete 10:49:20.497 [6346] 16 bpbkar Exit: ERR - read server exit status = 13: file read failed 10:49:20.497 [6346] 4 bpbkar Exit: INF - setenv FINISHED=0
TECH59836 | 2013-11-21
Technical Solutions | CMS-XML

Exchange 2007 backup fails with status 40 "network connection broken"

Exchange 2007 backup fails with status 40 "network connection broken"
TECH75088 | 2013-10-24
Technical Solutions | CMS-XML

STATUS CODE: 40, OpenLDAP is triggering status 40 for Linux clients

STATUS CODE : 40 , OpenLDAP is triggering status 40 for Linux clients
TECH39083 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE: 41 and 150 - SAP backups with device type of "util_file_online" fail with Status Code 41 and 150. Client logs show Status Code 40.

STATUS CODE : 41 and 150 - SAP backups with device type of "util_file_online" fail with Status Code 41 and 150. Client logs show Status Code 40.
TECH44488 | 2013-10-23
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?