 | ||
| Configuring disk groups for separate storage capacity pools or common pools | ||
|---|---|---|
| Prev | Best practices configuring SFW disk groups for availability | Next |
| ||
| Configuring disk groups for separate storage capacity pools or common pools | ||
|---|---|---|
| Prev | Best practices configuring SFW disk groups for availability | Next |
Creating multiple disk groups creates separate storage capacity pools.
Effective use of subdisks is key to efficient disk group structure. The subdisks composing any given volume must be allocated from disks within a single disk group. Raw physical storage in one of these pools is available exclusively for use within the pool and cannot be used in other disk groups, unless an administrator specifically moves a disk from one disk group to another.
System administrators must decide on the basis of projected application and administrative needs whether to use disk groups to create disjointed storage pools or to manage all storage as a common pool.
Effective configuration of disk groups depends on an organization's application needs.
If a critical application requires frequent volume expansion, allocating its storage in a private disk group helps guarantee that capacity is available when required. When storage capacity is added to the system, it is not absorbed by other applications.
If a critical application unexpectedly requires additional storage and none is available in the disk group from which its volumes are allocated, the application will fail, even if the required amount of storage is available in other disk groups.
In general, multiple pools give the administrator greater flexibility, whereas a common pool may be more convenient for applications.