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

NetBackup for VMware full virtual machine restore fails with Status 5

Restoring virtual machine fails with following message reported in proxy server bpvmutil log: 11:53:51. 209 [4068.708] 2 findConverter: found path = C:\Program Files (x86)\VMware\VMware Converter\ 11:53:51.287 [4068.708] 2 bpVMutil main: Unable to access mount point f:\\MNT\ vm_name for restore, errno = 2
TECH77028 | 2009-01-25
Technical Solutions | CMS-XML

A restore on a Windows 2003 operating system fails with status code 85 media read error.

log: 12:01:58. 209 PM: [3312.4892] 4 tar_restore_shm::v_exitshm: INF - [5044] shared memory restore exit status = 40 12:01:58.240 PM: [3312.4892] 2 dtcp_read: TCP - success: recv socket (1844), 4 of 4 bytes
TECH31290 | 2005-01-16
Technical Solutions | CMS-XML

Strange catalog backup error | Symantec Connect

Strange catalog backup error Critical One or more catalog entries, including /opt/openv/var/host_cache/037/e7861a37+1891,1,4,2,2,0+172.24.66.103.txt, indicate they are TIR entries, but are not in the previous backup Warning Of 444 files to add, expected 209 TIR entries, but 13 were missing
Connect Forums | HTML

Getting Error Failed to initialize EMM connection. Please help... | Symantec Connect

Getting Error Failed to initialize EMM connection. Please help... 04:42:52.090 [18463] <2> local_getallbeornbhostinfo: platform of client mokscy3uvgfpa02.itservices.sbc.com is pc-x64, WindowsXP 04:42:52. 209 [18463] <2> bpcr_get_uname_rqst: bpcr.c: 3875 count=28, buffer=uname_sysname = windows2008 04:42:52.209 [18463] <2> bpcr_get_uname_rqst: bpcr.c: 3875 count=33, buffer=uname_nodename = mokscy3uvgfpa02
Connect Forums | HTML

SQL backup exits status 1 - all child streams successful | Symantec Connect

SQL backup exits status 1 - all child streams successful Backup Database backed up. Database: database_2, creation date(time): 2010/03/18(15:43:05), pages dumped: 600, first LSN: 18: 209 :124, last LSN: 18:263:1, number of dump devices: 1, device information: (FILE=1, TYPE=virtual_device: {'vnbu0-7092-5408-1269362254'}). This is an informational message only.
Connect Forums | HTML

Backup failing with Error code 23 on Solaris client NBU version 6.5.6 | Symantec Connect

01:22:31.208 [15871] <2> logconnections: BPCD ACCEPT FROM 192.168.72.12.62630 TO 192.168.73.234.13724 01:22:31. 209 [15871] <2> bpcd main: setup_sockopts complete 01:22:31.211 [15871] <2> vauth_acceptor: vauth_comm.c.337: no methods for address: no authentication required
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:45:35. 209 [4665] <2> db_end: Need to collect reply 14:45:39.218 [4665] <2> ConnectionCache::connectAndCache: Acquiring new connection for host ampsnbma, query type 78 14:45:39.220 [4665] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML

Snapshot error(not in cluster) | Symantec Connect

Snapshot error(not in cluster) 9:10:17. 209 PM: [23272.46184] <4> dos_backup::tfs_include: INF - folder (finxc192) has been created recently (since 6/15/2012 12:46:07 AM). It will be backed up in full.
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?