NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 209

Robotic status code 209
HOWTO104715 | 2014-11-20
How To | CMS-XML

NetBackup status code: 209

NetBackup status code : 209
HOWTO104126 | 2014-11-20
How To | CMS-XML

NDMP backups are failing with status 174 (media manager - system error occurred) reported. Status code 14 (file write failed) can also be seen in logs.

v-134-105 [ConnectionToBrm::WriteSocket] write socket err 32 (Broken pipe) v-134-19 [NdmpAgent::SetErrorAndHalt] ConnectionToBrm.cpp( 209 ) - error code 14 (file write failed) [Error] v-134-112 FH send to BRM failed - Ddi - 0 0 0 0 764210 0 0 21 764208 port_grp_name_add.htm
TECH59140 | 2014-01-17
Technical Solutions | CMS-XML

VMware Backup fails with error status 25

Checking bpcd log on the VM backup host: 07:58:54. 209 [3060.3776] 2 bpcd main: VERBOSE = 5 07:58:54.209 [3060.3776] 2 logparams: C:\Program Files\Veritas\NetBackup\bin\bpcd.exe -standalone
TECH193946 | 2012-07-28
Technical Solutions | CMS-XML

Client initiated operations using only ipv6 fail with status 25

entries from the command show that a status 25 is recorded when attempting to connect to the master server. 14:22:48. 209 [1234] 8 connect_to_service: [vnet_connect.c.545] init_connect_reces() failed 6 0x6 14:22:48.209 [1234] 8 vnet_connect_to_service: [vnet_connect.c:215] connect_to_service() failed 6 0x6
TECH193460 | 2012-07-23
Technical Solutions | CMS-XML

NDMP backups failed with status 13 - file read failed

12:18:23.030 [24840] 2 logconnections: BPDBM CONNECT FROM xx.xx.xx.xx.53734 TO xx.xx.xx.xx.13724 12:18:23. 209 [24840] 2 db_end_sts: no DONE from db_getreply(): file read failed 12:18:23.210 [24840] 2 db_flistsend: db_end_sts() failed: file read failed (13)
TECH162205 | 2012-02-22
Technical Solutions | CMS-XML

VMware backup failing with EXIT STATUS 11: system call failed

[dc10.000000hds0.000000prod SATA Datastore (LUN 209 )] BackupHost/BackupHost.vmdk
TECH168372 | 2011-09-15
Technical Solutions | CMS-XML

ms2012 and Exchange 2013 error 2 bpresolver | Symantec Connect

ms2012 and Exchange 2013 error 2 bpresolver 6/26/2014 4:42:47 PM - Info nbjm(pid=213155) starting backup job (jobid= 209 ) for client okcexchdag01, policy exchange_2013, schedule Full 6/26/2014 4:42:47 PM - Info nbjm(pid=213155) requesting media_server_only resources from RB for backup job (jobid=209, request id:{cfc05576-fd7a-11e3-9803-3f757377f30a}) 6/26/2014 4:42:47 PM - requesting resource stu_disk_plsoknbumedia01
Connect Forums | HTML

Status Code Chart

207 209 210
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

Status Code 82: Media Manager killed by signal

02:07:50.040 [10446] 2 bpbrm send_parent_msg: POSITION ABC123 211 0 02:09:15.208 [10446] 2 bpbrm read_media_msg: read from media manager: POSITION SSP441 31 1 02:09:15. 209 [10446] 2 bpbrm send_parent_msg: POSITION ABC123 31 1
TECH71491 | 2011-02-03
Technical Solutions | CMS-XML

NetBackup messages

error creating or getting message queue See NetBackup status code : 209 error encountered attempting backup of catalog (multiple tape catalog backup)
HOWTO103773 | 2014-11-20
How To | CMS-XML

Media and device management messages

Unable to open drive See Robotic status code 209 Unable to open robotic path
HOWTO104779 | 2014-11-20
How To | CMS-XML

view_exportimport

3000 10. 209 .19.10 Note:
HOWTO103486 | 2014-11-18
How To | CMS-XML

bptestnetconn

- 10.80.73.101 : 0 ms [local] FL: www.google.com - 74.125.19.106 : 0 ms FL: r2d2.starwars.galaxy.com - 0.0.0.0 : 4 ms FL: whoknows.what.com - 209 .139.193.224 : 0 ms [cluster/ri]
HOWTO104826 | 2014-11-20
How To | CMS-XML

bpbkar32.exe faults on DFSR backup jobs of NetBackup 7.5.0.x Windows clients

Faulting application name: bpbkar32.exe , version: 7.500.513. 209 , time stamp: 0x511714d0 Faulting module name: msvcr100.dll
TECH203717 | 2013-12-16
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?