What allows firmware to be updated non-disruptively on the Hitachi Unified Storage systems?

Question

Options

• AFirmware updates are performed in less than the host I/O timeout value.
• BWhile one controller is rebooting, the other handles all host operations.
• CHost connectivity to both controllers established using multi-pathing software.
• DFirmware updates only affect the first five drives and no controller reboot is required.

• A
  3% (1)
• B
  87% (26)
• C
  3% (1)
• D
  7% (2)

Explanation

On Hitachi Unified Storage (HUS) systems, non-disruptive firmware updates are possible because the dual-controller architecture allows one controller to reboot and apply the update while the other controller takes over all host I/O - once the first controller is back online, the process repeats for the second, keeping storage continuously available throughout. Option A is wrong because the goal isn't to race under a timeout value - the update process can take longer than any timeout if handled correctly by failover; the timeout alone doesn't prevent disruption. Option C describes a prerequisite (multi-pathing ensures hosts can reach both controllers), but multi-pathing alone doesn't make the firmware update non-disruptive - it's the controller failover during the update that does. Option D is completely fabricated; firmware updates involve the controllers and require reboots, and drive count is irrelevant to the update mechanism.

Memory tip: Think of it like changing tires on a moving car - one controller "pulls off the road" to update while the other keeps driving; then they swap.

No community discussion yet for this question.