How SMAPP handles changes in disk pool configuration
When you restart the system, the system checks to see if your disk pool configuration has changed. The system may change either the size of the SMAPP receiver or the placement of the receiver based on the change to the disk units.
When you restart your system, the system checks to see if your disk pool configuration has changed. The system does the following:
- If any disk units have been added or removed from an existing disk pool, the system may change either the size of the SMAPP receiver or the placement of the receiver.
- If any new disk pools are in the configuration and do not have any access path recovery times assigned for SMAPP, the system assigns a recovery time of *NONE for that disk pool. If you remove a disk pool from your configuration and later add it back, the access path for that disk pool is set to *NONE, even if that disk pool previously had a recovery time for access paths.
- If all basic user disk pools have been removed from your configuration so that you have only the system disk pool, the system access path recovery time is set to the lower of the following values:
- The existing system access path recovery time.
- The current access path recovery time for disk pool 1. If the current access path recovery time for disk pool 1 is *NONE, the system access path recovery time is not changed.
When you vary on an independent disk pool, the system checks to see if any disk units have been added or removed from the independent disk pool. The system may change either the size of the SMAPP receiver or the placement of the receiver based on the change to the disk units. If this is the first time the independent disk pool is varied on, then the system assigns a recovery time of *NONE for that independent disk pool.
When you add disk units to your disk configuration while your system is active, or your independent disk pool is varied on, the system does not consider those changes in making SMAPP storage decisions until the next time you restart the system, or vary on the independent disk pool. The system uses the size of the disk pool to determine the threshold size for SMAPP receivers. If you add disk units, the system does not increase the threshold size for the receivers until the next time you restart the system restart or vary on the independent disk pool. This means that the frequency of changing SMAPP receivers will not go down until you restart the system, or vary off the independent disk pool.
When you create a new user disk pool while your system is active, add all of the planned disks to the disk pool at the same time. The system uses the initial size of the new disk pool to make storage decisions for SMAPP. If you later add more disk units to the disk pool, those disk units are not considered until the next time you restart the system or vary on the independent disk pool. When you create a new user disk pool, the access path recovery time for that disk pool is set to *NONE. You can use the EDTRCYAP command to set a target recovery time for the new disk pool, if desired.
Parent topic:
System-managed access-path protectionRelated concepts
Disk management