Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error while connecting with novel backup

Created: 05 May 2010 • Updated: 07 Nov 2010 | 4 comments
Zahid.Haseeb's picture

Novel version = 6
NBU OS is = Windows 2003 R2 (64bit)
NBU version =6.5.5

Novel has the client install for novel but i am facing the below error on the novel machine in NBU (see the below snap)

Any help will be appriciated.

Comments 4 CommentsJump to latest comment

Per Holmgren's picture

Hi, a few questions to be able to help you better...

Was this client working previously and "just failed" now or is this a new Netware client installation ?

If it is a new installation:
Are all Netware related NLM's loaded (tsafs, smdr etc)
Was it the "Netware target client" that was installed ?
Has the client been configured ?
Has the client been loaded ?
Can the masterserver and Netware client ping each other by short name ?


ayodeji's picture

i tink u need to answer Per Holmgren questions. and also do check to ensure that u edit the hosts file of the client to include the master server entry.

Ayodeji Oni

Zahid.Haseeb's picture

Thanks for all guys kind replies

ayodeji :  Yes i can ping via host name

Per :         it is a new installation
                 Are all Netware related NLM's loaded (tsafs, smdr etc)  ??? (what is this)
                 Was it the "Netware target client" that was installed ?    (WHat is this)
                how can i confirmed that the client is configured  and loaded ?
                Yes   the masterserver and Netware client ping each other by short name

Any comment will be appreciated. Mark as Solution if your query is resolved
Thanks in Advance
Zahid Haseeb

Per Holmgren's picture


Ok, if you have access to the netware server console you can type "m tsa*" and see if either TSA500, TSA600 or TSAFS is loaded. If any of the three is loaded then I'm sure that SMDR is also loaded. These Netware modules are loaded by smsstart.ncf in autoexec.ncf when the OS boots. Also you could try "m bp* on the console to see if the Netbackup client is loaded. Only installing the client will not load it. On the netware server console enter "bpstart" to start the client load process. Once that is done you have to configure the client. During configuration you can create target files for different resources. I usually start by creating a "SYS" target file. When you create a backup policy on the master server you refer to this target file (SYS) as a resource to back up.

Search for "Netware target client" here:
and you will find more information.