HP StorageWorks Enterprise Virtual Array 3000/5000 Release Notes VCS V4.004 (5697-5794, March 2006)

IMPORTANT NOTES AND WORKAROUNDS
This section identifies important notes and workarounds specific to the EVA3000/5000 hardware and
VCS software
. O perating constraints for related software applications a re included in the following
documents:
• HP OpenView Storage Management Appliance Software release notes
• HP StorageW
orks Com mand View EVA release notes
• HP StorageWorks Continuous Access EVA release notes
• HP StorageWorks Business Copy EVA release notes
• HP Storage
Works Replication Solution Manager release notes
Refer to Ta
ble 3 for links to the web sites for these products.
Any operating constraints pertaining to the host operating system can be found in the individual operating
system release notes. See "Supported operating system speci fications" on page 3.
Upgrading in an HP Continuous Access EVA environment
The following restrictions apply when upgrading to VCS v4.004 on EVA3000/5000 storage systems
running Continuous Access EVA. This is only an overview of some of the steps involved in using HP
Continuous Access EVA. For more information on HP Continuous Access EVA, access the documentation
using the link in Table 3 on page 3.
• The upgrade process should be completed within one week (168 hours). The time window begins
with the upgrade of the first storage system. It concludes when all storage systems with a direct or
indirect Continuous Access relationship to the first storage system have been upgraded.
• Ensure that all storage systems involved in a D R relationship are fully functional with no failed
hardware.
• When using multiple Continuous Access relationships, make sure the following cond itions are met:
• Not more than two VCS versions (either v3.028 or v4.004) are running.
• All EVA 4000/6000/8000 storage systems must be running only one version of XCS (V5.031
or later).
• If you need to update both VCS and XCS, do not attempt to upgrade b oth simultaneously.
Complete the upgrade of one family of firmware before upgrading the other .
• Suspend DR group replication for the duration of the upgrade process on the destination, even if
the intersite links are not available.
A code load of one controller forces both controllers on a storage system to reboot. If the controller being
upgraded is used as a d estination for replication I/O, the source controller logs new I/O while the
destination controller reboots. After completing the fi rmware upgrade of the destination then resume
the replication to allow the controller to perform a merge. Wait for the merge to conclude after a code
load, or wait three minutes—whichever is longer—before performing the code load on any other storage
system in the relationship.
Disk Resource Pending Timeout for Microsoft® Windows® cluster configurations
If the disk resourc e count is greater than 8, HP recommends increasing the Pending Timeout parameter
for each disk resource from 180 seconds to 360 seconds. Increasing the timeout value helps maintain
continuous operation of disk resources across SAN perturbations.
T
o view and set the Pending Timeout parameter:
1. Open the Microsoft Cluster Administrator.
2. Select a disk group resource in the left pane.
3. Right click each disk resource in right pane, one at a time, and select Properties.
4. Select the Advanced tab from the Properties menu.
5. Locate the Pending Timeout value and change it to 360.
6