MU3 Release Notes

resync time for the Remote Copy groups. Setting up periodic resync time for Remote Copy groups

when recovery manager is active could disrupt the operation of Recovery Manager.

Workaround:

Remote Copy can support the mixture of Recovery Manager snapshots and Remote Copy snapshots

(outside of Recovery Manager) if the following procedure is followed:

Inside the Recovery Manager Windows scheduler script:

1. Set the Remote Copy period to 0.

2. Verify Remote Copy SyncStatus as "Synced".

3. Execute Recovery Manager snapshot creation for Remote Copy.

4. Wait for SyncStatus to be completed and Recovery Manager to take snapshot of secondary

volumes.

5. Recovery Manger will monitor the SyncStatus to be "Synced" every 120 seconds as default

then issue snapshot creation of secondary volumes.

6. Reset Remote Copy period to the sync period it was at prior to setting to 0 in step 1.

WARNING! Steps 2 and 4 are critical to ensure Recover Manager-created snapshots and

Remote Copy-created snapshots do not interfere with each other.

Windows 2003 Pop-Up

Client machines running the Windows 2003 operating systems receive an unknown device pop-up

from Windows Plug and Play security checking when connecting to a 2.3.1 InServ Storage Server

system.

Workaround: To avoid this device pop-up message you can install the NULL driver for 3PAR SCSI

Enclosure Service device available at HP Software Depot: https://h20392.www2.hp.com/portal/

swdepot/displayProductInfo.do?productNumber=3PAR_Null_Driver.

Cage Loop Down Alert is not Auto-Recovered (Bug 40274)

There are certain conditions during which a drive cage loop missing alert may not be auto-resolved

even though the drive cage loop comes back.

Workaround: Once it is verified that the alert is indeed invalid, check showcage -d and showpd

to verify the loop is present. The alert can be removed by removealert or setalert.

System Manager Could Fail During Rolling Upgrade if Remote Copy Groups Running

(Bug 40867)

When creating snapshots during the shutdown process there is a known race condition that may

result in a system manager terminating unexpectedly. Therefore, the user is no longer permitted to

manually take snapshots during this process. However, this is not the case with snapshots that are

taken when a synchronous remote copy group is stopped.

During a rolling upgrade synchronous groups are normally not stopped. However, if there is a

target failure during the process any associated groups will automatically be stopped, and if the

group is synchronous a snapshot for each volume in the group will be taken. This leaves the system

open to hitting the race condition described above.

Workaround: Stop all remote copy groups before starting a rolling upgrade.

No Explicit Way to Reset the Default Value for Tunelinks (Bug 43579)

The setrcopytargettunelinks command can be used to adjust the performance value for

the target's links using the <bandwidth> and <latency> specifiers. After using this command,

there is no explicit way for the user to reset the tuning parameters back to the default value.

20 HP 3PAR InForm OS 3.1.1 GA Release Notes