MU3 Release Notes

ManualsBrandsHP ManualsSoftwareHP 3PAR Operating System Software

downgrade, dual SD TPVVs must be converted to single SD TPVVs by removing all of the

snapshots for those TPVVs.

• RAID Multi-Parity (MP) - InForm OS releases prior to 2.3.1 do not support RAID MP; therefore,

any RAID MP Logical Disks (LDs) must be tuned to a supported RAID type or removed prior to

downgrade.

• SD Reclaim Space - SD Reclamation is not supported by previous InForm OS releases. Prior

to a downgrade, SD volumes that has its space reclaimed must be removed. If that SD is used

by snapshots only, then all of its snapshots must be deleted so that SD can be freed. If that

SD space is used by the TPVV itself, then that TPVV would need to be copied over to a new

single SD TPVV. After the copy operation completed, the original TPVV can be removed.

• 256 Read/Write Snapshots - As of InForm OS 2.3.1, the number of read/write snapshots was

increased to 256 per virtual volume. Previous releases supported a smaller maximum number

of read/write snapshots per virtual volume. A downgrade is prevented if any virtual volume

has more read/write snapshots than the maximum supported on the previous release. When

enough snapshots are removed to meet this criterion, the downgrade is allowed.

• Multiple Read/Write Snapshots per Read-Only Snapshot - As of 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 is prevented

if any read-only snapshot has more than one read/write snapshot. Once enough read/write

snapshots are 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 - As of InForm OS release 2.3.1, multiple Remote Copy

links are allowed 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.

Issues Causing a Change to the InForm Configuration

The following issue causes a change to the InForm configuration when downgrading from InForm

OS release 3.1.1.

• Host Personas - If a system running InForm OS release 3.1.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 3.1.1. On a system which only ran 3.1.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 must

be resolved before the downgrade is permitted. One example of this is different host persona

settings sharing a port which can not be supported via port personas.

Running Recovery Manager and Remote Copy (from outside of Recovery Manager)

at the Same Time is not Supported

To synchronize Recovery Manager snapshot data from the production site to secondary site,

Recovery Manager makes direct programmatic calls to the 3PAR Remote Copy product to perform

the background synchronization. When Recovery Manager is doing Application Consistent Remote

Syncs using Remote Copy in Asynchronous Periodic Mode, it is not required to setup the periodic

Known Issues with the InForm OS 19