What are two characteristics of the active/active architecture on the Hitachi Unified Storage (HUS) systems? (Choose two.)

Question

Options

• AMultiple ports from the same controller are required to support the active/active feature.
• BFirmware upgrades are non-disruptive even with one path from a host.
• CController workload balancing is managed by the HUS system.
• DHDLM needs to be used to benefit from the active/active feature.

Explanation

HUS Active/Active Architecture

B and C are correct. In HUS active/active, the system itself automatically manages workload distribution across both controllers (C) - this is handled internally without host-side intervention. Additionally, because both controllers remain operational simultaneously, firmware upgrades are non-disruptive even when a host has only a single path (B), since the surviving controller continues handling I/O during the rolling upgrade.

Why the distractors are wrong:

• A is incorrect because active/active actually requires paths to different controllers, not multiple ports from the same controller - the whole value is cross-controller redundancy.
• D is incorrect because HDLM (Hitachi Dynamic Link Manager) is optional multipath software; standard OS-native multipathing can leverage the active/active feature without HDLM.

Memory tip: Think "active/active = the array does the work." The HUS system balances load (C) and the HUS system keeps both controllers alive during upgrades (B) - the host doesn't need special software (not D) or extra ports on one controller (not A).

No community discussion yet for this question.