Configuration Database Adoption Failed - One or More Limit(s) Exceeded

What Caused the Problem?

The storage array has failed to adopt the configuration database of one or more recently inserted physical disks because the configuration database exceeds the limits set by this storage array. More specifically, the configuration database has exceeded one or more of the allowable limits set by the storage array for the following:

Total number of virtual disks allowed
Number of Remote Virtual Disk Mirrors
Number of Snapshots per virtual disk
Number of partitions allowed
Number of expansion enclosures allowed
Number of host ports allowed

Due to the nature of the failure the Recovery Guru Details area does not provide specific information about the problem or the physical disks causing the problem.

Caution: Electronic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.

Important Notes

This problem typically results when you 1) insert one or more physical disks or expansion enclosures into a storage array that did not previously contain any physical disks, and 2) the RAID controller modules failed to adopt the configuration database because one or more allowable limits is exceeded. As a result of this failure, the physical disks are recognized only as unassigned physical disks and are locked out of usage by this storage array in order to protect any data on the physical disks.
Every physical disk in a storage array holds a copy of the configuration database, which contains information about the entire storage array, not just what applies to the individual physical disk. Therefore, it is possible that the physical disks you inserted directly contain items as described above OR the physical disks may NOT contain any of these items, rather there are only references to the additional items. For example, there may only be three virtual disks on the physical disks you inserted, but if there were 2048 virtual disks on the storage array that the physical disks came from, then the configuration database will contain references to all 2048 virtual disks, and you would receive this problem if this (the destination) storage array only allows 1024 virtual disks.
The RAID controller modules 'adopt' the configuration database from a set of physical disks ONLY when there were no physical disks previously attached to the RAID controller modules.
The configuration database cannot be repaired in this storage array. Recovering from the failure requires that all of the physical disks are returned to the original storage array (where the physical disks are still considered 'native' and all of the disk groups are still accessible), or they may be inserted into an empty storage array the limits support all items referenced by the configuration database.

Recovery Steps

1	Refer to the Summary tab of the Storage Array Profile and record the maximum limit allowed by this storage array for the following items: Total number of virtual disks allowed Number of Remote Virtual Disk Mirrors allowed* Number of Snapshots per virtual disk allowed* Number of partitions allowed Number of expansion enclosures allowed Notes: *Some premium feature limit information is only available when the feature is enabled. If the limit field is not present, then the limit can be assumed to be 0. In the case of when the expansion enclosure limit is exceeded, you cannot simply remove the additional expansion enclosures from this (the destination) storage array, because there will still be references to the remaining expansion enclosures in the configuration database. You must proceed with step 2. The number of host ports may also be exceeded, but the host port limit is not information that is available in the Storage Array Profile. Contact your Sales representative if you believe the number of host ports is being exceeded. Do not continue with the remaining Recovery Steps because a host port limit problem cannot be corrected without assistance from your Sales Representative.
2	Remove all of the physical disks that were recently inserted into this storage array and return them back to the original storage array. Note: At the original storage array all of the physical disks will still be native and all of the data will still be accessible. Alternatively, instead of returning the physical disks to the original storage array, you may insert them into an empty storage array that is known to have limits that support the items referenced by the configuration database. If you use an alternate storage array, ensure that the RAID controller modules are powered off prior to attaching the physical disks.
3	After the physical disks are recognized by the original or alternate storage array, view the Summary tab of the Storage Array Profile (in the storage management software of the original or alternate storage array) to see how many of each of the following items are currently on that storage array: Total number of virtual disks Number of Remote Virtual Disk Mirrors Number of Snapshots per virtual disk Number of partitions Number of expansion enclosures
4	Follow the appropriate steps to remove the extra items until the total number of each item is at or below the limits supported by this (the destination) storage array, which you recorded in step 1. Notes: Refer to the online help for the original or alternate storage array if you require assistance with this step. If there is a disk group that span more than the number of allowed expansion enclosures, you will need to reconfigure the disk groups so that they are spanning only the allowed number of expansion enclosures. A missing disk group counts against the total virtual disk count.
5	When all of the items meet the limits of this (the destination) storage array, remove the physical disks from the original or alternate storage array.
6	Power down the RAID controller modules to this (the destination) storage array, and ensure that there are no additional foreign physical disks attached to them.
7	Re-insert the physical disks into this (the destination) storage array, and then power-on the RAID controller modules.
8	Click Recheck to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.