Backup System For 5 PC SMB
-
The long and the short of this is, the desired solution is just not what should be looked at for this problem.
We've been beating this topic to death with very little gain. I realize that @BRRABill isn't happy seeing vendors selling things and making claims that appear to be illegal, but this isn't new. It happens every day.
How about we work toward a real solution to his problem instead of continuously hashing over why this is illegal, improper, etc.
steps off soap box.. sorry.... just had to rant a bit, nothing personal.
-
@Dashrender said:
The long and the short of this is, the desired solution is just not what should be looked at for this problem.
We've been beating this topic to death with very little gain. I realize that @BRRABill isn't happy seeing vendors selling things and making claims that appear to be illegal, but this isn't new. It happens every day.
How about we work toward a real solution to his problem instead of continuously hashing over why this is illegal, improper, etc.
steps off soap box.. sorry.... just had to rant a bit, nothing personal.
However, we did, after all of that, circle around to why these products exist and where some of the unique nuances exist. We kept taking different tacks and finally found one that was really important - the piece that we had been missing. That if this was being done purely through VDI, all of these products are legal and work exactly as described. We figured out where disconnect was and found that it was purely the use of the DR as a P2V workaround that was the issue.
-
None taken.
It's more informative at this point.
I have an idea what to do with the OP.
-
But I still question the testing use of spinning up the image to test. You'd have that license live TWICE. Is that legal? Can you VDI the same license as much as you want?
(I'm unfamiliar with VDI licenses.)
-
@scottalanmiller said:
@Dashrender said:
The long and the short of this is, the desired solution is just not what should be looked at for this problem.
We've been beating this topic to death with very little gain. I realize that @BRRABill isn't happy seeing vendors selling things and making claims that appear to be illegal, but this isn't new. It happens every day.
How about we work toward a real solution to his problem instead of continuously hashing over why this is illegal, improper, etc.
steps off soap box.. sorry.... just had to rant a bit, nothing personal.
However, we did, after all of that, circle around to why these products exist and where some of the unique nuances exist. We kept taking different tacks and finally found one that was really important - the piece that we had been missing. That if this was being done purely through VDI, all of these products are legal and work exactly as described. We figured out where disconnect was and found that it was purely the use of the DR as a P2V workaround that was the issue.
LOL Yeah, I considered that during my rant. Though I'd argue that's a pretty poor use case though side benefit that probably even the software vendor themselves didn't actually consider.
-
@BRRABill said:
But I still question the testing use of spinning up the image to test. You'd have that license live TWICE. Is that legal? Can you VDI the same license as much as you want?
(I'm unfamiliar with VDI licenses.)
VDI licensing is based upon the devices accessing the VDI instances. I think I read somewhere that you can have 3 VDI instances per VDI Device license you have. But that might be out of date now.
-
@BRRABill said:
But I still question the testing use of spinning up the image to test. You'd have that license live TWICE. Is that legal? Can you VDI the same license as much as you want?
(I'm unfamiliar with VDI licenses.)
No, you license by capacity regardless of how you use it. But with VDI you can license by capacity. That's the difference.
-
@Dashrender said:
@BRRABill said:
But I still question the testing use of spinning up the image to test. You'd have that license live TWICE. Is that legal? Can you VDI the same license as much as you want?
(I'm unfamiliar with VDI licenses.)
VDI licensing is based upon the devices accessing the VDI instances. I think I read somewhere that you can have 3 VDI instances per VDI Device license you have. But that might be out of date now.
Depends on how you license VDI, I would think. There are a few different models. But I believe that you are correct that there is one that allows one user to have more than one VM for him.
-
@Dashrender said:
no, because MS allows you to move non OEM server licenses to the hosts every 90 days, be it physical or virtual.
If you use Datacenter on every host that becomes somewhat irrelevant.
-
@Jason said:
@Dashrender said:
no, because MS allows you to move non OEM server licenses to the hosts every 90 days, be it physical or virtual.
If you use Datacenter on every host that becomes somewhat irrelevant.
However, the licensing for Datacenter for 5 "servers" could cost just as much as a DIY VDI approach, yea? (What's the Price on Server 2012 R2 DC? )
-
@dafyre said:
@Jason said:
@Dashrender said:
no, because MS allows you to move non OEM server licenses to the hosts every 90 days, be it physical or virtual.
If you use Datacenter on every host that becomes somewhat irrelevant.
However, the licensing for Datacenter for 5 "servers" could cost just as much as a DIY VDI approach, yea? (What's the Price on Server 2012 R2 DC? )
About $2k per server. Yes, but you do get unlimited licencing so it's way better than VDI, unless you actually need a true VDI.
Even for $10k it would be heard to bulid a good in house VDI setup. Usually your talking $30-40k starting. VDI goes against the normal combine loads because we know what the load will be, and combines lots of unkown loads, Desktop loads are pretty unpredictable going up and down all the time.
-
@Jason said:
About $2k per server. Yes, but you do get unlimited licencing so it's way better than VDI, unless you actually need a true VDI.
Going this route the customer could get VDI for the desktops AND server options like AD, central file server, intranet portal and more for "free".
-
LOL, not to beat a dead horse here, but I still don't get why this would be kosher in a server environment.
-
@BRRABill said:
LOL, not to beat a dead horse here, but I still don't get why this would be kosher in a server environment.
Because the licenses are wholly unrelated. There is nothing about a desktop license that applies to a server one.
-
Or do you mean why there is logic to doing one and not to the other?
-
I mean that...
I have a server licensed, whether it is physical or virtual. How could I possibly boot up another copy of that server (the virtualboot of the backup image to test the backup) while the original is still running?
I know there are "cold boot" rights, which this would seem to fall under, but you need SA for those.
Also, it was mentioned earlier that to test it you'd have to perform a BMR. But wouldn't that ALSO be a violation, since the same server and license are active in two places?
-
@BRRABill said:
I have a server licensed, whether it is physical or virtual. How could I possibly boot up another copy of that server (the virtualboot of the backup image to test the backup) while the original is still running?
Because that with DC licensing you license capacity, not VMs. The idea that you have a "server licensed" doesn't exist.
-
Without DC you are still licensing capacity and not VMs, So If I had 2 WIndows Server VMs that could run on 3 hosts in event of a failure, I would have to have 3 Standard Server 2012 Licenses, one for each host, even though i only have two vms.
-
What is "DC licensing"?
-
