HP 3PAR InForm OS 3.1.1 MU1 Release Notes

also during the resync periods. The snapshots end up using administrator space depending on the
IOPS and throughput load on the Remote Copy volumes.
• Workaround: Use setcpg -sdgs <increment_value> <volume_name> to increase
the default grow increment. The recommended value is 96 GB.
controlport Configuration Gives Warning after Being Taken Offline (Bug 44989)
Using the -f option with controlport config, the system responded with a confirmation
request, or refused to force the mode change.
• Workaround: If the -f flag was used and the system still prompts for confirmation, respond
to the prompt. If there are other messages, they need to be resolved (e.g. take port offline),
or possibly reissue the command.
showtask for updatevv Displays Incorrect Completion Time (Bug 46328)
showtask for updatevv displays the incorrect completion time.
• Workaround: In these cases updatevv did complete for all virtual volumes in the set, however
the completion time is incorrect. The actual completion time can found by gathering the creation
time of the new snapshots.
Tasks Become Active after a Failed Upgrade (Bug 46418)
There are certain situations after a failed upgrade when tasks that were scheduled and suspended
become active.
• Workaround: After the failed upgrade, use the showsched command to determine which
scheduled tasks need to be suspended again. Use the setsched -suspend
<schedule_name> command.
Remote Copy: Long Waits for Remote Copy Commands to Return Data
When using a 2-node secondary system for a 2-to-1 Remote Copy configuration, commands can
take quite some time to return on a busy system. For this reason, the secondary Remote Copy
system cannot be used as a standalone system. Commands such as showrcopy and showvv
have been observed to take between 2 and 8 minutes to return data. Remote Copy operations are
not impacted, however during the time of a DR restore, where multiple resyncs to different targets
could be taking place, commands can take a significant amount of time to execute.
IMC Crashes during Rolling Upgrade (Bug 46452)
The IMC receives a fatal error when a rolling upgrade is performed on the HP 3PAR Storage
System.
• Workaround: When performing an HP 3PAR Storage System rolling upgrade, it is
recommended that all IMC instances that are connected to that HP 3PAR Storage System be
shutdown.
22 HP 3PAR InForm OS 3.1.1 GA Release Notes