Windows
Storage System Configuration
If DMP is used, retain the default settings of the initiator and configure Host Access Mode and Preferred Path for HyperMetro as required. Table 7-25 lists the detailed settings.
HyperMetro Working Mode |
Storage System |
OS Setting |
Host Access Mode |
Preferred Path for HyperMetro |
Description |
---|---|---|---|---|---|
Load balancing mode |
Local storage |
Windows |
Asymmetric |
Yes |
The host uses all paths of a disk with equal priority. |
Remote storage |
Windows |
Asymmetric |
Yes |
||
Local preferred mode |
Local storage |
Windows |
Asymmetric |
Yes |
The host considers the paths from the local storage system as preferred paths, and those from the remote storage system as non-preferred paths. |
Remote storage |
Windows |
Asymmetric |
No |
- Use Huawei Storage Interoperability Navigator to query the combinations supported by DMP.
- If a LUN has been mapped to a host, you must restart the host for the configuration to take effect after you modify the initiator parameters. If the host is running services, stop the services and export the disk group before restarting the host. If you configure the initiator for the first time, restart is not needed.
- If you do not use the recommended configurations, DMP may fail to identify and process paths properly.
- If the storage system version is Dorado V6 6.1.RC3 or later, enable automatic LUN SN synchronization on both storage systems before configuring HyperMetro. If this function is not enabled, one HyperMetro LUN may be identified as two disks by host applications. For details, see section "What Can I Do If the Host Identifies One HyperMetro LUN as Two Disks?" in the HyperMetro Feature Guide for Block.
Configuring the Load Balancing Mode
The method for configuring the load balancing mode when DMP is used is the same as that when the OS native multipathing software is used.
Configuring the Local Preferred Mode
The method for configuring the local preferred mode when DMP is used is the same as that when the OS native multipathing software is used.
Host Configuration
Install Multipath I/O.
Then, install Veritas InfoScale. In this document, installing Veritas InfoScale 7.3.1 on Windows Server 2016 is used as an example. For details about the prerequisites and method for installing Veritas InfoScale 7.3.1, see Veritas InfoScale Installation and Upgrade Guide.
- After installing Storage Foundation/InfoScale, install Device Driver Installers (DDIs) for versions earlier than InfoScale 7.1. It is recommended that you install the latest version of DDIs. You can obtain the DDIs installation package from https://sort.veritas.com/asl. For InfoScale 7.1 and later versions, you do not need to install DDIs.
- After installing Storage Foundation/InfoScale and DDIs, install the DMP patches corresponding to the Storage Foundation/InfoScale version. Table 7-26 provides the links for the patches.
Storage Foundation/InfoScale Version |
Applicable Windows Version |
Patch Link |
Remarks |
---|---|---|---|
Storage Foundation 6.0 |
Windows Server 2008 R2 |
http://svlvault.veritas.com/cgi-bin/patch_central?archive=14248 |
This patch is released on Veritas's internal website. You can obtain the patch from Veritas technical support engineers. |
Storage Foundation 6.0.1 |
Windows Server 2008 R2 |
http://svlvault.veritas.com/cgi-bin/patch_central?archive=14247 |
This patch is released on Veritas's internal website. You can obtain the patch from Veritas technical support engineers. |
Storage Foundation 6.0.2 |
Windows Server 2012 |
- |
|
Storage Foundation 6.1 |
Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 |
- |
|
InfoScale 7.0 |
Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 |
- |
|
InfoScale 7.1 |
Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 |
- |
|
InfoScale 7.2 |
Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 |
- |
|
InfoScale 7.3 |
Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 |
- |
|
InfoScale 7.3.1 |
Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 |
- |
Verification
Verifying the Load Balancing Mode
- After installing DDIs and patches, verify that VHUAWEIAP is displayed under DMP DSMs, Array Type is Active/Active-Asymmetric, and Load Balance Policy is Round Robin(Active/Active) on Veritas Enterprise Administrator.Figure 7-91 Verifying that Huawei storage systems have been properly identified by DMP
- Verify that HyperMetro LUNs have been aggregated on the host. As shown in Figure 7-92, HyperMetro LUNs have been aggregated into the Harddisk1 disk. There are 16 paths in total for this aggregated disk, each of which is marked with a green dot. This indicates that I/Os can be delivered to all of these paths, implementing load balancing.
Alternatively, run the mpclaim -s -d command to check the path quantity and status.
Figure 7-93 Querying path information about the aggregated disk using the CLIIn the preceding command output, LB Policy is Round Robin and State of all paths is Active/Optimized, indicating that I/Os will be distributed on all of these paths for load balancing.
Verifying the Local Preferred Mode
- After installing DDIs and patches, verify that VHUAWEIAP is displayed under DMP DSMs, Array Type is Active/Active-Asymmetric, and Load Balance Policy is Round Robin(Active/Active) on Veritas Enterprise Administrator.Figure 7-94 Verifying that Huawei storage systems have been properly identified by DMP
- Verify that HyperMetro LUNs have been aggregated on the host. As shown in Figure 7-95, HyperMetro LUNs have been aggregated into the Harddisk2 disk. There are 14 paths in total for this aggregated disk, eight of which are marked with green dots. This indicates that I/Os can be delivered to these eight paths, implementing load balancing. The six paths from the non-preferred storage system are not marked with green dots. They are non-preferred paths.
Alternatively, run the mpclaim -s -d command to check the path quantity and status.
Figure 7-96 Querying path information about the aggregated disk using the CLIIn the preceding command output, eight preferred paths (whose LB Policy is Round Robin and TPG_State is Active/Optimized) and six non-preferred paths (whose TPG_State is Active/Unoptimized) are displayed, indicating that the configuration has taken effect.