Managing independent disk pools
In a high-availability environment, it is necessary that the application
and its data remain consistent among the nodes that participate in high availability. An independent
disk pool, also called an independent auxiliary storage pool (IASP), is a disk pool that contains
objects, the directories, or libraries that contain the objects, and other object attributes such as
authorization and ownership attributes. An independent disk pool can be used to help in this
situation. Ownership of data and applications that are stored in an independent disk pool can be
switched to other systems that are defined in the device CRG. PowerHA® technology provides high availability during planned and some unplanned
outages. 
- Making a disk pool unavailable
You can select an independent disk pool to make it unavailable (vary it off). You cannot access any of the disk units or objects in the independent disk pool or its corresponding database until it is made available (varied on) again. The pool can be made available again on the same system or another system in the recovery domain of the cluster resource group. - Making your hardware switchable
In anIBM® i high-availability environment, you must
make an external expansion unit switchable. - Quiescing an independent disk pool
In anIBM i high-availability
solution, independent disk pools are used to store resilient data
and applications. Some system functions, such as performing backups,
require that you temporarily suspend changes to that data while the
operation occurs. - Resuming an independent disk pool
After you have quiesced an independent disk pool in anIBM i high availability environment for backup
operations, you will need to resume the independent disk pool to ensure changes
that are made to the data during the quiesce are updated.
Parent topic: Managing PowerHA
Related information:
