630 Implementing the IBM Storwize V5000 Gen2 with IBM Spectrum Virtualize V8.1
The IP quorum substitutes the active quorum disk’s tiebreaker role. Redundancy can be
implemented by using multiple quorum apps, similar to multiple quorum disks. However, only
one app is active at a time. The other apps are available if the active quorum device app fails.
For more information about quorum devices, see the Storwize V5000 IBM Knowledge Center:
https://ibm.biz/BdjaUk
Because HyperSwap is running as a single cluster that is distributed across two main data
centers, one Storwize V5000 control enclosure is required in each site. Both control
enclosures must be added to the same cluster. Only the Storwize V5030 supports the
clustering of two control enclosures, so two Storwize V5030 control enclosures are required
for HyperSwap. Metro Mirror is used to keep both data copies in sync.
The host accesses both I/O groups, as shown in Figure 10-156. The original Metro Mirror
target ID is not used for host access. Instead, HyperSwap presents the Metro Mirror source
ID for the target volume to the host. From the host perspective, the same volume is available
on both I/O groups, although the Storwize V5000 volumes are connected through Metro
Mirror.
Figure 10-156 HyperSwap
To Next Page
Loading...
Need help?
General