Hot answers tagged

16

It's a waste of time. You won't be able to induce failure or stress the drives in a meaningful manner. You have RAID, and that's a good start. Just make sure you have monitoring in place to actually detect failures as they occur and backups to protect against disaster.


5

It may be better to use different brands or series of disk together if you're worried about this. I have seen disks of similar type and age fail in clusters, so IMHO it's not an urban leend.


3

I admire your effort to try to automate this process... However, I don't think it's necessary. You don't have to send a diagnostic report to HP to obtain a warranty part. The IML log or RAID controller status is good enough to open a support case. Some things shouldn't be automated. If drive failures are frequent enough to need to automate the case ...


2

Great Question - However, unlike automobile headlights, this is a waste of time. The MTBF [mean time between failures] rating for 4 GB drives [WD Red in this example] is 1,000,000 hours. The odds of two drives going bad in a mirror at the same time is extremely rare. When I have seen this happen, it is has been because the first drive failed without ...


2

Are you sure that's the required solution for you? You are basically asking for a clustered solution for web hosting. Generally IIS is best left out of clustering and should utilise Network Load Balancing (NLB) instead. With NLB you will have both servers up simultaneously and split the load between them. If one of them goes down the second will handle all ...


2

You can do this by Microsoft NLB, or IIS shared configuration as Lior mentioned. You can also use the "Application Request Routing" or a hardware load balancer but all depends on the environment, resources and your requirements. Here are some resources: https://technet.microsoft.com/en-us/library/jj129384.aspx ...


2

Call your IBM reseller. They can get it. (as Newegg/amazon still have it in stock) A tip for IBM, HMM. Google 7945 HMM, and open first link. http://publib.boulder.ibm.com/infocenter/systemx/documentation/topic/com.ibm.sysx.7945.doc/PDF_4255_7945_7949_PDSG.pdf Page 387, send that to the reseller


1

EDIT: i first thought it was mirror pool, not raidz. Firstly, zpool replace should work fine. If it is slow because that dying disk is acting slow, you can offline/detach it first so data is rebuilt from other disks and reads are not attempted from the bad disk. Multiple failing disks is not a good thing though. Exporting pool, using ddrescue and then ...


1

While it makes sense in theory, the data doesn't support the need to work in your drive. Not only will a few weeks not really make an impact, the failure percentages don't really work when looking at only two drives. While there has been some indication of more normalized failure rates when it comes to drives of the same model. Most age-related results ...


1

I can really only see a couple of options here. They both assume that the only thing on this datastore is the VMDK that's housing the SQL Server's MDFs. No VMX files, no log files, no datastore heartbeating. The first would be to unmount the volume on the host in question. You can do it via the vSphere clients, esxcli or it's PowerCLI equivalent. I don't ...



Only top voted, non community-wiki answers of a minimum length are eligible