Soru

Zorluk: ZorResilience, High Availability, and Redundancy

A security architect is designing a high-availability infrastructure for an enterprise core database server connected to a Storage Area Network (SAN) using dual Host Bus Adapters (HBAs) connected across separate SAN fabrics. During failure simulation testing, disconnecting one fiber channel link caused the database operating system to freeze due to input/output timeouts rather than redirecting I/O operations through the secondary healthy storage fabric. Which of the following operating system level capabilities should the architect configure to enable seamless storage path failover and traffic load distribution?

  1. Multipath I/O (MPIO) software with active-active path managementCevap
  2. B
    Link Aggregation Control Protocol (LACP) on the primary network interfaces
  3. C
    Synchronous block-level replication to an off-site disaster recovery data center
  4. D
    Active-passive server clustering with a cloud witness node for quorum isolation

Cevap

Multipath I/O (MPIO) software with active-active path management
Multipath I/O (MPIO) provides operating system level fault tolerance and load balancing across redundant physical paths (such as host bus adapters and switches) connecting a server to a storage array. When configured, MPIO masks multiple physical storage paths as a single logical drive and diverts block traffic automatically if one path experiences a cable or port failure.

Adım Adım Çözüm

1
Analyze the technical scenario requirements and underlying failure condition.
The server has physical hardware redundancy (dual HBAs and redundant SAN fabrics), but the operating system fails to recognize and switch between redundant storage paths when one path fails.
Without host-level multipathing logic, the operating system treats each physical connection as a separate storage device or locks I/O queues when a single path drops.
2
Evaluate candidate high-availability storage and network technologies against SAN HBA path redundancy.
Multipath I/O (MPIO) is specifically designed to abstract redundant storage connections (Fibre Channel/iSCSI) into a single logical device while performing continuous path monitoring, automatic failover, and load balancing.
MPIO integrates directly into the storage driver stack of the operating system to prevent I/O timeouts and kernel freezes.
3
Differentiate MPIO from network aggregation, remote disaster recovery, and compute clustering.
LACP handles network layer interfaces rather than HBA storage buses, synchronous site replication targets disaster recovery objectives, and active-passive clustering manages node failover rather than internal storage bus path management.
Only MPIO addresses the specific fault boundary described in the scenario.

Anahtar Kavram

Multipath I/O (MPIO) and Storage Path Resilience
Bu soruyu puanla