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.
What ambiguities? Read the docs, they are pretty clear. I don't see ambiguities, just a lot of misinformation from outside sources that people assume originated from MS.
-
@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.
What documentation do you want? There is no reason to even be looking for it, there is nothing from MS that should suggest a need for it.
-
@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.
It's not ME calling it that. It's what it IS. Veeam, Unitrends, StorageCraft, Microsoft, the industry... they all use replica as a type of backup mechanism.
-
@tim_g 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.
If that is true, then you need a license to replicate Linux VMs as well... and that can't be right. Because I'm using Hyper-V Server 2016 to replicate Linux VMs. There's no way I'm going to buy a Windows license to cover a Linux VM.
Exactly. That can't be true. So we've pretty much determined that the Hyper-V Replication feature licensing is a myth as well.
-
@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.
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.
Yes, of course. Anything "warm" needs a license. Whether Full or SA depends on the case.
-
@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.
I agree. That would be the hinge. But a cold file is never an OSE. MS has never waivered on that.
-
@scottalanmiller 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.
It's not ME calling it that. It's what it IS. Veeam, Unitrends, StorageCraft, Microsoft, the industry... they all use replica as a type of backup mechanism.
No, it doesn't matter what it is. It matters what MS calls it, and MS, from what I've seen, make the terms mean something different...
Where Backup means cold storage or a cold replica... and Replicating VM to mean Warm backup. I can't remember where I've seen it anymore, but liek with clustering (warm copies/backups/replicas), they must be licensed.
-
@scottalanmiller @Tim_G
Software Assurance Benefit Centers on “Cold” Server Backups for Disaster Recovery
Effective June 1, 2004, customers with Software Assurance for Microsoft server software, as well as related Client Access Licenses (CALs), will be eligible for complimentary “cold backup” server Licenses for the purpose of disaster recovery. A cold server is a server that is turned off until a disaster arises. No other processing or production is done on this server.To qualify for this Software Assurance benefit, the customer will need to have a Microsoft server License enrolled in active Software Assurance. The customer will also need to have all corresponding Client Access Licenses (CALs) (if required by the software) enrolled in Software Assurance. Use of the software under a complimentary disaster recovery license is subject to the use rights for that software and the following conditions:
download.microsoft.com/download/6/c/5/6c576c0c-f740-48e2-86e1.../dr_brief.doc
-
@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.
Right, and not just for their own hardware, but licensed for any hardware that they COULD be restored to. Once you breach the "could be used" barrier, it's a slippery slope. Because what about hardware that's running, but not the restore target? What about cold hardware that could be plugged in. What about hardware you've not bought yet, but could? Where do you draw the line once it is about theoretical capability only?
-
@scottalanmiller 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.
I agree. That would be the hinge. But a cold file is never an OSE. MS has never waivered on that.
Correct, I agree that cold files are never an OSE.
-
@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?
This isn't true. Replica is not warm. Backups and Replicas CAN be warm. But we are ONLY discussing Cold Replicas in this thread. Only. Nothing warm, nada. Cold Repicas are a form of Cold Backup. And never need a license.
A warm replica, of course, is an OSE and must be licensed.
-
@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:
@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.
Nearly everything CAN be a warm backup these days. The question is.. is it?
-
@scottalanmiller 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.
Right, and not just for their own hardware, but licensed for any hardware that they COULD be restored to. Once you breach the "could be used" barrier, it's a slippery slope. Because what about hardware that's running, but not the restore target? What about cold hardware that could be plugged in. What about hardware you've not bought yet, but could? Where do you draw the line once it is about theoretical capability only?
That's a great point.
But when you "Replicate a VM" as in what MS referrs to by VM replication, you do have an intent of using that replica as a running machine, should the original server fail.
-
@tim_g said in I can't even:
@scottalanmiller 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.
Right, and not just for their own hardware, but licensed for any hardware that they COULD be restored to. Once you breach the "could be used" barrier, it's a slippery slope. Because what about hardware that's running, but not the restore target? What about cold hardware that could be plugged in. What about hardware you've not bought yet, but could? Where do you draw the line once it is about theoretical capability only?
That's a great point.
But when you "Replicate a VM" as in what MS referrs to by VM replication, you do have an intent of using that replica as a running machine, should the original server fail.
I guess I answered my own point here... then in that case, you'd need a license either by SA disaster recovery benefit, or another license on the replica host.
-
@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?
It's not an exception exactly, it's not within the context. It's never covered. Cold Backups (e.g. cold replicas) aren't ever needing a license until you intent to turn them on (make them hot) which is why MS specifies that in the document - because if you needed to license them cold, they'd not have to specify that you need to get the license to turn them hot.
-
@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:
@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.
Right, and not just for their own hardware, but licensed for any hardware that they COULD be restored to. Once you breach the "could be used" barrier, it's a slippery slope. Because what about hardware that's running, but not the restore target? What about cold hardware that could be plugged in. What about hardware you've not bought yet, but could? Where do you draw the line once it is about theoretical capability only?
That's a great point.
But when you "Replicate a VM" as in what MS referrs to by VM replication, you do have an intent of using that replica as a running machine, should the original server fail.
I guess I answered my own point here... then in that case, you'd need a license either by SA disaster recovery benefit, or another license on the replica host.
But I think that's besides the point. Of course then in that case it would be an OSE for sure.
But this is about an OSE already on HOST1, adn the question of whether or not the VM on the replica server is considered a Warm Backup, which is by microsoft's definition, and in which case is an OSE that needs licensed.
-
@dbeato said in I can't even:
Can we create a post regarding the Microsoft Licensing to a Topic so we don't derail this whole thread more? Just a recommendation.
Not at this scale, no we can't.
-
@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?
No, you never need a license for a replica, only for turning on a replica (which makes it a VM that happens to have been created via replication.)
-
@scottalanmiller said in I can't even:
@dbeato said in I can't even:
Can we create a post regarding the Microsoft Licensing to a Topic so we don't derail this whole thread more? Just a recommendation.
Not at this scale, no we can't.
Anyone see my link and excerpt above from Microsoft?
-
@scottalanmiller said in I can't even:
@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?
No, you never need a license for a replica, only for turning on a replica (which makes it a VM that happens to have been created via replication.)
But isn't that a WARM backup if Veeam is replicating a VM using Veeam Replication feature?
