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.

Open-E JovianDSS Storage License Calculator

The Open-E JovianDSS Storage License Calculator is a tool which enables setting up configurations that are proven to be secure and efficient and that are recommended by Open-E.

Please note that despite the Open-E JovianDSS's flexibility some unconfirmed configurations might result in low efficiency and thus to lower security. For your data security, please set up and adjust your configuration exactly to the type of stored data.

x

Select system type / architecture

Please select system type.

Single node

Simple architecture with one server.

Single node

Drives can be SAS or SATA. When using JBODs, SAS JBODs and SAS cables are required.

Shared storage HA Cluster

Single storage shared between the nodes.

Shared HA Cluster

Common storage (internal, JBODs, JBOFs, etc.), both nodes are directly connected to all storage devices in the cluster at the same time. When using JBODs, SAS JBODs and SAS cables are required.

Non-shared storage HA Cluster

Each node has it's own storage.

Non-shared HA Cluster

Each node has direct access only to its own storage devices. Nodes communicate with each other to access their counterparts' storage. When using JBODs, SAS JBODs and SAS cables are required.

Calculation parameters

Select data group redundancy level

Only "2-way Mirror" and "4-way Mirror" redundancy types are allowed for Non-shared storage HA clusters.

Select calculation mode

Please select one of two calculation methods.

Calculate by required storage capacity

Please fill out fields below.

Calculate by number of disks and data groups

Please fill out fields below.
Please fill out fields below.

Calculation results

Zpool storage characteristics

  • Gross unformatted storage capacity:

    -

  • Net unformatted storage capacity:

    -

  • Gross formatted storage capacity:

    -

  • Net formatted storage capacity:

    -

  • Usable data storage capacity:

    -

Zpool data groups

  • Number of data groups:

    -

  • Groups redundancy type:

    -

  • Disks in data group:

    -

  • Total number of disks:

    -

  • Single disk capacity:

    -

  • Disk groups layout:

Please specify calculation parameters first...

Data disk #1
Dots
Parity disk #3

Data disk Data disk

Parity disk Parity disk

Additional pool information

Zpool Performance Rating

The performance Rating demonstrates the amount of effective performance when compared to single disk performance.
Example: A performance index of 4.6 is equal to the performance of 4.6 single disks without redundancy or striping.

Important: Zpool Performance Rating does not equal overall system performance as it is accelerated significantly by cache and by random I/O into sequential I/O conversion.
However, it may be important with sustained I/O. With sustained I/O, the pool that consists of 2 data groups is about twice faster than the pool with a single data group. Also, disk replacement or scrub speed scales with Zpool Performance Rating.

  • Read Performance Rating:

    x single disk

  • Write Performance Rating:

    x single disk

Zpool capacity efficiency

The ratio of usable capacity to total physical capacity in pool. 80% means that 8 out of 10 TB is usable

  • Zpool capacity efficiency

    %


0%

100%

NR%

Write log disks

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.

Number of disks

Capacity of each disk

GB

Read cache disks

Used to provide an additional layer of caching between main memory and disk. For read-heavy workload, using cache devices allows much of the work to be served from low latency media.

Number of disks

Capacity of each disk

GB

Licenses recommendations

Only data storage groups are calculated! The calculations 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 or disks mirroring is applied.

Net unformatted storage capacity

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

Gross formatted storage capacity

The formatted capacity of all disks, before RAID or disks mirroring is applied. It is used to calculate the licensed capacity for RAID Z-1, Z-2 and Z-3.

Net formatted storage capacity

The formatted capacity of all disks, after RAID or disks mirroring is applied. This capacity 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.

1 Formatted storage capacity is shown in TiB (240 byte units), the same way operating systems calculate it. Hard drive manufacturers use TB (1012 byte units) based on the required license capacity. Because of that a normal capacity, e.g. formatting a 1TB hard disk will result in 931 GB space on drive, despite the 1000 GB claim on the label. More info in the article on our blog.

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 »

Open-E JovianDSS Storage License Calculator

x

Select system type / architecture

Please select system type.

Single node

Simple architecture with one server.

Single node

Drives can be SAS or SATA. When using JBODs, SAS JBODs and SAS cables are required.

Shared storage HA Cluster

Single storage shared between the nodes.

Shared HA Cluster

Common storage (internal, JBODs, JBOFs, etc.), both nodes are directly connected to all storage devices in the cluster at the same time. When using JBODs, SAS JBODs and SAS cables are required.

Non-shared storage HA Cluster

Each node has it's own storage.

Non-shared HA Cluster

Each node has direct access only to its own storage devices. Nodes communicate with each other to access their counterparts' storage. When using JBODs, SAS JBODs and SAS cables are required.

Select data group redundancy level

