Storage License Calculator for Open-E JovianDSS

This calculator helps you to find the exact license required for your storage setup with Open-E JovianDSS, based on your individual specifications.

Storage license calculator

1. System configuration


2. Storage calculation


3. Summary

ZFS Pool design details

The Pool
A virtual storage pool is used by Open-E JovianDSS to control its data groups. The pool treats each data group as single device. This means that performance of the pool is dependent on the amount of groups and not the amount of total disks. For high performance installations, mirrors with 2 or 3 disks in each data group are recommended. In normal scenarios, redundancy levels Z-1, Z-2 and Z-3 are used to increase the pools capacity efficiency. Thanks to RAM and SSD Caching, enough performance for typical scenarios can still be achieved.

Data groups
Data groups are virtual devices that consist of any amount of HDDs or SSDs. It is very important to use the same disks for the whole pool. Data stored in the pool, is striped evenly over all data groups in order to maximize performance. Redundancy is provided by parity disks within each data group. Their amount is determined by the redundancy level. The number of parity disks equals the amount of disks that are allowed to fail within a data group without losing data.

Non-data groups
These groups are not included in the Storage License Calculator, because they don't affect the license's required storage capacity. Non-data groups are disks in read cache, write log and spares. Typically, SSDs are used for read cache and write log, to increase the systems overall performance. Spare disks are identical to the disks in the data group and available in the pool to replace faulty disks. None of these are used to store the original data, and are therefore not licensed by Open-E JovianDSS.

X

Step 1 of 3 - System configuration

Choose the configuration from the list below.

Configuration type

Single Node
Disk located internally in storage server
JBOD connected to storage server through SAS
JBOD connected to storage server through FC
HA Cluster with Common Storage
Standard HA Cluster Feature Pack
Disk located internally in storage server
JBOD connected to storage server through SAS
JBOD connected to storage server through FC
HA Cluster with Dual Storage
Standard HA Cluster Feature Pack
Disk located internally in storage server
JBOD connected to storage server through SAS
JBOD connected to storage server through FC
JBODs connected to storage server with ATTO switches
HA Cluster over Ethernet
Advanced HA Metro Cluster Feature Pack
Disk located internally in storage server
JBOD connected to storage server through SAS
JBOD connected to storage server through FC

Step 2 of 3 - Calculate your storage

Learn more about ZFS Pool design »
Selected system configuration

SYSTEM DESCRIPTIOIN

CONNECTION TYPE

Select one of two calculation methods and fill fields with correct values.

Calculate by demanded usable storage capacity

Select the capacity of disks you want to use in your system and the total size of usable capacity. The Storage License Calculator will automatically select the smallest amount of disks with recommended disks per data group to reach the demanded usable storage capacity.
Fill fields below with correct values.

Demanded usable data storage capacity

TiB

Disk capacity

TB

Calculate by number of data groups and disks in data group

Select how many data groups are in your system and how many disks should be in each data group. The Storage License Calculator will automatically calculate the usable storage capacity.
Fill fields below with correct values.

Disk capacity

TB

Disks in data group

Number of data groups

Disk capacity

The RAW unformatted disk size as provided by the disk vendor.

Number of data groups

The number of data groups that will be used in the pool. The data is striped over all groups by Open-E JovianDSS.

Disks in data group

The number of disks that will be used in each data group. When a disk fails it is replaced with a preinstalled spare or the administrator replaces the faulty disk with a new one. The data is then rebuilt from the remaining disks. Each redundancy level has a minimum and recommended maximum number of disks. The minimum is needed to create the smallest possible group, while the recommended maximum minimizes the risk of losing too many disks during rebuild (and therefore the data on the data group).

Data group redundancy level

Select one data group redundancy level from below.

Mirror (min. 2 disks in group)


Mirror allowing any number of disks to be mirrored. A mirror group built out of 2 disks has 1 parity disk. Total capacity equals the sum of all disks minus two.

Z-1 (3-8 disks in group)


One disk in a data group may fail. Total capacity equals the sum of all disks minus one.

Z-2 (4-24 disks in group)


Two disks in a data group may fail. Total capacity equals the sum of all disks minus two.

Z-3 (5-48 disks in group)


Three disks in a data group may fail. Total capacity equals the sum of all disks minus three.
The redundancy level sets the number of parity disks in a data group. This number specifies how many disks may fail without losing operation of the data group. Higher parity levels require more calculation from the system, which increases redundancy at the cost of performance.
RAID-Z is a data parity distribution scheme like RAID-5, but uses dynamic stripe width; every block is its own RAID stripe, regardless of block size, resulting in every RAID-Z write being a full-stripe write. RAID-Z is also faster than traditional RAID-5 because it does not need to perform the usual read-modify-write sequence.

