Burned by Eschewing Best Practices
-
Implemented a SAN with clearly NO idea what a SAN even is.
-
It's a DAS, not a SAN. He didn't even know what it was. He doesn't even have a switch, yet he thought that a network that doesn't even exist was the network being used.
-
Typical attitude, the less he knows, the more confident he is.
-
-
Gets hit with Ransomware, doesn't have proper working backups, and restores systems without a working backup (even if it was encrypted).
-
Just wow... He doesn't understand that his backup system has failed and that he believes he is in good shape. Yet his Domain admin account keeps getting locked out "every 9 seconds".
-
The best part, he puts the log file in a .doc... yep, sure. I'll just download a word document from someone with a known crypto infection...
Sharing is caring
-
@nadnerb said in Burned by Eschewing Best Practices:
The best part, he puts the log file in a .doc... yep, sure. I'll just download a word document from someone with a known crypto infection...
Sharing is caring
I know - right.. /FFS
-
Guy got a Dell SCv3020 controller as an iSCSI SAN for his XenServer 7.1 install. SAN goes down constantly and Dell can't figure out what is wrong with it.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
Guy got a Dell SCv3020 controller as an iSCSI SAN for his XenServer 7.1 install. SAN goes down constantly and Dell can't figure out what is wrong with it.
God I wish we could still have links to ridicule these design choices. .
-
@dustinb3403 said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
Guy got a Dell SCv3020 controller as an iSCSI SAN for his XenServer 7.1 install. SAN goes down constantly and Dell can't figure out what is wrong with it.
God I wish we could still have links to ridicule these design choices. .
It's not about ridiculing them. It's about documenting how often bad things happen. Vendors constantly claim that if we don't collect this data, it didn't happen. That's why we have this thread. Showing that not following best practices really does lead to disaster, in the real world, at rates that people claim are impossible.
So many SAN vendors have called us liars for saying that SANs fail. They claim that that is impossible. Yet it's a constant source of evidence.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@dustinb3403 said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
Guy got a Dell SCv3020 controller as an iSCSI SAN for his XenServer 7.1 install. SAN goes down constantly and Dell can't figure out what is wrong with it.
God I wish we could still have links to ridicule these design choices. .
It's not about ridiculing them. It's about documenting how often bad things happen. Vendors constantly claim that if we don't collect this data, it didn't happen. That's why we have this thread. Showing that not following best practices really does lead to disaster, in the real world, at rates that people claim are impossible.
So many SAN vendors have called us liars for saying that SANs fail. They claim that that is impossible. Yet it's a constant source of evidence.
Glad you said that, certainly seems to be about the ridiculing for a few on here.
-
@jackcpickup said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@dustinb3403 said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
Guy got a Dell SCv3020 controller as an iSCSI SAN for his XenServer 7.1 install. SAN goes down constantly and Dell can't figure out what is wrong with it.
God I wish we could still have links to ridicule these design choices. .
It's not about ridiculing them. It's about documenting how often bad things happen. Vendors constantly claim that if we don't collect this data, it didn't happen. That's why we have this thread. Showing that not following best practices really does lead to disaster, in the real world, at rates that people claim are impossible.
So many SAN vendors have called us liars for saying that SANs fail. They claim that that is impossible. Yet it's a constant source of evidence.
Glad you said that, certainly seems to be about the ridiculing for a few on here.
That is as much a joke as it is honesty. Some people refuse to learn via "nice" approaches, and thus have to be ridiculed into the realization that what they have done is absolutely insane.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
Guy got a Dell SCv3020 controller as an iSCSI SAN for his XenServer 7.1 install. SAN goes down constantly and Dell can't figure out what is wrong with it.
Is it going down, like it freezes and needs reboot, or is the thing going to sleep and causing tapdisk errors, which causes linux vms to go RO, and Windows vms to BSOD? I had to disable c6 and c7 on my storage server to stop this phenomenon.
-
@momurda said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
Guy got a Dell SCv3020 controller as an iSCSI SAN for his XenServer 7.1 install. SAN goes down constantly and Dell can't figure out what is wrong with it.
Is it going down, like it freezes and needs reboot, or is the thing going to sleep and causing tapdisk errors, which causes linux vms to go RO, and Windows vms to BSOD? I had to disable c6 and c7 on my storage server to stop this phenomenon.
It goes offline and has to be rebooted.
-
@dustinb3403 said in Burned by Eschewing Best Practices:
@jackcpickup said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@dustinb3403 said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
Guy got a Dell SCv3020 controller as an iSCSI SAN for his XenServer 7.1 install. SAN goes down constantly and Dell can't figure out what is wrong with it.
God I wish we could still have links to ridicule these design choices. .
It's not about ridiculing them. It's about documenting how often bad things happen. Vendors constantly claim that if we don't collect this data, it didn't happen. That's why we have this thread. Showing that not following best practices really does lead to disaster, in the real world, at rates that people claim are impossible.
So many SAN vendors have called us liars for saying that SANs fail. They claim that that is impossible. Yet it's a constant source of evidence.
Glad you said that, certainly seems to be about the ridiculing for a few on here.
That is as much a joke as it is honesty. Some people refuse to learn via "nice" approaches, and thus have to be ridiculed into the realization that what they have done is absolutely insane.
But that's not the reason for this thread. There is a value to shaming bad ideas publicly, rarely for the person who already made the mistake, and this thread is about bad ideas and how people got burned for not listening, but we know that the majority of people to whom it has happened aren't the same ones who caused the problem (see Why IT Builds a House of Cards) so there is no educational purpose to shaming the people, but there is a huge one to shaming the ideas.
Because so often people feel that they are "better than" or "above" best practices, they need to see hubris in action and the downfalls it creates. If we don't get to document the failures, people claim that they are myths.
We started this thread as a reaction to a continuous stream of claims that as this thread didn't exist, that was taken as proof that the problems were lies that we made up.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
But that's not the reason for this thread.
Not the reason it should exist no. But it has always been Dustin's reason.
-
@jaredbusch said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
But that's not the reason for this thread.
Not the reason it should exist no. But it has always been Dustin's reason.
Quit trolling!
-
@dustinb3403 said in Burned by Eschewing Best Practices:
@jaredbusch said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
But that's not the reason for this thread.
Not the reason it should exist no. But it has always been Dustin's reason.
Quit trolling!
You created the "I can't even" thread
-
@dustinb3403 said in Burned by Eschewing Best Practices:
@dustinb3403 said in Burned by Eschewing Best Practices:
@jaredbusch said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
But that's not the reason for this thread.
Not the reason it should exist no. But it has always been Dustin's reason.
Quit trolling!
You created the "I can't even" thread
Yes, but you always make it a point to ridicule. ALl I did was start a thread to shake our heads at.
