To establish a hierarchy, identify the next storage pool, sometimes called the subordinate storage pool. The server migrates data to the next storage pool if the original storage pool is full or unavailable.
About this task
You can set up
a storage pool hierarchy when you first define storage pools. You
can also change the storage pool hierarchy later.
Restrictions:
- You cannot establish a chain of storage pools that leads to an endless loop. For example, you cannot define StorageB as the next storage pool for StorageA, and then define StorageA as the next storage pool for StorageB.
- The storage pool hierarchy includes only primary storage pools. It does not include copy storage pools or active-data pools. See Backing up the data in a storage hierarchy.
- A storage pool must use the NATIVE or NONBLOCK data formats to be part of a storage pool hierarchy. For example, a storage pool that uses the NETAPPDUMP data format cannot be part of a storage pool hierarchy.
For detailed information about how migration between storage pools works, see Migrating files in a storage pool hierarchy.