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:
@JaredBusch 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:
@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.
This would be easy to do. I've got available decommissioned Win 7 physical pc's that I can just note the product key is being used for the Veeam Win 10 VM.
Not OEM license on those
OEM Win 7 keys on the physical boxes. I'm going to need retail keys instead correct?
You are missing the points. You caught that OEM can't be moved, but other things can, and are missing that even if you can move them, you can't use Windows 10 this way. So you are asking questions that don't make any sense as they don't have any bearing on your resulting options.
-
@magicmarker said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Was really planning on installing the Veeam server as a Win 10 VM. Going back to the drawing board now. Looks like I'm either going to have to install the Veeam box on a physical Win 10 pc...
That won't change that Windows 10 cannot be licensed for use as a server. The Veeam process running on there is a server workload. Check your Windows 10 EULA, it'll tell you that that kind of usage is verboten.
-
@magicmarker said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Edit: A third option may be purchasing a Win 10 retail license and then "move" that license to the VM for paper trail purpose as @JaredBusch mentioned.
No, that's not an option. That's an option to get Windows 10 virtualized, not an option for using it as a server.
-
@magicmarker said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:
Not sure what makes more sense at the moment. Anyone else deploying Veeam servers as physical pc's?
Only getting Server licensing makes sense, as all of the other options violate the license and you might as well just pirate it, because it's not licensed once you misuse it.
No one is doing physical PCs, because it doesn't solve anything. If you are going to pirate it, you might as well pirate it well. If you aren't going to pirate it, then you get VM licensing naturally and there is no issue to solve. It's a bizarre middle ground where you would want to violate the license, but in a way that doesn't result in a good setup. Logically, that just doesn't make sense regardless of the ethical philosophies involved.
-
@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.
-
Straight from the license.rtf in Windows 10:
-
@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.
-
@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.
-
@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.
A lot of the same people involved.
-
@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".
