HP 6100 HP 4x00/6x00/8x00 Enterprise Virtual Array Updating Product Software G - Page 6

Getting started, Upgrade overview, Online upgrade, Offline upgrade (shutdown upgrade)

Page 6 highlights

1 Getting started This chapter provides information about required kits and reference documentation. Before you perform the upgrade procedures, ensure that your system meets the requirements. IMPORTANT: To upgrade from an HSV200-A or HSV210-A controller to an HSV200-B or HSV210-B controller, HP requires that you also upgrade the I/O modules (A and B) to AD623C and AD624C on each shelf. If you are upgrading to an EVA6100 (HSV200-B) or EVA8100 (HSV210-B) and you do not already have the 30-10022-01 loop switches installed, you must also upgrade the loop switches to 30-10022-01. See the HP 4x00/6x00/8x00 Enterprise Virtual Array User Guide for more information. Upgrade overview Depending on the upgrade path for your configuration, an upgrade can be done either online or offline. Online upgrade EVA controller software is upgraded while the controllers are receiving I/O. The controllers resynchronize simultaneously while hosts and applications continue to run. The resynchronization during an online upgrade represents a single disruption of I/O, not the multiple disruptions seen with some upgrade types. However, you must consider host and application timeouts when doing an online upgrade. Offline upgrade (shutdown upgrade) All host I/O to the storage system must be stopped. All applications and hosts are shut down before you begin the controller upgrade, and restarted when the upgrade is complete. An offline upgrade requires scheduling time with application managers and having staff on hand to shut down and restart applications and hosts. While actual upgrade time may be short, offline upgrades can require several hours to complete from the time first application shuts down until all hosts and applications have returned to service. 6 Getting started

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66

1 Getting started
This chapter provides information about required kits and reference documentation. Before you
perform the upgrade procedures, ensure that your system meets the requirements.
IMPORTANT:
To upgrade from an HSV200-A or HSV210-A controller to an HSV200-B or
HSV210-B controller, HP requires that you also upgrade the I/O modules (A and B) to AD623C
and AD624C on each shelf. If you are upgrading to an EVA6100 (HSV200-B) or EVA8100
(HSV210-B) and you do not already have the 30-10022-01 loop switches installed, you must also
upgrade the loop switches to 30-10022-01. See the
HP 4x00/6x00/8x00 Enterprise Virtual Array
User Guide
for more information.
Upgrade overview
Depending on the upgrade path for your configuration, an upgrade can be done either online or
offline.
Online upgrade
EVA controller software is upgraded while the controllers are receiving I/O. The controllers
resynchronize simultaneously while hosts and applications continue to run. The resynchronization
during an online upgrade represents a single disruption of I/O, not the multiple disruptions seen
with some upgrade types. However, you must consider host and application timeouts when doing
an online upgrade.
Offline upgrade (shutdown upgrade)
All host I/O to the storage system must be stopped. All applications and hosts are shut down before
you begin the controller upgrade, and restarted when the upgrade is complete.
An offline upgrade requires scheduling time with application managers and having staff on hand
to shut down and restart applications and hosts. While actual upgrade time may be short, offline
upgrades can require several hours to complete from the time first application shuts down until all
hosts and applications have returned to service.
6
Getting started