Disk pools are used to manage system performance and backup requirements,
as follows:
- You can create a disk pool to provide dedicated resources for frequently
used objects, such as journal receivers.
- You can create a disk pool to hold save files. Objects can be backed up
to save files in a different disk pool. It is unlikely that both the disk
pool that contains the object and the disk pool that contains the save file
will be lost.
- You can create different disk pools for objects with different recovery
and availability requirements. For example, you can put critical database
files or documents in a disk pool that has mirrored protection or device parity
protection.
- You can create a disk pool to place infrequently used objects, such as
large history files, on disk units with slower performance.
- You can use disk pools to manage recovery times for access paths for critical
and noncritical database files using system-managed access-path protection.
- An independent disk pool can be used to isolate infrequently used data
in order to free up system resources to be utilized only when it is needed.
- An independent disk pool in a clustered environment can provide disk storage
that is switchable, allowing continuous availability of resources.