Hello, one of our partner sites is using the Essentials Edition and currently has 30 licenses.
15 for VMs
1 for Physical server
13.8 for NAS spread over 5 jobs. It lists as 30 of 30 licenses in use.
But here is the breakdown of the 5 NAS jobs license counts:
10.1
1.6
2.1
The curious part is if each license instance is 1=250 GB why are there decimals in the count?
Also, the other two jobs are below 250 GB so it seems they are not listed but most likely are taking up .1 each or what ?
And, I have watched those licenses adjust slightly over time but I am not seeing any warnings of going over the limit as the jobs run.
Sometimes the above jobs would show:
10.3
1.5
2
Is there a clear cut way to know if anything is not being backed up? We also run VeeamOne and see no errors except once on initial deploy but no repeat even after clearing the alarm.
Also, why aren't the other two NAS jobs listed in the License Management section since fractions are being used?
It would be great to see in the daily jobs how many licenses are being used by the job each time it runs so we can see if there is any issues with the math or operations.
thanks,
William
-
- Enthusiast
- Posts: 38
- Liked: 8 times
- Joined: Mar 11, 2019 6:19 pm
- Full Name: Bill Bohn
- Contact:
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Tracking license use fluctuating with NAS
We'll investigate those decimal parts... probably they are there because devs track consumption per share precisely, and then to calculate total consumption they sum all those value up and only then round the result.
If the job protects less than 250GB of data, then it does not consume a license. So, it's normal those shares are not listed in the list of workloads not consuming a license.
If anything is not being backed up, the file backup job session's will have the corresponding record at the end.
Seeing "how many licenses are being used by the job each time it runs" is not possible, because this is not how licensing works. We license protected data, where data considered protected if it has at least one restore point in the last 31 days (you can refer to the licensing policy for more information). In other words, even if a given job run does not back up anything (because the share it is backing up has just been emptied), it will not affect license consumption for this share for another 30 days.
Thanks!
If the job protects less than 250GB of data, then it does not consume a license. So, it's normal those shares are not listed in the list of workloads not consuming a license.
If anything is not being backed up, the file backup job session's will have the corresponding record at the end.
Seeing "how many licenses are being used by the job each time it runs" is not possible, because this is not how licensing works. We license protected data, where data considered protected if it has at least one restore point in the last 31 days (you can refer to the licensing policy for more information). In other words, even if a given job run does not back up anything (because the share it is backing up has just been emptied), it will not affect license consumption for this share for another 30 days.
Thanks!
-
- Enthusiast
- Posts: 38
- Liked: 8 times
- Joined: Mar 11, 2019 6:19 pm
- Full Name: Bill Bohn
- Contact:
Re: Tracking license use fluctuating with NAS
Thanks for the confirmation that no error equals all is ok. We wanted confirmation on that before planning to buy more licenses (as in, knowing what we really need instead of guessing)
Have a great day
Have a great day
Who is online
Users browsing this forum: No registered users and 4 guests