I can't even
-
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@jaredbusch said in I can't even:
@tim_g said in I can't even:
@jaredbusch said in I can't even:
@Tim_G everything you link is referring to Hyper-V replication. It is understood that using Hyper-V to replicate requires SA or full licensing on both servers.
What does it matter which program you use for VM replication? That doesn't change anything at all.
That's like saying you only need volume licensing to image desktops if you use WDS, and not if you use another OS imaging solution...
It absolutely does. We are talking about using a tool that requires a license to copy files versus a tool that does not require a license to copy files.
@Tim_G 's argument is that regardless of tool it still requires a license.
Right, and Scott's argument earlier was that it was the Replication tool inside Hyper-V that was being licensed, but has since turned 180 and feels that as long as the copy/backup/replica isn't started, no license at all is required.
Huh? That's not how I read that side of the argument. I don't really want to go through the thread again though so I'll take your word for it. It's been an interesting conversation for sure. Amazing that the intentional licensing ambiguities can create two completely different ideas on this.
https://i.imgur.com/gi0hPcy.png
I'm not sure how else to read that. There there are around 50 more posts talking about this point, but I don't think anything definitive was provided.
Right, that you don't need licensing for backups is how I read that. That there has been little to no actual documentation on it leaves a lot to be desired though.
and scott is calling a replica the same as a backup, as long as you never turn it on.
Is a license needed for warm backups? That's what Microsoft considers data "replication"... but where I seen that was not in the context of virtualization or Hyper-V.
-
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@jaredbusch said in I can't even:
@tim_g said in I can't even:
@jaredbusch said in I can't even:
@Tim_G everything you link is referring to Hyper-V replication. It is understood that using Hyper-V to replicate requires SA or full licensing on both servers.
What does it matter which program you use for VM replication? That doesn't change anything at all.
That's like saying you only need volume licensing to image desktops if you use WDS, and not if you use another OS imaging solution...
It absolutely does. We are talking about using a tool that requires a license to copy files versus a tool that does not require a license to copy files.
@Tim_G 's argument is that regardless of tool it still requires a license.
Right, and Scott's argument earlier was that it was the Replication tool inside Hyper-V that was being licensed, but has since turned 180 and feels that as long as the copy/backup/replica isn't started, no license at all is required.
Huh? That's not how I read that side of the argument. I don't really want to go through the thread again though so I'll take your word for it. It's been an interesting conversation for sure. Amazing that the intentional licensing ambiguities can create two completely different ideas on this.
https://i.imgur.com/gi0hPcy.png
I'm not sure how else to read that. There there are around 50 more posts talking about this point, but I don't think anything definitive was provided.
Right, that you don't need licensing for backups is how I read that. That there has been little to no actual documentation on it leaves a lot to be desired though.
and scott is calling a replica the same as a backup, as long as you never turn it on.
I think it comes down to the questions I asked here: https://mangolassi.it/post/361143
The only thing that matters is whether or not it's considered an OSE, which OSEs needing licensed is documented clearly all over the place on Microsoft documentation.
-
I should print the last day or so of this thread, and when presented with the question of "What's the cost of Winodws?" provide the printout.
-
@eddiejennings said in I can't even:
I should print the last day or so of this thread, and when presented with the question of "What's the cost of Winodws?" provide the printout.
Capital idea!
-
@tim_g said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@jaredbusch said in I can't even:
@tim_g said in I can't even:
@jaredbusch said in I can't even:
@Tim_G everything you link is referring to Hyper-V replication. It is understood that using Hyper-V to replicate requires SA or full licensing on both servers.
What does it matter which program you use for VM replication? That doesn't change anything at all.
That's like saying you only need volume licensing to image desktops if you use WDS, and not if you use another OS imaging solution...
It absolutely does. We are talking about using a tool that requires a license to copy files versus a tool that does not require a license to copy files.
@Tim_G 's argument is that regardless of tool it still requires a license.
Right, and Scott's argument earlier was that it was the Replication tool inside Hyper-V that was being licensed, but has since turned 180 and feels that as long as the copy/backup/replica isn't started, no license at all is required.
Huh? That's not how I read that side of the argument. I don't really want to go through the thread again though so I'll take your word for it. It's been an interesting conversation for sure. Amazing that the intentional licensing ambiguities can create two completely different ideas on this.
https://i.imgur.com/gi0hPcy.png
I'm not sure how else to read that. There there are around 50 more posts talking about this point, but I don't think anything definitive was provided.
Right, that you don't need licensing for backups is how I read that. That there has been little to no actual documentation on it leaves a lot to be desired though.
and scott is calling a replica the same as a backup, as long as you never turn it on.
I think it comes down to the questions I asked here: https://mangolassi.it/post/361143
The only thing that matters is whether or not it's considered an OSE, which OSEs needing licensed is documented clearly all over the place on Microsoft documentation.
If that's true, then every backup that can be instantly turn on is an OSE, and they all need to be licensed as well - and I just don't think that's right. i.e. unitrends appliances would need licenses.
-
@dashrender said in I can't even:
@tim_g said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@jaredbusch said in I can't even:
@tim_g said in I can't even:
@jaredbusch said in I can't even:
@Tim_G everything you link is referring to Hyper-V replication. It is understood that using Hyper-V to replicate requires SA or full licensing on both servers.
What does it matter which program you use for VM replication? That doesn't change anything at all.
That's like saying you only need volume licensing to image desktops if you use WDS, and not if you use another OS imaging solution...
It absolutely does. We are talking about using a tool that requires a license to copy files versus a tool that does not require a license to copy files.
@Tim_G 's argument is that regardless of tool it still requires a license.
Right, and Scott's argument earlier was that it was the Replication tool inside Hyper-V that was being licensed, but has since turned 180 and feels that as long as the copy/backup/replica isn't started, no license at all is required.
Huh? That's not how I read that side of the argument. I don't really want to go through the thread again though so I'll take your word for it. It's been an interesting conversation for sure. Amazing that the intentional licensing ambiguities can create two completely different ideas on this.
https://i.imgur.com/gi0hPcy.png
I'm not sure how else to read that. There there are around 50 more posts talking about this point, but I don't think anything definitive was provided.
Right, that you don't need licensing for backups is how I read that. That there has been little to no actual documentation on it leaves a lot to be desired though.
and scott is calling a replica the same as a backup, as long as you never turn it on.
I think it comes down to the questions I asked here: https://mangolassi.it/post/361143
The only thing that matters is whether or not it's considered an OSE, which OSEs needing licensed is documented clearly all over the place on Microsoft documentation.
If that's true, then every backup that can be instantly turn on is an OSE, and they all need to be licensed as well - and I just don't think that's right. i.e. unitrends appliances would need licenses.
No, because backups are cold. Replication is warm. Does a warm backup of an OS count as an OSE that needs licensed?
-
@tim_g said in I can't even:
@dashrender said in I can't even:
@tim_g said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@dashrender said in I can't even:
@coliver said in I can't even:
@jaredbusch said in I can't even:
@tim_g said in I can't even:
@jaredbusch said in I can't even:
@Tim_G everything you link is referring to Hyper-V replication. It is understood that using Hyper-V to replicate requires SA or full licensing on both servers.
What does it matter which program you use for VM replication? That doesn't change anything at all.
That's like saying you only need volume licensing to image desktops if you use WDS, and not if you use another OS imaging solution...
It absolutely does. We are talking about using a tool that requires a license to copy files versus a tool that does not require a license to copy files.
@Tim_G 's argument is that regardless of tool it still requires a license.
Right, and Scott's argument earlier was that it was the Replication tool inside Hyper-V that was being licensed, but has since turned 180 and feels that as long as the copy/backup/replica isn't started, no license at all is required.
Huh? That's not how I read that side of the argument. I don't really want to go through the thread again though so I'll take your word for it. It's been an interesting conversation for sure. Amazing that the intentional licensing ambiguities can create two completely different ideas on this.
https://i.imgur.com/gi0hPcy.png
I'm not sure how else to read that. There there are around 50 more posts talking about this point, but I don't think anything definitive was provided.
Right, that you don't need licensing for backups is how I read that. That there has been little to no actual documentation on it leaves a lot to be desired though.
and scott is calling a replica the same as a backup, as long as you never turn it on.
I think it comes down to the questions I asked here: https://mangolassi.it/post/361143
The only thing that matters is whether or not it's considered an OSE, which OSEs needing licensed is documented clearly all over the place on Microsoft documentation.
If that's true, then every backup that can be instantly turn on is an OSE, and they all need to be licensed as well - and I just don't think that's right. i.e. unitrends appliances would need licenses.
No, because backups are cold. Replication is warm. Does a warm backup of an OS count as an OSE that needs licensed?
Unitrends can be warm backups from that POV.
-
@scottalanmiller said in I can't even:
Straight from the MS docs.
As MS makes clear, SA doesn't cover cold backups, but only cold backups that have additionally been set up for disaster recovery purposes only. They make it clear that standard replicas that are kept cold need no license.
My definition, industry definition, MS definition - all agree. I got it from this originally.
So a warm backup requires turning it on to receive backups of data from prod server. Then they list mirroring, replication, and log shipping.
But replication does not require turning the VM on, soooo.... replication is an exception to the turning on rule?
-
Can we create a post regarding the Microsoft Licensing to a Topic so we don't derail this whole thread more? Just a recommendation.
-
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
Straight from the MS docs.
As MS makes clear, SA doesn't cover cold backups, but only cold backups that have additionally been set up for disaster recovery purposes only. They make it clear that standard replicas that are kept cold need no license.
My definition, industry definition, MS definition - all agree. I got it from this originally.
So a warm backup requires turning it on to receive backups of data from prod server. Then they list mirroring, replication, and log shipping.
But replication does not require turning the VM on, soooo.... replication is an exception to the turning on rule?
So am I to understand that if I have VEEAM set up to replicate I need a license for both the Production and the replicated backup?
-
Now we need to know what MS classifies as replication - is an hourly backup to Unitrends considered replication - especially in light of the fact that the VM can be started on the Unitrends box in case of DR?
This definition of warm definitely tells us that continuous backup is not required to be consider warm - only periodical.
-
@wls-itguy said in I can't even:
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
Straight from the MS docs.
As MS makes clear, SA doesn't cover cold backups, but only cold backups that have additionally been set up for disaster recovery purposes only. They make it clear that standard replicas that are kept cold need no license.
My definition, industry definition, MS definition - all agree. I got it from this originally.
So a warm backup requires turning it on to receive backups of data from prod server. Then they list mirroring, replication, and log shipping.
But replication does not require turning the VM on, soooo.... replication is an exception to the turning on rule?
So am I to understand that if I have VEEAM set up to replicate I need a license for both the Production and the replicated backup?
That is the point of this discussion.
Which at this point should really be ripped out of the I can't even thread and put in it's own. -
@dashrender said in I can't even:
@scottalanmiller said in I can't even:
Straight from the MS docs.
As MS makes clear, SA doesn't cover cold backups, but only cold backups that have additionally been set up for disaster recovery purposes only. They make it clear that standard replicas that are kept cold need no license.
My definition, industry definition, MS definition - all agree. I got it from this originally.
So a warm backup requires turning it on to receive backups of data from prod server. Then they list mirroring, replication, and log shipping.
But replication does not require turning the VM on, soooo.... replication is an exception to the turning on rule?
The thing is this... that document is from 2004 and is not in the context of Hyper-V or VM replication. But I don't see anything else to go by, because everything else is in the context of the Software Assurance "disaster recovery" benefit.
All we can do is is assume, because nothing is clear. Is VM replication considered a warm backup? Is it an OSE? Is it an OSE that needs licensed?
I'm right in the middle of it all. I honestly don't care, because I either replicate SA-binded VMs, or to a DC hypervisor... so I'm covered by licensing anyways. But in the weird cases where people aren't using appropriate licensing... who knows.
I can side with Scott easily, and i can also not side with Scott easily. It depends on how you view it all. Do you consider an actively replicating VM "just a cold backup file" that is not considered by Microsoft to be an OSE that needs licensed?
-
@tim_g said in I can't even:
Do you consider an actively replicating VM "just a cold backup file" that is not considered by Microsoft to be an OSE that needs licensed?
At this point I do consider it a cold backup file. And therefore requires no more licensing than a backup does, i.e. no SA or other Windows Server Licensing. Now, once you turn it on, all bets are off. To turn it on, you need SA for DR benefits.
-
@dashrender said in I can't even:
@tim_g said in I can't even:
Do you consider an actively replicating VM "just a cold backup file" that is not considered by Microsoft to be an OSE that needs licensed?
At this point I do consider it a cold backup file. And therefore requires no more licensing than a backup does, i.e. no SA or other Windows Server Licensing. Now, once you turn it on, all bets are off. To turn it on, you need SA for DR benefits.
That's how I used to think of it too, even though it doesn't matter in my current environment.
But after reading all of the information out there from reputable sources saying otherwise, I started looking at it differently.
Mainly this part: "If you don't need any additional licensing for VM replication, then why is it part of a benefit of Software Assurance in any context?"... I can see having the ability to "run" the replica as part of it... and another being an OSE is an "Instance means an image of software that is created by executing the software’s setup or install procedure or by duplicating an existing Instance."
Microsoft's own documentation is full of contradiction and vagueness.
-
@tim_g said in I can't even:
@dashrender said in I can't even:
@tim_g said in I can't even:
Do you consider an actively replicating VM "just a cold backup file" that is not considered by Microsoft to be an OSE that needs licensed?
At this point I do consider it a cold backup file. And therefore requires no more licensing than a backup does, i.e. no SA or other Windows Server Licensing. Now, once you turn it on, all bets are off. To turn it on, you need SA for DR benefits.
That's how I used to think of it too, even though it doesn't matter in my current environment.
But after reading all of the information out there from reputable sources saying otherwise, I started looking at it differently.
Mainly this part: "If you don't need any additional licensing for VM replication, then why is it part of a benefit of Software Assurance in any context?"... I can see having the ability to "run" the replica as part of it... and another being an OSE is an "Instance means an image of software that is created by executing the software’s setup or install procedure or by duplicating an existing Instance."
Microsoft's own documentation is full of contradiction and vagueness.
Right but by those definitions, any backup is an image of an instance.
-
@dashrender said in I can't even:
@tim_g said in I can't even:
@dashrender said in I can't even:
@tim_g said in I can't even:
Do you consider an actively replicating VM "just a cold backup file" that is not considered by Microsoft to be an OSE that needs licensed?
At this point I do consider it a cold backup file. And therefore requires no more licensing than a backup does, i.e. no SA or other Windows Server Licensing. Now, once you turn it on, all bets are off. To turn it on, you need SA for DR benefits.
That's how I used to think of it too, even though it doesn't matter in my current environment.
But after reading all of the information out there from reputable sources saying otherwise, I started looking at it differently.
Mainly this part: "If you don't need any additional licensing for VM replication, then why is it part of a benefit of Software Assurance in any context?"... I can see having the ability to "run" the replica as part of it... and another being an OSE is an "Instance means an image of software that is created by executing the software’s setup or install procedure or by duplicating an existing Instance."
Microsoft's own documentation is full of contradiction and vagueness.
Right but by those definitions, any backup is an image of an instance.
Yeah, which doesn't make sense, and is exactly my point.
-
@dashrender said in I can't even:
@tim_g said in I can't even:
@dashrender said in I can't even:
@tim_g said in I can't even:
Do you consider an actively replicating VM "just a cold backup file" that is not considered by Microsoft to be an OSE that needs licensed?
At this point I do consider it a cold backup file. And therefore requires no more licensing than a backup does, i.e. no SA or other Windows Server Licensing. Now, once you turn it on, all bets are off. To turn it on, you need SA for DR benefits.
That's how I used to think of it too, even though it doesn't matter in my current environment.
But after reading all of the information out there from reputable sources saying otherwise, I started looking at it differently.
Mainly this part: "If you don't need any additional licensing for VM replication, then why is it part of a benefit of Software Assurance in any context?"... I can see having the ability to "run" the replica as part of it... and another being an OSE is an "Instance means an image of software that is created by executing the software’s setup or install procedure or by duplicating an existing Instance."
Microsoft's own documentation is full of contradiction and vagueness.
Right but by those definitions, any backup is an image of an instance.
By ANY definition, backups are an image. At least image based backups. Which is important, because relicas aren't special snowflakes, they are normal and fall under normal licensing rules making them very easy to deal with.
-
@dashrender said in I can't even:
@coliver said in I can't even:
@jaredbusch said in I can't even:
@tim_g said in I can't even:
@jaredbusch said in I can't even:
@Tim_G everything you link is referring to Hyper-V replication. It is understood that using Hyper-V to replicate requires SA or full licensing on both servers.
What does it matter which program you use for VM replication? That doesn't change anything at all.
That's like saying you only need volume licensing to image desktops if you use WDS, and not if you use another OS imaging solution...
It absolutely does. We are talking about using a tool that requires a license to copy files versus a tool that does not require a license to copy files.
@Tim_G 's argument is that regardless of tool it still requires a license.
Right, and Scott's argument earlier was that it was the Replication tool inside Hyper-V that was being licensed, but has since turned 180 and feels that as long as the copy/backup/replica isn't started, no license at all is required.
That's not quite true. I KNOW that the replica itself does not need a license, that has never once been questioned. It is if the feature to DO the replication might need a license. But that, too, appears to have been a myth.
-
@jaredbusch said in I can't even:
@Tim_G everything you link is referring to Hyper-V replication. It is understood that using Hyper-V to replicate requires SA or full licensing on both servers.
@scottalanmiller please provide the link to your source document for 2016 as well as the page number you are referencing. Otherwise this is all speculation on your part. I mean I believe you found the correct document and it is a real quote, but it needs to verifiable.
It was page 11.
