Veeam backup licensing socket

Instances will be used for everything else. This is the existing Veeam licensing policy that is now enforced at the product level.

To avoid backup interruption after v10 upgrade, please ensure your socket license is sufficient to cover all hypervisor hosts where protected VMs reside, no matter of which Veeam product is used for protecting those VMs. Re: licensing socket and instances in same server Post by jamcool » Wed Jul 01, am this post So if I read this write, even if I install Windows agent on a VM and back it just I do my physical servers via a protection group, it will find that VM's Host it resides on and assign it a socket license instead of using an instance license like it did in version 9.

I have 4 VMs in a 50 node cluster that I want to backup but I do not want to backup the rest of the 1, VMs in that cluster as they are self generating each day. I was using Windows agent and it consumed instance license. It consumed the 6 instances 1. Now the job is failing and I see 2 of the 4 using instance but I see one of the VM Host getting a license and it is complaining about not enough socket licenses. Re: licensing socket and instances in same server Post by Mildur » Wed Jul 01, am this post If you add the hypervisor as a host in Veeam, then agent backups will try to use socket license if your license is socked based.

If you install veeam agent on a vm, where the host is not added as a hypervisor, veeam will consume an instance for this agent. Re: licensing socket and instances in same server Post by jamcool » Wed Jul 01, pm this post I was trying to think of some fancy reply but all I can say is "Yuck". What is weird is that 2 of the 4 VMs that are running Windows agents are working just fine and consume 2 instance licenses. Can I have both VUL per-workload and legacy per-socket licenses?

How do I merge license files? If a customer wants to have a centrally managed environment, they may need to merge license files. The requirement is that maintenance is current for both the per-socket and VUL components. Contact Veeam support for assistance with any issues. Veeam Backup Essentials sockets and universal licenses can be upgraded to Veeam Availability Suite for centralized management and license mergeability.

How can I migrate from a legacy perpetual per-socket license contract to a fully featured, portable Veeam Universal License VUL subscription? Purchasing these SKUs converts contracts from perpetual per-socket licenses to a VUL subscriptions and extends the support term for one year.

Additional years may be purchased at the same time. Customers are entitled to migrate at the cost of new license price for the respective VUL. In some cases, additional promotions to make this transition are available. The purchase of new VUL subscriptions to replace perpetual per-socket licenses without using the authorized Migration SKU is not permitted. For more details on migration, please reach out to the Veeam Renewals Team.

You can try up to six licenses at no cost. These licenses appear in the product as shown below and do not expire. How do I continue my subscription term? To continue using your Veeam products with a VUL subscription, simply renew your VUL licenses prior to the expiration of your current term.

For assistance with a quote, please contact our team here. Which edition features and support level will I get if I have both Socket and VUL licenses in the same, centrally managed console? When Sockets and VUL are centrally managed, the Socket License Key will define the product edition feature-set and support level of the entire merged environment.

Please refer to Licensing policy sections 2. Definitions for all capitalized terms are found in Definitions section below. Veeam Licensing. Instance calculation for Veeam Universal License. Veeam Universal License available in both Subscription and Perpetual License Types removes complexity from license consumption tracking, providing portability of the license across a breadth of product functionality.

Standalone Offerings non-Veeam Universal Licenses. BYOL version only. Non-transferable to or from other Veeam products using Instances. For VMware virtual machine workloads only. Multiyear Subscription Billing Options. Customer commits to pay for the entire length of the contract upfront. Multiyear Subscriptions with Annual Billing require all yearly options to be purchased together on initial order. Customer commits to pay annual amount by the yearly anniversary each year for the length of contract.

Gifted Built-in Product License. Product Edition. When present, Product Edition of the license regulates the Software capabilities level. Only Customers who are current on Support and Maintenance are eligible for a downgrade. Veeam does not refund the difference in price for downgrades.

Offering Downgrades are only offered for Perpetual Licenses, may require a downgrade SKU, and a penalty or fee may be charged. Product Edition Downgrades have no penalty or fee. Support and Maintenance expiration date s and licensing terms are not altered in the event of Product Edition Downgrade. Downgrades to Product Editions that Customer does not currently own are not available.

Support and Maintenance Downgrades are not available. Only Customers who are current on Support and Maintenance are eligible for upgrades. Upgrades may require a fee — even in cases where Customer is upgrading to what they were previously entitled to.

Support and Maintenance expiration date s and licensing terms are not altered in the event of Product Edition Upgrades. Production level Support and Maintenance is required for, and thus is included in, all upgrades. Support and Maintenance Upgrades are available. License Purchase Terms. Except as expressly agreed otherwise, Veeam reserves the right to change Packaging and Pricing as needed without advanced or written notification and price changes are not enforced retroactively.

