|
|
|
|
|
A storage pool is defined within a disk group in VxVM for use by ISP. A storage pool is a policy-based container for LUNs and volumes. This means that the templates, capabilities and policies that are associated with a storage pool define how storage is organized within the pool.
The following types of storage pools are defined:
For convenience, storage pool definitions are provided that include a number of associated templates that can be used for different purposes.
See Storage pool.
A data storage pool is the first storage pool that is created within a disk group. All other storage pools that are subsequently created within a disk group are clone pools.
Only one data pool can be created within a disk group. It should not usually be necessary to move a data pool to another disk group. However, if this is required, only an entire data pool can be moved. An individual application volume within a data pool cannot be moved. If you want to move a data pool into a different disk group, you must ensure that the data pool contains only those objects that you require.
A clone storage pool contains one or more full-sized instant volume snapshot replicas of volumes within a data pool. (A volume snapshot is an image of a volume's contents at the moment in time that the snapshot was taken. See the Veritas Volume Manager Administrator's Guide for more information about volume snapshots.)
Full-sized, linked break-off and space-optimized instant snapshots are supported for use with ISP. Third-mirror break-off volume snapshots are not supported.
In the release of VxVM 5.0, the introduction of linked break-off snapshot volumes means that it is unnecessary to set up a clone pool. A linked break-off snapshot volume can have different layout and characteristics from its parent volume, it can be set up in a data pool in a different disk group, and it retains its identity if it is relinked to its parent volume and subsequently broken off again.
A clone pool can be moved into another disk group, but an individual snapshot within it cannot. If you want to move a clone pool into a different disk group, you must ensure that the clone pool contains only those snapshots that you require. As an alternative, consider using linked break-off snapshots, as these can be created in a different disk group and storage pool from their parent volume.