NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

THIRD PARTY: Multiple client backups exit with status 24 when the network is heavily loaded.

THIRD PARTY: Multiple client backups exit with status 24 when the network is heavily loaded.
TECH56950 | 2014-05-01
Technical Solutions | CMS-XML

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

Backup fails with status 24 after the network stops delivering data to the media server.
TECH76201 | 2013-06-20
Technical Solutions | CMS-XML

Status 24 on backup of Windows clients to RedHat media server during media spanning

This problem is observed to occur when the backup for a Windows client host to a RedHat media server fills a tape. During the minute or so during which the current tape is unmounted and a new tape mounted and positioned, the client receives a broken socket indication from the Windows O/S and exits with status 24 . A retry or restart of the backup a few minutes later will be successful if it does not result in a second span media event.
TECH160330 | 2014-08-15
Technical Solutions | CMS-XML

STATUS CODE 24: Socket write failed

: TransporterRemote::write[2](), Line: 307 | Local Address: [::]:0 | Remote Address: [::]:0 | OS Error : 10054 (An existing connection was forcibly closed by the remote host.
TECH150369 | 2014-07-22
Technical Solutions | CMS-XML

NetBackup backups are failing with Status 24 due to network issue in the environment

NetBackup backups are failing with Status 24 due to network issue in the environment
TECH217961 | 2014-05-30
Technical Solutions | CMS-XML

Clients failing backups with status code 24 errors

Clients failing backups with status code 24 errors
TECH145234 | 2014-05-18
Technical Solutions | CMS-XML

Windows 2008r2 server server failing with status 24

Windows 2008r2 server server failing with status 24
TECH216943 | 2014-04-26
Technical Solutions | CMS-XML

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

From the client’s dbclient log: 12:03:00.988 [XXXX] 16 serverResponse: ERR - server exited with status 23: socket read failed 12:03:00.989 [XXXX] 16 CreateNewImage: ERR - serverResponse() failed
TECH215286 | 2014-02-25
Technical Solutions | CMS-XML

Status 24 or 42 for Linux clients

Status 24 or 42 for Linux clients
TECH124766 | 2014-01-23
Technical Solutions | CMS-XML

Backup of client behind firewall fails with status code 24 (socket write failed) despite port 13782 and 13724 being open.

10:17:17.190 [23963] 2 bpbrm handle_backup: client MYCLIENT EXIT STATUS = 24: socket write failed 10:17:17.400 [11180] 2 bpbrm brm_sigcld: child 23963 exited with status 24 : socket write failed bpbkar log:
TECH202245 | 2013-12-02
Technical Solutions | CMS-XML

Microsoft Exchange DAG backup failing with error code "socket write failed(24) "

Remote Address: [::]:0 OS Error : 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Expected bytes: 131072
TECH193354 | 2013-11-11
Technical Solutions | CMS-XML

hyper-v restore may fail with "EXIT STATUS 24: socket write failed " or "hyper-v policy restore error(2821)" due to network connectivity issues

Detail Status : 10/24/2013 12:09:48 PM - begin reading 10/24/2013 12:10:18 PM - Info bptm(pid=7440) EXITING with status 24 ----------
TECH212287 | 2013-11-07
Technical Solutions | CMS-XML

SQL backups fail with status code 24, socket write failed

SQL backups fail with status code 24 , socket write failed
TECH62322 | 2013-10-24
Technical Solutions | CMS-XML

After upgrading to NetBackup 7.0.1 Exchange 2003 server backup fails with Status 24.

After upgrading to NetBackup 7.0.1 Exchange 2003 server backup fails with Status 24 .
TECH146715 | 2013-10-24
Technical Solutions | CMS-XML

A possible cause of and remedy for status 24 failure with BMR when utilizing VxSS(NBAC).

Failed to restore system file, rc=5 Example failure log ( Deteiled Status of Activity Monitor ) 2013/08/30 12:15:00 - begin Restore
TECH210423 | 2013-10-22
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?