Networker

Re: [Networker] Windows NT cluster license issue

2008-09-17 09:43:22
Subject: Re: [Networker] Windows NT cluster license issue
From: Phil Myers <PMyers2 AT CONEMAUGH DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 17 Sep 2008 09:37:25 -0400
Thanks for the information.  It looks like I may have to upgrade to 7.4
SP2 for this to work.

-------------
Phil Myers
Network Administrator
Memorial Medical Center
(814) 534-1559
pmyers2 AT conemaugh DOT org
-------------
-------------

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Jonathan Walsh
Sent: Tuesday, September 16, 2008 10:41 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: Windows NT cluster license issue

Please excuse the tranche of data.  Have a look for ...

Frequently Asked Questions: EMC NetWorker License Simplification

... on PowerLink

=================================================

Cluster Client Connections

Question:       What is the difference between NetWorker Client
Connection (CC) and NetWorker Cluster Client Connection (CC)?

Answer: Historically, NetWorker has offered two types of client
licenses: the traditional client and a cluster client. The NetWorker
Cluster Client Connection enables more functionality than a traditional
NetWorker Client Connection as it tracks virtual clients which are
typical of a clustered environment. The Clustered Client Connection
license also carries a higher price. 

Question:       Why was Cluster Client Connections licenses eliminated,
when did it happen and what's the impact to customers?  

Answer: In older releases of NetWorker, the code required Cluster Client
Connection licenses to support protection of applications and file
systems running in a cluster. This license was often mis-understood and
confused with client connection license. With NetWorker 7.4 SP2, we have
eliminated the concept of a cluster client connection license and
customers will order a single license for all clients (clustered and
non-clustered).  

        Details:

*       Cluster Client Connection licenses are no longer required for
NetWorker 7.4 SP2 and later versions. "Standard" client connections --
the NetWorker Client Connection -- should now be used for clusters. 

*       In NetWorker 7.4 SP2, the licensing logic remains the same for
clustered servers. The Open Storage Software Guide details the licensing
requirements for each combination of cluster type and Application
Module. 

*       Cluster Client Connection licenses are still required for
NetWorker 7.4 SP1 and prior versions.

*       For customers upgrading the NetWorker server to 7.4 SP2 or later
release, pre-existing Cluster Client Connection licenses will be treated
like "standard" client connection licenses. One Cluster Client
Connection license will be treated as one "standard" client connection
license.

*       For customers upgrading the NetWorker server to 7.4 SP2 or later
release, credit will not be given for pre-existing Cluster Client
Connection licenses.

*       For customers running NetWorker 7.4 SP2, the maintenance charges
for pre-existing Cluster Client Connections will be adjusted to the
equivalent price as a standard Client Connection. The maintenance
charges will be adjusted only at the time of contract renewal. No
decommission of Cluster Client Connection licenses will be required.

Question:       What if I have a mix of NetWorker versions in my
environment?

Answer: The code changes that eliminate the need for Cluster Client
Connection licenses is part of the NetWorker 7.4SP2 server, so any
clients attached to this server can use the traditional Client
Connection license. If you have a NetWorker server version 7.4SP1 or
earlier, you will still need to purchase both Cluster Client Connection
and Client Connection for the environment. It is the NetWorker server
that is looking for the Client Connection and Cluster Client Connection
licenses.

Question:       What is the impact to maintenance? 

Answer: Since NetWorker 7.4 SP2 and newer still honors the Cluster
Client Connection (CCC) license as a standard client, customers who
upgrade their NetWorker environment to 7. 4 SP2 or newer will be able to
adjust the maintenance price at support renewal time.

=================================================

 
 
Jonathan Walsh  |  Principal Consultant  
GlassHouse Technologies (UK) Ltd. 
 
T: +44 203 040 8996  l  M: +44 7734 681630  l  F: +44 870 762 7045  
Jonathan.Walsh AT glasshouse DOT com l  www.glasshouse.com
Infrastructure :: Optimised
This message is intended only for the use of the individual or entity to
which it is addressed and may contain information that is privileged,
confidential and exempt from disclosure.  If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering the message to the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please accept our apology. We should be obliged
if you would telephone the sender on the above number or email them by
return. Thank you. 
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Stan Horwitz
Sent: 16 September 2008 15:35
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Windows NT cluster license issue

On Sep 16, 2008, at 8:57 AM, Phil Myers wrote:

> Hello, everyone.
>
> We have a Windows NT cluster client that persists in using a regular
> networker license instead of an available NT cluster license.  Node  
> 1 is
> named LX-SQL1 and node 2 is LX-SQL2, with the cluster name LXSQL.
> LX-SQL2 shows up under the license report as using an NT cluster
> license, while LX-SQL1 is using a regular client license.  It's as if
> Networker is not seeing LX-SQL1 as part of the cluster.  We still have
> an available NT cluster license.  I have deleted and reinstalled the
> cluster licenses numerous times without any effect.  I have deleted  
> and
> re-added the clients to no effect.  Any ideas how I can get  
> Networker to
> see this client correctly?

Which NetWorker server version are you running? NetWorker 7.4SP2 does  
away with cluster licensing.

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

<Prev in Thread] Current Thread [Next in Thread>