HP StorageWorks Continuous Access EVA Administrator Guide (T3687-96043, December 2005)

Upgrading contr
oller software
Planning a controller software upgrade
Before upgrading array controller software, ensu re that all a rrays in remote replication relationships are
fully functional with no failed hardware. The following additional conditions must be met:
• All arrays in remote replication relationships are running the same version of controller software
in the VCS or XCS series.
• In multiple replication relationships, ensure that:
• No more than two versions (the previous version and the new version) of the controller
software that is being upgraded are running at any time.
• No more than one version of the controller software (XCS or VCS) that is not being upgraded
is running.
• If you need to update both VCS and XCS, complete the upgrade of one before upgrading
the other.
• Complete the upgrade process within one week (168 hours). The upgrade window begins with
the upgrade of the first array. It concludes when a ll arrays in a direct or indirect replicatio n
relationship with the first array have been upgraded.
• S uspend DR group replication for the duration of the upgrade process on the destination, even if
the intersite links are unavailable.
• Do not create or delete DR groups or add or remove members from DR groups while any array in
a remote replication relationship is on the previous version and others are on the new version.
HP recommends upgrading controller software during the lowest I/O activity on the array.
Coordinating controller software upgrades on source and destination arrays
HP recommends the following procedure for upgrading controller software on source and destination
arrays:
1. Suspend
remote replication of DR groups on the source array . Logging of source DR groups will
begin an
d there will be little, if any, remote replication to the destination array. Replication must be
suspen
ded, even if the intersite links are unavailable.
2. While source DR groups are suspended, upgrade the controller software on the destination array.
3. After upgrading the controller software on the destination array, resume remote replication of the
source DR groups.
4. Wait for the source D R group logs to complete merging on the destination array.
5. When m erging i s complete, upgrade the controller soft ware on the source array.
Special remote replication uses
Usin
g DR groups a nd snapclones to move data
NOTE:
An HP Business Copy EVA license is requir ed for the following procedur e.
Use this procedure to move a copy of your data residing on a virtual disk to a remote location by the use
of a snapclone. A snapclone is an exact copy of your virtual disk at the particular point–in–time it was
created. The virtual disk being copied to the remote site becomes part of a DR group that can then be
used as a new source virtual disk. You can use this procedure with data movement services such as:
58
Managing remote replication