Please select Redundancy Level.

NO REDUNDANCY

1 disk per group

Data disk

There are no parity disks, the total capacity equals the capacity of all disks.

NO REDUNDANCY

This redundancy level is not allowed for selected system architecture.

A group consists only of a SINGLE disk. This configuration in scope of the Pool behaves as a regular RAID-0.

The "No redundancy" configuration DOES NOT accept any disk failures. This configuration should not be used for mission critical applications at all!

It is also recommended not to exceed 8 of SINGLE disks in the Pool because a single disk damage results in the destruction of the whole Pool. The chances of suffering disk failures increase with the number of disks in the Pool.

Important
The pool performance with SINGLE drive in each group is the highest possible and is increasing with the number of groups (disks) in the pool. For mission critical applications, it is recommended to use RAID-Z2 or RAID-Z3, or 3-way mirror instead of "No redundancy".

This configuration can be used with Hardware RAID volumes where redundancy is preserved on a hardware level.

Suitability for mission critical solutions:

2-WAY MIRROR

2 disks in a group

Data disk NODE A

Parity disk NODE B

Data disk Parity disk

1 disk is a parity disk. Total capacity equals the capacity of 1 disk.

2-WAY MIRROR

The chances of suffering multiple disk failures increase with number of MIRRORs in the Pool.

The 2-WAY MIRROR accepts single disk failure only per MIRROR group.
MIRRORs can be used for mission critical applications, but it is recommended not to exceed 12 MIRRORs in the Pool and to avoid HDDs bigger than 4TB (recommended up to 12*2=24 disks for mission critical applications and 24*2=48 disks for non-mission critical applications in the pool).

Note, the pool performance is increasing with number of MIRRORs in the pool. For mission critical applications and using disks bigger than 4TB or more than 12 groups, it is recommended to use 3-way MIRRORs or RAID-Z2 or RAID-Z3.

Suitability for mission critical solutions:

3-WAY MIRROR

3 disks in a group

Data disk Parity disk Parity disk

2 out 3 disks are parity disk. Total capacity equals the capacity of 1 disk.

3-WAY MIRROR

This redundancy level is not allowed for selected system architecture.

The chances of suffering multiple disk failures increase with number of MIRRORs in the Pool.

The 3-WAY MIRROR accepts up to two disks failures per 3-WAY MIRROR group.
3-WAY MIRRORs can be used for mission critical applications, but it is recommended not to exceed 16 MIRRORs in the Pool and to avoid HDDs bigger than 10TB (recommended up to 16*3=48 disks for mission critical applications in the pool and 24*3=72 disks for non-mission critical applications in the pool).

Note, the pool performance is increasing with number of MIRRORs in the pool. For mission critical applications and using disks bigger than 10TB, it is recommended to use RAID-Z3.

Suitability for mission critical solutions:

4-WAY MIRROR

4 disks in a group

Data disk Parity disk NODE A

Parity disk Parity disk NODE B

Data disk Parity disk Parity disk Parity disk

3 disks out of 4 are parity disks. Total capacity equals the capacity of 1 disk.

4-WAY MIRROR

The chances of suffering multiple disk failures increase with number of MIRRORs in the Pool.

The 4-WAY MIRROR accepts three disks failure per MIRROR group.
The 4-WAY MIRROR is recommended for METRO Cluster that can be used for mission-critical applications.

It is also recommended not to exceed 24 of 4-WAY MIRROR groups in the Pool because the single group damage results with the whole Pool destruction (recommended up to 24*4=96 disks for mission-critical applications in the pool). HDDs bigger than 16TB should be avoided.

Note, the pool performance is increasing with number of MIRRORs in the pool.

Suitability for mission critical solutions:

RAID-Z1

3-8 disks in a group

Data disk Dots Data disk Parity disk

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

RAID-Z1

This redundancy level is not allowed for selected system architecture.

The chances of suffering multiple disk failures increase with number of disks in the RAID-Z1 group.

The RAID-Z1 accepts single disk failure only per RAID-Z1 group.
The RAID-Z1 can be used for NON-mission critical applications and it is recommended to not exceed 8 disks per group and to avoid HDDs bigger than 4TB.

It is also recommended not to exceed 8 RAID-Z1 groups in the Pool because the single group damage results with the destruction of the whole Pool (recommended up to 8*8=64 disks for non-mission critical applications in the pool).

Note, the pool performance is doubled with 2 * RAID-Z1 with 4 disks each comparing to single RAID-Z1 with 8 disks. For mission critical applications, it is recommended to use RAID-Z2 or RAID-Z3 or 3-way mirrors instead of RAID-Z1.

Suitability for mission critical solutions:

RAID-Z2

4-24 disks in a group

