Looks like we have lots of interest in licensing. Over the past year or so, we have tried to make improvements in licensing for NetWorker to make things easier – and in most cases, lower cost. Some of the things we’ve done:
As for other improvements, if you were the EMC Product Manager responsible for making a balanced and attractive licensing structure, how would you approach it? Remember that you get to be both the customer and the vendor and you need to balance out the needs of both.
I no longer have to purchase ClientPak licenses?
Does that mean I can remove them from my maintainance contract?
Do I have to upgrade to a certain version for this to take effect?
I really need to find out what I REALLY need because we keep getting more and more budget cuts, I work for the state of South Carolina, need I say more?
I have a small setup here and am not totally sure why our part of the DR isn't included with the rest of the division's DR. Basically I just backup the Operations Department computers; 2 AIX servers, 1 running Oracle, 3 Windows 2003 servers, and 6 PCs running Windows XP. I have 1 54 slot IBM LTO2 jukebox with 3 drives. That's it, there might not be much there but those 2 AIX servers are critical, they hold ALL the crucial data for us.
As for improvements in licensing, I would like to see each customer have a policy custom tailored to their needs. For example using my own situation; I do not need 64 slots for my jukebox so why not just charge me for 54? Also I am only backing up 11 clients which is practically nothing compared to some of the people where with thousands, so how about designing a package for low-end users like myself at a reduced cost, say less than 50 clients and have it include everything. I guess that was the idea behind the ClientPak.
That brings up a suggestion, at home I have a growing network and would like a cheap and easy to use backup program that could back everything up to one central PC (server). Keep in mind that these PCs have very little critical data (mostly pictures) on them so I would not want to spend a whole lot just to back them up. So how about a home version for just a couple hundred bucks and a small annual support fee (under $100)?
This change of licensing happened I think with 7.4.1. You do not need ClientPaks now. You also don't need Cluster Client Connections and there are no more Tiers in application modules. For VMs, you can now have a VCC license. VSS enabler no more required.
Check the latest release notes, you will more reasons to upgrade.
Now that you mention it, it does seem like I read that somewhere. I am going to go back through and see if I can find it and have it removed from our maintenance contract. I'm at 7.4 sp2.
Seems like I also read that I was supposed to be able to update all the clients from the server but I was never able to figure that out, or at least I never got it to work. So some of my clients are still at 7.3
Here's some info on the changes and releases in which the changes occured (so you have to install and use that version to benefit from the change)
|ClientPaks||7.4 SP1 and higher||No longer requires ClientPak licenses to enable heterogeneous operating system support.|
|Cluster Client Connection||7.4 SP2 and higher||Clusters no longer require unique cluster licenses. Use standard client connections per cluster node.|
|Open File Backup with VSS||7.4 SP2 and higher||VSS client license no longer required for open file backup on Windows. Supported with standard client connection.|
|Windows Application Modules||Version independent||Eliminates processor tiering for Windows Application Modules.|
|Virtual Edition Client||7.4 SP3 and higher||Virtual Edition client license enables protection of any number of virtual machine guests per physical host.|
|Application Module licensing for virtual environments||7.4 SP3 and higher||Only one Application Module license for each application type (SQL Server, Exchange, SharePoint, Oracle, SAP, etc.) is required per physical host regardless of the number of virtual guests running the application and module.|
Hope this helps.
Thanks, that does help.
So I do not have to have the ClientPak for Windows anymore but I do have to maintain my number of connections licenses. Every little bit helps.
Going back to the original topic, rather than the license thoughts.
We have two silos attached to all of our storage nodes through a SAN. One of our main requirements of doing this is to make sure that a complete backup must go into one of the silos, even though the storage node is the same.
Those of you who are aware of our site will recognise our tag line "location location" - say its about time that was mentioned within the Community Network!
Is this important to you? If not then don't worry about it.
But to us, our SAN covers 2 buildings and each building has one of the silos in it. Thus making sure that a backup is entirely stored within one silo is extremely important. i.e. if a backup is split between silos/buildings, and we were to lose the silo/building, we would not be able to do a recovery.
It is worth thinking about.
That's cool, I never got that lucky. The first jukebox I had was 10 slots, then I had one that was 26 slots, now I have one that is 54 slots.
I can see the logic, kind of, of charging in blocks (for lack of a better word) of slots. Most people are going to want to see if they made a good purchase when buying that new jukebox so they will naturally want to enable enough slot to use the entire thing. They might actually lose money if they let you only get what you actually need.