[NFR] Getting a new NFR key after the existing one expires

[eider]

No, we never had any limitations like that, you can keep renewing your NFR license every year. This is essential to enable you to keep using the latest Veeam version in your lab, which is the only point of providing an NFR license.

Factually incorrect. Attempting to acquire another NFR license after its expiration period will result in email being sent with old license that is already expired, or no email at all. Only by waiting for about another half a year does this get lifted and you will be able to acquire new license. Ask me how I know :>

Countless other reports as such:
- veeam-backup-replication-f2/getting-a-n ... 99161.html
- https://www.reddit.com/r/homelab/commen ... r_license/
- https://www.null-byte.org/homelab/veeam ... 4-onwards/
- https://www.reddit.com/r/Veeam/comments ... _licenses/
- https://www.reddit.com/r/Veeam/comments ... nses_dead/
- https://www.reddit.com/r/Veeam/comments ... wal_issue/

I can't find the thread from Veeam Community anymore, but I was told in no uncertain terms that I will not be given another NFR license unless I prove that I am working for a company that does business with Veeam. Now, we can of course play hide-and-seek by making new email addresses and/or domains, but please do not mislead us that nothing has changed.

--- EDIT ---

Found other Veeam Community thread here: https://community.veeam.com/blogs-and-p ... ndex3.html

If you don't trust me, maybe trust your fellow Veeam Employee :>

[Gostev]

Madalina is a community manager, she has nothing to deal with licensing so her responses in that regard are not necessarily authoritative.

Also, nobody says there couldn't not be a bug in certain scenarios. If you are personally experiencing it, PM me your "old" license that has already expired and the exact time of your attempt to get a new one (within last 24 hours). I will then ask the responsible department to look up your attempt in the server logs and see what went wrong and why the system sends the already expired license.

By all means it sounds like a bug in some corner case because the licence is actually being sent, but it is already expired which makes sending it completely pointless. The standard workflow in case of restrictions is to display a message explaining why you are not eligible for something. But since backend does send a licence, this can only mean it erroneously "thinks" that it is still valid.