#1 Software for Data Storage, Backup & Business Continuity
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.
xSelect system type / architecture
Single node
Simple architecture with one server.
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.
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.
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.
The calculation is per one zpool and - when selecting a regular cluster architecture - for an active-passive cluster.
For active-active cluster configurations you may consider creating additional pool with the same parameters (number of disks, redundancy) Please contact our pre-sales engineers for more details.
Calculation parameters
Switch to advanced mode
-
Usable data storage capacity:
-
-
Total number of data disks:
-
-
Number of data groups:
-
-
Disks in data group:
-
Please specify calculation parameters first...
#1
#3
Data disk
Parity disk
Expected annual zpool reliability
The expected period of time for a year when zpool works in a reliable way, given the configuration and the possiblity of disk failure.
00.0%
Not recommended! Storage solutions with expected annual reliability below 99.0% should not be considered for any production deployment!
Zpool reliability parameters
-
Mean Time To Recovery (MTTR)2 in days:
14
-
Mean Time Between Failures (MTBF)3 in hours:
850 000
Detailed calculation results
Zpool storage characteristics
What each value mean?
-
Gross unformatted storage capacity:
12 TB
-
Net unformatted storage capacity:
32 TB
-
Gross formatted storage capacity:
34 TiB1
-
Net formatted storage capacity:
45 TiB1
-
Usable data storage capacity:
23 TiB1
For mirrored pools recommended license capacity is calculated based on Net formatted storage capacity
For RAID-Z recommended license capacity is calculated based on Gross formatted storage capacity
Zpool non-data groups
Non data groups do not affect the size of license storage capacity regardless of their amount and capacity.
Selected zpool non-data groups
-
Write log disks:
0
-
Read cache disks:
0
-
Spare disks:
0
-
Total number of non-data disks:
0
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:
50%
0%
100%
50%
Recommended licenses
- 2x Open-E JovianDSS Product Key
-
- 1x Open-E JovianDSS Storage Extension 256TB
-
- 1x JovianDSS Standard HA Cluster Feature Pack
-
- 2x Support license of your choice
-
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. This capacity is used to calculate the licensed capacity for RAID Z-1, Z-2 and Z-3 (also for no redundancy scenarios).
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 (also for no redundancy scenarios).
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 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 1000 GB claim on the label. More info in the article on our blog.
2 Mean Time To Recovery (MTTR) applies to the average time that takes to recover the pool after a disk failure (including RAID rebuild).
3 Mean Time Between Failures (MTBF) is the predicted elapsed time between disks failures during normal system operations.
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.
Open-E JovianDSS Storage License Calculator
Select system type / architecture
Single node
Simple architecture with one server.
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.
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.
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
NO REDUNDANCY
1 disk per group
There are no parity disks, the total capacity equals the capacity of all disks.
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
NODE A
NODE B
1 disk is a parity disk. Total capacity equals the capacity of 1 disk.
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
2 out 3 disks are parity disk. Total capacity equals the capacity of 1 disk.
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
NODE A
NODE B
3 disks out of 4 are parity disks. Total capacity equals the capacity of 1 disk.
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
1 disk in a data group may fail. Total capacity
equals the sum of all disks
minus 1.
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
2 disks in a data group may fail. Total capacity equals the sum of all disks minus 2.
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
3 disks in a data group may fail. Total capacity equals the sum of all disks minus 3.
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 Parity disk
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 expected disks & 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.
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 is available in the article on our blog.
Add non-data groups
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.
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.
Spare disks
Spare disks are drives that are kept on active standby for use when a disk drive fails. The function enables spare disks to be used for any data group. It should be disks with a capacity equal or more than disks in data groups.
Zpool reliability parameters
General information
The calculation is based on the zpool configuration and zpool reliability parameters.
Zpool configuration parameters used to make this calculation:
- Number of datagroups
- Amount of disks in data group
- Amount of parity disks
Zpool reliability parameters:
- Mean Time To Recovery (MTTR)
- Mean Time Between Failures (MTBF) or Annual Failure Rate (AFR)
You can use the default zpool reliability parameters or enter your own based on data provided by the disks vendor. More precise data make the result more accurate.
Zpool reliability parameters description
Mean Time To Recovery (MTTR)
MTTR applies to the average time that takes to recover the pool after a disk failure (including RAID rebuild).
Mean Time Between Failures (MTBF)
MTBF is the predicted elapsed time between disks failures during normal system operations.
Annual Failure Rate (AFR)
Annual Failure Rate is the parameter that represents the same information as MTBF but expressed as a percentage. It is the probability of a disk failing during a single year. Which value will be available about specific disk depends on a disk vendor.
Usable data storage capacity
Usable data storage capacity is a functional storage space for user data after redundancy has been applied and 10% of pool space has been reserved (To ensure the pool working correctly and efficiently 10% of its capacity must be reserved).
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 consist of 2 data groups is about twice faster than the pool with single data group. Also, disk replacement or scrub speed scales with Zpool Performance Rating.
Performance rating does not take into account write log and read cache disks
Zpool storage characteristics - what each value means
To understand the presented values please note that storage hardware is using the base 10 system, therefore disks capacity is shown in TB (1012 byte units). Software is using the base 2 system, therefore the storage capacity is shown in TiB (240 byte units). For more info refer to our blog article.
Gross unformatted storage capacity is the sum of capacity of all disks before RAID or disks mirroring is applied. Shown in TB.
Net unformatted storage capacity is the sum of capacity of all disks after RAID or disks mirroring is applied (excluding the capacity of parity disks). Shown in TB.
Gross formatted storage capacity is a result of the conversion of gross unformatted storage capacity to units used by the operating systems (TB -> TiB).
Gross formatted storage capacity is used to calculate the licensed capacity for RAID Z-1, Z-2 and Z-3 (also for no redundancy scenarios).
Net formatted storage capacity is a result of the conversion of net unformatted storage capacity to units used by the operating systems (TB -> TiB).
Net formatted storage capacity is used to calculate the licensed capacity for mirrored arrays (also for no redundancy scenarios).
Usable data storage capacity is a functional storage space for user data after redundancy has been applied and 10% of pool space has been reserved. To ensure the pool is working correctly and efficiently 10% of its capacity must be reserved. Usable data storage capacity is shown in TiB.
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.
Available Support Licenses
1 year Standard Support (Up to 16TB of storage) (SKU: 1853)
1 year Premium Support (Up to 16TB of storage) (SKU: 1855)
1 year 24/7 Support (Up to 16TB of storage) (SKU: 1857)
1 year Standard Support (From 20TB to 128TB of storage) (SKU: 1877)
1 year Premium Support (From 20TB to 128TB of storage) (SKU: 1879)
1 year 24/7 Support (From 20TB to 128TB of storage) (SKU: 1881)
1 year Standard Support (From 132TB to 512TB of storage) (SKU: 1793)
1 year Premium Support (From 132TB to 512TB of storage) (SKU: 1794)
1 year 24/7 Support (From 132TB to 512TB of storage) (SKU: 1795)
1 year Standard Support (516TB of storage and more) (SKU: 1901)
1 year Premium Support (516TB of storage and more) (SKU: 1903)
1 year 24/7 Support (516TB of storage and more) (SKU: 1905)
3 years Standard Support (Up to 16TB of storage) (SKU: 1859)
3 years Premium Support (Up to 16TB of storage) (SKU: 1861)
3 years 24/7 Support (Up to 16TB of storage) (SKU: 1863)
3 years Standard Support (From 20TB to 128TB of storage) (SKU: 1883)
3 years Premium Support (From 20TB to 128TB of storage) (SKU: 1885)
3 years 24/7 Support (From 20TB to 128TB of storage) (SKU: 1887)
3 years Standard Support (From 132TB to 512TB of storage) (SKU: 1796)
3 years Premium Support (From 132TB to 512TB of storage) (SKU: 1797)
3 years 24/7 Support (From 132TB to 512TB of storage) (SKU: 1798)
3 years Standard Support (516TB of storage and more) (SKU: 1907)
3 years Premium Support (516TB of storage and more) (SKU: 1909)
3 years 24/7 Support (516TB of storage and more) (SKU: 1911)