Renewal prices that incur volume or term decreases will result in repricing based on current market price without regard to prior Pricing. Veeam License Keys. License Start Date. License Key Merge. Below are clarifications and exceptions to general merge rules:. License Key merge exception Merge rules Veeam Backup Essentials This product offering is not allowed for merging between License Types or with other products.

Veeam Backup Starter This product offering is not allowed for merging between License Types or with other products. This product will no longer be offered on October 1, Support will be discontinued with v11 release.

All other License Key parameters will follow License Key merge rules. Below are merging directions for resulting key: License type: Subscription License expiration: the earliest expiration date of selected Instance Subscriptions License Keys Support expiration: the earliest support expiration date of all involved licenses Support ID: Socket Perpetual License Key with the earliest support expiration date.

License Auto-update. Customers who enable the license auto-update feature will benefit from having automatic installation of Software updates and version upgrades, if their Subscription or Support and Maintenance Agreement is current.

If separate environments are merged, please contact support to understand how this will affect the auto-update function. Legacy Licenses. In case a Customer on maintenance needs a License Key for a legacy product version Veeam may provide such a License Key, with the condition that the License terms and License Units are available for that legacy product version.

Promotional License Key. Promotional licenses do not change any pre-existing licensing agreement for paid products. License Transfer. License Administrator. The End User is responsible for providing correct contact information about License Administrator and keep it up to date. Source Infrastructure. Sharing of the Source Infrastructure between different Licenses and license terms is prohibited.

Post by lolbebis » Wed May 19, am 1 person likes this post. Post by ChrisGundry » Mon Jun 14, pm 1 person likes this post. Post by Gostev » Mon Jun 14, pm this post. Post by alpha1 » Tue Jun 15, pm this post. Post by Regnor » Tue Jun 15, pm this post. Post by Gostev » Tue Jun 15, pm this post. Post by Gostev » Tue Jun 15, pm 2 people like this post.

Post by Regnor » Wed Jun 16, pm this post. Post by pirx » Mon Jul 05, am this post. Post by Gostev » Mon Jul 05, am this post. Users browsing this forum: Google [Bot] and 77 guests. Privacy Terms Cookie Settings. Quick links. Phasing Out our Socket-based Licensing.

Re: Phasing Out our Socket-based Licensing Post by ejenner » Mon May 17, pm 2 people like this post I guess what's going to happen with Veeam will be similar to what has happened with other buyouts over the years. The 'investors' will find a way to milk the cow to death.

When it dies they'll have a lot more 'milk' than they would've had otherwise, it'll be more profitable to get another cow than to have kept the old one going longer just for the nostalgia. I doubt whether anyone who works at Veeam will be able to stop that happening whether they have sound reasoning or not.

Once the engines have failed it's very difficult to get them restarted so best to prepare for the most comfortable possible crash landing. The first customers to take flight will be the small guys watching their costs. Then the large customers who carry out periodic reviews of their arrangements with suppliers, they won't be able to justify the higher cost when there are scores of rivals out there. Last of all will be the gigantic corporates who don't care about money at all, they may not ever change their product and this will keep Veeam alive as a name for however long.

I think anyone looking to justify cost increases must bear in mind many customers already consider Veeam expensive to begin with. This episode reminds me of the time I raised an objection to the massive license consumption of the then new File Server backup function.

I've essentially been told I was incorrect, mine is just an exceptional case so Veeam did nothing wrong. My response is simply not to use that feature if nothing is going to change. To understand what's going on you have to take the view that the new owners of Veeam see their time with Veeam as a temporary involvement, take out as much as possible..

The perfect analogy for this scenario isn't about taking a flight of possibly miles or 10, miles for the same price. It's better illustrated by the story of what happened when Saab was bought by GM, hollowed out and sold as a bankrupt shell which was no longer able to make any cars.

Re: Phasing Out our Socket-based Licensing Post by dsegel » Mon May 17, pm this post Another point - surely not every client is moving to the cloud. For those of us small business sized who won't, this is a negative change for us. Re: Phasing Out our Socket-based Licensing Post by jvlad » Mon May 17, pm this post Every time you think you have a way to save some money, someone has to come around and ruin it because they want a bigger piece of the pie now. I'm with the leave things alone gang of this conversation thread.

I also backup multiple VM that are not powered on as well for various reasons. Will I need to keep paying for these VM even though they are powered off, but i need them backed up to repository and tape every night.

Yeap our standard is to put everything on tape every night.