What Caused the Problem?
The Storage Partitions Premium Feature is out of compliance. This normally occurs if an array with Storage Partitions data has been moved into this Storage Subsystem and one of the following conditions exists.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Recovery Steps
1 | Use the table below and the information in the Recovery Guru Details area to determine what actions to take.
|
||||||
2 | A separate Feature Key File is needed to enable each level of Storage Partitions. To increase or enable Storage Partitions, you will need to perform the following:
|
||||||
3 | Select Configure>>Topology/Storage Partitions in the Subsystem Management Window to display the Storage Partition Definitions Window. | ||||||
4 | Highlight the Storage Subsystem (root) node on the left-side of the screen. The right-side of the screen displays all the mappings for this Storage Subsystem and also provides a tally of the Partitions allowed and currently used. There are three rules you should be aware of when considering what mappings need to change to reduce the number of partitions to the allowable limit.
![]() Deleting or changing mappings may cause any host attached to the Storage Subsystem to lose visibility of a filesystem mounted on the Storage Subsystem. Make certain I/Os are stopped on the affected logical drives before changing or deleting them. |
||||||
5 | Delete and/or change a mapping one at a time until the number of partitions is reduced to the allowable limit. Highlight a mapping and use either the Configure>>Logical Drive-to-LUN Mapping>>Change Mapping or Edit>>Delete option. If you change a mapping, either move the mapping to another host group or host that already has mappings, or move it to the default host group. After making the appropriate changes, go to step 6. | ||||||
6 | Select Recheck to rerun the Recovery Guru to ensure that the failure has been fixed.
|