Troubleshooting
Problem
When adding units to a ASP that already contains Network Server Storage Spaces (NWSSTG), the NWSSTGs are not guaranteed to have any allocations on the new disks.
Resolving The Problem
If Network Server Storage Space (NWSSTG) performance is a concern and new disk units are being added to increase the number of available arms to improve performance, additional steps may be needed.
When disks are added to an existing ASP, the drives should be added using the Add drives to the ASP and balance data option from the service tools menu. This moves some of the data off the old units to the new units, bringing all drives in the ASP to the same percentage full to prevent performance problems caused by "hot" disk arms.
However, there are two factors that may prevent the new drives from improving the performance of the storage spaces:
| o | Disk balancing (add and balance in service tools, or STRASPBAL) will not move NWS storage spaces if the NWSD is varied on. |
| o | Disk balancing does not guarantee that every existing object will be spread onto the new drives. |
If you wish to make sure previously existing NWSSTGs and their internal structures are spread across all available disks in the ASP, you should do the following:
| 1. | Back up all NWSSTGs that are in the ASP in question. (Two copies would be a good idea to ensure against media failure.) |
| 2. | Delete all NWSSTGs that were backed up in Step 1. |
| 3. | Re-balance the ASP by using the following command: STRASPBAL TYPE(*CAPACITY) ASP(ASP number) TIMLMT(*NOMAX) |
| 4. | Wait for ASP balancing for ASP message (CPI1475 to be logged in QHST). |
| 5. | Once the ASP re-balance has completed, restore and re-link the NWSSTGs that were backed up in Step 1 to spread the data across all drives in the ASP. |
Historical Number
523382513
Was this topic helpful?
Document Information
Modified date:
11 November 2019
UID
nas8N1012969