Burned by Eschewing Best Practices
-
@scottalanmiller said in Burned by Eschewing Best Practices:
This would be akin to buying a couch from Nebraska Furniture Mart and shipping it on BNSF. Yes, the same company owns both of those companies, but those two companies don't comingle data or accounts.
nice
-
I buy my couches from Ikea. And call them settees.
-
I'm putting this here in case of future burn:
https://www.itnews.com.au/news/sa-health-takes-disaster-recovery-gamble-to-save-money-465730South Australia's Health department has decided not to implement a secondary site for disaster recovery with its new state-wide pathology system in an effort to save costs from a project that is running late and over budget.
State wide... Expected cost of $40 million... Dropping plan for DR site...
-
So this is a system that does centralized pathology computing for the entire state?
-
@scottalanmiller said in Burned by Eschewing Best Practices:
So this is a system that does centralized pathology computing for the entire state?
I believe so.
-
@nadnerB said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
So this is a system that does centralized pathology computing for the entire state?
I believe so.
Okay, that does seem pretty foolish then. Assuming that just having the computer system online is valuable should the site fail.
-
Potential IPOD in the works for a mere 43TB.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
Potential IPOD in the works for a mere 43TB.
Mere?
Someone's perspective seems odd.
-
@Dashrender said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Potential IPOD in the works for a mere 43TB.
Mere?
Someone's perspective seems odd.
Really it is a mere 43TB. Not until you're in the 100's of TB range should SAN's even be considered. Which this is where you start to reach the limit of single servers.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@Dashrender said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Potential IPOD in the works for a mere 43TB.
Mere?
Someone's perspective seems odd.
Really it is a mere 43TB. Not until you're in the 100's of TB range should SAN's even be considered. Which this is where you start to reach the limit of single servers.
The size of data isn't really a limiting factor. It's the number of hosts that need to share the storage.
-
@stacksofplates said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
@Dashrender said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Potential IPOD in the works for a mere 43TB.
Mere?
Someone's perspective seems odd.
Really it is a mere 43TB. Not until you're in the 100's of TB range should SAN's even be considered. Which this is where you start to reach the limit of single servers.
The size of data isn't really a limiting factor. It's the number of hosts that need to share the storage.
Sure, but I can fit that much storage into a single server and be within the tolerances set by the OP.
So while he is downsizing to 2 servers, 1 is all that he might actually require. Assuming SA is good enough.
-
@stacksofplates said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
@Dashrender said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Potential IPOD in the works for a mere 43TB.
Mere?
Someone's perspective seems odd.
Really it is a mere 43TB. Not until you're in the 100's of TB range should SAN's even be considered. Which this is where you start to reach the limit of single servers.
The size of data isn't really a limiting factor. It's the number of hosts that need to share the storage.
There is no reasoning as to why the OP thinks he needs a SAN other than it's what he had before and is familiar with. So that reason right there is a "red herring" and immediately means he should welcome outside review before purchasing anything.
Assuming he had 100 TB of storage across 3 servers he could go with scale or starwind's vsan and still be way better off than with the SAN.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@stacksofplates said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
@Dashrender said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Potential IPOD in the works for a mere 43TB.
Mere?
Someone's perspective seems odd.
Really it is a mere 43TB. Not until you're in the 100's of TB range should SAN's even be considered. Which this is where you start to reach the limit of single servers.
The size of data isn't really a limiting factor. It's the number of hosts that need to share the storage.
Sure, but I can fit that much storage into a single server and be within the tolerances set by the OP.
So while he is downsizing to 2 servers, 1 is all that he might actually require. Assuming SA is good enough.
The point was the statement you made was definitive statement without any relation to the OP. If you said "in this case" fine. But it was just a blanket statement.
-
@stacksofplates said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
@stacksofplates said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
@Dashrender said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Potential IPOD in the works for a mere 43TB.
Mere?
Someone's perspective seems odd.
Really it is a mere 43TB. Not until you're in the 100's of TB range should SAN's even be considered. Which this is where you start to reach the limit of single servers.
The size of data isn't really a limiting factor. It's the number of hosts that need to share the storage.
Sure, but I can fit that much storage into a single server and be within the tolerances set by the OP.
So while he is downsizing to 2 servers, 1 is all that he might actually require. Assuming SA is good enough.
The point was the statement you made was definitive statement without any relation to the OP. If you said "in this case" fine. But it was just a blanket statement.
Semantic police are in force today. . . .
-
@DustinB3403 FFS, the size of the data has nothing to do with the need for a SAN.
If you need more data than you can fit in a 4U box, then you buy a DAS to connect to your box to get more storage. Or you look at multiple boxes with local storage and then a vSAN or something to get the storage amount you need.
You use a SAN when you need lots of hosts on the same set of data.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@stacksofplates said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
@stacksofplates said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
@Dashrender said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Potential IPOD in the works for a mere 43TB.
Mere?
Someone's perspective seems odd.
Really it is a mere 43TB. Not until you're in the 100's of TB range should SAN's even be considered. Which this is where you start to reach the limit of single servers.
The size of data isn't really a limiting factor. It's the number of hosts that need to share the storage.
Sure, but I can fit that much storage into a single server and be within the tolerances set by the OP.
So while he is downsizing to 2 servers, 1 is all that he might actually require. Assuming SA is good enough.
The point was the statement you made was definitive statement without any relation to the OP. If you said "in this case" fine. But it was just a blanket statement.
Semantic police are in force today. . . .
No, you are wrong and are being called out on it.
-
@JaredBusch said in Burned by Eschewing Best Practices:
@DustinB3403 FFS, the size of the data has nothing to do with the need for a SAN.
If you need more data than you can fit in a 4U box, then you buy a DAS to connect to your box to get more storage. Or you look at multiple boxes with local storage and then a vSAN or something to get the storage amount you need.
You use a SAN when you need lots of hosts on the same set of data.
Of which he's said he doesn't need a lot of hosts, since he is downsizing. FFS!
He even said "1250 iops should be more than enough" which is indicative that he isn't doing dick with the underlying storage.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
@DustinB3403 FFS, the size of the data has nothing to do with the need for a SAN.
If you need more data than you can fit in a 4U box, then you buy a DAS to connect to your box to get more storage. Or you look at multiple boxes with local storage and then a vSAN or something to get the storage amount you need.
You use a SAN when you need lots of hosts on the same set of data.
Of which he's said he doesn't need a lot of hosts, since he is downsizing. FFS!
He even said "1250 iops should be more than enough" which is indicative that he isn't doing dick with the underlying storage.
I never read the linked thread. Just responding to your statement here.
-
@JaredBusch said in Burned by Eschewing Best Practices:
I never read the linked thread. Just responding to your statement here.
Oh FFS! . . .
Where is my beer. . .
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@JaredBusch said in Burned by Eschewing Best Practices:
I never read the linked thread. Just responding to your statement here.
Oh FFS! . . .
Where is my beer. . .
But the linked thread is not relevant to your statement here that I was responding to.
