HP LeftHand SAN Solutions Support Document - Application Notes - Best Practices for Enabling Microsoft Windows with SAN/iQ®
Table Of Contents
- Application Notes Best Practices for Enabling Microsoft Windows with SANiQ
- Contents
- 1 Chapter: Enabling LeftHand SAN volumes with the Microsoft™ iSCSI 2.0x Initiator
- 2 Chapter: Finding the iSCSI Initiator Version
- 3 Chapter: LeftHand Networks and Microsoft™ MPIO Support
- 4 Chapter: Expanding a Windows Volume on the SAN
- 5 Chapter: Shrinking a Windows Volume on the SAN
- 6 Chapter: Setting the Windows Disk Partition Offset for Optimal Performance
- 7 Chapter: Ensure That Application Resources on iSCSI Volumes Come Online After a Server Reboot
- 8 Chapter: Microsoft™ iSCSI Initiator Session Timeout Setting
- 9 Chapter: Measuring Performance in a Windows Environment
- Overview
- Using Windows Performance Monitor to Measure SAN Performance
- Setting up Windows Performance Monitor
- Saving a Performance Monitor Log for Analysis
- Monitoring More Than One Server Simultaneously
- Scheduling Performance Data Collection
- Using IOMeter as a SAN Benchmark Tool
- Configuring the ISCSI Volume
- Configuring IOMeter
- Configuring IOMeter Access Specification for each Test
- Running the Test
- Interpreting Results
- Access Specifications to Run
- 10 Chapter: Frequently Asked Questions
30
Removing Microsoft™ DSM from the System
If the Microsoft™ DSM is installed, when using SAN/iQ 6.6.x or earlier or on
ANY version of SAN/iQ if not using the LeftHand DSM. LeftHand Networks
recommends uninstalling it from the host server. This is as simple as
re-running the Microsoft™ iSCSI Initiator setup program again and
de-selecting the “Microsoft™ MPIO Multipathing Support for iSCSI” option
(see figure below). Note that this will likely require a server reboot. The
Microsoft™ DSM will then be safely removed. If the LeftHand Networks DSM
was installed prior to re-running the Microsoft™ iSCSI program, the
LeftHand Networks DSM software is left intact.
Note: Any time the iSCSI initiator is reinstalled or upgraded, the
MaxRequestHoldTime value may revert to its default value of 60
seconds. Always reconfirm this setting after reinstalling or upgrading
the initiator. See section 8 for details.