The Textbook Things Gone Wrong in IT Thread
-
That gave me the idea. But it is based off of "every hour of my day".
-
TL;DR - Do your research before implementing stuff.
-
I can understand how people can get lost though. There are so many bad tutorials and how to's out there.
For example, the gazillion tutorials that just tell you to turn off SELinux.
-
@MattSpeller said:
TL;DR - Do your research before implementing stuff.
Or ask. And don't use terms you aren't sure about, that leads people down the rabbit hole all of the time.
-
My boss is being sold on a SAN for our network of 4TB of data, expected to grow to 6TB within 4 years. Not that a SAN isn't needed but it seems like a really big chuck of any money we have for our virtualization project.
When we could buy two 32TB NAS devices (or build them) for $1500 and have the replicate between each other...
-
One to add to the list:
- Changes on a Friday afternoon
-
@DustinB3403 said:
When we could buy two 32TB NAS devices (or build them) for $1500 and have the replicate between each other...
SAN and NAS cost the same. You could build a high availability SAN cluster for the exact same money using the exact same hardware.
-
@DustinB3403 said:
My boss is being sold on a SAN for our network of 4TB of data, expected to grow to 6TB within 4 years.
For the size of a single cheap disk?
-
@DustinB3403 said:
My boss is being sold on a SAN for our network of 4TB of data, expected to grow to 6TB within 4 years. Not that a SAN isn't needed ...
There is only one reason ever to have a SAN in a case like this, large scale storage consolidation for a large number of physical hosts. Hard to imagine 4-6TB being able to save money even if it was being shared by twenty physical servers.
This sounds like it is breaking several of the textbook rules. Can't be sure, but hard to imagine a case where it is not.
-
@DustinB3403 said:
My boss is being sold on a SAN for our network of 4TB of data, expected to grow to 6TB within 4 years. Not that a SAN isn't needed but it seems like a really big chuck of any money we have for our virtualization project.
When we could buy two 32TB NAS devices (or build them) for $1500 and have the replicate between each other...
May want to look at an R730xd... you can put a crazy amount of disks in that. But really even for 4-6TB you don't need anything like a NAS or a SAN.
-
We have a few separate network shares hosted on different servers at the moment.
-
@DustinB3403 said:
We have a few separate network shares hosted on different servers at the moment.
Well four physical servers is the absolute minimum to possibly get value from shared storage and the rule of thumb is ten is the beginning of the reasonable part of the bell curve and a dozen or more start to become likely - but only when they are heavily consolidating and sharing.
-
@coliver said:
May want to look at an R730xd... you can put a crazy amount of disks in that. But really even for 4-6TB you don't need anything like a NAS or a SAN.
4-6TB you can put in a laptop!
-
Maxing at 6 TB, do you need more processing power and RAM than can be stuck in a single VM host? Or do you have a situation where you can't VM for some reason?
Sounds like a single server with possibly direct attached external storage (if needed for the number of spindles for performance - assuming you can't afford SSD storage) would do the trick - again unless you have work load that requires huge amounts of compute power.
-
@Dashrender said:
Sounds like a single server with possibly direct attached external storage (if needed for the number of spindles for performance - assuming you can't afford SSD storage) would do the trick - again unless you have work load that requires huge amounts of compute power.
SSD would be far less than the cost of a DAS chassis and spindles. You could be at a million IOPS for cheaper!
-
SAM, again this is the same MSP making this recommendation as in past conversations. . .
We have a few locations some over seas, but they all come back to the main office via our VPN for network shares etc.
-
@DustinB3403 said:
We have a few locations some over seas, but they all come back to the main office via our VPN for network shares etc.
It's not locations, it is the physical number of servers attached to the storage. For SAN you would need roughly ten or more virtualization hosts for SAN to even come up in conversation. That's it. A million users, large storage, many locations, etc. have no bearing on making a SAN more or less useful. SAN has one purpose and if there isn't the large number of host servers directly sharing the storage AND saving money by doing so, the SAN is doing the opposite of its purpose.
-
That's my point, we have 3 servers as file servers. And maybe 100 employees, the entire idea is just baffling.
-
@scottalanmiller said:
@Dashrender said:
Sounds like a single server with possibly direct attached external storage (if needed for the number of spindles for performance - assuming you can't afford SSD storage) would do the trick - again unless you have work load that requires huge amounts of compute power.
SSD would be far less than the cost of a DAS chassis and spindles. You could be at a million IOPS for cheaper!
With enterprise drives? Granted I haven't looked at them recently so I really have no clue how much enterprise class SSDs with a RAID 10 array of 6 TB usable would be - though I'm guessing at least $10K just in drives, not counting the enclosure!
-
@DustinB3403 said:
SAM, again this is the same MSP making this recommendation as in past conversations. . .
Yes, and whoever brought them in seems to be very textbook in their mistakes. Textbook business mistakes (bringing in a reseller claiming to be an MSP who is sending salespeople instead of engineers), getting advice from salespeople who aren't even remotely IT people, using a SAN where it doesn't make sense, etc.
As is often the case, it's an onion. One bad textbook mistake happens because another was done. The SAN might be the top layer. That only happened because a reseller was brought in for advice. That was only done because the IT manager doesn't know IT but doesn't want anyone else to know and is hoping to get someone else to do their job, but since they are trying to hide that fact they can't pay for the advice so have to get free advice from the salespeople. But those things together and the person entrusted to provide good IT advice isn't just not doing their job at all, but has sold the company out to the very people they should be protecting the company from.
The onion of bad IT decision making