Data disk Dots Data disk Parity disk Parity disk

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

RAID-Z2

This redundancy level is not allowed for selected system architecture.

The chances of suffering multiple disk failures increase with number of disks in the RAID-Z2 group.

The RAID-Z2 accepts up to two disks failure per RAID-Z2 group.
The RAID-Z2 can be used for mission critical applications.

It is recommended not to exceed 12 disks per group for mission critical and 24 disks for NON-mission critical applications. It is also recommended to not exceed 16 of RAID-Z2 groups in the Pool because the single group damage results with the destruction of the whole Pool (recommended up to 16*12=192 disks for mission critical applications and 16*24=384 disks for non-mission critical in the pool). HDDs bigger than 16TB should be avoided.

Note, the pool performance is doubled with 2 * RAID-Z2 with 6 disks each comparing to single RAID-Z2 with 12 disks. If 3 disks failure per RAID group is required, it is recommended to use RAID-Z3.

Suitability for mission critical solutions:

RAID-Z3

5-48 disks in a group

Data disk Dots Data disk Parity disk Parity disk Parity disk

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

RAID-Z3

This redundancy level is not allowed for selected system architecture.

The chances of suffering multiple disk failures increase with number of disks in the RAID-Z3 group.

The RAID-Z3 accepts up to three disks failure per RAID-Z3 group.
The RAID-Z3 can be used for mission critical applications.

It is recommended not to exceed 24 disks per group for mission critical and 48 disks for NON-mission critical applications. It is also recommended to not exceed 24 of RAID-Z3 groups in the Pool because the single group damage results with the whole Pool destruction (recommended up to 24*24=576 disks for mission critical applications and 24*48=1152 disks for non-mission critical in the pool). HDDs bigger than 16TB should be avoided.

Note, the pool performance is doubled with 2 * RAID-Z3 with 12 disks each comparing to single RAID-Z3 with 24 disks.

Suitability for mission critical solutions:

Data disk Data disk Parity disk Parity disk

Learn more about data redundancy in ZFS

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 it's 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.

Select calculation mode

Please select one of two calculation methods.

Calculate by required 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.

Please fill out fields below.
TiB1
How much storage do you require or plan to use
TB
The RAW unformatted size of a single disk as provided by the disk vendor. Decimal values (comma separated) are allowed.

1Storage capacity is shown in TiB (240 byte units), the same way operating systems calculate it. Hard drive manufacturers use TB (1012 byte units) based on the required license capacity. Because of that a freshly formatted hard disk or RAID array volume is smaller than the nominal capacity, e.g. formatting a 1TB hard disk will result in 931 GB space on drive, despite the 1000GB claim on the label. More info in the article on out blog.

Calculate by number of disks and data groups

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.

Please fill out fields below.
Please fill out fields below.
TB
The RAW unformatted size of a single disk as provided by the disk vendor. Decimal values (comma separated) are allowed.
The number of disks that will be used in each data group. Each redundancy level has a minimum and recommended maximum number of disks.
The number of data groups that will be used in the pool. The data is striped over all groups by Open-E JovianDSS.

ZFS Pool design details

x

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.

Available Support Licenses

x

1 year up to 16TB Standard Support License (SKU: 1853)
1 year up to 16TB Premium Support License (SKU: 1855)
1 year up to 16TB 24/7 Support License (SKU: 1857)

1 year 20 to 128TB Standard Support License (SKU: 1877)
1 year 20 to 128TB Premium Support License (SKU: 1879)
1 year 20 to 128TB 24/7 Support License (SKU: 1881)

1 year 132 to 512TB Standard Support License (SKU: 1793)
1 year 132 to 512TB Premium Support License (SKU: 1794)
1 year 132 to 512TB 24/7 Support License (SKU: 1795)

1 year over 512TB Standard Support License (SKU: 1901)
1 year over 512TB Premium Support License (SKU: 1903)
1 year over 512TB 24/7 Support License (SKU: 1905)

3 years up to 16TB Standard Support License (SKU: 1859)
3 years up to 16TB Premium Support License (SKU: 1861)
3 years up to 16TB 24/7 Support License (SKU: 1863)

3 years 20 to 128TB Standard Support License (SKU: 1883)
3 years 20 to 128TB Premium Support License (SKU: 1885)
3 years 20 to 128TB 24/7 Support License (SKU: 1887)

3 years 132 to 512TB Standard Support License (SKU: 1796)
3 years 132 to 512TB Premium Support License (SKU: 1797)
3 years 132 to 512TB 24/7 Support License (SKU: 1798)

3 years over 512TB Standard Support License (SKU: 1907)
3 years over 512TB Premium Support License (SKU: 1909)
3 years over 512TB 24/7 Support License (SKU: 1911)