I can't even
-
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
-
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
-
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
Correct.
-
Although I don't know personally that Hyper-V Replica requires a license, only that replicas themselves don't. I've not seen any docs about Hyper-V's technology needing it specifically.
https://community.spiceworks.com/topic/465839-do-i-need-a-windows-license-for-a-virtual-replica
I'd like to see where MS lists there being a need for the replica process to have a license.
-
Everyone states that you need a license, but they always include the assumption that you will turn it on. I've searched and never found any MS statements that say that backups in that state need a license. I have a feeling it's not needed for Hyper-V Replica, either.
-
@scottalanmiller said in I can't even:
Although I don't know personally that Hyper-V Replica requires a license, only that replicas themselves don't. I've not seen any docs about Hyper-V's technology needing it specifically.
https://community.spiceworks.com/topic/465839-do-i-need-a-windows-license-for-a-virtual-replica
I'd like to see where MS lists there being a need for the replica process to have a license.
Yeah, you have a good point, and that would seem strange, because it does basically mean that Hyper-V does require a license to do things.
-
@scottalanmiller said in I can't even:
Everyone states that you need a license, but they always include the assumption that you will turn it on. I've searched and never found any MS statements that say that backups in that state need a license. I have a feeling it's not needed for Hyper-V Replica, either.
So, what does SA give you in this situation then?
-
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
Everyone states that you need a license, but they always include the assumption that you will turn it on. I've searched and never found any MS statements that say that backups in that state need a license. I have a feeling it's not needed for Hyper-V Replica, either.
So, what does SA give you in this situation then?
The ability to fire it up.
-
@scottalanmiller said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
Correct.
If you have Hyper-V HOST1 and Hyper-V HOST2, and you replicate VM1 between them, you need a license for the replica, no matter what.
-
@tim_g said in I can't even:
@scottalanmiller said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
Correct.
If you have Hyper-V HOST1 and Hyper-V HOST2, and you replicate VM1 between them, you need a license for the replica, no matter what.
And if you back up VM1 to BACKUPSERV1, no license needed. The backup of VM1 is not a Hyper-V Replica, it's just a "dumb" .vhdx file you can't do anything with, and is not "attached" to Hyper-V Replication.
-
@tim_g said in I can't even:
@tim_g said in I can't even:
@scottalanmiller said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
Correct.
If you have Hyper-V HOST1 and Hyper-V HOST2, and you replicate VM1 between them, you need a license for the replica, no matter what.
And if you back up VM1 to BACKUPSERV1, no license needed. The backup of VM1 is not a Hyper-V Replica, it's just a "dumb" .vhdx file you can't do anything with, and is not "attached" to Hyper-V Replication.
In this scenario, there are 3 VM1.vhdx files. Two of them are in Hyper-V replication of one-another. The third is not.
-
@scottalanmiller said
but they always include the assumption that you will turn it on.
If a server is in the woods, but is never turned on, is it really a server?
-
@tim_g said in I can't even:
@scottalanmiller said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
Correct.
If you have Hyper-V HOST1 and Hyper-V HOST2, and you replicate VM1 between them, you need a license for the replica, no matter what.
Not quite. There are many ways that I can replicate a VM to another server that do not involve using the built in replication method.
It is very specifically the use of the Hyper-V Replication function within Hyper-V that requires SA to be allowed to replicate a VM to another server.
-
@scottalanmiller said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
Everyone states that you need a license, but they always include the assumption that you will turn it on. I've searched and never found any MS statements that say that backups in that state need a license. I have a feeling it's not needed for Hyper-V Replica, either.
So, what does SA give you in this situation then?
The ability to fire it up.
Incorrect. You do gain that allowance also. But SA also grants you the use of the Hyper-V Replication functions to create the replica.
-
@tim_g said in I can't even:
@scottalanmiller said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
Correct.
If you have Hyper-V HOST1 and Hyper-V HOST2, and you replicate VM1 between them, you need a license for the replica, no matter what.
What do you mean? You absolutely don't need any license for what you described. The act of replication never requires a license from MS - no matter what. That's not something that MS licenses.
-
@tim_g said in I can't even:
@tim_g said in I can't even:
@scottalanmiller said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
Correct.
If you have Hyper-V HOST1 and Hyper-V HOST2, and you replicate VM1 between them, you need a license for the replica, no matter what.
And if you back up VM1 to BACKUPSERV1, no license needed. The backup of VM1 is not a Hyper-V Replica, it's just a "dumb" .vhdx file you can't do anything with, and is not "attached" to Hyper-V Replication.
Replica and Dumb file are the same thing. Replica is just a name for a dumb file that includes the entirety of the source in its original format. Once it is anything but that, it's more than a replica.
-
@tim_g said in I can't even:
@tim_g said in I can't even:
@tim_g said in I can't even:
@scottalanmiller said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
@tim_g said in I can't even:
@bnrstnr said in I can't even:
How the F does a turned off computer/VM need to be licensed? Does this mean that full backups of VMs each need their own licenses?! If so, I'm so screwed on licenses...
No, just Hyper-V Replicas.
Whatever you are replicating in Hyper-V Manager that is actually a Hyper-V Replica...
A huge key here...
Hyper-V Replica requires a license.
A Hyper-V replica does not.Semantics, that capital letter matters.
So use Veeam to replicate and you're golden.
Correct.
If you have Hyper-V HOST1 and Hyper-V HOST2, and you replicate VM1 between them, you need a license for the replica, no matter what.
And if you back up VM1 to BACKUPSERV1, no license needed. The backup of VM1 is not a Hyper-V Replica, it's just a "dumb" .vhdx file you can't do anything with, and is not "attached" to Hyper-V Replication.
In this scenario, there are 3 VM1.vhdx files. Two of them are in Hyper-V replication of one-another. The third is not.
All are replicas equally. Replica, backup, dumb file... all one and the same. The concepts of one server being Hyper-V and one being a backup server are purely human designations. Every Hyper-V server can store backups (replicas) and any given backup server might run on Hyper-V.
All of these things overlap.
To show it another way, since it is ONLY a replica on the second Hyper-V server, just called it a backup server, because it is. Does that explain why no license is needed? The Hyper-V server is a backup server, too.
-
I was actually consulting on a backup design just yesterday where we were using Hyper-V in exactly this way as a backup target, but building the backup system using Starwind. It was a backup device in every way, no expectation of VMs to run there, no live systems ever, just Hyper-V + Starwind used to handle the replica-based file backups.
-
@jaredbusch said in I can't even:
It is very specifically the use of the Hyper-V Replication function within Hyper-V that requires SA to be allowed to replicate a VM to another server.
Do you have the reference on that? I've heard it so much that I keep assuming that it is true, but I realized today that I've not been able to actually find anything that says that. It's all something I've heard from a third party and I wonder if it isn't the same misquoting that we get about replicas in general.
-
@brrabill said in I can't even:
@scottalanmiller said
but they always include the assumption that you will turn it on.
If a server is in the woods, but is never turned on, is it really a server?
Nope, and that's the rub. It's just metal.
