When to use VMWare over free hypervisors?
-
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
Where is the reckless spending? Its an extra 1 x Windows Server Standard license (£900). That's it.
The host we would need anyway is doing HA with VMWare... which to have vMotion with (something OOB with Hyper-V), is around 4-5k like I said earlier.It's an extra physical server, extra Windows licenses, and SQL Server Standard SA upgrade. Plus the power draw, maintenance time and so forth. It adds up. Given that in the US, any server purchase is nearly impossible, having two often means you can't get funds to maintain them. Nearly doubling the budget is rarely trivial.
Why would you need VMware anyway? that makes no sense. We already covered that Vmware would never apply in a company of your size. Failover with someone else would be free. Of course, what we are pointing out, is that likely you don't need that either.
The post was asking when to consider VMWare over Hyper-V, and at an early stage HA came up as a reason... hence saying what I am saying. For any HA, you would need that second server, even with HyperV. So if you need that you need that, its not double cost... its needed. To have the second server for HA, with VMWare... is even more cost.
If you need HA, you have to have that second server. So its not an additional cost - as both VMWare and HyperV, if you need HA would have that cost.
IF you need HA, you need two servers. But HA is free beyond that (except with Vmware.) But first you have to decide what the value of HA is to your business. Most SMBs, (like 95%) should not have HA.
Agree. And for us, we do need it. And as I tried to show, we do that without having to license VMWare just through using Hyper-V. Same kit. Same licenses we need for Windows Server and SQL Server as that's the db of choice for our devs... all the same... but no VMWare.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
I will have to read up on that... but my comments again, were in relation to people saying vMotion = HA etc.
People is Dustin and it's established that he didn't know what either was at all. He thought vMotion was something WAY different from HA, in fact. All of his info was wrong.
vMotion and HA are different, and free from everyone but Vmware. Let's move past that. No need to keep responding to that misinformation as if anyone else believes it. That was one person off on a tangent. Now in the real world, they are different things, and free.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
So, is memory of the VM stored on the shares storage too or something, so when the node fails, a partner can instantly grab the running state of the VM?
No, memory would be too slow to do that. Your memory would be limited to the speed of a disk. Imagine if ALL memory was the speed of swap! Eek.
HA doesn't maintain memory state. It just recovers in a few seconds.
FT keeps the CPU and memory in lock step. So both systems have the VMs loaded into memory. So all transactions are live in both places. Everything is live between the two. Same as mainframes. -
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
I will have to read up on that... but my comments again, were in relation to people saying vMotion = HA etc.
People is Dustin and it's established that he didn't know what either was at all. He thought vMotion was something WAY different from HA, in fact. All of his info was wrong.
vMotion and HA are different, and free from everyone but Vmware. Let's move past that. No need to keep responding to that misinformation as if anyone else believes it. That was one person off on a tangent. Now in the real world, they are different things, and free.
Agreed
you know, chatting face to face is such an easier process! Darn internet. Lol. -
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
So, is memory of the VM stored on the shares storage too or something, so when the node fails, a partner can instantly grab the running state of the VM?
No, memory would be too slow to do that. Your memory would be limited to the speed of a disk. Imagine if ALL memory was the speed of swap! Eek.
HA doesn't maintain memory state. It just recovers in a few seconds.
FT keeps the CPU and memory in lock step. So both systems have the VMs loaded into memory. So all transactions are live in both places. Everything is live between the two. Same as mainframes.Ahhh, I see. Now that's cool. So, the VMs are sort of warm mirror, and when node1 dies, node 2 would be fairly instant. That's cool... and is one reason why i'd consider VMWare
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
Same licenses we need for Windows Server and SQL Server as that's the db of choice for our devs... all the same... but no VMWare.
Different discussion, but why would you ever let devs have a say in that (that's an IT decision, not a dev one and I come from a dev background) and this is the exact scenario I warn SMBs about all of the time - building technical debt into the bespoke systems making little things unnecessarily costly. That means that every penny of Windows, SQL Server and lots of your admin costs are all created by the devs. Has anyone looked at the devs to see what kind of impact letting them make those kinds of decisions on IT is having on the business?
As someone that manages dev teams, while there are insanely rare exceptions where that kind of stuff makes sense, it just doesn't make sense. Windows and especially SQL Server as dev platforms are huge red flags to something being really wrong and proper business analysis failing. Again... always an exception somewhere. But "dev preference" or "dev skills" certainly would never apply in that case. It huge money that we are talking.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
So, is memory of the VM stored on the shares storage too or something, so when the node fails, a partner can instantly grab the running state of the VM?
No, memory would be too slow to do that. Your memory would be limited to the speed of a disk. Imagine if ALL memory was the speed of swap! Eek.
HA doesn't maintain memory state. It just recovers in a few seconds.
FT keeps the CPU and memory in lock step. So both systems have the VMs loaded into memory. So all transactions are live in both places. Everything is live between the two. Same as mainframes.Ahhh, I see. Now that's cool. So, the VMs are sort of warm mirror, and when node1 dies, node 2 would be fairly instant. That's cool... and is one reason why i'd consider VMWare
Yes, but that's VERY expensive. It uses bigger Vmware licensing, limits you to about four cores and slows things way down. It's super cool, but you only use anything like that when you REALLY need it. And Xen does this for free, as well.
-
Not that Xen does it as well or as easily as Vmware. But it's important not to overlook that it is there and has been around for a while. But in both VMware and Xen camps, people avoid fault tolerance almost always even when they can easily afford it. It is so hard to justify with all of the overhead and limitations.
-
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
Same licenses we need for Windows Server and SQL Server as that's the db of choice for our devs... all the same... but no VMWare.
Different discussion, but why would you ever let devs have a say in that (that's an IT decision, not a dev one and I come from a dev background) and this is the exact scenario I warn SMBs about all of the time - building technical debt into the bespoke systems making little things unnecessarily costly. That means that every penny of Windows, SQL Server and lots of your admin costs are all created by the devs. Has anyone looked at the devs to see what kind of impact letting them make those kinds of decisions on IT is having on the business?
As someone that manages dev teams, while there are insanely rare exceptions where that kind of stuff makes sense, it just doesn't make sense. Windows and especially SQL Server as dev platforms are huge red flags to something being really wrong and proper business analysis failing. Again... always an exception somewhere. But "dev preference" or "dev skills" certainly would never apply in that case. It huge money that we are talking.
Yeah, agree. But, the development team are the team who select what they want to use, for reasons I'm not privy to... they wanted SQL Server when they assessed it a long time ago, and that's what the solution has been built on. I hope their reasons were good. But, its still what we have to use.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
I hope their reasons were good. But, its still what we have to use.
There is no reasonable possibility of that. The logic to using SQL Server in the SMB is similar to VMware, but far worse. It's not easier, not as well known , not as powerful, not as flexible as free alternatives.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
Yeah, agree. But, the development team are the team who select what they want to use, for reasons I'm not privy to... they wanted SQL Server when they assessed it a long time ago, and that's what the solution has been built on.
It sounds like layer after layer of business and political failures resulting in IT trying to find expensive technical band-aids to poor management oversight. Not a good situation. Good that there is enough money to pay for some fixes, but bad that money is needed to fix things that never needed to be broken.
-
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
Yeah, agree. But, the development team are the team who select what they want to use, for reasons I'm not privy to... they wanted SQL Server when they assessed it a long time ago, and that's what the solution has been built on.
It sounds like layer after layer of business and political failures resulting in IT trying to find expensive technical band-aids to poor management oversight. Not a good situation. Good that there is enough money to pay for some fixes, but bad that money is needed to fix things that never needed to be broken.
I really don't know the reasons why back in day one, the decision was to use this stack. That was decided a long time ago, and i'n never at this stage be able to get them to change their entire stack. Maybe it was a good decision, maybe bad... I don't know as I wasn't there. The fact it is wasn't a poor decision, just a more expensive one to use SQL Server. Nothing broken.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
Yeah, agree. But, the development team are the team who select what they want to use, for reasons I'm not privy to... they wanted SQL Server when they assessed it a long time ago, and that's what the solution has been built on.
It sounds like layer after layer of business and political failures resulting in IT trying to find expensive technical band-aids to poor management oversight. Not a good situation. Good that there is enough money to pay for some fixes, but bad that money is needed to fix things that never needed to be broken.
I really don't know the reasons why back in day one, the decision was to use this stack. That was decided a long time ago, and i'n never at this stage be able to get them to change their entire stack. Maybe it was a good decision, maybe bad... I don't know as I wasn't there. The fact it is wasn't a poor decision, just a more expensive one to use SQL Server. Nothing broken.
The fact is, we are highly available in a range of different ways, and IT can do what we need when we need without affecting customers. In addition, the company is happy with the cost, and know Linux is cheaper, and are happy to be paying more to have a happy team of developers using the products they are most used to and happy with. That's not broken. More expensive, yes - but not broken and entirely fine for the business as management are happy with our profit and figures.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
I really don't know the reasons why back in day one, the decision was to use this stack. That was decided a long time ago, and i'n never at this stage be able to get them to change their entire stack.
That's the danger. This kind of technical debt can, and normally does, haunt a company for decades with far reaching ramifications that are normally ignored. Like the cost of SQL Server, Windows licenses, license managment, extra admin time, and so forth. Things that might seem trivial at start up time but when considered over decades of use and how that technical debt will often spawn more related technical debt, what feels like a few thousands dollars might result in tens or hundreds of thousands of dollars in long term tech debt.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
The fact it is wasn't a poor decision, just a more expensive one to use SQL Server. Nothing broken.
That's not how IT ever works. Broken is not a definition of good or bad. Not being the most cost effective solution for the business by definition is what makes it poor. That is the sole criteria by which IT is judged.
You can never say it was not a poor decision without knowing how and why the original decision was made, there is no ability to evaluate that. What we do know is that in decades of doing this evaluation, I've never found a company that made this choice AND it wasn't poor once analyzed.
In the 1990s, with SQL Server 7, this was sometimes a good choice. By the early 2000s, that era had essentially ended.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
The fact is, we are highly available in a range of different ways, and IT can do what we need when we need without affecting customers. In addition, the company is happy with the cost, and know Linux is cheaper, and are happy to be paying more to have a happy team of developers using the products they are most used to and happy with. That's not broken. More expensive, yes - but not broken and entirely fine for the business as management are happy with our profit and figures.
That's broken by business criteria.
Can you HONESTLY go to your management and say "you could be more profitable and we could all be making more... but are you happy enough earning less, so we won't bother" do you think that they would agree that the profits are "enough" and that doing better is not a goal?
In the US, that's not just unlikely, in a public company it is called a violation of fiduciary responsibility. The purpose of a company is to make money. That they would happily earn less for no reason isn't logical.
-
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
The fact it is wasn't a poor decision, just a more expensive one to use SQL Server. Nothing broken.
That's not how IT ever works. Broken is not a definition of good or bad. Not being the most cost effective solution for the business by definition is what makes it poor. That is the sole criteria by which IT is judged.
You can never say it was not a poor decision without knowing how and why the original decision was made, there is no ability to evaluate that. What we do know is that in decades of doing this evaluation, I've never found a company that made this choice AND it wasn't poor once analyzed.
In the 1990s, with SQL Server 7, this was sometimes a good choice. By the early 2000s, that era had essentially ended.
But equally, we cannot say it was. I have to just go based on what senior management, directors, boards are saying... 'We use SQL Server'.
Anyway, off to bed. Great discussing this with you... Best, Jim
-
Remember, in IT and business (which are the same thing)... "not being as cost effective as possible" and "broken" are identical. Anyone can make a system work, but the purpose of having IT is to make it work well. If it isn't working as well as it should, that's broken from that perspective.
-
@scottalanmiller said in When to use VMWare over free hypervisors?:
Remember, in IT and business (which are the same thing)... "not being as cost effective as possible" and "broken" are identical. Anyone can make a system work, but the purpose of having IT is to make it work well. If it isn't working as well as it should, that's broken from that perspective.
It is working well. Very well. Using the tools I have to use. I cant change that, I can only make it as good as it can be.
-
@Jimmy9008 said in When to use VMWare over free hypervisors?:
@scottalanmiller said in When to use VMWare over free hypervisors?:
@Jimmy9008 said in When to use VMWare over free hypervisors?:
The fact it is wasn't a poor decision, just a more expensive one to use SQL Server. Nothing broken.
That's not how IT ever works. Broken is not a definition of good or bad. Not being the most cost effective solution for the business by definition is what makes it poor. That is the sole criteria by which IT is judged.
You can never say it was not a poor decision without knowing how and why the original decision was made, there is no ability to evaluate that. What we do know is that in decades of doing this evaluation, I've never found a company that made this choice AND it wasn't poor once analyzed.
In the 1990s, with SQL Server 7, this was sometimes a good choice. By the early 2000s, that era had essentially ended.
But equally, we cannot say it was. I have to just go based on what senior management, directors, boards are saying... 'We use SQL Server'.
Well whoever says it is IT, that's how we define who IT is. We aren't trying to say that some specific person made a bad decision, only that one was made. Whether that was someone not properly checking in on devs making bad decisions, or someone high up making bad decisions directly... it happened and now you are saddled with high costs that shouldn't be necessary.
