Xcs 09522000 Upgrade Considerations - HP 6400/8400 Software Manual

total amount of time that a host I/O will be allowed to complete successfully beyond the 60 second
timeout values. Note that some applications may be more sensitive to I/O delays.
• Processing host I/O during the upgrade – The upgrade competes with host requests that have a
higher priority, which can affect the upgrade outcome. To ensure that host I/O from business
critical applications or operations is minimized during the upgrade, select a time when a host I/O
disruption would minimize the impact to the business operations.
• Communicating with HP Command View EVA – The first steps of the upgrade have a lower priority
than host I/O. The upgrade can extend beyond the timeout values expected by HP Command
View EVA, which may result in losing management connectivity to the EVA. A HP Command View
EVA discover operation may be required to re-establish communication with the EVA.

XCS 09522000 upgrade considerations

Before upgrading to XCS 09522000, consider the following:
• The EVA resynchronization time is affected by both mapped virtual disk capacity and the number
of virtual disks. Mapped virtual disk capacity is the total of all virtual disks, snapshots, snapclones,
mirrorclones, containers, and data replication log disks. When upgrading from XCS 0950xxxx
or 0952x000 to 09522000, to ensure a resynchronization time of less than 60 seconds, the total
mapped virtual disk capacity and number of virtual disks configured on an EVA should be one of
the following:
• less than 400 TB mapped capacity and less than 512 virtual disks created
• less than 300 TB mapped capacity and less than 1024 virtual disks created
• less than 125 TB mapped capacity and less than 2048 virtual disks created
NOTE:
Multiply the capacity of each data replication log disk by 15 to calculate the total capacity of the
data replication log disks. Add the total capacity of the data replication log disks to your total
virtual disk capacity (all virtual disks, snapshots, snapclones, containers, and mirrorclones); if it
is less that the total mapped virtual disk capacity for the number of virtual disks you have, an
online upgrade is supported.
• Stop all storage modification jobs (such as creation, deletion, presentation) 30 minutes before
beginning the controller software upgrade.
• If the configuration contains mirrorclones, you must delete, detach, or fracture the mirrorclones
before starting the controller software upgrade.
• Do not change any array components during the controller resynchronization process, which occurs
after the controller software upgrade has completed. The controller software upgrade process
maintains a copy of the metadata within the controller memory instead of retrieving metadata from
disks during a resynchronization. Component changes will cause metadata to be retrieved from
disks, making the resynchronization process take longer to complete, which may be beyond host
or application timeout values.
• After the controller software upgrade has completed (which includes upgrading the firmware on
the disk enclosure I/O modules), it may take up to 20 minutes to stabilize device port operations.
(The I/O module firmware upgrades are performed sequentially to ensure host I/O continues
during the upgrade.) HP recommends that you check the state of the I/O modules on each disk
enclosure to ensure the upgrade completed successfully, which you can verify by checking that
the latest I/O module firmware version displays.
In a few cases, it has been observed that some fields on the I/O module tab of the Disk Enclosure
Properties page (in HP Command View EVA) appear blank, specifically Hardware type, Hardware
10 Getting started