TSM EE server License, vs TSM Client.

[timgren]

We have 1000+ machines that we call "servers".

5 Of these machines have the TSM Server EE edition installed. These are what all the other machines backup to.

Our IBM rep is saying we need to license "every core on ALL 1000+ machines for TSM Enterprise Edition Server". And that a "TSM Client" license is only for laptops, etc.

What if we use laptops as "application servers"? Not TSM servers, but OTHER application servers. We can't use the TSM client license?

Can anyone confirm this to be true?

It seems to me that the ambigious term "server" is being exploited, and companies are being decieved and deliberately misled by IBM sales reps. If this is the case, out legal department will surely want to know about it.

 

[moon-buddy]

As of late, and anyone can correct me, IBM licensing is based on per core and each core is assigned a Value Unit depending on the type of processor - CISC or RISC.

Therefor, it does not matter whether the "box" serves as a TSM Server or TSM Client (node) from TSM EE perspective.

I have confirmed this with IBM's procurement specialist.

 

[timgren]

Thanks Moon.
Talk about convoluted, blatently open-ended and ambigious on IBM's part.

I think it's time to do a TCO of TSM vs Netbackup.

Competitively priced is one thing, but this appears to be gouging. I for one don't feel "privilaged" about using TSM. It's simply a means to an end.

 

[moon-buddy]

Thanks Moon.

I think it's time to do a TCO of TSM vs Netbackup.

I wouldn't think about using any backup system other than TSM IF the company's DR and BCP is at stake. TSM is more than just a backup solution BUT a Data Management solution. Version 5.4/5.5 offers a lot more that any vendor can offer.

BUT, this is me and my two cents...

 

[sgabriel62]

Our favorite subject - Licensing. Keep in mind TSM server can be sold and operate as a Basic Application rather than an Extended Edition. The Extended Edition allows for Library sharing as well as DRM just to name a few. You purchase TSM server licenses based on the configuration.

The "client" license applies to all platforms, and functions. And yes although its now bound to the Processor Core Count - We are learning more and more of its advantages and disadvantages. For example - VmWare clients of a VmWare Host - are not bound to a TSM license - only the host is bound to licensing. Here's another - Servers in a Dev or QA environment are where they act test& burn servers - are not bound to licensing until the servers status becomes a production server. Passive nodes of a cluster are not bound to licensing as well - since they act as "warm" or even "cold" devices dependent on the cluster type.

Bottom line - Licensing is all bound to "honor society"; pay for what you are using - review each year - True Up or Down as it applies.

Its not all bad in the long run - technology such as VMWare - Vpars/LPars - provide the means to "adjust" based on the business need.

Now this is me speaking based on what Ive learned from previous accounts and conversations with Sales Reps. I would recommend to all of us to remain in contact with our Sales and Tech teams to keep abreast of all license updates, changes etc...I would not hold it to IBM management that are indeed listening to its customer base and will "adjust" accordingly.
Stay Honest and True and we're all Golden. - There ya go - my two cents

 

[BrianP]

Be careful with LPAR and VMWare licensing. Remember that you do not just license the VMWare VC server, but also the CPU's on the actual VMWare servers as well. With LPAR"s you need to license the whole server, not just the LPAR's that you are using. There was a discussion on this a month back. also validate that you are getting the proper discoount levels for your licensing. If your rep is inflexible, get his or her manager involved. It will save you big $$$.

Brian​