Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cluster problems 1

Status
Not open for further replies.

wotsit

MIS
Oct 18, 2002
47
GB
We're running Networker 6.02 on a Windows 2000 domain with a cluster.
It has been running fine and we've had no problems backing up the cluster for several months, but for some reason since last Friday, the group has started failing with this error: "save: rap error: Unable to grant nt cluster client licence: too many clients. maximum is 2".

Nothing has changed, so has anyone got any ideas as to what i can do to resolve it so we can run a full backup ?

Thanks

Helen
 
Check your other clients to make sure they don't have cluster services installed. then restart the legato services on the mail cluster clients.
 
Run nsrlic on the backup server to see number of licenses that you have. Than add one more temporary cluster client license, run a backup and watch for errors. Than use nsrlic again to see which server takes the extra license.
 
There was a problem where it would count the virtual nodes as well when determining how many cluster licenses you needed.

Are you running exchange or sql on the the cluster, and using NetWorker Module for backing up? If you are, then this is fixed in the latest release (assuming that you have an older version).
 
just take Legato networker version 6.13 it works fine with MSCS.

We have 3 MSCS (2 file/print 1 exchange).

No problems at all.

Did you install another MSCS in your network with is also in the backup?

cyberted
 
We have the same problem with a exchange 2000 cluster. The 2 virtual nodes are also counted in the output of the nsrlic command. There seems to be a known problem with the exchange client on a cluster. Our OEM (fujitsu Siemens) is investigation. If they come up with a solution or a path i post it here
 
Thanks for you help guys.

We've yet to find permanant solution to this, but we got round it by getting a temporary licence for the time being.

Thanks again

helen
 
What application are you running on the cluster? Exchange? SQL? What version of the NetWorker Module did you install?

Like I said, there was a problem where it would count the virtual nodes as well when determining how many cluster licenses you needed.

 
The gethostbyaddr() function is used on a cluster to retrieve the hostname for a local online virtual IP address. On a Windows 2000 computer running MSCS, the gethostbyaddr() function returns the physical node name instead of the virtual server name. Subsequently, this problem causes the nsrd process to fail to start during a failover condition, and may cause the NetWorker software to inappropriately index files during a backup.
On Windows 2000 with Service Pack 2, the NetWorker clients and servers will not fail over when configured on a virtual host. The problem appears to be intermittent in earlier versions of Windows 2000.

If you are running Microsoft Windows versions 2000, 2000 with Service Pack 1, or 2000 with Service Pack 2, you must apply Service Pack 3.

Bye.
 
Thanks for your help on this one.

They're going to close our office down in a months time and everyone is being made redundant. As the temprary licence workaround is running ok at the moment, i've been told to leave it.

Thanks again for all your help.

helen
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top