Enterprise HDD firmware updates

[Lanz]

Hi

I'm wondering if people generally keep their production server/san HDD firmwares up to date, or if you think these updates are pretty low priority unless there's an actual issue. ?

 

[LostCorpse]

general rule of thumb is to patch to a specific level and leave it alone unless you have a specific reason to keep it top notch. there's a lot of work involved and in some cases risk updating firmware in my limit experience.

 

[Semple]

As above, with the software we create/support, HDD firmware only rolls when there is a fix or a particular new feature we're after.

 

[Deleted member 138126]

For a vendor-supported array, the vendor will notify you of any firmwares that are considered "required" or critical, and there will typically be a seamless online method of updating the firmware.

For server drives, again the vendor will typically allow you to sign up for notifications (you specify the models of hardware you have, and it tailors the notifications to those models only). You will usually have "critical", "recommended", and "optional", or similar. Generally speaking, vendors are pretty conservative, so a critical firmware I would more or less consider essential (you evaluate each one, obviously). The pain is that for servers, a drive firmware upgrade requires a reboot.

In cases like that, I will contact the vendor, and ask them to confirm the danger of not upgrading.

 

[Armageus]

At work with HP Servers we tend to do the following:

Set up a HP Update repository (including current drive firmwares, raid controller firmwares, as well as everything else) and use that as a base for the next 6-12 months. Multiple servers get setup within that 6-12 month window, so all are consistent.

Any replacement drives with firmware older than our current repository get updated, anything newer stay as is.

If we run into a specific issue then we would apply any newer individual firmware to the affected drives/servers - and depending on the age of our repository, add the individual fixes to our deployment process or if old enough then update the repository.

 

[nox_uk]

I would to keep them all on the same firmware level if possible, but honestly there is literally always something with higher priority. If some bug came out that was relevant, they would get done pretty smartish.

 

[Caged]

Patch it before you deploy, then leave it alone unless you need to fix a bug.

 

[nutcase]

Patch it before you deploy, then leave it alone unless you need to fix a bug.

This. And as above HP tell you about critical updates.