![Intel RAID High Availability User Manual Download Page 44](http://html1.mh-extra.com/html/intel/raid-high-availability/raid-high-availability_user-manual_2073422044.webp)
44
Intel
®
High Availability Storage User Guide
The operating system on Server A only sees VDs with shared host access and exclusive host access
to Server A.
The operating system on Server B only sees VDs with shared host access and exclusive host access
to Server B.
Before failover, the operating system perspective of I/O transactions is as follows:
Server A is handling I/O transactions that rely on A-DG0:VD1 and A-DG0:VD2.
Server B is handling I/O transactions that rely on A-DG0:VD0 and B-DG0:VD3.
Figure 35 After Failover from Server A to Server B
After failover, the cluster status is as follows in terms of the management of the drive group and the VDs:
All shared VDs in A-DG0 have failed over and are now managed by Server B.
VD3 in B-DG0 is still managed by Server B.
The SSD Cache VD (CC-VD) in A-CC now appears as a foreign VD on Server B but does not
service any VDs in A-DG0 or B-DG0.
After failover, the operating system perspective is as follows:
The operating system on Server B manages all shared VDs and any exclusive Server B VDs.
After failover, the operating system perspective of I/O transactions is as follows:
Failover Cluster Manager has moved the I/O transactions for VD2 on A-DG0 to Server B.
Server B continues to run I/O transactions on B-DG0:VD3.