NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 173

Media Manager status code 173
HOWTO91027 | 2013-10-02
How To | CMS-XML

NetBackup status code: 173

NetBackup status code : 173
HOWTO90591 | 2013-10-02
How To | CMS-XML

Media Manager status code 173

Media Manager status code 173
HOWTO51376 | 2012-11-19
How To | CMS-XML

NetBackup status code: 173

NetBackup status code : 173
HOWTO50939 | 2012-11-19
How To | CMS-XML

NetBackup status code: 173

NetBackup status code : 173
HOWTO35049 | 2010-10-29
How To | CMS-XML

Media Manager status code: 173

Media Manager status code : 173
HOWTO35486 | 2010-10-29
How To | CMS-XML

NetBackup status code 173: cannot read backup header, media may be corrupted

173
TECH58630 | 2009-01-12
Technical Solutions | CMS-XML

Client Direct backups to MSDP fail with status 83

15:24:52.619 [5887] 2 59249:bpbrm:5887:master1:probe: libsts openp() 13/10/30 15:24:52: opening module /usr/openv/lib/libstspinbostpxy.so 15:24:53. 173 [5887] 2 59249:bpbrm:5887:master1:probe: libsts openp() 13/10/30 15:24:53: opening module /usr/openv/lib/libstspinearstore.so
TECH212376 | 2013-11-11
Technical Solutions | CMS-XML

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

pciex1077,2532.1077.172 pciex1077,2532.1077. 173 pciex1077,2532.1077.174
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

Backup failing with status 13 for VMware client residing on a NAS (NFS) datastore.

08/24/2011 15:44:00.0949 : logBinaryFile:.\VixMetaSave.cpp: 173 INFO : Entered
TECH171186 | 2011-10-10
Technical Solutions | CMS-XML

Many small jobs in a large MPX group may result in slow performance and status 13 or status 6

12:47:51.960 [22497] 4 write_backup: successfully wrote backup id myclient_1249907325, copy 1, 1699 Kbytes 12:48:17. 173 [22497] 4 write_backup: successfully wrote backup id myclient_1249907952, copy 1, 3431 Kbytes 12:48:42.597 [22497] 4 write_backup: successfully wrote backup id myclient_1249908304, copy 1, 1443 Kbytes
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML

Image cleanup keeps failing with 158 error failed accessing daemon lock file (158) | Symantec Connect

Image cleanup keeps failing with 158 error failed accessing daemon lock file (158) [24116] <2> clean_stream: wellingtonbk 14:31:40.169 [24116] <2> IsCatalogCleanupTerminated: Terminated = 0 14:31:40. 173 [24116] <2> db_error_add_to_file: dberrorq.c:midnite
Connect Forums | HTML

The status code 58 Can’t connect to client | Symantec Connect

The status code 58 Can’t connect to client 01:29:54.097 [2796.5276] <2> vnet_pop_byte: ..\libvlibs\vnet.c. 173 : Function failed: 11 0x0000000b
Connect Forums | HTML

MY backup is falling with error code 25 | Symantec Connect

MY backup is falling with error code 25 22:41:48.038 [24619] <2> vnet_sock_ready: vnet.c.509: Function failed: 11 0x0000000b 22:41:48.038 [24619] <2> vnet_pop_byte: vnet.c. 173 : Function failed: 11 0x0000000b 22:41:48.038 [24619] <2> vnet_pop_string: vnet.c.268: Function failed: 11 0x0000000b
Connect Forums | HTML

NetBackup 7.1 - error 71 "unable to successfully enumerate folder: Microsoft Exchange Mailboxes:\ | Symantec Connect

Friday 018:00:00 029:00:00 138:00:00 149:00:00 Saturday 018:00:00 029:00:00 162:00:00 173 :00:00 005:00:00 Schedule: differential-inc
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?