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:
@scottalanmiller 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:
@scottalanmiller Really wish Veeam would do a linux appliance for the backup server. Veeam allows the backup software to install on a Win 10 OS. I get it though, I need to install it on a Server 2016 VM. Thanks for you input.
Me too, Veeam would really benefit from that. BUT, tons of their features exist by leverage Windows features under the hood to make the magic happen. So unfortunately, Windows Server licensing is just part of the Veeam ecosystem. Veeam is amazing, but this is a key factor as to why we don't just use it across the board. The cost of Veeam plus the often needed cost of Windows can make it pretty formidable for many SMBs.
I've already committed to Veeam, but after I committed, I found Nakivo which runs the backup server on a linux box. Seems like a good competitor to Veeam.
I set up the Veeam server on a stand alone server running Windows Server 2016 w/SA, backup repository elsewhere. On-prem backups (in backup repo) get thrown on to tape on a schedule, and have a few tape sets that rotate off-site.
-
@Obsolesce 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:
@scottalanmiller 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:
@scottalanmiller Really wish Veeam would do a linux appliance for the backup server. Veeam allows the backup software to install on a Win 10 OS. I get it though, I need to install it on a Server 2016 VM. Thanks for you input.
Me too, Veeam would really benefit from that. BUT, tons of their features exist by leverage Windows features under the hood to make the magic happen. So unfortunately, Windows Server licensing is just part of the Veeam ecosystem. Veeam is amazing, but this is a key factor as to why we don't just use it across the board. The cost of Veeam plus the often needed cost of Windows can make it pretty formidable for many SMBs.
I've already committed to Veeam, but after I committed, I found Nakivo which runs the backup server on a linux box. Seems like a good competitor to Veeam.
I set up the Veeam server on a stand alone server running Windows Server 2016 w/SA, backup repository elsewhere. On-prem backups (in backup repo) get thrown on to tape on a schedule, and have a few tape sets that rotate off-site.
I have it on a 2012 R2 VM with the backup repo on a Synology DS3617+
-
@magicmarker
We use the Nakivo appliance it works well. -
@Coreytay I wish I would have known about them sooner. I played around with the trial license and was impressed.
-
@magicmarker said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@Coreytay I wish I would have known about them sooner. I played around with the trial license and was impressed.
Not sure what type of vm's you're looking to backup...Have you looked at Altaro VM Backup?
-
@JaredBusch said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
My long time understanding is no.
There is no license being upgraded when you are using a new VM like this.
Now, do you have a piece of hardware with a non OEM license that you can decommission and "move" the license to the hypervisor host? That would make it legal.
Obviously move is a fake term for paper trail purposes. You do not have to actually P2V anything. Just mark that license as "used" by the Win 10 instance.
Technically you can't move the license like this. . . so no that isn't legal.
-
@DustinB3403 said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
@JaredBusch said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
My long time understanding is no.
There is no license being upgraded when you are using a new VM like this.
Now, do you have a piece of hardware with a non OEM license that you can decommission and "move" the license to the hypervisor host? That would make it legal.
Obviously move is a fake term for paper trail purposes. You do not have to actually P2V anything. Just mark that license as "used" by the Win 10 instance.
Technically you can't move the license like this. . . so no that isn't legal.
Yes you can. Non-OEM as noted.
-
My favorite backup software is SCDPM. Nothing that I've tried comes close in almost every aspect, and I've used and evaluated Many. But the costs of it and associated costs are high for SMB.
-
@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
-
@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?
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?
-
@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".
-
@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".
Makes much more sense now.
-
@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?
Lower down, in d. iii, it specifically lists file and printer services as exceptions.
-
@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.
-
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.
-
@Dashrender what @pmoncho asked was "Doesn't the portion you highlighted make every win 10 PC that shares a printer or file share illegal?"
And there is a limit to the number of concurrent connections.
From SAM on SpiteWorks
"There is no user limit nor necessarily even a way for the OS to know. Modern Windows desktops have a 20 concurrent connection limit which means effectively figure ten or fewer users or machines connected. And this refers to all kinds of things, not just things you might picture like RDP and SMB protocols.
Pretty much if you need to worry about this, you have a design flaw"
-
@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.
