NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 194

Media Manager status code 194
HOWTO91042 | 2013-10-02
How To | CMS-XML

NetBackup status code: 194

NetBackup status code : 194
HOWTO90609 | 2013-10-02
How To | CMS-XML

Media Manager status code 194

Media Manager status code 194
HOWTO51391 | 2012-11-19
How To | CMS-XML

NetBackup status code: 194

NetBackup status code : 194
HOWTO50957 | 2012-11-19
How To | CMS-XML

NetBackup status code: 194

NetBackup status code : 194
HOWTO35068 | 2010-10-29
How To | CMS-XML

Media Manager status code: 194

Media Manager status code : 194
HOWTO35501 | 2010-10-29
How To | CMS-XML

DOCUMENTATION: How to troubleshoot and correct problems with media servers when the status changes in the Media Servers area of the NetBackup Administration GUI.

The connect back was made to the sending IP address, which is the IP associated with mastnode2 13:29:10. 194 [14608.19392] 2 TAO: TAO (14608|19392) - pbxiop_connector::make_connection, to x.x.x.c:1556:EMM 13:29:10.210 [14608.19392] 2 TAO: TAO (14608|19392) PBXIOP connection to peer x.x.x.c:1556
TECH69625 | 2009-01-15
Technical Solutions | CMS-XML

hyper-v Backups using the cluster name for the hyper-v host fails with Status 39 "client name mismatch"

16:36:50.451 [12535] 2 hosts_equal: host2 hypervnode1 hypervnode1.symantec.com addr 192.168.4. 194 (0xc204a8c0)
TECH162842 | 2011-12-19
Technical Solutions | CMS-XML

hyper-v restore fails with Status 24 or other socket related error

) | Expected bytes: 65536 | Bytes read: 9196 | (TransporterRemote.cpp: 194 ) In addition to the above error messages, the tar32.exe process may produce an APPCRASH
TECH177061 | 2011-12-15
Technical Solutions | CMS-XML

Unable to start NetBackup services. Status 153

This message indicates that the master server s hostname is not the first entry in it s own servers s list. As noted on page 194 of the Symantec NetBackup Administrator s Guide, Volume I referenced below:
TECH164708 | 2011-08-23
Technical Solutions | CMS-XML

GENERAL ERROR: When running nbpushdata during upgrade to NetBackup 6.0, error message "nbpushdata must be run on the Global Device Database host first" is displayed.

Local host GDB Host = master2 Error : EMM DB record not found ( 194 ) The output shows master1 is configured to recognize master2 as the globDB host.
TECH57509 | 2009-01-21
Technical Solutions | CMS-XML

BUG REPORT: (Cold) offline catalog backup reports 'failed to perform database backup' even though the job completed successfully with status 0.

01/21/08 09:51:31. 194 [Application] NB 51216 nbpem 116 PID:5112 TID:4 File ID:116 [No context] [Info] v-116-36 running session_notify
TECH56239 | 2008-01-26
Technical Solutions | CMS-XML

Solaris 10u9. Unable to connect new client: Status 24/25 | Symantec Connect

Solaris 10u9. Unable to connect new client: Status 24/25 host riv-login: riv-login at 194 .66.XXX.XXX(0xc242a0ae) checkhname: aliases: From the NBU server:
Connect Forums | HTML

Sharepoint backup status code 2 | Symantec Connect

Sharepoint backup status code 2 [Info] v-117-94 FSM JobTable[sharepoint_granular_resolver:ReadFileList] m_jobstep=4, Jobid=2619, returns=0 20/05/10 14:08:26.294 [Info] v-117-88 FSM JobTable[sharepoint_granular_resolver:ResolverDiscovery] m_jobstep=5, Jobid=2619 20/05/10 14:08:34. 194 [Info] v-117-94 FSM JobTable[sharepoint_granular_resolver:ResolverDiscovery] m_jobstep=5, Jobid=2619, returns=2 20/05/10 14:08:34.195
Connect Forums | HTML

Netbackup 6.5 - Solaris 10 status"6" | Symantec Connect

under : vnetd 11:39:31. 194 [7015] <2> vtext_open: vtext.c.92: Function failed: 7 0x00000007 11:39:31.194 [7015] <2> vnet_read_service: vnet_text.c.554: Function failed: 19 0x00000013
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?