Non data disk group information

Write log

Number of disks

Capacity of each disk

GB
Read cache

Number of disks

Capacity of each disk

GB
A storage area on data disks that temporarily holds synchronous writes until they are written to the zpool. Stored on separate media from the data, typically on a fast device such as a SSD
A device used to cache storage pool data. These devices provide an additional layer of caching between main memory and disk. For read-heavy workload, where the working set size is much larger than what can be cached in the main memory, using cache devices allows much more of this working set to be served from low latency media.

Step 3 of 3 - Summary

Selected system configuration

TYPE

CONNECTION TYPE

Selected calculation mode

Calculated by demanded usable storage capacity

Demanded usable data storage capacity: 0 TB

Disk capacity: 0 TB

The RAW unformatted disk size as provided by the disk vendor.

Calculated by number of data groups and disks in data group

Disk capacity: 0 TB

The RAW unformatted disk size as provided by the disk vendor.

Disks in data group: 0

The number of disks that will be used in each data group.

Number of data groups: 0

The number of data groups that will be used in the pool. The data is striped over all groups by Open-E JovianDSS.

Data group redundancy level: REDUNDANCY

Mirror allowing any number of disks to be mirrored. A mirror group built out of 2 disks has 1 parity disk.

Non data disk group information

Write log:

0 GB

Read cache:

0 GB
Zpool configuration details
  • Number of data groups0

  • Disks in data group0

  • 0 disks in total0

  • Demanded usable data storage capacityTiB

Zpool storage characteristics
  • Gross unformatted storage capacityTB

  • Net unformatted storage capacityTB

  • Gross formatted storage capacityTiB

  • Net formatted storage capacityTiB

  • Usable data storage capacityTiB

Pool performance Index
  • ReadNR

  • WriteNR

Pool Capacity Efficiency
The ratio of usable capacity to total physical capacity in pool. 80% means that 8 out of 10 TB are used as usable storage. The higher the percentage the better for the user.

0%

100%

NR%

Zpool data groups simulation

Group NR

NR
NR

X

...

Recommended licenses

Required total license capacity 0 TB

Only data storage groups are calculated! The calculation made by this tool do not include the number of disks required for additional groups: read cache, write log and spare disks. Please consider contacting pre-sales for more information.

Gross unformatted storage capacity

The unformatted capacity of all disks, before RAID is applied.

Net unformatted storage capacity

The unformatted capacity of all disks, after RAID is applied.

Gross formatted storage capacity

The formatted capacity of all disks, before RAID is applied. This capacity is used to calculate this value in TB we use the formatted capacity factor of 0.91, as operating systems show disk space in 1,024 byte units, while hard drive manufacturers use 1,000 byte units. The formatted capacity factor allows calculating one unit into the other. Find more information in the article on our blog

Net formatted storage capacity

The formatted capacity of all disks, after RAID is applied. It is used to calculate the licensed capacity for mirrored arrays.

Usable data storage capacity

The actual usable capacity that is exported to the storage client. It is the result of multiplying net formatted storage capacity with the pool max used capacity factor.

Pool max used capacity factor

Open-E JovianDSS creates metadata to write and read the stored information, and it needs free space to work with the stored data and use features such as copy-on-write and snapshots. This is an estimated value of how much space should be reserved for these purposes.

Pool performance Index

The disks in a data group work in unison, which means that their effective performance is the same as one disk, no matter how many there are. Additionally, more computing power is required when more data groups are used in a pool. The Performance Index demonstrates the amount of effective performance when compared to single disk. Example: A performance index of 4.6 is equal to the performance of 4.6 single disks without redundancy or striping. Learn more about ZFS Pool design »

Write log

A storage area on data disks that temporarily holds synchronous writes until they are written to the zpool. Stored on separate media from the data, typically on a fast device such as a SSD

Read cache

A device used to cache storage pool data. These devices provide an additional layer of caching between main memory and disk. For read-heavy workload, where the working set size is much larger than what can be cached in the main memory, using cache devices allows much more of this working set to be served from low latency media.

Note: Results are for single pools only! The required total license capacity is estimated for data groups in a single pool only. If you want to estimate the license capacity for more than one pool, please calculate each pool separately or multiply the results by the desired number of pools (pools must have the same size).