Hmm we only experienced an issue with some older Oracle clients...
I'd leave it alone until you run into an issue.  You may also be able
to use an alias from your hosts file to keep the limit short.

On 7/21/09, Preston de Guise <enterprise.backup AT gmail DOT com> wrote:
> Tim,
>
> On 22/07/2009, at 09:11 , Tim Mooney wrote:
>
>> In regard to: Re: [Networker] Networker 7.5 server with older
>> clients,...:
>>
>>> On 22/07/2009, at 02:18 , Tim Mooney wrote:
>>>
>>>> In regard to: Re: [Networker] Networker 7.5 server with older
>>>> clients,...:
>>>>> The only thing you need to be wary of is the security model.
>>>>> NetWorker
>>>>> 7.3 introduced a new security model. So, for clients older than
>>>>> that you
>>>>> need to make sure that you use the old security model.
>>>> Is it possible to set the security model on a client-by-client
>>>> basis?
>>>> When we ran into this issue when going to 7.4.x, EMC seemed to
>>>> imply that
>>>> we must disable the new authentication site-wide, which is what we
>>>> did.
>>>> If we could disable it on a client-by-client basis, that would be
>>>> better.
>>>
>>> That's not the case. You can disable/set the authentication model
>>> on a client by client basis. I already have several customers who
>>> are doing this for various reasons.
>>>
>>> Run up:
>>>
>>> nsradmin -s nsrServer -p nsrexec
>>> nsradmin> print type: NSRLA
>>>
>>> What you want to change is the "auth methods" option. On any new
>>> server it will have a default value of:
>>>
>>> "0.0.0.0/0,nsrauth/oldauth"
>>>
>>> The auth methods are processed in order, so say you had a client
>>> called cerberus that could only use the old security model - you'd
>>> change it to:
>>>
>>> nsradmin> update auth methods:
>>> "cerberus,oldauth","0.0.0.0/0,nsrauth/oldauth"
>>
>> Thanks Preston.  Since we use FQDN for all our clients I can already
>> see
>> that we're in for a treat maintaining this and a potential resource
>> length
>> limitation, but I think we'll want to give this a try anyway.
>
> If you're using Unix, you at least have the option of doing:
>
> nsradmin> print type: NSRLA
> nsradmin> edit
>
> And launching into a "vi" editor session to edit the resource
> information - it makes prepending information much easier, I find.
>
> Cheers,
>
> Preston.
>
> --
> Preston de Guise
>
>
> "Enterprise Systems Backup and Recovery: A Corporate Insurance Policy":
>
> http://www.amazon.com/Enterprise-Systems-Backup-Recovery-Corporate/dp/1420076396
>
> http://www.enterprisesystemsbackup.com
>
> NetWorker blog: http://nsrd.wordpress.com
>
>
> 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
>

-- 
Sent from my mobile device

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