Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor
-
@pmoncho said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Doesn't the portion you highlighted make every win 10 PC that shares a printer or file share illegal?
No, further down under Device connections, it explains the maximum allowance of that.
-
@dave_c said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@magicmarker said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
What is the typical Veeam backup server OS recommendation for SMB then? Should I be looking at going with a Windows 2016 OS instead?
We always use Windows Server 2016 with ReFS. Another option recommended by Veeam is Windows 10 Pro for Workstations, especially if you are going to use ReFS
Problem is "recommended by Veeam" doesn't mean that you can get a license to do it. That's only for people where MS EULA doesn't apply. Which is a lot of the world (India, China, etc.) but for people in the US and EU and most first world countries, Windows 10 can't be used that way. MS alone determines the usage allowances, not Veeam.
nearly all software vendors do this... they "recommend" super cheap things that are "nearly certain to be a license violation", but since all ethical and legal requirements to use the proper license are on the end user, not on the vendor, they can make those recommendations with impunity.
-
@pmoncho said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@Obsolesce said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Straight from the license.rtf in Windows 10:
Doesn't the portion you highlighted make every win 10 PC that shares a printer or file share illegal?
I could be wrong but "sharing" makes it a server, No?
It absolutely would, if Microsoft didn't give a specific allowance for that one use case, in very limited situations. The license specifically allows that usage.
-
@pmoncho said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Also, if so, isn't Microsoft knowingly telling users to violate its EULA by putting in documentation on how to share pieces of its OS to other users?
No, for loads of reasons. Remember, nearly everything CAN be used for a legit reason some how.
-
@Dashrender said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@DustinB3403 said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@pmoncho no because there is a usable limit that is allowed under the license.
So they aren't saying "go ahead do whatever you want".
it's not a usable limit (that is there too - is it 10 or 20 today?) but file and printer sharing are expressly allowed server functions somewhere else in the eula.
That's connections, not users. The user limit is lower in a practical sense since each user normally uses more than one connection.
-
@Dashrender said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
So here's my question:
Does Veeam do a push or pull type backup? If Veeam is doing a pull only type backup, then how is it acting as a server? The local machine reaches out to the Veeam agent and pulls the backup. I don't see that violating (v).
How would this be any different than using an FTP client to pull data from another server?
If the agent in fact pushes the data - well that's another story.
Pull is still a server. You are thinking of "server" in a limited way that is not how server is defined. No matter how you slice or dice it, this is a Veeam server (hence the name) providing a "service" to machines on the network. Being a device that central pulls their backups is by definition a server.
The point of backups is not for consumption by that workstation. That's the difference between me using FTP on my desktop to download videos or games. That's for me, on that desktop. This is not for use on this desktop, it's for use in a restore operation.
-
@scottalanmiller
Got it. I was speaking on a purely technical way, but that’s a limited view. -
The only really good answer is getting Veeam over to Linux so that this licensing overhead just isn't needed. But it would be a crazy amount of work for them and their customer base, because of their heavy focus on agentless and VMware / Hyper-V is almost purely Windows shops. So the licensing is normally part of an enterprise agreement and really trivial. Those of us affected by the cost of the licensing are not their bread and butter customers.
-
@scottalanmiller said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
The only really good answer is getting Veeam over to Linux so that this licensing overhead just isn't needed. But it would be a crazy amount of work for them and their customer base, because of their heavy focus on agentless and VMware / Hyper-V is almost purely Windows shops. So the licensing is normally part of an enterprise agreement and really trivial. Those of us affected by the cost of the licensing are not their bread and butter customers.
SInce so much of what we talk about here at ML is Linux-based, I was shocked there wasn't a solution there for a Veeam setup. But what you say here makes perfect sense.
-
Veeam leverages too many windows technologies currently. Hence, I run it on Server 2012r2
-
@BRRABill Nakivo, URBackup... lots of options. Just not from Veeam. Which is too bad as Veeam is amazing.
-
@scottalanmiller said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@BRRABill Nakivo, URBackup... lots of options. Just not from Veeam. Which is too bad as Veeam is amazing.
Right. I know everyone loves it.
-
@scottalanmiller said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@dave_c said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@magicmarker said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
What is the typical Veeam backup server OS recommendation for SMB then? Should I be looking at going with a Windows 2016 OS instead?
We always use Windows Server 2016 with ReFS. Another option recommended by Veeam is Windows 10 Pro for Workstations, especially if you are going to use ReFS
Problem is "recommended by Veeam" doesn't mean that you can get a license to do it. That's only for people where MS EULA doesn't apply.
...Just found this on http://www.veeam.com/veeam_backup_9_5_whats_new_wn.pdf (page 5)
Instant recovery of agent backups to a Hyper-V VM now support Windows 10 Hyper-V as the target hypervisor. This is particularly useful for managed service providers by enabling them to create low-cost all-in-one BCDR appliances to deploy at their clients’ premises.It seems like Veeam doesn't care about MS EULA. Or perhaps I'm missing an exception in the EULA
-
@dave_c said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@scottalanmiller said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@dave_c said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@magicmarker said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
What is the typical Veeam backup server OS recommendation for SMB then? Should I be looking at going with a Windows 2016 OS instead?
We always use Windows Server 2016 with ReFS. Another option recommended by Veeam is Windows 10 Pro for Workstations, especially if you are going to use ReFS
Problem is "recommended by Veeam" doesn't mean that you can get a license to do it. That's only for people where MS EULA doesn't apply.
...Just found this on http://www.veeam.com/veeam_backup_9_5_whats_new_wn.pdf (page 5)
Instant recovery of agent backups to a Hyper-V VM now support Windows 10 Hyper-V as the target hypervisor. This is particularly useful for managed service providers by enabling them to create low-cost all-in-one BCDR appliances to deploy at their clients’ premises.It seems like Veeam doesn't care about MS EULA. Or perhaps I'm missing an exception in the EULA
This should be totally ok, as long as they are only used on that local machine, and not served as servers to others on the network (and it's licensed as required).
-
Just remember that per the Win10 EULA, you can only virtualize Win10 if it's the only licensed Windows VM.
I don't have it in front of me to verify, but that's what I remember reading on there. Will verify a bit later.
-
Nothing in that says it is running Windows 10 guests. It is using Hyper-V on Windows 10 for temporary DR.
-
@dave_c of course Veeam doesnt care. EuLA is your problem to deal with. Has nothing to do with them.
We already stated that.
-
@Obsolesce said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Just remember that per the Win10 EULA, you can only virtualize Win10 if it's the only licensed Windows VM.
I don't have it in front of me to verify, but that's what I remember reading on there. Will verify a bit later.
Thats not the issue. And not the case. VDI licensing gets you around that. But nothing gets you around the no-server use EULA.
-
@scottalanmiller said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@Obsolesce said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Just remember that per the Win10 EULA, you can only virtualize Win10 if it's the only licensed Windows VM.
I don't have it in front of me to verify, but that's what I remember reading on there. Will verify a bit later.
Thats not the issue. And not the case. VDI licensing gets you around that. But nothing gets you around the no-server use EULA.
Did not know VDI was involved in the OPs case.
-
@Obsolesce said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@scottalanmiller said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@Obsolesce said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Just remember that per the Win10 EULA, you can only virtualize Win10 if it's the only licensed Windows VM.
I don't have it in front of me to verify, but that's what I remember reading on there. Will verify a bit later.
Thats not the issue. And not the case. VDI licensing gets you around that. But nothing gets you around the no-server use EULA.
Did not know VDI was involved in the OPs case.
Its the licensing for more than one Windows workstation on a server.
