HP StorageWorks EVA Hardware Providers for Windows 2003 for 32-bit and Ext systems 64-bit platforms release notes (T1634 - 96063, September 20, 2006)
• Supports VDS 1.1 only on Windows Server 2003 EE or SE Release 2 (VDS 1.0 is supported on
WindowsServer2003EEorSESP1)
• Supports mixed RAID types between source and copy
Fixes
None
Prerequisites
• EVA 3000 and EVA 5000 disk arrays
Microcode: (minimum level) 4.004
HP StorageWorks Command View EVA 4.1 and 5.0.3
HP StorageWorks Business Copy EVA
• EVA 4000, EVA 6000 and EVA 8000 disk arrays
Microcode: (minimum level) XCS 5.110
HP StorageWorks Command View EVA 4.1 and 5.0.3
HP StorageWorks Business Copy EVA
Installation instructions
There are two i
nstallers for the hardwa re providers: HP StorageWorks VDS Hardware Provider
for EVA.msi and HP StorageWorks VSS Hardware Provider for EVA.msi.
See the following manuals provided with the software for installation instructions:
• The HP Storag
eWorks EVA Hardware Providers administration guide (T1634–96052, February
2006) provides detailed installation and removal instructions
• The HP StorageWorks EVA Hardware Providers quick start guide (T1634–96053, February
2006) provid
es summary instructions.
Before you install the HP EVA Hardware Providers, remove the previous provider versions using the
Windows Add/Remove Programs Control Panel. Before removing the hardware providers, issue a net
stop VSS and/or a net stop VDS command from the command line.
In order to install and configure the HP EVA VSS hardware provider on cluster nodes, you must h ave
installed the Microsoft Distributed Transaction Coordinator, and it must be running.
In most cases, such as in Microsoft Exchange and SQL clusters, it is required that a MSDTC cluster
resource be created as part of the Application setup, so it’s likely no additional steps are required to
install th
e HP EVA VSS hardware provider.
If you intend to install the HP EVA VSS hardware provider on application server cluster nod es that do
not already have the MSDTC installed and running, see Microsoft TechNet article, "How to Install the
Microsoft Distributed Transaction Coordinator in a Windows Server 2003 Server Cluster" located at the
followin
gURL:h
ttp://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/
be6c39e1
-7432-4a5e -b638-57a7826f13f1.ms px?mfr=true.
Compatibility/Interoperability
• Only one dedicated Command View workstation is supported within the SAN configuration
which manages VDS/VSS storage resources.
• If VSS EVA and C V EVA are present on the same server, do not include the drive letter or mount
point where the CV EVA software is located as p a rt of a shadow copy volume set. For example, if
CV EVA is on drive D, do not include drive D with an EVA LUN in a shadow copy set. Doing so
causes VSS EVA to time out due to con flict with Command View logging on this drive.
4