HP 4400 Software Manual page 22

Mirrorclones: For each mirrorclone, go to the Vdisk – General Properties window of the
◦
original virtual disk and record the value listed in the Requested capacity box.
Containers: For each container, go to the Container properties window and record the
◦
value listed in the Capacity box.
To calculate (13 * the capacity of DR group logs): For both the source and
destination DR groups, go to the Log tab of the DR group properties window. Under Log Size,
record the value in the Actual box. Add the log size values of both and multiply the result by
13.
To calculate (0.5 TB * number of DR groups): On the Data Replication Folder
Properties page, record the value in the Total DR groups box, and multiply the value by 0.5
TB.
For example, given 100 virtual disks with total virtual disk capacity of 200 TB, 3 TB of DR
group logs, and 30 DR groups, the total virtual mapped capacity is 200 + (13*3 TB) + (0.5
TB*30) or 200+39+15 or 254 TB. This configuration is supported for an online upgrade. A
configuration with 400 virtual disks with total virtual disk capacity of 800 TB, 4 TB of DR
group logs and 40 DR groups, has a total virtual mapped capacity of 800 + (13*4 TB) +
(0.5 TB*40) or 800+52+20 or 872 TB. This configuration is not supported for an online
upgrade.
If the result is less than the total virtual mapped capacity values cited for the number of virtual
disks you have, an online upgrade is supported. If it is more than the values cited, you must
do an offline upgrade. For HP P6000 Continuous Access environments, see
HP P6000 Continuous Access environment for an upgrade" (page
Stop all storage modification jobs (such as creation, deletion, shrinkage, expansion, and
presentation) 30 minutes before starting the controller software upgrade.
If you are upgrading from XCS 09522000 or earlier and if the configuration contains
mirrorclones, you must delete, detach, or fracture the mirrorclones before starting the controller
software upgrade.
Do not change array components during the controller resynchronization process, which occurs
after the controller software upgrade is complete. The controller software upgrade process
maintains a copy of the metadata in controller memory instead of retrieving metadata from
disks during a resynchronization. Component changes cause metadata to be retrieved from
disks, making the resynchronization process take longer to complete, which may exceed host
or application timeout values.
When the controller software upgrade is complete (including 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 that 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 that the upgrade was completed successfully. To do this,
confirm that the latest I/O module firmware version is displayed.
In a few cases, it has been observed that certain fields on the I/O module tab of the Disk
Enclosure Properties page (in HP P6000 Command View) appear blank, specifically, Hardware
type, Hardware revision, and Assembly serial number. These blank fields do not affect I/O
module operation and do not mean that the upgrade was unsuccessful. HP recommends that
you wait 20 minutes to see if the fields become populated. If not, you can reset the I/O module;
this is an optional step. However, if a disk enclosure reports a failed port or SPOF condition
20 minutes after the upgrade has completed, you must reset the I/O module.
See "Resetting the I/O module" (page 56)
version and reset the I/O module.
22 Preparing for the upgrade
for the steps to verify the I/O module firmware
"Preparing the
38).