3PAR InForm Operating System 2.3.1 Release Notes (320-200178 Rev D, May 2010)

2.24
3PAR InForm Operating System Release Notes InForm OS Version 2.3.1
■ Multiple Read/Write Snapshots per Read-Only Snapshot - In InForm OS 2.3.1, the
creation of multiple read/write snapshots per read-only snapshot is permitted. Previous
releases supported a single read/write snapshot per read-only snapshot. A downgrade will
be prevented if any read-only snapshot has more than one read/write snapshot. Once
enough read/write snapshots have been removed to meet this criteria, the downgrade is
allowed.
■ Synchronous Long Distance Remote Copy - If there are Remote Copy groups
configured with multiple targets, those groups must be removed or reduced to a single
target before a downgrade is allowed.
■ 16 TB Support - Virtual volumes larger than the maximum size supported in a previous
release must be removed before a downgrade is allowed.
■ Multiple Remote Copy Links per Node - InForm OS release 2.3.1 allows multiple Remote
Copy links to be configured on a individual node. Previous releases only allowed a single
link per node. Before downgrading, ensure that additional Remote Copy links are dismissed
to ensure a valid configuration for the downgrade. A check is run prior to downgrade to
validate the existing Remote Copy link configuration.
2.8.2.2 Issues Causing a Change to the InForm Configuration
The following issue causes a change to the InForm configuration when downgrading from
InForm OS release 2.3.1.
■ Host Personas - If a system running InForm OS release 2.3.1 is downgraded, host persona
fields are cleared and the old port persona settings resume effect. However, these settings
are not kept up-to-date nor are they converted back on downgrade, so they will not reflect
any configuration changes made since loading 2.3.1. On a system which only ran 2.3.1,
there will be no port persona settings to revert to.
Prior to the downgrade, a check is run to ensure the system can run in the downgraded
state. If host persona specific configurations are detected, a message is issued. This
condition will need to be resolved before the downgrade is permitted. One example of this
would be different host persona settings sharing a port which can not be supported via
port personas.