For cloud deployments: if supported by the cloud provider, the VE license server instance can be moved to a different subnet, as long as the original instance can be moved. It is also possible to backup and restore (to the same instance) the license server data. However, the following actions will invalidate the license: - All supported environments:
- Copying the license server data to a different instance
- Seriously damaging the root filesystem of the license server system
- Re-installing the license server system
- Copying the virtual machine on which the license server runs
- Changing the number of CPU cores of the license server system.
- VMware environments:
- If the license server is bound to the ESXi host: using vMotion on the VM in which the VE license server runs
- Changes to the API interface of the ESXi host or vCenter Server
- The license can become temporarily unavailable if the user credentials or address information recorded by esxi_bind are changed. In this case, esxi_bind must be run again to define the correct user credentials and address information.
- AutoVE deployments:
- Charon emulator host instance register with their license server only once at start.
This is recorded on the license server in /opt/license-server/instances.db.
If this file is lost, the license is not invalidated from the license server's view, but it can no longer be used from the Charon host instances as they will not register a second time. The Charon host instances would have to be recreated (fresh instance launch from a supported marketplace instance). Therefore, it is very important to backup up the instance database file. If a peer license server is used, the databases are synchronized between the two servers providing another level of data backup.
|