HyperBac for Sybase - Licensing FAQs

How is HyperBac Licensed?

HyperBac offers customers a very simple licensing model. HyperBac is simply licensed per server.

•  All licensing is perpetual and include software assurance for the 1st year
•  Options for 2 and 3 years prepaid maintenance can be adopted if required
•  Cumulative volume breaks occur at 10, 30 and 70 servers purchased

It is simply a HyperBac instance per server and nothing more.

What if I have a number of virtual servers on the one physical server?

Some customers may have two or more virtual machine instances running on the one physical server. In this case each virtual machine instance is treated as a server and would have to be licensed individually.

This is not to say that all virtual machine instances running on a physical server need to be licensed. You only need to license the instances that you require.

I have an active/passive cluster. How is HyperBac licensed in this case?

HyperBac needs to be licensed for each node of the cluster. HyperBac's architecture requires that it is installed on each host where a Sybase instance is running. In the case of a cluster this is a physical node.

Do I have to subscribe to the product every year?

No you don’t. HyperBac is licensed on a perpetual basis with the 1st year of software maintenance included in the price of the solution. At the anniversary of purchase the customer may elect to renew software maintenance to guarantee free support and upgrades.

If the customer chooses to forego their maintenance renewal, then the solution will continue to function.

What is the cost of migrating a license from one server to another?

HyperBac permits license migrations for those customers current under software maintenance. If you are moving a license from Server A to Server B, then this attracts a small administration fee of USD $100 per license migrated.

My support has expired, can I upgrade HyperBac?

HyperBac is licensed on a perpetual basis. If you do not renew software maintenance, then you can continue to use your presently installed product. Technical support will not be available to those whose maintenance has lapsed.

** HyperBac does not make past product releases available for general download. It is assumed that the customer is keeping a master copy at their premises.

If you try to upgrade HyperBac after software maintenance has lapsed, you will be able to install the new release, but it will not start because HyperBac recognises both the software version and maintenance expiry to determine product validity. In such a situation, you will render your deployed instance of HyperBac unworkable. You will be required to contact HyperBac support and renew your software maintenance to continue using the deployed HyperBac instance. Similarly you may revert back to the product release that you were running at the time of maintenance expiry.