Calculating Pool Size; Pool Manager Best Practices - HP StoreEasy 1000 Administrator's Manual

View Jobs—Displays the storage jobs running on the system. You can view the information,
such as name, description, state, and so on.
View Logs—Displays the Pool Manager components and most recent log entries for each
component. Use the Select Component list to select the components for which you want
to view the logs. The available components are Pool Manager Provider, Management Web
Service, and Storage Management Provider.
For detailed information on these tasks, click the respective help icon on the screen.

Calculating pool size

When creating a storage pool, the capacity and free space is calculated based on a number of
factors, including where the storage pool is created. Consider the following when creating pools:
If a storage pool is created for a specific RAID level, the capacity is based on the specified
RAID level. The free space is calculated based on the free space on the smallest of the
physical disks in the pool to support the specified RAID level.
If a storage pool contains a LUN which is greater than 20 MB and has the Logical Drive label
as Reserved, the RAID level of the pool is set to the RAID level of the LUN. Any subsequent
volume in the pool is created at the same RAID level. However, this might fail if a similar
LUN already exists in the pool which is of an incompatible RAID level.
A virtual disk in a storage pool is always striped across all physical disks in the pool.
If the storage pool is created with a tool other than StoreEasy Pool Manager, the free space
calculation is based on the recommended RAID level or it is derived from the reserved LUN
in the pool. If the reserved LUN does not exist, it is automatically created (if there is space
available in the pool) and based on the assumed RAID level. If the reserved LUN is deleted
using a tool other than Windows Server Manager, the RAID level specified in Pool Manager
is used. The chosen RAID level will be whichever offers the highest fault tolerance using
the available set of physical disks in the pool.
As an example, a RAID 6 storage pool is created using StoreEasy Pool Manager that contains
five 3 TB drives. The available space is 9 TB (3 x 3 TB, excluding the two parity drives). If the
pool already contains a 2 TB RAID 1 LUN (virtual disk) using two of the five drives, the available
space is 6 TB (3 x 2 TB, excluding the two parity drives and considering that the available space
in the smallest drive is 2 TB (3-1)).

Pool Manager best practices

The StoreEasy pool best practices provide:
Preset configuration options (pool sets) calculated on a per enclosure basis. An enclosure
may refer to the StoreEasy system and its internal drives or an attached external disk
enclosure, such as the D2700, D3600/D3700, D6020, or D6000.
Guidance to prevent pools from being too large (based on disk type and RAID level) or too
small. Pools that are too large run the risk of data loss if there are multiple disk failures within
the pool. Pools that are too small increase the chance of inefficient capacity utilization.
HPE StoreEasy 1650 Expanded Storage and D3600/D3700 disk enclosures provide a new
pool configuration to provide maximum capacity.
◦
When you select the pool configuration, which has RAID 5 and no spare, the system
displays the following message:This configuration is not recommended as
it may result in data loss due to drive failure. Do you want to
continue?
In case of a drive failure, you must replace the failed drive immediately to prevent data loss.
When you select a pool configuration that contains more than 12 drives, the system displays
the following message: Selected option is not a recommended pool
Using Pool Manager 93