What is a key characteristic of the Modular Volume Migration feature on a Hitachi Unified Storage (HUS) system?

Question

Options

• AIt migrates volumes between HUS systems.
• BIt uses the Copy-on-Write Snapshot engine.
• CIt migrates volumes within the same RAID group.
• DIt migrates volumes within a HUS system.

• A
  3% (1)
• B
  3% (1)
• C
  6% (2)
• D
  88% (28)

Explanation

Modular Volume Migration on a HUS system is designed to move volumes within the same HUS system - between different RAID groups or storage pools inside that single array. This makes option D correct: the feature is an intra-system migration tool used for load balancing, tiering, or reorganizing data without needing external systems or special snapshot engines.

• A is wrong because this feature does not cross system boundaries; cross-system migration would require a separate replication or data migration utility.
• B is wrong because Copy-on-Write Snapshot is a distinct feature used for point-in-time copies, not volume relocation - Modular Volume Migration moves the actual data blocks, not snapshots.
• C is wrong because migration within the same RAID group would be pointless for performance or capacity goals; the whole purpose is to move data between RAID groups or pools inside the HUS.

Memory tip: Think of "Modular" as "within the module (the HUS box itself)" - you're rearranging furniture inside one house, not moving to a new house.

No community discussion yet for this question.