Related products	CHARON-AXP (≥ V4.6) and CHARON-VAX (≥ V4.6)
Operating systems	Windows, Linux

Question

What are the best practices for Charon HASP licensing in complex environments (multiple instances, VMware, Hyper-V)?

Recommendations

Single point of failure.
Latest Charon versions support specifying 2 license IDs in its config file (Charon versions required: Charon-AXP and Charon-VAX V4.6 and up). You can have many licenses available to Charon, but it will look for licenses specified in its config in a specific order.
We highly recommend to use this option.
Local dongles on VMware can work pretty well. There is an option (USB Pass-through) which you can set for a USB device to follow a VM appliance around the farm. Even if a VM is vMotioned to another ESXi host, the farm still provides access. Please refer to VMware documentation:Configuring USB Passthrough Devices for vMotion
Disadvantage: if an original ESXi host goes down, so does the license.
Local dongles can be served to Charon VMs with some USB over TCP solutions, like AnywhereUSB. Its stability totally depends on the stability of a third party solution.
Advantage: licensing over network
Disadvantage: dependency on the network
Charon Software licenses are bound to VM machine ID and set of other IDs which are not changed if the VM is vMotioned (though they would if the VM is cloned). Charon Software licenses can also be used in non VM environments. We recommend to use SL only if your Charon landscape is static. If you create/recreate/change configs for Charon VMs, this will not fit.
Advantage: no dependency on USB
Disadvantage: dependency on VM configuration
Charon Network license. There could be a "license server" (a Windows or a Linux box with a lightweight application) in the network, equipped with a special dongle or a software license which serves other Charon VMs over the network. This comes for an additional cost (USD or EUR 1K).
Advantage: Starting from Charon-VAX and -AXP version 4.7, network license counts number of Charon instances, not number of hosting servers and instances per server. For example, a Network license with 6 CHARON instances allows to run 3 instances on a first hosting server, 2 instances on a second hosting server, and one instance in a third hosting server. In the previous versions of Charon Network license set number of hosting systems and Charon instances per host system.
Disadvantage: if this server or network goes down, so do all the Charon instances.

Our recommendations

Have 2 licenses per Charon instance - a PRODUCTION one and a BACKUP one
Configure them explicitly in the Charon config files
Mix the license types. Physical dongles are recommended for BACKUP licenses, as they are much more flexible in all disaster recovery scenarios. PRODUCTION license can be served over the network or be a software license.

Please notice every Software License update has an associated cost.

Related articles

Browser not supported