NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 232

Robotic status code 232
HOWTO104735 | 2014-11-20
How To | CMS-XML

NetBackup status code: 232

NetBackup status code : 232
HOWTO104147 | 2014-11-20
How To | CMS-XML

Job fails with status 232 after going active on RHEL media server using NIS/YP

Job fails with status 232 after going active on RHEL media server using NIS/YP
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

Robotic status code 232

Robotic status code 232
HOWTO91232 | 2013-10-02
How To | CMS-XML

NetBackup status code: 232

NetBackup status code : 232
HOWTO90644 | 2013-10-02
How To | CMS-XML

NetBackup status code: 232

NetBackup status code : 232
HOWTO50992 | 2012-11-19
How To | CMS-XML

Robotic status code 232

Robotic status code 232
HOWTO51582 | 2012-11-19
How To | CMS-XML

NetBackup status code: 232

NetBackup status code : 232
HOWTO35103 | 2010-10-29
How To | CMS-XML

Robotic status code: 232

Robotic status code : 232
HOWTO35692 | 2010-10-29
How To | CMS-XML

NetBackup status code 232: a protocol error has occurred

232
TECH58729 | 2009-01-12
Technical Solutions | CMS-XML

Image Cleanup job failing with error 2060037 and exit status 174

4/3/2013 1:26:23 AM - Info bpdm(pid=7584) started 4/3/2013 1:26:23 AM - started process bpdm (7584) 4/3/2013 1:26:25 AM - Info bpdm(pid=7584) initial volume Q:\\disk_staging: Kbytes total capacity: 954196672\ used space: 954196440\ free space: 232
TECH205365 | 2014-02-10
Technical Solutions | CMS-XML

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

10:53:59.993 [11988.540] 2 set_job_details: Tfile ( 232 ): LOG 1341586439 32 bpbrm 11988 from client dag01: FTL - socket write failed 10:53:59.993 [11988.540] 2 send_job_file: job ID 232, ftype = 3 msg len = 77, msg = LOG 1341586439 32 bpbrm 11988 from client dag01: FTL - socket write failed 10:53:59.993 [11988.540] 4 db_error_add_to_file: from client dag01: FTL - socket write failed
TECH193354 | 2013-11-11
Technical Solutions | CMS-XML

Exchange GRT backup getting "Unable to initialize nbfsd" error

19:06:29. 232 [8148.8320] 16 nbfsd_op: call 3595 to NBMEDIA1 failed (rv 5, status 5 1853189997, 0x6e756f6d 0x732d2074)
TECH180400 | 2013-11-19
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

shows a successful connection to bpcd followed by a forwarding socket request, both reach the client host and receive a file descriptor (fd). However, xinetd closed the forwarding socket immediately as indicated by the errno 232 .
TECH58196 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup backup job for System State fails with Status 42 / Status e_fs_volume_not_found (0xe0000352) for object 'System Files'. Faild to resolve volume path

Nov 13, 2012 8:03:51 PM - Error bptm (pid=27922) unable to perform read from client socket, connection may have been broken Nov 13, 2012 8:03:51 PM - Error bpbrm (pid=27895) socket read failed: errno = 232 - Connection reset by peer Nov 13, 2012 8:03:51 PM - Error bpbrm (pid=27895) could not send server status message
TECH200104 | 2013-04-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?