[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

402.0. "license & client setup problem" by SIOG::BR_MURPHY () Wed Feb 12 1997 04:13

    Hi all,
    	I was wondering if someone could shed some light on a problem I'm
    having. I'm working on an Alpha 2100, DU3.2G, & NSR4.2A. The system has
    a NAS200 license & the DECNSR-NET-SVR license has been loaded into lmf
    & is active. It also has a Jukebox Tier 1 license. At one point it had
    a temporary Client license. 
    
    When I install the client license, I am able to modify the client setup
    for the server (Alpha1) itself & enter multiple entries for the same
    client machine (Alpha1). 
    
    When I remove the multiple entries, & then the client license, I
    believe I should still be able to backup Alpha1, since it has a server
    license. However, I'm having a problem with the client setup. If I try
    to modify it in any way I get the "too many clients" error. The only
    client is Alpha1 itself. Similarly, if I try to create multiple entries
    for the same client I am unable to do so.
    
    I tried emulating the same situation on my DEC3000 in the office. I
    removed all NSR licenses, installed a NAS200 license & ran nasinstall
    to install the NSR Server license. Everything worked fine. I was also
    able to create multiple entries in the client setup for the same
    node...the NSR server.
    
    The reason I want multiple entries is that each filesystem on the
    client machine can then be setup with a different backup schedule &
    still be backed up as part of the same backup group.
    
    
    
T.RTitleUserPersonal
Name
DateLines
402.1DECWET::KOWALSKITime's not for savingWed Feb 12 1997 08:146
If you start from scratch on the problem system, do
you still have a problem?  If so, I would suspect
that you have a BIND problem causing networker not
to recognize Alpha1 as the server.

/m
402.2DECWET::ONOSoftware doesn't break-it comes brokenWed Feb 12 1997 08:288
Is the node name really mixed case?  NetWorker sometimes has 
problems with this.

Do an nsr_shutdown then restart networker using nsrd -D3.  This 
will tell you exactly what licenses are being requested for which 
systems.  Post the output here.

Wes