You must be using a 4.x client. Can you upgrade to the 7.x netware client?
That'll solve the problem.

Siobhan


On 1/11/07 2:04 PM, "Ben Harner" <benjamin.harner AT MARYMOUNT DOT EDU> wrote:

> I have set the storage node before the nsrserverhost.  The data goes to
> the storage node and is written to that device.  Just not directly.  It
> is going to the server then to the storage node.   I was looking for a
> way to skip coming across the wan to the server and then back to the
> storage node.  Is this possible?
> 
> Thanks
> 
> Ben
> 
> 
> Michael S Baker wrote:
>> If you added the local storage node to the 'storage node' attribute in the
>> client definition by itself or in front of nsrserverhost then it should be
>> working. The index and bootstrap will always go across to the NW sever, but
>> the client's data should go to the local storage node defined in it's client
>> entry.
>>  
>> --- 
>> Michael S. Baker
>> Implementation Specialist
>> EMC² Technical Solutions Group
>> Baker_Michael AT emc DOT com | 860.710.1195 (Cell)
>> 
>> 
>> ________________________________
>> 
>> From: EMC NetWorker discussion on behalf of Ben Harner
>> Sent: Thu 11/1/2007 04:53
>> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>> Subject: Re: [Networker] Backup over WAN
>> 
>> 
>> 
>> Okay I tried this but the data is still going to the backup server and
>> then to the storage node.  Not from the client to the storage node.  Am
>> I missing something?  I am snooping the interface between the client and
>> the storage node and there is no traffic.  Everyone says this should
>> work but it does not.  Any ideas?
>> 
>> Ben
>> 
>> 
>> 
>> Ben Harner wrote:
>>   
>>> Hey Paul,
>>> 
>>> Thanks!
>>> 
>>> Ben
>>> 
>>> 
>>> 
>>> Goslin, Paul wrote:
>>>     
>>>> You Edit the client resource and in the preferences indicate in the
>>>> 'storage node' attribute field which Storage Node is to receive the
>>>> backup stream and write it to an enabled device....
>>>> -----Original Message-----
>>>> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT 
>>>> EDU] On
>>>> Behalf Of Ben Harner
>>>> Sent: Monday, October 29, 2007 3:05 PM
>>>> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>>>> Subject: Re: [Networker] Backup over WAN
>>>> 
>>>> How does Networker know when to have the data travel from cient -->
>>>> storage node?  Do they need to be on the same c class or something?
>>>> 
>>>> Ben
>>>> 
>>>> 
>>>> Zwe Paing wrote:
>>>> 
>>>>       
>>>>> Hi Fazil,
>>>>> 
>>>>> Thanks for your reply. For my previous problem, I finally got my
>>>>> backup running successfully after 4 days using netware with
>>>>> compression directives.
>>>>> 
>>>>> Fazil Saiyed wrote:
>>>>>   
>>>>>         
>>>>>> Hello,
>>>>>> Depending on how you configure the client resource the backups can be
>>>>>>      
>>>>>>           
>>>>       
>>>>>> directed to SN ( index will flow to backup server) or backup server (
>>>>>>      
>>>>>>           
>>>>       
>>>>>> index & data will be backed up by backup server).
>>>>>>        
>>>>>>           
>>>>> I'm not sure about the above part on how to do the configuration. As
>>>>> of right now, here's what I have for the client configuration.
>>>>> http://my.networker.googlepages.com/home
>>>>> 
>>>>> I only have the storage node not the server for the storage node under
>>>>>    
>>>>>         
>>>>       
>>>>> "client properties > preferences"
>>>>> So, as you suggested, it may be worth a try to place the storage
>>>>> node and client together.
>>>>> 
>>>>> Thanks again.
>>>>> 
>>>>> Zwe
>>>>> 
>>>>>   
>>>>>         
>>>>>> If it's a small client try compression on the client resource via
>>>>>> networker directive to get the most out of the wan pipeline, if the
>>>>>> data is large and you start seeing performance issues it's best to
>>>>>> configure SN at the site where you have the client ( data will flow
>>>>>> to local SN-i.e the client itself, backup index will flow to backup
>>>>>> server).
>>>>>> HTH
>>>>>> 
>>>>>> To sign off this list, send email to listserv AT listserv.temple DOT edu 
>>>>>> and
>>>>>>      
>>>>>>           
>>>>       
>>>>>> type "signoff networker" in the body of the email. Please write to
>>>>>> networker-request AT listserv.temple DOT edu if you have any problems 
>>>>>> with
>>>>>> this list. You can access the archives at
>>>>>> http://listserv.temple.edu/archives/networker.html or
>>>>>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>>>>>> 
>>>>>>        
>>>>>>           
>>>>> To sign off this list, send email to listserv AT listserv.temple DOT edu
>>>>> and type "signoff networker" in the body of the email. Please write
>>>>> to networker-request AT listserv.temple DOT edu if you have any problems
>>>>> with this list. You can access the archives at
>>>>> http://listserv.temple.edu/archives/networker.html or
>>>>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>>>>>    
>>>>>         
>>>> To sign off this list, send email to listserv AT listserv.temple DOT edu 
>>>> and
>>>> type "signoff networker" in the body of the email. Please write to
>>>> networker-request AT listserv.temple DOT edu if you have any problems with 
>>>> this
>>>> list. You can access the archives at
>>>> http://listserv.temple.edu/archives/networker.html or
>>>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>>>> 
>>>> To sign off this list, send email to listserv AT listserv.temple DOT edu 
>>>> and
>>>> type "signoff networker" in the body of the email. Please write to
>>>> networker-request AT listserv.temple DOT edu if you have any problems with
>>>> this list. You can access the archives at
>>>> http://listserv.temple.edu/archives/networker.html or
>>>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>>>>  
>>>>       
>>> To sign off this list, send email to listserv AT listserv.temple DOT edu and
>>> type "signoff networker" in the body of the email. Please write to
>>> networker-request AT listserv.temple DOT edu if you have any problems with
>>> this list. You can access the archives at
>>> http://listserv.temple.edu/archives/networker.html or
>>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>>>     
>> 
>> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
>> type
>> "signoff networker" in the body of the email. Please write to
>> networker-request AT listserv.temple DOT edu if you have any problems with 
>> this
>> list. You can access the archives at
>> http://listserv.temple.edu/archives/networker.html or
>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>> 
>> 
>> 
>> 
>> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
>> type
>> "signoff networker" in the body of the email. Please write to
>> networker-request AT listserv.temple DOT edu if you have any problems with 
>> this
>> list. You can access the archives at
>> http://listserv.temple.edu/archives/networker.html or
>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>>   
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list.
> You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 


Siobhán

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER