Server Migration and Licensing
Before a server migration, the existing licensing data of the installation should be reviewed.
The specific steps required depend on the version you are using, your license configuration, and your previous installation setup.
What should be checked first before a server migration?
The following details are particularly important for the initial review:
- currently used webPDF version
- company name of the licensee
- existing license key or license certificate
- existing subscription and subscription certificates
- previous and new server environment
- whether only the server is being migrated or a version change is also planned at the same time
Why is this review important?
After a server migration, the technical and licensing context may change. It should therefore be verified before continued use whether:
- the existing license configuration can continue to be used unchanged
- an updated license key is additionally required
- an upgrade to a new major version should be requested at the same time
Can the old and new servers run at the same time?
Each installation requires its own server license. Therefore, no more installations may be in operation at the same time than there are licenses available.
For a server migration, this means: If you set up the new server while the previous server is still in operation, you’ll need an additional license for this transition period. Alternatively, you can take the previous installation offline before the new installation takes over processing jobs. For non-production installations, we offer discounted licenses please contact us.
When does an installation count as “in operation”?
What matters is active use, not the mere existence of an installation. An installation counts as long as it is processing jobs or is ready to process them.
As soon as the webPDF service is stopped, the installation can no longer accept jobs and is no longer counted. It is not necessary to shut down the server, remove the license, or uninstall webPDF. You can keep the existing installation as a fallback during the migration, as long as the service remains stopped.
It is not sufficient to simply remove the installation from a load balancer while the service continues to run: In this case, it remains technically ready to process jobs and can be reintegrated at any time.
What applies to failover or standby installations?
An installation that is designated in the operational concept to resume processing jobs when needed continues to be counted. This applies equally to load-balancing, failover, and cold and hot standby scenarios.
This must be distinguished from the temporary transition phase of a server replacement, at the end of which the previous installation is decommissioned. If, on the other hand, the old installation remains in place permanently as a reserve, it is subject to licensing.
When is an upgrade also involved?
If you want to combine the server migration with a version change, this topic should be considered together with the license review. In this case, both the upgrade entitlement and the matching license key for the target version are often relevant. If, for example, no matching license key for a major version is available, the installation will switch to demo mode.
What documents help with a quick resolution?
Helpful are:
- Support information from the Admin Portal
- existing license documents (license or subscription certificates)
- details about the desired target environment (e.g. update from version x to y)
- a brief description of what changed during the server migration