How to merge Veeam Backup & Replication licenses
Challenge
This article describes the process of merging licenses for Veeam Backup & Replication.
Cause
A license file installed to your Veeam software replaces the information from the previous license of that type. A merged license file allows for increased socket or instance capacity by combining licenses from multiple Support IDs.
Please note that the merged license key will use the earliest support expiration date of all product keys.
Solution
Veeam Backup & Replication v10 and higher
Starting with Version 10, Veeam Backup & Replication is designed to accept two separate license files; one for sockets and one for instances. If you have multiple licenses for either type, you will need to merge them together via the Customer Portal before installation.
For more information on the built-in merge capability of Veeam Backup & Replication please review the Merging Licenses section of the User Guide. As noted above the built-in merge operation only allows on of each type of license.
For more information on the built-in merge capability of Veeam Backup & Replication please review the Merging Licenses section of the User Guide. As noted above the built-in merge operation only allows on of each type of license.
Merging Licenses in Customer Support Portal
Merge Limitations
NOTE! Licenses can be merged only when they have the same:
- Account Name
- Product Name and Edition
- Product Version
- Licensing Terms
- License Administrator
- They must all be Active on Support
The License Administrator may obtain a merged license file by following the steps below.
- Log on to the Veeam My Account dashboard and go to License management >> Production Licenses (https://my.veeam.com/#/licenses/production)
- If multiple accounts are being managed by the same account, select the account for which the merge is being performed.
- Once the correct account is selected, all Production Licenses for that account will be visibile.
- To begin the merge process, click License merge:
- Then, select the products and their respective licenses which should be merged.
- After the desired SupportID’s have been selected, click the Preview button to preview the new license information. There will be an option to select which product version the license should be created for.
- After verifying the information in the preview and selecting the correct software version, click “Merge Licenses” button to finalize the merge process. A pop-up will appear with the options to download the license or send a copy to the license administrator’s email.
Veeam Backup & Replication 9.5.x
Veeam Backup & Replication 9.5 U4\U4a\U4b (Build numbers: 9.5.4.x) is designed to accept only a single license key. If you have multiple license keys or keys for different workloads (sockets and instances); they must be merged into a single license file via the Customer Portal prior to installation. The action of installing a license file will replace the previously installed license file.
More information
.
- To revert the License Key merge operation, Customers may choose “Cancel merge” to destroy the merged license and revert to original product License Keys.
- License Key split option on the Customer portal is available to select Customers only. Splitting licenses within one SupportID requires opening a licensing support case.
https://my.veeam.com/#/open-case/step-1?type=1
- Please note that the license auto-update feature does NOT correctly update merged licenses created on the license management portal. If you have enabled auto-update, disable it before installing a merged license from the license management portal.
- More info about the merge policy in the EULA (1.11.2. License Key Merge).
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
