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
-
@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.
-
@jaredbusch said in Burned by Eschewing Best Practices:
@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.
So you're the founder. Grats.
-
Found this. . . (and reworded so can grasps the level of WTF)
Hi all,
I currently offer my services as a System Admin to a client who I installed a physical installation of Microsoft Windows Server 2012. I setup this client as I simply don’t understand virtualization or system design and have been using Windows Backup and Previous Versions to create and maintain my backups of this system. These backups (besides PV) get pushed to a USB drive.
Well the client called me the other day saying they need some files restored from several months ago, I went and looked at the Windows Backup restore points and I can’t find anything from August of 2017 to February of 2018.
Is there anyway that I can get to these backups? I have backups from just the other day, but nothing in between that time span, and that is the window in which the files should have been saved.
Wbadmin shows a few recovery points in the console, but there have to be more recovery points than this; as this system has been running for a long time now.
I limited Previous Versions (to a 2 week span) as I accidentally filled each volume, and realized that I can’t use it to retain backups for long term. This caused all kinds of issues and I had to delete a lot of my backups.
I don’t want to hear about other solutions going forward or how to remedy this for the future. I only want to know if I can magically pull backups that were never created. I clearly wasn’t doing my job and monitoring or testing the backup system and for all I know this USB drive could’ve actually been unplugged or defective the entire time.
It’s great that you’re all responding to me, but telling me I’m up shit’s creek without a paddle isn’t helping. Veeam looks like a great option, but I don’t want to risk production to the free version, I only want to purchase it now. Never mind the fact that I’ve been using Windows Backup for years now and have had no support.
Some how it only make sense to use software without support for years on end that includes no support. But if I’m offered free software that includes support it scares me and I don’t want to use it.
Please, please help me as the client is getting anxious to get these files and I don’t want to be the person who has to tell them the files just aren’t there and can’t be recovered.
-
@dustinb3403 fail.
-
@dustinb3403 Sure, let me just get some rainbow unicorn farts sent their way and everything will be good.....
