NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 175

NetBackup status code : 175
HOWTO104095 | 2014-11-20
How To | CMS-XML

Media Manager status code 175

Media Manager status code 175
HOWTO104531 | 2014-11-20
How To | CMS-XML

NetBackup 5.x BUG REPORT: Synthetic backup fails with status 665, when source bpdm failed with status 175.

NetBackup 5.x BUG REPORT: Synthetic backup fails with status 665, when source bpdm failed with status 175 .
TECH43197 | 2009-01-01
Technical Solutions | CMS-XML

BUG REPORT: When using VERITAS NetBackup (tm) 5.1 Maintenance Pack 3 (MP3), Status 175, 5, or 174 may be encountered on restore attempts.

BUG REPORT: When using VERITAS NetBackup (tm) 5.1 Maintenance Pack 3 (MP3), Status 175 , 5, or 174 may be encountered on restore attempts.
TECH39377 | 2006-01-05
Technical Solutions | CMS-XML

Event manager service is unable to start: [Error] v-231-106 Attempted to start the Event Manager on a non-master Server

inet addr:10.10.10.10 Bcast:10.10. 175 .255 Mask:255.255.248.0
TECH67287 | 2014-08-23
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

pciex1077,2532.1077.173 pciex1077,2532.1077.174 pciex1077,2532.1077. 175
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

CORBA connection failures and status 25 after upgrading media server to 7.5.0.6 or 2.5.3

17:16:28.793 [1711] 2 ConnectList::update: updated host 10.0.0.1 as GOOD , used 0 of 3 retries(ConnectList.cpp: 175 ) bptm receives the forward profile from the remote PBX and prepares to query the EMM service.
TECH208869 | 2013-09-24
Technical Solutions | CMS-XML

While backing up certain Virtual Machines via NetBackup, VmWare Consolidated Backup (VCB) method generates status code 11: system call failed

The following is seen in the bpbrm log: 02:11:51. 175 [1012.5548] 2 write_file_names: buffering file name BACKUP \\.\E:\ USING \\?\Volume{0e670a74-e1a6-11dd-9b98-001f2954e051}\ OPTIONS:alt_path_prefix=C:\Veritas\NetBackup\temp\_vrts_frzn_img_4260,FITYPE=MIRROR,MNTPOINT=\\.\E:\,FSTYPE=NTFS for output
TECH67977 | 2010-01-10
Technical Solutions | CMS-XML

GENERAL ERROR: Administration Console is unresponsive and all jobs fail with Status 25 after NetBackup was upgraded to version 6.5

01:20:30.848 [4400.5772] 2 vnet_bind_and_connect_extra: ..\libvlibs\vnet_bind.c.287: Function failed: 41 0x00000029 01:20:30.848 [4400.5772] 2 vnet_bind_and_connect: ..\libvlibs\vnet_bind.c. 175 : Function failed: 41 0x00000029 log snipped
TECH55786 | 2009-01-31
Technical Solutions | CMS-XML

Synthetic backup on netbackup5.1 MP2 error | Symantec Connect

Synthetic backup on netbackup5.1 MP2 error I have tested systhetic backup on netbakcup 5.1 mp2.While doing UAT we found that there are known bugs in netbackup 5.1 mp2 1)Synthetic backup fails with status 665, when source bpdm failed with status 175 . 2)
Connect Forums | HTML

RMAN Backup completed without generating child stream or sometime failing with error code 6 | Symantec Connect

18:01:09.026 [23359] <2> int_getmminfo: INF - support for Proxy Copy enabled 18:01:14. 175 [23359] <4> sbtend: INF - --- END of SESSION --- 18:11:24.475 [28545] <8> xbsa_getenv: WRN - nbbsa_schedule not found in environment block
Connect Forums | HTML

Sharepoint Status 13 since upgrade to 7.1.0.1 | Symantec Connect

Kicked off a manual Sharepoint backup. One backup stream now fails with Status 175 and a Status 150 can also be seen in Job details:
Connect Forums | HTML

timed out connecting to client (Error Code=54) | Symantec Connect

[veritas:root] / # bpclntcmd -hn app host app: app at 202.154. 175 .27 (0xca9aaf1b) checkhname: aliases:
Connect Forums | HTML

HP UX File System Backup Failed with Error 49 | Symantec Connect

12:57:45. 175 [28338] <2> bpcd valid_server: comparing MasterServer.fully.qualified.domain.name and MasterSerer.fully.qualified.domain.name 12:57:45.202 [28338] <4> bpcd valid_server: hostname comparison succeeded 12:57:45.210 [28338] <2> bpcd main: output socket port number = 1
Connect Forums | HTML

MS SQL backup error | Symantec Connect

01:20:30.848 [4400.5772] <2> vnet_bind_and_connect: ..\libvlibs\vnet_bind.c. 175 : Function failed: 41 0x00000029
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?