Open-E Wiki - User contributions [en]

Small blocks policy settings

2025-01-21T09:49:10Z

Ma-W:

<div>This feature is available only when the special devices group exists in the pool.</div><br/><div>Devices assigned to the special devices group are designated for storing specific data, including metadata, indirect blocks of user data, and deduplication tables. Additionally, devices in the special devices group can be configured to handle small file blocks that are not listed above by applying the small blocks policy.</div><div>The size of the small block refers to the size of a single block of data configured on the dataset. Maximum size of such blocks can be set for each dataset under the “Record size” option.</div><div>Deduplication tables can alternatively be placed in a separate group known as the deduplication group.</div><br/><div><span style="color:#ff0000">'''WARNING''': If the size of the small block is greater than or equal to the value of record size on the dataset, all the blocks will be offloaded to the special devices group.</span></div><br/><div>The small block size can be configured for the whole Pool or for each dataset separately. Options to choose range from 4 KiB to 16 MiB.</div><br/><div>Configuring a bigger size for the small block policy can be helpful in case the administrator expects the to have a substantial amount of small files that will require low access times separated from the bigger files. Using this option is recommended only if the administrator understands what kind of data will be stored in configured datasets and the maximum size of offloaded files is exactly known, to avoid accidental data offload and special devices congestion.</div><div></div><div></div>
[[Category:Help topics]]

Backup & Recovery destination server

2025-01-20T12:04:40Z

Ma-W:

<div>Remote servers that are added as snapshot targets are called Destination servers. To add one, click the “Add server” button.</div><br/><div>[[File:Add server option.png|none|800px|Add server option.png]]</div><br/><div>You will be asked for the following information:
*'''IP address/domain''': provide IP address or a hostname associated with your Destination server.<br/>'''<u>Note</u>: In case the snapshot target is an HA cluster, it is highly recommended to use Virtual IP configured on a Pool. It allows the connection to be stable even after exporting the pool to the other node'''.
*'''Port''': 40000 is set by default. This value should not be changed, unless explicitly asked by the Support Team.
*'''Password''': to establish the connection, it is required to provide the administrator password to the remote server.
*'''Description''': This field is optional. Provide a short description of your server to identify it in the future.
</div><br/><div>[[File:Add server form.png|none|450px|Add server form.png]]</div><br/><div>Destination servers configured here will be available during the Destination configuration step of the Replication task wizard.</div><div>If you wish to remove the Destination server click the “Remove” button. '''Remember to remove all Backup tasks related to this server beforehand!'''</div><br/><div>[[File:Remove server option.png|none|800px|Remove server option.png]]</div><div></div>
[[Category:Help topics]]

Backup & Recovery Esx server

2025-01-20T12:04:21Z

Ma-W:

<div>Snapshot feature can be integrated with VMware ESX/vSphere snapshots. To integrate a new VMware server with click on the “Add server” option.</div><br/>
[[File:V-center add server option.png|800px|V-center add server option.png]]
<div>You will be asked for the following information:
*'''IP address''': provide IP address or a hostname associated with your Destination server.
*'''Port''': 443 is set by default. This value should not be changed, unless explicitly asked by the Support Team.
*'''Username''': provide the username for the VMware user you wish to use during integration. It is recommended to use the root user for this purpose.
*'''Password''': to establish the connection, it is required to provide the password to the VMware user account provided in the previous step.
</div><br/>
[[File:Add VMware server form.png|450px|Add VMware server form.png]]
<div><br/>The integrated server will be visible in the table below. The user can browse through the configured datastores and Virtual Machines by going to the Options > Details.</div>
[[File:Details of WMware server.png|800px|Details of WMware server.png]]

[[File:VMware server details.png|450px|VMware server details.png]]
<div><br/>It is also possible to remove the server from integration by clicking the Remove option. <span style="color:#ff0000">'''Remember to remove all Backup tasks related to this server beforehand!'''</span></div>
[[File:Remove WMware server.png|800px|Remove WMware server.png]]

[[Category:Help topics]]

Redundancy in Disks Groups

2024-12-19T10:12:28Z

Ma-W:

__NOTOC__

<br/><br/>Disk group redundancy refers to the ability of a zpool to maintain data integrity and availability in the event of disk failures. This is achieved through mirrored or RAID-Z configurations, which store multiple copies of data across different disks. When a disk fails or data corruption is detected, ZFS can use the redundant copies to repair or reconstruct the lost data, ensuring the system continues to operate without data loss.

It is important not to mix the types of data groups (vdevs) inside your storage zpool, as it might lead to potential issues, so it is strongly recommended to consistently use only one type of vdev.

== <br/>Data Group redundancy level: 2-way mirror (2 disks per group) ==

*The chances of suffering multiple disk failures increase with the number of mirror vdevs in the zpool.
*The 2-way mirror accepts a single disk failure in a given vdev.
*The 2-way mirrors can be used for mission critical applications, but it is recommended not to exceed 12 vdevs in a zpool (recommended up to 12 x 2 = 24 disks for mission-critical applications and 24 x 2 = 48 disks for non-mission critical applications in a zpool).
*'''Note''': as a rule, the zpool performance increases with the number of vdevs in the pool. For mission-critical applications and using more than 12 groups, It is recommended to use 3-way mirrors or RAID-Z2 or RAID-Z3.
*For mission critical applications it is not recommended to use HDDs bigger than 4TB.

== Data Group redundancy level: 3-way mirror (3 disks per group) ==

*The chances of suffering multiple disk failures increase with number of mirror vdevs in the zpool.
*The 3-way mirror accepts up to two disks failures in a given vdev.
*3-way mirrors can be used for mission critical applications, but it is recommended not to exceed vdevs in a zpool (recommended up to 16 x 3 = 48 disks for mission critical applications and 24 x 3 = 72 disks for non-mission critical applications in a zpool).
*'''Note''': the zpool performance increases with the number of vdevs in a zpool. For mission-critical applications, it is recommended to use RAID-Z3.
*For mission critical applications it is not recommended to use HDDs bigger than 10TB.

== Data Group redundancy level: 4-way mirror (4 disks per group) ==

*The chances of suffering multiple disk failures increase with number of mirror vdevs in the zpool.
*The 4-way mirror accepts up to three disks failures in a given vdev.
*The 4-way mirror is recommended for a Non-Shared HA Cluster that can be used for mission-critical applications.
*It is also recommended not to exceed 24 of 4-way mirror vdevs in a zpool as a single group damage results in the destruction of the entire zpool (recommended up to 24 x 4 = 96 disks for mission-critical applications in a zpool).
*'''Note''': as a rule, the zpool performance increases with the number of vdev in the pool.
*HDDs bigger than 16TB should be avoided for mission critical applications.

== Data Group redundancy level: RAIDZ-1 (3-8 disks in a group) ==

*The chances of suffering multiple disk failures increase with the number of disks in a RAID-Z1 vdev.
*RAID-Z1 accepts one disk failure in a given vdev.
*The RAID-Z1 can be used for non-mission critical applications and it is not recommended to exceed 8 disks in a vdev. HDDs bigger than 4TB should be avoided.
*It is also not recommended to exceed 8 RAID-Z1 vdevs in a zpool as a single group damage results in the destruction of entire zpool (recommended up to 8 x 8 = 64 disks for non-mission critical applications in a zpool).
*RAID-Z1 configuration is not possible in a Non-Shared HA Cluster configuration.
*'''Note''': the zpool performance is doubled with 2 x RAID-Z1 with 4 disks each comparing to a single RAID-Z1 vdev with 8 disks.

== <br/>Data Group redundancy level: RAIDZ-2 (4-24 disks per group) ==

*The chances of suffering multiple disk failures increase with the number of disks in the RAID-Z2 group.
*The RAID-Z2 accepts up to two disks failures in a given vdev.
*The RAID-Z2 can be used for mission-critical applications.
*It is not recommended to exceed 12 disks in a vdev for mission-critical and 24 disks for non-mission critical applications.
*It is also not recommended to exceed 16 of RAID-Z2 groups in a zpool as a single group damage results in the destruction of the entire zpool (recommended up to 16 x 12 = 192 disks for mission-critical applications and 16 x 24 = 384 disks for non-mission critical in a zpool). HDDs bigger than 16 TB should be avoided.
*If 3 disks failure in a vdev is required, it is recommended to use RAID-Z3.
*RAID-Z2 configuration is not possible in a Non-Shared HA Cluster configuration.
*'''Note''': the pool performance is doubled with 2 x RAID-Z2 with 6 disks each comparing to a single RAID-Z2 with 12 disks.

== <br/>Data Group redundancy level: RAIDZ-3 (5-48 disks per group) ==

*The chances of suffering multiple disk failures increase with the number of disks in the RAID-Z3 group.
*The RAID-Z3 accepts up to three disks failure in a given vdev.
*The RAID-Z3 can be used for mission-critical applications.
*It is not recommended to exceed 24 disks in a vdev for mission-critical and 48 disks for non- mission critical applications.
*It is also not recommended to exceed 24 of RAID-Z3 groups in a zpool as a single group damage results in the destruction of the entire zpool (recommended up to 24x 24 =576 disks for mission critical applications and 24x 48 = 1152 disks for non-mission critical applications in a zpool). HDDs bigger than 16TB should be avoided.
*RAID-Z3 configuration is not possible in a Non-Shared HA Cluster configuration.
*'''Note''': the zpool performance is doubled with 2 x RAID-Z3 with 12 disks each comparing to single RAID-Z3 vdev with 24 disks.

== Write Log redundancy level ==

*In both single nodes and HA clusters, it should be configured as a 2-way mirror.
*When choosing a disk model for the Write Log, make sure to take the endurance parameter into consideration. Selecting a disk classified by the manufacturer as write intensive is strongly recommended.
*When selecting a disk size for the write log, consider the potential amount of data that’ll be able to reach the server in three consecutive ZFS transactions, e.g. based on the network card bandwidth for the data transfer. If the transaction length is set to 5 seconds (default), the write log device should be able to accommodate the amount of data that can be transferred within three transaction groups, i.e. 15 seconds of writing. Using a larger disk does not make sense economically, while a smaller one can be a performance bottleneck during synchronous writes. '''Practically speaking, 100GB for a write log should be more than enough.'''

== Read Cache redundancy level ==

Read Cache disks can only be configured as single disks, but it is possible to configure any number of them. In an HA cluster, Read Cache can only be configured as local disks on both nodes on the cluster.

== Special devices and deduplication group redundancy level ==

In both single nodes and HA clusters, it should be configured as a 2-way mirror.

[[Category:ZFS and data storage articles]]

Main Page

2024-12-19T09:24:47Z

Ma-W:

===== ''Release Notes:'' =====

{{
#tag:DynamicPageList|
category = Release Notes
ordermethod = categorysortkey
order = descending
count = 1
mode = none
}}
<div>[[Release Notes|All release notes »]]</div>

----

'''''Help topics:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = Help topics
count=50
ordermethod = categorysortkey
order = ascending
}}

|
{{
#tag:DynamicPageList|
category = Help topics
offset = 50
count= 50
ordermethod = categorysortkey
order = ascending
}}

| style="vertical-align: top" |
{{
#tag:DynamicPageList|
category = Help topics
offset = 100
count=50
ordermethod = categorysortkey
order = ascending
}}

|}

----

'''''ZFS and data storage articles:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = ZFS and data storage articles
count=60
ordermethod = categorysortkey
order = ascending
}}

|}

----

'''''Video tutorials:'''''

'''''<span style="color:#696969"><span><span>Open-E JovianDSS Video Tutorials</span></span></span>''''' {{
#tag:DynamicPageList|
category = Open-E JovianDSS Video Tutorials
ordermethod = sortkey
order = ascending }}<br/>'''''<span style="color:#696969"><span><span>Setting up Open-E JovianDSS Standard HA Cluster</span></span></span>''''' {{
#tag:DynamicPageList|
category = Setting up Open-E JovianDSS Standard HA Cluster
ordermethod = sortkey
order = ascending }}<br/>'''''<span style="color:#696969"><span><span>Setting up Open-E JovianDSS Advanced Metro HA Cluster</span></span></span>''''' {{
#tag:DynamicPageList|
category = Setting up Open-E JovianDSS Advanced Metro HA Cluster
ordermethod = sortkey
order = ascending
}}

Open-E JovianDSS ver.1.0 up30r2 Release Notes

2024-04-25T15:01:59Z

Ma-W:

'''Release date: 2024-03-11'''

'''Build: 55016'''

   <span style="color:#cc0033">'''Important!''' </span>To upgrade the product, you need to have an active Technical Support plan. You will be prompted to re-activate your product after installing the upgrade to verify your Technical Support status.

If you don't have an active Technical Support plan, please contact Open-E sales team or your reseller for further assistance.

{| class="cke_show_border cke_show_border cke_show_border"
|-
| __TOC__

|}

== New ==

=== Support for LED disk location for NVMe drives on Intel platforms ===

== Updated ==

=== ZFS (v2.1.14) ===

=== Ledctl (v0.97) ===

=== Chelsio T4/T5 10 Gigabit Ethernet controller driver (cxgb4, v3.19.0.1) ===

== Fixed ==

=== The Hot-Plug mechanism for NVMe drives does not work properly on several environments ===

=== The system restart or shutdown procedure does not function correctly in environments utilizing the HP Smart Array controller (hpsa driver) ===

== Important notes for JovianDSS HA configuration ==

=== It is necessary to use sync always option for zvols and datasets in cluster  ===

=== It is strongly recommended not to use more than eight ping nodes ===

=== It is strongly recommended to configure each IP address in separate subnetwork ===

=== It is necessary to run Scrub scanner after failover action triggered by power failure (dirty system close) ===

=== It is strongly recommended to use UPS unit for each cluster node ===

=== It is necessary to use static discovery in all iSCSI initiators ===

=== It is strongly not recommended to change any settings when both nodes do not have the same JovianDSS version, for example during software updating ===

=== It is necessary to use different Server names for cluster nodes ===

=== HA cluster does not work properly with Infiniband controllers ===

=== HA cluster does not work stable with ALB bonding mode ===

=== FC Target HA cluster does not support Persistant Reservation Synchronization and it cannot be used as a storage for Microsoft Hyper-V cluster. This problem will be solved in future releases. ===

=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===
<p style="text-align: justify"><span class="toctext">    You can find details below:</span></p><p style="text-align: justify"><span class="toctext">    [https://kb.open-e.com/index.php?View=entry&EntryID=3101 https://kb.open-e.com/index.php?View=entry&EntryID=3101]</span></p><p style="text-align: justify"><span class="toctext">    *Please consult Broadcom vendor for specific firmware that is suitable for your hardware setup.</span></p>
== Performance tuning ==

=== iSCSI Target with VMware ESX performance tuning ===

     In case of low iSCSI Target performance with VMware ESX, a few parameters need to be changed in VMware ESX iSCSI Initiator. Go to Storage Adapters -> iSCSI Software Adapter -> Advanced Options and the change the following settings:
<pre>
MaxOutstandingR2T change the default 1 to 8

FirstBurstLength change the default 262144 to 65536

MaxBurstLength change the default 262144 to 1048576

MaxRecvDataSegLen change the default 131072 to 1048576
</pre>
=== Write cache sync requests performance tuning ===

     Write cache sync requests (sync) set to “always” for zvol is the safest option and is set by default. However, it can cause write performance decreases since all operations are written and flushed directly to the persistent storage. In case of using sync=always, it is strongly recommended using mirrored write log devices (very fast random writes devices).<br/>     Sync=standard or sync=disabled zvol options provide huge performance improvement but the most recent (up to 5 seconds) cached data can be lost in case of a sudden power failure. Use this option only in environments equipped with UPS.<br/>     For NFS shares the Synchronous data record is enabled by default. This option causes performance to be worse, but data can be safely written. In order to improve the NFS performance you can use Asynchronous data record but in such case, it is strongly recommended to use UPS.

== Known issues ==

=== Browser recommendations ===

     It is strongly recommended to use Mozilla Firefox browser to navigate the system’s GUI. When using other browsers some slight problems with displaying content may occur.

=== Web browser’s cache ===

     After updating from previous versions, some problems with WebGUI content and navigation may occur. To resolve this problems, please clear Web browser cache.

=== System as a guest in virtual environments ===

     Hyper-V:<br/>     In case of installing the system as a Hyper-V guest please use the following settings:<br/>       - Number of virtual processors: 4<br/>       - Memory: Minimum 8GB<br/>       - Boot Disk: 20GB IDE Disk<br/>       - Add at least 6 virtual disk

The utilization of physical hard drives in virtual machines hosted by Hyper-V is not supported and may cause problems. The problem does not occur when utilizing virtual hard drives in virtual machines within a Hyper-V environment.

     VMware ESXi:<br/>     In case of installing the system as a VMware ESXi guest please use the following settings:<br/>       - Guest OS: Other 2.6.x Linux ( 64bit )<br/>       - Number of Cores: 4<br/>       - Memory: Minimum 8GB<br/>       - Network Adapter: VMXNET 3<br/>       - SCSI Controller Type: Paravirtual or LSI Logic SAS<br/>       - Boot Disk : 20GB Thick Provision Eager Zeroed<br/>       - Add at least 6 virtual disk<br/>       - Edit Settings->Options->Advanced-General->Configuration-> Add row: disk.EnableUUID : TRUE

=== Reclaim deleted blocks on thin-provisioned LUNs in various systems ===

     In case of deleting large amounts of data, reclaimed deleted blocks on thin-provisioned LUNs in Windows 2012 can significantly slow down system performance. If you predict frequent deletions of large amounts of data, we recommend turning off the automatic reclaim function in Windows 2012. This can be done by disabling the "file-delete notification" feature in the system registry. To do so, follow the steps below:<br/>       - start Registry Editor.<br/>       - locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem       <br/>       - double-click DisableDeleteNotification.<br/>       - in the Value data box, enter a value of 1, and then click OK.<br/> <br/>     In order to reclaim the free space in Windows 2012 please change the    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\DisableDeleteNotification key value back to 0 and use "Optimize" tool located in Disc Management->[disk]->Properties->Tools. As the operation can generate a very high load in the system, it is recommended to perform it after-hours.  <br/>In case of VMware ESXi, the automatic reclaim feature is disabled by default. To reclaim the space of deleted blocks on thin-provisioned LUNs, please use vmkfstools. For details, please refer to the VMware Knowledge Base:

For VMware ESXi 5.0: [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849]<br/>For VMware ESXi 5.5 and newer: [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513 https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513]<br/>For VMware ESXi 6.7 and newer: search in Internet for “Space Reclamation Requests from VMFS Datastores” and read vendor documentation.

In case of using Windows 2008 there is no possibility to reclaim the space released by deleted data of thin-provisioned LUNs.

=== Deduplication issues and recommendations ===

     Please be aware that deleting the zvol with deduplication enabled can generate a very high load in the system and lead to unstable behavior. It is strongly recommended to perform such operation only after-hours. To avoid this issue, please use (if possible) single zvol on zpools dedicated for deduplication and delete the zpool which includes the single zvol.<br/>   <br/>     To determine the amount of System RAM required for deduplication, use this formula:<br/> <br/>                                                                                                                    (Size of Zvol / Volume block size) * 320B / 0.75 / 0.25<br/> <br/>Where:<br/>320B - is the size of entry in DDT table<br/>0.75 - Percentage of RAM reservation for ARC (75%)<br/>0.25 - Percentage of DDT reservation in ARC (25%)<br/> <br/>     Example for 1TB data and 64KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 65536B) * 320B / 0.75 / 0.25 = 28633115306.67B<br/>                                                                                                                       28633115306.67B / 1024 / 1024 / 1024 = 26.67GB<br/> <br/>so for every extra 1TB of storage, system needs extra 26.67GB RAM.<br/><br/>     Example for 1TB data and 128KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 131072B) * 320B / 0.75 / 0.25 = 14316557653.33B<br/>                                                                                                                        14316557653.33B / 1024 / 1024 / 1024 = 13.33GB<br/> <br/>so for every extra 1TB of storage, system needs extra 13.33GB RAM.
<div><br/></div><div>     Example for 1TB data and 1MB Volume block size:</div><div><br/></div><div>                                                                                                      (1099511627776B / 1048576B) * 320B / 0.75 / 0.25 = 1789569706,66B</div><div>                                                                                                                        1789569706,66B / 1024 / 1024 / 1024 = 1.66GB</div><div> </div><div>     so for every extra 1TB of storage, system needs extra 1.66GB RAM.</div><div><br/></div>
<br/>'''IMPORTANT: '''The above calculations only apply to the worst case scenario, when data is completely unique and will not be deduplicated. For the deduplicable data, the need for RAM drastically decreases. If SSD based Read Cache is present, part of deduplication table will be moved to the SSD and deduplication will work with good performance using less RAM.

<br/>'''IMPORTANT: '''With SAN (iSCSI) it is CRITICAL to match User-File-System format block size with the zvol volume-block-size. A simple example is a Windows file system NTFS with default format block size 4k and zvol default volume-block-size is 128k. With defaults like this deduplication will mostly NOT match because files can be aligned in 32 (128/4) different positions on the pool. If the NTFS format is increased to 64k and the zvol default volume-block-size is 128k, deduplication match can fail only one time because a file can be aligned to 2 (128/64) different positions on the pool. Every next write will match already as both alignment options already exist on the pool. In order to achieve all files matching and efficient memory usage NTFS must use 64k format block size and the zvol volume-block-size must equal 64k. Another option is that the NTFS=32k and zvol=32k, but in this case the deduplication table will be twice as large. That is why the NTFS=64k and zvol=64k is the most efficient setting for deduplication.

'''IMPORTANT: '''With NAS (NFS, SMB/CIFs) deduplication matching works always due to the data blocks being aligned by ZFS natively.

'''IMPORTANT: '''De-duplication is working on the pool level in the pool-range. This is why zvol-Physical size cannot show de-duplication benefit. In order to prove that deduplication saved space run the scrub and notice the current physical data space on the pool reported by the scrub. Next copy of new data and run the scrub again. Now scrub will show new physical data space. Comparing the data size from storage client side with the data space growth from the scrub will give the deduplication advantage. The exact pool of the deduplication ratio can be found in LOGs in zfs.log.

=== Zvols configuration issues and recommendations ===

     It is strongly recommended to set the client file system block size same as the zvol volume block size. For example, when using 64k zvol volume block size, the Windows Allocation unit size of NTFS should be set to 64k.

=== Target number limit ===

    In case of more than 60 targets, GUI will not be displayed correctly. This issue will be fixed in the next releases.

=== Targets with the same name are not assigned correctly ===

    Having two or more targets with the same name but belonging to various Zpools, will cause that all targets with the same name will be assigned to one Zpool during the import process.

=== Installation on disks containing LVM metadata ===

     There is no possibility to install the system on disks containing LVM metadata. You will need to clear those disks before installation. To do so, use the “Remove ZFS data structures and disks partitions” function located in the Extended tools. To access this function, boot the system from a temporary media like a USB drive or DVD.

=== Import Zpool with broken write log ===

     There is no option to import Zpool with a broken write log disk using the system’s functions. This is why it is STRONGLY recommended to use mirrored disks for write logs. In case it is necessary to import Zpool with a broken write log, please contact technical support.

=== Replacing disks in data groups for larger ones can cause your storage license capacity to be exceeded ===

     In case of replacing damaged disks for larger ones, the size of the entire Zpool will increased. Make sure that the new size will not exceed your purchased storage license.

=== Periodically after some operations, the GUI needs to be manually refreshed ===

     After performing some operations, e.g. resilvering, the GUI will show outdated information. In this case refresh the web page manually by pressing F5 on your keyboard. This issue will be fixed in next releases.

=== Replacing disks in data groups for smaller ones can cause an error and make the disk disappear from the list of available disks ===

     Operation of replacing a disk in a data group for a smaller one will cause an error "zpool unknown error, exit code 255", and the disk will become unavailable. In order to reuse this disk, please use function "Remove ZFS data structures and disks partitions" located in the Extended tools on the Console screen.

=== It is strongly recommended to use 64KB or higher Volume block size ===

     Smaller than 64KB block sizes used with deduplication or read cache will cause very high memory consumption.

=== RAM recommendations for Read Cache ===

     To determine how much System RAM is required for Read Cache, use the following formula:

<br/> <br/>                                                                      RAM needed = (Size of Read Cache - reserved size and labels) * bytes reserved by l2hdr structure / Volume block size<br/> 

     For 8KB Volume block size and 1TB Read Cache:<br/><br/>                                                                           RAM needed = (1099511627776B - 4718592B) * 432B / 8192B = 57981809664B<br/>                                                                                                        57981809664B / 1024 / 1024 / 1024 = 54GB<br/> <br/>Where:<br/>1099511627776B - 1TB Read Cache<br/>4718592B - reserved size and labels<br/>432B - bytes reserved by l2hdr structure<br/>8192B - Volume block size<br/> <br/>                                                                                                  For 64KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 65536B = 7247726208B<br/>                                                                                                       7247726208B / 1024 / 1024 /1024 = 6.75GB<br/><br/><br/>                                                                                                  For 128KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 131072B = 3623863104B<br/>                                                                                                       3623863104B / 1024 / 1024 /1024 = 3.37GB

=== Multiple GUI disk operations may result in an inaccurate available disks list ===

     Multiple operations of adding and detaching disks from groups can cause that the next operation of detaching will fail, but the disk will be shown on a list of available disks. When trying to add this disk to one group it will fail with the following error "[zfslib-wrap-zpool-ZpoolCmdError-1] invalid vdev specification". In this case, detach this disk once again.

=== After removing disks from groups they may not be displayed on a list of available disks ===

     Sometimes after removing disks from groups, Spare/Read Cache/Write Log disks are displayed on a list of unassigned disks, but they are not on a list of available disks. In this case, click the rescan button located in the adding group form.

=== Reusing disks from an exported and deleted Zpool ===

     After deleting an exported Zpool, not all disks which were a part of a Zpool become immediately available. Before you can reuse disks, which were previously used as a Spare or a Read Cache, you must first clean them. Use “Remove ZFS data structures and disks partitions” function located in the “Extended tools”.

=== Negotiated speed of network interfaces may not display correctly ===

     For some network interfaces, the negotiated speed field may display an incorrect value in GUI and Console. This issue will be fixed in next releases.

=== Limited possibility to display a large number of elements by the GUI ===

     After creating multiple snapshots, clones or zvols some forms in GUI work very slow. If you need to create many snapshots, clones or zvols, it is strongly recommended to use CLI in order to perform operations on them.

=== Open-E VSS Hardware Provider system recommendations ===

     It is strongly recommended to use Windows Server 2012. On the other Windows systems, Open-E VSS Hardware Provider Configuration works unstable.

=== Exceeded quota for dataset does not allow to remove files ===

     Files located on datasets with exceeded quota cannot be removed. In this case, please resize quota and then remove unnecessary files.

=== Slow WebGUI with multiple datagroups ===

     Zpool with more than 20 datagroups causes that some forms on WebGUI work very slow. If you need to create many datagroups, it is strongly recommended to use CLI API.

=== Slow WebGUI with multiple datasets ===

     More than 25 datasets cause that WebGUI works slow.

=== ZFS Upgrade ===

     For Open-E JovianDSS users, it is recommended to upgrade Zpools to the latest ZFS file system. Although the file system upgrade is absolutely safe for your data, and takes only few minutes, please be aware that this operation cannot be undone. In order to upgrade a single Zpool, please use "WebGUI -> Zpool options -> Upgrade file system" from Zpool's option menu.

=== Intel® Ethernet Controller XL710 Family ===

     In case of using Open-E JovianDSS with Intel® Ethernet Controller XL710 Family, it is necessary to update firmware’s network controller to the version: f4.33.31377 a1.2 n4.42 e1932.

=== Motherboards with x2APIC technology ===

     In case of using a motherboard with x2APIC technology enabled, it is necessary to disable x2APIC in BIOS. Otherwise, problems with CPU cores will occur.

=== NFS FSIDs and Zpool name ===

     One of the factors that have been taken into account when NFS FSIDs are generated is Zpool name. It indicates that when Zpool name is changed, e.g. during export and import with different names, FSIDs for NFS Shares located on this Zpool will also be changed.

=== High Availability shared storage cluster does not work with Infiniband controllers ===

     Due to technical reasons the High Availability shared storage cluster does not work properly when using the Infiniband controllers for VIP interface configuration. This limitation will be removed in the future releases.

=== Disks with LVM data cannot be used with the created Zpool ===

     Attempt to create Zpool with drives that contain LVM data will fail with the following error:

''"cannot open 'lvm-pv-uuid-R25lTS-kcDc-eiAN-eAlf-ppgi-rAqu-Oxy1Si': no such device in /dev must be a full path or shorthand device name"''

In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.

=== Unexpected long failover time, especially with HA-Cluster with two or more pools ===

     Current failover mechanism procedure is moving pools in sequence. Since up27 release, up to 3 pools are supported in HA-cluster. If all pools are active on single node and failover needs to move all 3 pools, the failover may take longer than 60 seconds which is a default iSCSI timeout in Hyper-V Clusters. In some environments, under heavy load a problem with too long time of cluster resources switching may occur as well. If the switching time exceeds the iSCSI initiator timeout, it is strongly recommended to increase the timeout up to 600 seconds.

     '''In case of using Windows, to increase iSCSI initiator timeout, please perform following steps:'''

1. Run regedit tool and find: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\...\Parameters\MaxRequestHoldTime registry key''

2. Change value of the key from default 60 sec to 600 sec (decimal)

     '''In case of using VMware, to increase iSCSI initiator timeout, please perform following steps:'''

1. Select the host in the vSphere Web Client navigator

2. Go to Settings in the Manage tab

3. Under System, select Advanced System Settings

4. Choose the ''Misc.APDTimeout'' attribute and click the Edit icon

5. Change value from default 140 to 600 sec.

     '''In case of using XenServer, to increase iSCSI initiator timeout, please perform following steps:'''

A. For existing Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Detach and reattach SRs. This will update the new iSCSI timeout settings for the existing SRs.

B. For new Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Create the new SR. New and existing SRs will be updated with the new iSCSI timeout settings.

=== Activation may be lost after update ===

     In some environments, after update to up11 system may require re-activation. This issue will be removed in the future releases.

=== Bonding ALB, Round-Robin and Round-Robin with RDMA do not work in Hyper-V and VMware environments ===

     In case of using Open-E JovianDSS as Hyper-V or VMware guest, bonding ALB, Round-Robin and Round-Robin with RDMA is not supported. Please use another type of bonding.

=== Continuous writing in VMware guest can cause that deleting VMware snapshot can take long time ===

     Using ODPS on zvol/dataset with VMware guest where many I/O operations are performed can cause that the process of deleting VMware snapshot can take long time. Please take this into consideration while you set up the scheduler for Off-site Data Protection Service task.

=== Enabling quota on dataset can cause file transfer interrupt ===

     Enabling quota functionality on a dataset can cause file transfer interrupt. Before using it in production environment, please enable quota on dataset, or make sure that no file transfers are active.

=== Nodes connected to the same AD server must have unique Server names ===

     If JovianDSS nodes are connected to the same AD server, they cannot have the same Server names.

=== Share can not be named the same as Zpool ===

     In case of share with the same name as Pool connections problem will occur. Please use different names.

=== No persistent rules for network cards in virtual environment ===

     Changing settings of virtual network cards (delete, changing MAC, etc.) can cause unstable system behaviour. Please do not change settings on production system. This issue will be fixed in next releases.

=== Downgrade to up17 or earlier is not possible ===

     Starting from up18 bootable medium has always SW RAID structure. Attempt to come back to earlier version is impossible. If you need come back to earlier version, you must reinstall version again.

=== System cannot be installed on cciss based controllers ===

     This issue will be fixed in next releases.

=== Interrupt the process of adding second disk to SW RAID (bootable medium) can cause run system from disk with uncompleted data ===

     Performing operation like: reboot, shutdown, power off, etc. during mirroring data on new added disk can cause that system will be booted from new disk which has incomplete data. In this case, SW RAID function shows empty status and wrong number of RAID members. To resolve this issue, please plug off disk which has incomplete data, boot system, plug in disk and add it once again to SW RAID.

=== SAS-MPIO cannot be used with Cluster over Ethernet ===

     It is strongly not recommended to use Cluster over Ethernet with SAS-MPIO functionality. Such a configuration can lead to a very unstable cluster behavior.

=== On- & Off-site Data Protection backward compatibility problem ===

     In case of using On- & Off-site Data Protection functionality in up21 or earlier, it is strongly recommended to remove all backup tasks created by CLI API and re-create it using GUI.

=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===

     In FC Target HA environment, power cycle of both nodes simultaneously may lead to a situation when VMware is not able to restore proper state of the storage devices. In vSphere GUI LUNs are displayed as Error, Unknown or Normal,Degraded. Moving affected pools to another node and back to its native node should bring LUNs back to normal. A number two option is to restart the Failover in Jovian’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.

=== Problem with maintenance in case of disk failure ===

     In case of disk failure, please remove the damaged disks from the system, before starting administrative work to replace the disk. The order of actions is important.

=== Separated mode after update from JovianDSS up24 to JovianDSS up25 ===

     In HA cluster environment after updating of one node from JovianDSS up24 to JovianDSS up25 the other node can fall into separated mode and the mirror path might indicate disconnected status. In such a case go to Failover Settings and in the Failover status section select Stop Failover on both nodes. Once this operation is finished select Start Failover.

=== Different Write Cache default setting for zvols in early beta versions of Jovian DSS up25 ===

     In the early beta versions of JovianDSS up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of Jovian up25 the Log bias is set to “Write log device (Latency)”.<br/>Please note, that “In Pool (Throughput)” setting may cause a drop in performance in environments with a lot of random access workloads which is a common factor for a majority of production environments.

=== Target alias name is required while configuring HA FC Target in case of adding two or more ports to one FC group ===

     If we want to have more then one port in each FC group (in HA FC configuration) it is necessary to type in Target alias name for every port. Otherwise an error message “Target alias is already used” can show up while setting up remote port mapping for FC targets in (pool name) -> Fibre Channel -> Targets and initiators assigned to this zpool. This issue will be resolved in the future release.

=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===

     In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of Jovian up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open Jovian TUI and use CTRL+ALT+W key combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select qla2xxx_scst QLogic Fibre Channel HBA Driver and make sure the value of this parameter is set to “exclusive”.<br/><br/>Please note that in order to change this parameter Failover must be stopped first.

=== Very low performance of FIO/WT in case of mixed FIO/WT and FIO/WB zvol configurations over Fiber Channel ===

     In case of the mixed FIO/WT and FIO/WB zvol configurations over FC one can observe significantly decreased performance on FIO/WT.

=== More than one zvol with FIO/WB mode can cause instability of the Fiber Channel connection ===

     If there's more than one FIO/WB zvol or a FIO/WB zvol is coexisting with other types of zvols it can cause an instability of the FC connection with client machines. As a result client machines may unexpectedly lose FC connected resources.

=== In certain situations system page cache is not able to flush File I/O errors by itself and cache flushing has to be performed manually ===

     Under certain conditions (like overfilling zvol and then expanding its size) some File I/O errors may be held by the system page cache and it requires manual flushing (in GUI use Storage -> Rescan).

=== Updating nodes of the Jovian cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===

     There is a significant difference in FC configurations in up24 and earlier versions. Those versions allowed the FC ports to be configured in initiator mode only, while later versions allow both target and initiator mode with target as default, so in case of using storage connected via FC initiator, FC port(s) must be manually corrected in GUI of the updated node.

=== Updating Metro Cluster node with NVMe disks as read cache from JovianDSS up26 or earlier can cause the system to lose access to the NVMe disks ===

     The process of updating of Metro Cluster node from JovianDSS up26 or earlier is changing NVME disk IDs. In consequence moving pool back to updated node is possible but the read cache is gone (ID mismatch). In order to bring read cache back to the pool we recommend to use console tools in the following way: press Ctrl+Alt+x -> “Remove ZFS data structures and disks partitions”, locate and select the missing NVMe disk and press OK to remove all ZFS metadata on the disk. After this operation click Rescan button in GUI -> Storage. The missing NVMe disk should now appear in Unassigned disks at the bottom of the page which allows to select that disk in pool’s Disk group’s tab. Open Disk group tab of the pool, press the Add group button and select Add read cache. The missing disk should now be available to select it as a read cache.

=== Synchronization of a large LDAP database can last for a long time (e.g. 10h for 380K users) and can be associated with high system load ===

     This problem will be solved in future releases.

=== Long time of a failover procedure in case of Xen client with iSCSI MPIO configuration ===

     In a scenario where Xen client is an iSCSI initiator in MPIO configuration, the power-off of one node starts the failover procedure that takes a very long time. Pool is finally moved successfully but there are many errors showing up in dmesg in meantime. In case of such an environment we recommend to add the following entry in the device section of the configuration file: /etc/multipath.conf:

'''no_path_retry queue'''

<br/>The structure of the device section should look as follows:
<pre>device {
vendor "SCST_FIO|SCST_BIO"
product "*"
path_selector "round-robin 0"
path_grouping_policy multibus
rr_min_rio 100
no_path_retry queue
}
</pre>
=== In case of large number of disks, zpool move can take a long time ===

     In certain environments in case of large number of disks (about 100 and more) the zpool move operation can take a long time.

=== Rolled back data are not properly refreshed both in Windows and Vmware systems ===

     Before using rollback operation on zvol please detach iSCSI or FC target, perform rollback operation and reattach target.

=== User gets deleted from share access list after changing its username on AD server ===

     If the AD user is assigned to a share and later the username is changed we should let JDSS know about it. Using the "Synchronize and update shares configurations" operation on JDSS leads to a situation where the changed user gets deleted from the share’s access list. The new username needs to be added to the share’s access list manually.

=== QLogic 32Gbit FC HBA is no longer supported ===

     Starting from JovianDSS up29 we no longer support QLogic 32Gbit FC adapters.

=== Certain 16Gbit FC HBAs are no longer supported ===

     Starting from JovianDSS up29 we no longer support certain 16Gbit FC adapters. If you are using a 16Gbit FC adapter based on the Qlogic chipset using the qla2xxx_scts driver, please refer to our online hardware compatibility list (HCL) to verify if that particular adapter is supported.

Our HCL is available at this link: [https://www.open-e.com/support/hardware-compatibility-list/open-e-jovian-dss/ https://www.open-e.com/support/hardware-compatibility-list/open-e-jovian-dss/]

=== E-mail password cannot contain special non-ASCII characters ===

     The following special characters # : + cannot be used in a password used in an e-mail notification feature. They can break the authentication process.

=== LSA e-mail notifications does not work with SMTP servers requiring SSL/TLS authentication ===

     E-mail alert configuration in LSI Storage Authority Software does not work with SMTP servers which require SSL/TLS authentication

=== Moving IP address of the NFS share’s IP read only access list to read/write access list cannot be performed in one step ===

     If an IP address is already present on the NFS access list and you would like to move it to another access list, it has to be performed in two steps. First delete the IP address from the current list and apply the changes. Next edit the NFS share again and add the IP address to the other access list.

=== If the used space on zpool reaches more than 80%, the system may generate high load and become unstable ===

     If the used space on the zpool reaches more then 80%, the system is trying to utilize the available space to the maximum. As a result, the system load may increase, especially waiting I/O and cause its unstable work. Expanding the pool size space is recommended.

=== In certain situations WebGUI is not showing the current state of the system ===

     There are situations when the system is performing actions taking too long for the WebGUI to refresh the values in the web browser. In such a case the system is showing the old value taken directly from cache memory. We recommend using the F5 key to refresh the WebGUI.

=== An ongoing O&ODP process involving small zvol block size or dataset record size generate high load and render the system unstable ===

     O&ODP backup tasks involving small zvol block sizes as well as small dataset record sizes (4KB - 16KB) are known to generate very high load rendering the system unstable. We recommend using at least 64KB sizes for zvols and datasets.

=== Runtime UPS calibration in the client-server configuration unexpectedly shutdowns JovianDSS ===

     In the client-server configuration of the UPS, the runtime UPS calibration process returns an improper value interpreted by JovianDSS as being on battery. When it timeouts it shuts the system down.

=== Starting from up29 (including updating from previous version), system cannot boot up in UEFI mode if your boot medium is controlled by LSI SAS 9300 HBA with outdated firmware ===

     Make sure your LSI SAS 9300 HBA has the latest firmware installed. A quick workaround is changing the booting mode from UEFI to Legacy.

=== Bonded Mellanox network cards show negative values on the network usage chart ===

     This issue will be solved in the future release.

=== In case of hundreds of thousands of LDAP users system starts very slowly ===

     LDAP database is stored on the boot medium. If you have that large LDAP database we recommend using ultra fast NVMe disk for boot medium.

=== After update to JovianDSS up29 write back cache on some hardware RAID volumes can be unintentionally disabled ===

     Starting from JovianDSS up29 we disable write-back cache on all HDD disks by default, but we do not disable write-back cache on SSD drives and hardware RAID volumes. It can happen however that the write-back cache on some RAID volumes can be turned off. Hardware RAID volume performance can be heavily impacted by the lack of the write-back cache, so please make sure it's enabled after update. Open TUI and invoke Extended tools by pressing CTRL+ALT+t, then select Disk write-back cache settings.

=== Restarting or disconnecting JBOD with the write-back cache enabled on disks can lead to the data inconsistency ===

     If write-back cache is enabled on disks in JBOD then restarting or disconnecting JBOD can lead to data inconsistency. Starting from Jovian up29 we disable write-back cache on HDD disks by default during bootup procedure. We do not disable write-back cache on SSD drives and hardware RAID volumes.

=== Snapshots are not displayed after a system reboot if there are more than a few thousands of snapshots ===

     In case there is a large number of snapshots (more than a few thousands) there might be a significant delay in listing them in WebGUI after a system reboot. Depending on how big the number of snapshots is, it may take a few minutes or up to several dozen minutes to populate the list in WebGUI.

=== It is not recommended to use the gzip-9 compression algorithm. ===

     In case of using the gzip-9 compression algorithm the system can behave unstable when copying the data to storage. It is possible to use this compression algorithm only in environments where very efficient processors are being used.

=== It is not recommended to use more than 500 zvols. ===

     In case of using more than 500 zvols in the system, the responsiveness of the Web-GUI may be low and the system may have problems with the import of zpools.

=== It is recommended to use Fibre Channel groups in Fibre Channel Target HA Cluster environments that use the Fibre Channel switches. ===

     In case of using the Fibre Channel switches in FC Target HA Cluster environments, it is recommended to use only Fibre Channel groups (using the Fibre Channel Public group it is not recommended).

=== Manual export and import of zpool in the system or deactivation of the Fibre Channel group without first suspending or turning off the virtual machines on the VMware ESXi side may cause loss of access to the data by VMware ESXi. ===

     Before a manual export and import of a zpool in the system or deactivation of the Fibre Channel group in Fibre Channel Target HA Cluster environment, you must suspend or turn off the virtual machines on the VMware ESXi side. Otherwise, the VMware ESXi may lose access to the data, and restarting it will be necessary.

=== In Fibre Channel Target HA Cluster environments the VMware ESXi 6.7 must be used instead of VMware ESXi 7.0. ===

     In case of using the VMware ESXi 7.0 in Fibre Channel Target HA Cluster environment, restarting one of the cluster nodes may cause the Fibre Channel paths to report a dead state.

=== Sometimes cluster nodes hang up during boot of Open-E JovianDSS. ===

     In case one of the cluster nodes hangs up during Open-E JovianDSS boot, it must be manually restarted.

=== Sometimes when using the ipmi hardware solutions, the cluster node may be restarted again by the ipmi watchdog ===

     In this case, it is recommended to wait 5 minutes before turning on the cluster node after it was turned off.

=== Sometimes restarting one of the cluster nodes may cause some disks to be missing in the zpool configuration. ===

     In this case, click the “Rescan storage” button on the WebGUI to solve this problem.

=== The Internet Connection Check functionality has been removed. ===

     In order to check the internet connection, try to get the date and time from the NTP server using the Web-GUI (System Settings -> System -> Time and date settings).

=== After upgrading the system to a newer version, the event viewer reported an error message: An unexpected system reboot occurred. ===

     After upgrading the system to a newer version, the event viewer reported an error message: "An unexpected system reboot occurred. Run the 'Scrub scanner' on all pools to check the system integrity. Analysis of logs and previous events can help to find the cause of this problem and prevent the issue in the future. For more information, refer to the help article.". This information should be ignored.

=== Low performance on remote disks in case of new installation of JovianDSS up29r2. ===

     The source for this problem is the zfs_vdev_max_active parameter set to 1 on a new installation of JovianDSS up29r2. To resolve this problem, please change the value of the zfs_vdev_max_active parameter from 1 to 1000 in TUI.  In order to change the zfs_vdev_max_active parameter to 1000 open JovianDSS TUI and use CTRL+ALT+W keys combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select the zfs module, then the zfs_vdev_max_active parameter and change its value to 1000. This operation requires a restart of the JovianDSS. This should be done by selecting the Reboot option in the TUI. 

=== In case of no local storage disks in any Non-Shared storage HA Cluster node, the remote disks mirroring path connection status shows incorrect state: Disconnected. ===

     According to assumptions, each cluster nodes in Non-Shared storage HA Cluster must have at least one local storage disk before creating the remote disk mirroring path connection.

=== In some environments in case of using RDMA for remote disks mirroring path, shutdown one of the cluster nodes may causes its restart instead of shutting down. ===

     In some environments in case of using RDMA for remote disks mirroring path, shutdown one of the cluster nodes may causes its restart instead of shutting down.

=== It is not recommended to use the ATTO Fibre Channel Target in the HA cluster environment. ===

     In case of using the ATTO Fibre Channel Target in a HA Cluster environment, after the power cycle of one of the cluster nodes, the fibre channel path reports a dead state. In order to restore the correct status of these fibre channel paths, the VMware server must be restarted.<br/><br/>     In case of using the ATTO Fibre Channel Target in a HA cluster environment, restarting the cluster node with both zpools imported in the system causes the second cluster node to be unexpectedly restarted.

<br/>Therefore, using the ATTO Fibre Channel Target in the HA cluster environment is not recommended.

=== The SED functionality configuration issues. ===

     The SED functionality in Open-E JovianDSS enables to use the drives with verified SED configuration only - they are tagged as "SED" and listed on the Open-E JovianDSS HCL. In order to properly configure the functionality, please follow the steps described in the Knowledge Base article: [https://kb.open-e.com/jdss-sed-support-in-joviandss_3381.html https://kb.open-e.com/jdss-sed-support-in-joviandss_3381.html]

=== The SED configuration tool available in TUI also lists devices that are not currently supported. ===

     The SED configuration tool available in TUI also lists devices that are not currently supported. To check if a given device is supported, see the HCL list available on the Open-E webpage ([https://www.open-e.com/support/hardware-compatibility-list/open-e-jovian-dss/ https://www.open-e.com/support/hardware-compatibility-list/open-e-jovian-dss/]). To find devices for which we support the SED functionality, on the Open-E HCL page in the form: "Search by component", enter: “SED” in the keyword field and click the search button (loupe icon).

=== Enabling the autotrim functionality in the zpools may cause drastic increase load or iowait in the system. ===

     In case of a drastic increase load or iowait in the system after enabling the autotrim functionality in the zpools, consider disabling it. It is recommended to run the "Trim" function manually on demand and at a convenient time (e.g. at a time when the system is working under less load).

=== The Mellanox ConnectX-3 network controller is no longer supported in RDMA mode due to its instability. ===

     In order to provide stable work with RDMA we recommend using the Mellanox ConnectX-4, ConnectX-5, or ConnectX-6.

=== The Network usage charts display incorrect data for an Active-Backup bonding with RDMA. ===

     The Network usage charts incorrectly display data for systems using the Active-Backup bonding with RDMA. The charts only reflect the usage of one network interface included in the Active-Backup bonding (the charts for the second network interface are not generated at all).

=== Duplicate entries appear in the Service Status tab in the WebGUI. ===

     In certain scenarios, the Service Status tab in the WebGUI shows duplicated instances of the same connection.

=== Restoring data backups from the macOS Time Machine application may not work correctly with older versions of the macOS system. ===

     In case of problems with restoring a copy of data from the Time Machine application, it is recommended to update the macOS system to a new version.

=== The Virtual Hard disks smaller than 1B are visible in the WebGUI. ===

     It’s possible to disable the virtual disks through IPMI settings. In Settings -> Media Redirection Settings -> VMedia Instance Settings:
<pre> Uncheck "Emulate SD Media as USB disk to Host" checkbox - it manages one of the virtual disks.
Set "Hard disk instances" to 0 in a combo box.
Set "Remote KVM Hard disk instances" to 0 in the combo box - settings of the combo box manage the second virtual disk.
</pre>
=== Unsupported configuration of VMware virtual machines (consisting of multiple disks) for data rollback from snapshots in On- & Off-site Data Protection. ===

     The VMware virtual machine data rollbacks from snapshots using the On- & Off-site Data Protection functionality are not supported when the virtual machines consist of multiple disks. The specific virtual machine configuration is incompatible with the restoration process.

=== Subdomain statuses in the User Management tab in the WebGUI are not updated. ===

     In case of unavailability of a given subdomain, information about its status will not be updated on the WebGUI (even by pressing the refresh button).

=== The problems with users and groups synchronization within the Active Directory one-way trusted configuration. ===

     In case of problems it’s recommended to use two-way trusted configuration.

=== Partial support for REST API v3. ===

     The REST API v3 is currently only partially supported. As a result, not all operations can be executed using this version of the REST API. For optimal utilization of the REST API, we highly recommend all customers to employ REST API v4.

=== SAS Multipath configuration is not supported in the Non-Shared Storage Cluster. ===

     In the case of the Non-Shared Storage Cluster, the SAS Multipath configuration is not supported at all. In this scenario, all the disks need to be connected through one path only. In the case of using the JBOD configuration with disks connected through a pair of SAS cables, one of them must be disconnected.

=== Username in LDAP database can’t be changed. ===

     To modify a username in the LDAP database, the administrator needs to delete the user account and creating a new one in the WebGUI.

=== The hard disk LED locating and disk faulty functionality do not work properly using the Broadcom HBA 9600 Storage Adapter. ===

     In the case of using the Broadcom HBA 9600 Storage Adapter the Hard disk LED locating and disk faulty functionality do not work.

=== The Broadcom HBA 9600 Storage Adapter may cause “Target allocation failed, error -6” error messages in dmesg. ===

     In the case of using the Broadcom HBA 9600 Storage Adapter,using the “Rescan” button in the storage tab in the WebGUI may results in the “Target allocation failed, error -6” error messages in dmesg.

=== The ARCHTTP tool, when in use, might erroneously redirect to another network interface. ===

     To avoid redirection to another network interface, it’s recommended to connect to the ARCHTTP tool using the primary network interface available in the Open-E JovianDSS (the network interface is usually: eth0).

=== Resilver progress bar in the HA Non-shared Cluster Storage environment may show values over 100%. ===

     In the case of using the HA Non-Shared storage cluster with compression and deduplication enabled it has been observed that the resilver progress bar on the WebGUI may display values exceeding 100%.

=== Identification LED blinking does not work on NVMe drives in AMD-based servers. ===

     The Identification LED blinking on NVMe drives does not work on servers based on AMD processors. This problem will be solved in future releases.

=== The SED configuration tool available in TUI does not lists devices when using the Broadcom 9600 Storage Adapter. ===

     The SED configuration tool available in TUI does not lists devices when using the Broadcom 9600 Storage Adapter.

[[Category:Release Notes]]

Service discovery

2023-12-12T07:44:57Z

Ma-W:

__NOTOC__
=== Zeroconf service discovery ===
<div>This functionality allows discovering NAS devices by any operating system that supports zero-configuration networking (zeroconf), e.g., macOS.</div><div>Two types of services are currently supported:
*Discovering SMB services
*Discovering NAS for Time Machine via SMB
</div><br/>
===== Discovering SMB services =====
<div>Allows the server to broadcast information about its SMB services.</div><br/>
===== Discovering NAS for Time Machine via SMB =====
<div>Allows macOS users to perform backup tasks from the Mac computer to shared folders via SMB.</div><div>The following conditions must be met for the functionality to work:
*The “Discovering SMB services” option must be enabled.
*The “Discovering NAS for Time Machine via SMB” option must be enabled.
*The SMB protocol must be enabled, and the following options must be set as follows:
**Vfs_fruit ON
**oplocks ON
**level2 oplocks ON
**SMB2 leases ON
**kernel oplocks OFF
</div><br/><div>When all conditions above are met, the option that allows shares to be discovered by Time Machine becomes active. The next step is to select the "Enable macOS Time Machine support" option in every share the user wishes to make visible for Time Machine. All shares with this option enabled will be visible for Time Machine.</div><br/><div>'''<span style="color:#ff0000">Note!</span> If any of the above settings are changed, shares will no longer appear in Time Machine.'''</div>
[[Category:Help topics]]

Service discovery

2023-12-12T07:44:15Z

Ma-W:

__NOTOC__

=== Zeroconf service discovery ===
<div>This functionality allows discovering NAS devices by any operating system that supports zero-configuration networking (zeroconf), e.g., macOS.</div><div>Two types of services are currently supported:
*Discovering SMB services
*Discovering NAS for Time Machine via SMB
</div><br/>
===== Discovering SMB services =====
<div>Allows the server to broadcast information about its SMB services.</div><br/>
===== Discovering NAS for Time Machine via SMB =====
<div>Allows macOS users to perform backup tasks from the Mac computer to shared folders via SMB.</div><div>The following conditions must be met for the functionality to work:
*The “Discovering SMB services” option must be enabled.
*The “Discovering NAS for Time Machine via SMB” option must be enabled.
*The SMB protocol must be enabled, and the following options must be set as follows:
**Vfs_fruit ON
**oplocks ON
**level2 oplocks ON
**SMB2 leases ON
**kernel oplocks OFF
</div><br/><div>When all conditions above are met, the option that allows shares to be discovered by Time Machine becomes active. The next step is to select the "Enable macOS Time Machine support" option in every share the user wishes to make visible for Time Machine. All shares with this option enabled will be visible for Time Machine.</div><br/><div>'''<span style="color:#ff0000">Note!</span> If any of the above settings are changed, shares will no longer appear in Time Machine.'''</div>
[[Category:Help topics]]

Service discovery

2023-12-12T07:43:13Z

Ma-W:

__NOTOC__

=== Zeroconf service discovery ===
<div>This functionality allows discovering NAS devices by any operating system that supports zero-configuration networking (zeroconf), e.g., macOS.</div><div>Two types of services are currently supported:
*Discovering SMB services
*Discovering NAS for Time Machine via SMB
</div><br/>
===== Discovering SMB services =====
<div>Allows the server to broadcast information about its SMB services.</div><br/>
===== Discovering NAS for Time Machine via SMB =====
<div>Allows macOS users to perform backup tasks from the Mac computer to shared folders via SMB.</div><div>The following conditions must be met for the functionality to work:
*The “Discovering SMB services” option must be enabled.
*The “Discovering NAS for Time Machine via SMB” option must be enabled.
*The SMB protocol must be enabled, and the following options must be set as follows:
**Vfs_fruit ON
**oplocks ON
**level2 oplocks ON
**SMB2 leases ON
**kernel oplocks OFF
</div><br/><div>When all conditions above are met, the option that allows shares to be discovered by Time Machine becomes active. The next step is to select the "Enable macOS Time Machine support" option in every share the user wishes to make visible for Time Machine. All shares with this option enabled will be visible for Time Machine.</div><br/><div>'''<span style="color:#ff0000">Note!</span> If any of the above settings are changed, shares will no longer appear in Time Machine.'''</div>
[[Category:Help topics]]

Storage performance test tool

2023-07-05T13:20:52Z

Ma-W:

=== General information ===

The storage performance test tool allows you to test speed of raw disks or zvols. The tool is available via TUI (Text-based User Interface). To access the tool, perform the following steps:

#While in TUI, press '''Ctrl'''+'''Alt'''+'''T'''.
#Select '''Add-ons''' from the menu.
#Select '''Storage performance test''' from the list.

You are able to select either a raw device test or zvol device test. Also, you can view test results.Once the test type is selected, you will be asked to select a device to be tested. After performing this operation, a test profile has to be selected. The following types can be chosen:

*ran_write (blocksize 512B)
*ran_read (blocksize 512B)
*seq_write (blocksize 1MB)
*seq_read (blocksize 1MB) 
<div><div>Every random test takes 100 seconds and sequential test takes 150 seconds. Testing progress is shown while running the test. To interrupt the test, press the Ctrl+\ keyboard shortcuts. Test results are available from tool or in logs downloaded from the GUI.</div><div><br/></div>
=== Raw device test ===

This test allows you to choose disks that are not assigned to zpool. 

=== Zvol device test ===
</div><div>This test allows you to choose zvols. To ensure data safety on zvols in zpool, zvol name must contain: '''data_DESTRUCTIVE_benchmark_test_ONLY.''' Otherwise, it won’t be listed under the '''Zvol device selection''' list. Note that you can overwrite data on this zvol using ran_write or seq_write profile. Once a write profile is selected, you will need to confirm that you understand the risk of using such profiles.</div><div><br/></div>
=== Test results viewer ===
<div>Here you can view the results or remove them one by one. Test results are also available in logs downloaded from GUI in the “TEST_RESULTS” folder.</div><div><br/></div><div><br/></div><div><br/></div>
[[Category:ZFS and data storage articles]]

Main Page

2023-07-05T13:20:38Z

Ma-W:

===== ''Release Notes:'' =====

{{
#tag:DynamicPageList|
category = Release Notes
ordermethod = categorysortkey
order = descending
count = 1
mode = none
}}
<div>[[Release Notes|All release notes »]]</div>

----

'''''Help topics:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = Help topics
count=40
ordermethod = categorysortkey
order = ascending
}}

|
{{
#tag:DynamicPageList|
category = Help topics
offset = 40
count= 40
ordermethod = categorysortkey
order = ascending
}}

| style="vertical-align: top" |
{{
#tag:DynamicPageList|
category = Help topics
offset = 80
count=40
ordermethod = categorysortkey
order = ascending
}}

|}

----

'''''ZFS and data storage articles:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = ZFS and data storage articles
count=60
ordermethod=categorysortkey
order = ascending
}}

|}

----

'''''Video tutorials:'''''

'''''<span style="color:#696969"><span><span>Open-E JovianDSS Video Tutorials</span></span></span>''''' {{
#tag:DynamicPageList|
category = Open-E JovianDSS Video Tutorials
ordermethod = sortkey
order = ascending }}<br/>'''''<span style="color:#696969"><span><span>Setting up Open-E JovianDSS Standard HA Cluster</span></span></span>''''' {{
#tag:DynamicPageList|
category = Setting up Open-E JovianDSS Standard HA Cluster
ordermethod = sortkey
order = ascending }}<br/>'''''<span style="color:#696969"><span><span>Setting up Open-E JovianDSS Advanced Metro HA Cluster</span></span></span>''''' {{
#tag:DynamicPageList|
category = Setting up Open-E JovianDSS Advanced Metro HA Cluster
ordermethod = sortkey
order = ascending
}}

Main Page

2022-11-28T15:48:51Z

Ma-W:

===== ''Release Notes:'' =====

{{
#tag:DynamicPageList|
category = Release Notes
ordermethod = categorysortkey
order = descending
count = 1
mode = none
}}
<div>[[Release Notes|All release notes »]]</div>

----

'''''Help topics:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = Help topics
count=40
ordermethod = categorysortkey
order = ascending
}}

|
{{
#tag:DynamicPageList|
category = Help topics
offset = 40
count= 40
ordermethod = categorysortkey
order = ascending
}}

| style="vertical-align: top" |
{{
#tag:DynamicPageList|
category = Help topics
offset = 80
count=40
ordermethod = categorysortkey
order = ascending
}}

|}

----

'''''ZFS and data storage articles:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = ZFS and data storage articles
count=60
ordermethod=lastedit
order = descending
}}

|}

----

'''''Video tutorials:'''''

'''''<span style="color:#696969"><span><span>Open-E JovianDSS Video Tutorials</span></span></span>''''' {{
#tag:DynamicPageList|
category = Open-E JovianDSS Video Tutorials
ordermethod = sortkey
order = ascending }}<br/>'''''<span style="color:#696969"><span><span>Setting up Open-E JovianDSS Standard HA Cluster</span></span></span>''''' {{
#tag:DynamicPageList|
category = Setting up Open-E JovianDSS Standard HA Cluster
ordermethod = sortkey
order = ascending }}<br/>'''''<span style="color:#696969"><span><span>Setting up Open-E JovianDSS Advanced Metro HA Cluster</span></span></span>''''' {{
#tag:DynamicPageList|
category = Setting up Open-E JovianDSS Advanced Metro HA Cluster
ordermethod = sortkey
order = ascending
}}

Release Notes

2022-11-28T15:47:48Z

Ma-W: Created page with "{{ #tag:DynamicPageList| category = Release Notes ordermethod = categorysortkey order = descending }}"

{{
#tag:DynamicPageList|
category = Release Notes
ordermethod = categorysortkey
order = descending
}}

Open-E JovianDSS ver.1.0 up29r2 Release Notes

2022-07-06T13:29:16Z

Ma-W:

'''Release date: 2022-07-06'''

'''Build: 48155'''

{| class="cke_show_border cke_show_border"
|-
| __TOC__

|}

== New ==

=== NVMe Write Log devices mirror over Ethernet for HA Shared Storage Cluster ===

=== RDMA protocol support for mirroring path connection dedicated to Mellanox NIC ===

=== Intel Optane™ Persistent Memory support (PMem) ===

=== Self-Encrypting Drives (SED) feature support ===

=== SSD TRIM functionality ===

=== Custom OU (Organization Unit) parameter in Active Directory ===

=== Read and Write list for SMB shares ===

=== ‘Hosts allow’ parameter for Samba available in WebGUI ===

=== Additional scheduler to pause a scheduled scrub process, e.g. to suspend it during working hours ===

=== Paging mechanism for snapshots ===

=== ‘Expand pool size’ option for replacing disks with larger-sized available in TUI (CTRL+ALT+X) ===

=== Severity level included in the notification email’s subject ===

=== Option to launch the system in RESCUE MODE (with skipping pools import) ===

=== The most important statistics regarding the ZFS Pool usage on WebGUI ===

=== TLS 1.2 and 1.3 available in the SMTP server configuration ===

=== Checkmk agent checks for Percent Capacity per Pool replaced checks of available space per volume ===

=== VORTEX SHELF JBOD status monitoring ===

=== The source of force reboot is logged in IPMI ===

=== ATTO Config Tool (v4.36) ===

== Updated ==

=== Kernel (v4.19.190) ===

=== ZFS (v2.1.1-1) ===

=== Checkmk agent (v1.5.0p8) ===

=== Network UPS Tools (upsmon, v2.7.4) ===

=== Intel 1GbE driver (igb, v5.8.5) ===

=== Intel 1GbE driver (e1000e, v3.8.7-NAPI) ===

=== Intel 10GbE driver (ixgbe, v5.13.4) ===

=== Intel 40GbE driver (i40e, v2.17.4) ===

=== Intel 100GbE driver (i40e, v2.17.4) ===

=== Broadcom BCM573xx and Broadcom BCM574xx controllers (bnxt_en, v1.10.2-219.0.55.0) ===

=== Broadcom BCM577xx and Broadcom BCM578xx controllers (bnx2x, v1.715.10) ===

=== Marvell FastLinQ 41000 Series driver (qede, v8.55.13.0) ===

=== Solarflare 10GbE Driver (sfc, v4.15.13.1000) ===

=== Mellanox ConnectX-3 driver (mlx4_core, v4.9-3.1.5) ===

=== Mellanox ConnectX-4/5 driver (mlx5_core, v5.2-2.2.0) ===

=== Emulex LightPulse Fibre Channel Adapter driver (lpfc, v12.8.614.14) ===

=== ATTO Celerity 16Gb/32Gb Fibre Channel Adapter driver (celerity16fc, v2.04.0f1) ===

=== ATTO Celerity 8Gb Fibre Channel Adapter driver (celerity8fc, v2.21.0f1) ===

=== ATTO ExpressSAS 6Gb/s HBA (esas2hba, v2.38.0f1) ===

=== ATTO ExpressSAS 12Gb/s HBA (esas4hba, v1.48.0f1) ===

=== ATTO ExpressSAS 12Gb/s GT HBA (esas5hba, v1.03.0f1) ===

=== Areca RAID controllers driver (arcmsr, vv1.50.0X.07-20210712) ===

=== HP Smart Array driver (hpsa, v3.4.20-208) ===

=== Microsemi Adaptec Series SAS/SATA 6/12GB RAID driver (aacraid, v1.2.1.60001src) ===

=== Microsemi Adaptec SmartHBA and SmartRAID driver (smartpqi, v2.1.16-030) ===

=== Broadcom 12Gb SAS HBA driver (mpt3sas, v39.00.00.00) ===

=== Broadcom 12Gb MegaRAID driver (megaraid_sas, v07.719.03.00) ===

=== MegaRAID Storage Manager (MSM, v.17.05.02.01) ===

=== Microsemi Adaptec MaxView tool v3.10.24308 ===

=== LSI Storage Authority v007.019.006.000 ===

=== HPE Smart Storage Administrator v4.21.7.0 ===

=== HPE System Management Homepage v7.6.7 ===

== Fixed ==

=== Very long pool export/moving time in case of large number of O&ODP tasks. ===

=== System hang-ups during the reboot procedure. ===

=== Negative network speed values in the network usage charts. ===

=== It takes long time to display a large number of snapshots after a reboot. ===

=== It is not possible to export a pool when the share subdirectory is mounted through NFS. ===

=== Attempting to establish hundreds or thousands of connections to the resource's SMB simultaneously causes an LDAP service timeout. ===

=== When logging in to SMB shares, both as a guest and a user with a password, Workgroup name providing is obligatory. ===

=== Listing a very large number of files (several million and above) in one SMB share takes a long time or fails. NOTE: The problem was solved by adding the Metadata pinning functionality (System Console -> Addons -> Metadata pinning) ===

=== Removing dataset/zvol with thousands of snapshots cause timeouts on WebGUI. ===

=== Persistent Reservation Sync (PRS) mechanism on some environments can saturate one of the CPU cores to 100%. ===

== Important notes for JovianDSS HA configuration ==

=== It is necessary to use sync always option for zvols and datasets in cluster  ===

=== It is strongly recommended not to use more than eight ping nodes ===

=== It is strongly recommended to configure each IP address in separate subnetwork ===

=== It is necessary to run Scrub scanner after failover action triggered by power failure (dirty system close) ===

=== It is strongly recommended to use UPS unit for each cluster node ===

=== It is necessary to use static discovery in all iSCSI initiators ===

=== It is strongly not recommended to change any settings when both nodes do not have the same JovianDSS version, for example during software updating ===

=== It is necessary to use different Server names for cluster nodes ===

=== HA cluster does not work properly with Infiniband controllers ===

=== HA cluster does not work stable with ALB bonding mode ===

=== FC Target HA cluster does not support Persistant Reservation Synchronization and it cannot be used as a storage for Microsoft Hyper-V cluster. This problem will be solved in future releases. ===

=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===
<p style="text-align: justify"><span class="toctext">    You can find details below:</span></p><p style="text-align: justify"><span class="toctext">    [https://kb.open-e.com/index.php?View=entry&EntryID=3101 https://kb.open-e.com/index.php?View=entry&EntryID=3101]</span></p><p style="text-align: justify"><span class="toctext">    *Please consult Broadcom vendor for specific firmware that is suitable for your hardware setup.</span></p>
== Performance tuning ==

=== iSCSI Target with VMware ESX performance tuning ===

     In case of low iSCSI Target performance with VMware ESX, a few parameters need to be changed in VMware ESX iSCSI Initiator. Go to Storage Adapters -> iSCSI Software Adapter -> Advanced Options and the change the following settings:
<pre>
MaxOutstandingR2T change the default 1 to 8

FirstBurstLength change the default 262144 to 65536

MaxBurstLength change the default 262144 to 1048576

MaxRecvDataSegLen change the default 131072 to 1048576
</pre>
=== Write cache sync requests performance tuning ===

     Write cache sync requests (sync) set to “always” for zvol is the safest option and is set by default. However, it can cause write performance decreases since all operations are written and flushed directly to the persistent storage. In case of using sync=always, it is strongly recommended using mirrored write log devices (very fast random writes devices).<br/>     Sync=standard or sync=disabled zvol options provide huge performance improvement but the most recent (up to 5 seconds) cached data can be lost in case of a sudden power failure. Use this option only in environments equipped with UPS.<br/>     For NFS shares the Synchronous data record is enabled by default. This option causes performance to be worse, but data can be safely written. In order to improve the NFS performance you can use Asynchronous data record but in such case, it is strongly recommended to use UPS.

== Known issues ==

=== Browser recommendations ===

     It is strongly recommended to use Mozilla Firefox browser to navigate the system’s GUI. When using other browsers some slight problems with displaying content may occur.

=== Web browser’s cache ===

     After updating from previous versions, some problems with WebGUI content and navigation may occur. To resolve this problems, please clear Web browser cache.

=== System as a guest in virtual environments ===

     Hyper-V:<br/>     In case of installing the system as a Hyper-V guest please use the following settings:<br/>       - Number of virtual processors: 4<br/>       - Memory: Minimum 8GB<br/>       - Boot Disk: 20GB IDE Disk<br/>       - Add at least 6 virtual disk

 <br/>     VMware ESXi:<br/>     In case of installing the system as a VMware ESXi guest please use the following settings:<br/>       - Guest OS: Other 2.6.x Linux ( 64bit )<br/>       - Number of Cores: 4<br/>       - Memory: Minimum 8GB<br/>       - Network Adapter: VMXNET 3<br/>       - SCSI Controller Type: Paravirtual or LSI Logic SAS<br/>       - Boot Disk : 20GB Thick Provision Eager Zeroed<br/>       - Add at least 6 virtual disk<br/>       - Edit Settings->Options->Advanced-General->Configuration-> Add row: disk.EnableUUID : TRUE

=== Reclaim deleted blocks on thin-provisioned LUNs in various systems ===

     In case of deleting large amounts of data, reclaimed deleted blocks on thin-provisioned LUNs in Windows 2012 can significantly slow down system performance. If you predict frequent deletions of large amounts of data, we recommend turning off the automatic reclaim function in Windows 2012. This can be done by disabling the "file-delete notification" feature in the system registry. To do so, follow the steps below:<br/>       - start Registry Editor.<br/>       - locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem       <br/>       - double-click DisableDeleteNotification.<br/>       - in the Value data box, enter a value of 1, and then click OK.<br/> <br/>     In order to reclaim the free space in Windows 2012 please change the    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\DisableDeleteNotification key value back to 0 and use "Optimize" tool located in Disc Management->[disk]->Properties->Tools. As the operation can generate a very high load in the system, it is recommended to perform it after-hours.  <br/>In case of VMware ESXi, the automatic reclaim feature is disabled by default. To reclaim the space of deleted blocks on thin-provisioned LUNs, please use vmkfstools. For details, please refer to the VMware Knowledge Base:

For VMware ESXi 5.0: [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849]<br/>For VMware ESXi 5.5 and newer: [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513 https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513]<br/>For VMware ESXi 6.7 and newer: search in Internet for “Space Reclamation Requests from VMFS Datastores” and read vendor documentation.

In case of using Windows 2008 there is no possibility to reclaim the space released by deleted data of thin-provisioned LUNs.

=== Deduplication issues and recommendations ===

     Please be aware that deleting the zvol with deduplication enabled can generate a very high load in the system and lead to unstable behavior. It is strongly recommended to perform such operation only after-hours. To avoid this issue, please use (if possible) single zvol on zpools dedicated for deduplication and delete the zpool which includes the single zvol.<br/>   <br/>     To determine the amount of System RAM required for deduplication, use this formula:<br/> <br/>                                                                                                                    (Size of Zvol / Volume block size) * 320B / 0.75 / 0.25<br/> <br/>Where:<br/>320B - is the size of entry in DDT table<br/>0.75 - Percentage of RAM reservation for ARC (75%)<br/>0.25 - Percentage of DDT reservation in ARC (25%)<br/> <br/>     Example for 1TB data and 64KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 65536B) * 320B / 0.75 / 0.25 = 28633115306.67B<br/>                                                                                                                       28633115306.67B / 1024 / 1024 / 1024 = 26.67GB<br/> <br/>so for every extra 1TB of storage, system needs extra 26.67GB RAM.<br/><br/>     Example for 1TB data and 128KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 131072B) * 320B / 0.75 / 0.25 = 14316557653.33B<br/>                                                                                                                        14316557653.33B / 1024 / 1024 / 1024 = 13.33GB<br/> <br/>so for every extra 1TB of storage, system needs extra 13.33GB RAM.
<div><br/></div><div>     Example for 1TB data and 1MB Volume block size:</div><div><br/></div><div>                                                                                                      (1099511627776B / 1048576B) * 320B / 0.75 / 0.25 = 1789569706,66B</div><div>                                                                                                                        1789569706,66B / 1024 / 1024 / 1024 = 1.66GB</div><div> </div><div>     so for every extra 1TB of storage, system needs extra 1.66GB RAM.</div><div><br/></div>
<br/>'''IMPORTANT: '''The above calculations only apply to the worst case scenario, when data is completely unique and will not be deduplicated. For the deduplicable data, the need for RAM drastically decreases. If SSD based Read Cache is present, part of deduplication table will be moved to the SSD and deduplication will work with good performance using less RAM.

<br/>'''IMPORTANT: '''With SAN (iSCSI) it is CRITICAL to match User-File-System format block size with the zvol volume-block-size. A simple example is a Windows file system NTFS with default format block size 4k and zvol default volume-block-size is 128k. With defaults like this deduplication will mostly NOT match because files can be aligned in 32 (128/4) different positions on the pool. If the NTFS format is increased to 64k and the zvol default volume-block-size is 128k, deduplication match can fail only one time because a file can be aligned to 2 (128/64) different positions on the pool. Every next write will match already as both alignment options already exist on the pool. In order to achieve all files matching and efficient memory usage NTFS must use 64k format block size and the zvol volume-block-size must equal 64k. Another option is that the NTFS=32k and zvol=32k, but in this case the deduplication table will be twice as large. That is why the NTFS=64k and zvol=64k is the most efficient setting for deduplication.

'''IMPORTANT: '''With NAS (NFS, SMB/CIFs) deduplication matching works always due to the data blocks being aligned by ZFS natively.

'''IMPORTANT: '''De-duplication is working on the pool level in the pool-range. This is why zvol-Physical size cannot show de-duplication benefit. In order to prove that deduplication saved space run the scrub and notice the current physical data space on the pool reported by the scrub. Next copy of new data and run the scrub again. Now scrub will show new physical data space. Comparing the data size from storage client side with the data space growth from the scrub will give the deduplication advantage. The exact pool of the deduplication ratio can be found in LOGs in zfs.log.

=== Zvols configuration issues and recommendations ===

     It is strongly recommended to set the client file system block size same as the zvol volume block size. For example, when using 64k zvol volume block size, the Windows Allocation unit size of NTFS should be set to 64k.

=== Target number limit ===

    In case of more than 60 targets, GUI will not be displayed correctly. This issue will be fixed in the next releases.

=== Targets with the same name are not assigned correctly ===

    Having two or more targets with the same name but belonging to various Zpools, will cause that all targets with the same name will be assigned to one Zpool during the import process.

=== Installation on disks containing LVM metadata ===

     There is no possibility to install the system on disks containing LVM metadata. You will need to clear those disks before installation. To do so, use the “Remove ZFS data structures and disks partitions” function located in the Extended tools. To access this function, boot the system from a temporary media like a USB drive or DVD.

=== Import Zpool with broken write log ===

     There is no option to import Zpool with a broken write log disk using the system’s functions. This is why it is STRONGLY recommended to use mirrored disks for write logs. In case it is necessary to import Zpool with a broken write log, please contact technical support.

=== Replacing disks in data groups for larger ones can cause your storage license capacity to be exceeded ===

     In case of replacing damaged disks for larger ones, the size of the entire Zpool will increased. Make sure that the new size will not exceed your purchased storage license.

=== Periodically after some operations, the GUI needs to be manually refreshed ===

     After performing some operations, e.g. resilvering, the GUI will show outdated information. In this case refresh the web page manually by pressing F5 on your keyboard. This issue will be fixed in next releases.

=== Replacing disks in data groups for smaller ones can cause an error and make the disk disappear from the list of available disks ===

     Operation of replacing a disk in a data group for a smaller one will cause an error "zpool unknown error, exit code 255", and the disk will become unavailable. In order to reuse this disk, please use function "Remove ZFS data structures and disks partitions" located in the Extended tools on the Console screen.

=== It is strongly recommended to use 64KB or higher Volume block size ===

     Smaller than 64KB block sizes used with deduplication or read cache will cause very high memory consumption.

=== RAM recommendations for Read Cache ===

     To determine how much System RAM is required for Read Cache, use the following formula:

<br/> <br/>                                                                      RAM needed = (Size of Read Cache - reserved size and labels) * bytes reserved by l2hdr structure / Volume block size<br/> 

     For 8KB Volume block size and 1TB Read Cache:<br/><br/>                                                                           RAM needed = (1099511627776B - 4718592B) * 432B / 8192B = 57981809664B<br/>                                                                                                        57981809664B / 1024 / 1024 / 1024 = 54GB<br/> <br/>Where:<br/>1099511627776B - 1TB Read Cache<br/>4718592B - reserved size and labels<br/>432B - bytes reserved by l2hdr structure<br/>8192B - Volume block size<br/> <br/>                                                                                                  For 64KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 65536B = 7247726208B<br/>                                                                                                       7247726208B / 1024 / 1024 /1024 = 6.75GB<br/><br/><br/>                                                                                                  For 128KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 131072B = 3623863104B<br/>                                                                                                       3623863104B / 1024 / 1024 /1024 = 3.37GB

=== Multiple GUI disk operations may result in an inaccurate available disks list ===

     Multiple operations of adding and detaching disks from groups can cause that the next operation of detaching will fail, but the disk will be shown on a list of available disks. When trying to add this disk to one group it will fail with the following error "[zfslib-wrap-zpool-ZpoolCmdError-1] invalid vdev specification". In this case, detach this disk once again.

=== After removing disks from groups they may not be displayed on a list of available disks ===

     Sometimes after removing disks from groups, Spare/Read Cache/Write Log disks are displayed on a list of unassigned disks, but they are not on a list of available disks. In this case, click the rescan button located in the adding group form.

=== Reusing disks from an exported and deleted Zpool ===

     After deleting an exported Zpool, not all disks which were a part of a Zpool become immediately available. Before you can reuse disks, which were previously used as a Spare or a Read Cache, you must first clean them. Use “Remove ZFS data structures and disks partitions” function located in the “Extended tools”.

=== Negotiated speed of network interfaces may not display correctly ===

     For some network interfaces, the negotiated speed field may display an incorrect value in GUI and Console. This issue will be fixed in next releases.

=== Limited possibility to display a large number of elements by the GUI ===

     After creating multiple snapshots, clones or zvols some forms in GUI work very slow. If you need to create many snapshots, clones or zvols, it is strongly recommended to use CLI in order to perform operations on them.

=== Open-E VSS Hardware Provider system recommendations ===

     It is strongly recommended to use Windows Server 2012. On the other Windows systems, Open-E VSS Hardware Provider Configuration works unstable.

=== Exceeded quota for dataset does not allow to remove files ===

     Files located on datasets with exceeded quota cannot be removed. In this case, please resize quota and then remove unnecessary files.

=== Slow WebGUI with multiple datagroups ===

     Zpool with more than 20 datagroups causes that some forms on WebGUI work very slow. If you need to create many datagroups, it is strongly recommended to use CLI API.

=== Slow WebGUI with multiple datasets ===

     More than 25 datasets cause that WebGUI works slow.

=== ZFS Upgrade ===

     For Open-E JovianDSS users, it is recommended to upgrade Zpools to the latest ZFS file system. Although the file system upgrade is absolutely safe for your data, and takes only few minutes, please be aware that this operation cannot be undone. In order to upgrade a single Zpool, please use "WebGUI -> Zpool options -> Upgrade file system" from Zpool's option menu.

=== Intel® Ethernet Controller XL710 Family ===

     In case of using Open-E JovianDSS with Intel® Ethernet Controller XL710 Family, it is necessary to update firmware’s network controller to the version: f4.33.31377 a1.2 n4.42 e1932.

=== Motherboards with x2APIC technology ===

     In case of using a motherboard with x2APIC technology enabled, it is necessary to disable x2APIC in BIOS. Otherwise, problems with CPU cores will occur.

=== NFS FSIDs and Zpool name ===

     One of the factors that have been taken into account when NFS FSIDs are generated is Zpool name. It indicates that when Zpool name is changed, e.g. during export and import with different names, FSIDs for NFS Shares located on this Zpool will also be changed.

=== High Availability shared storage cluster does not work with Infiniband controllers ===

     Due to technical reasons the High Availability shared storage cluster does not work properly when using the Infiniband controllers for VIP interface configuration. This limitation will be removed in the future releases.

=== Disks with LVM data cannot be used with the created Zpool ===

     Attempt to create Zpool with drives that contain LVM data will fail with the following error:

''"cannot open 'lvm-pv-uuid-R25lTS-kcDc-eiAN-eAlf-ppgi-rAqu-Oxy1Si': no such device in /dev must be a full path or shorthand device name"''

In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.

=== Unexpected long failover time, especially with HA-Cluster with two or more pools ===

     Current failover mechanism procedure is moving pools in sequence. Since up27 release, up to 3 pools are supported in HA-cluster. If all pools are active on single node and failover needs to move all 3 pools, the failover may take longer than 60 seconds which is a default iSCSI timeout in Hyper-V Clusters. In some environments, under heavy load a problem with too long time of cluster resources switching may occur as well. If the switching time exceeds the iSCSI initiator timeout, it is strongly recommended to increase the timeout up to 600 seconds.

     '''In case of using Windows, to increase iSCSI initiator timeout, please perform following steps:'''

1. Run regedit tool and find: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\...\Parameters\MaxRequestHoldTime registry key''

2. Change value of the key from default 60 sec to 600 sec (decimal)

     '''In case of using VMware, to increase iSCSI initiator timeout, please perform following steps:'''

1. Select the host in the vSphere Web Client navigator

2. Go to Settings in the Manage tab

3. Under System, select Advanced System Settings

4. Choose the ''Misc.APDTimeout'' attribute and click the Edit icon

5. Change value from default 140 to 600 sec.

     '''In case of using XenServer, to increase iSCSI initiator timeout, please perform following steps:'''

A. For existing Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Detach and reattach SRs. This will update the new iSCSI timeout settings for the existing SRs.

B. For new Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Create the new SR. New and existing SRs will be updated with the new iSCSI timeout settings.

=== Activation may be lost after update ===

     In some environments, after update to up11 system may require re-activation. This issue will be removed in the future releases.

=== Bonding ALB and Round-Robin do not work in Hyper-V and VMware environments ===

     In case of using JovianDSS as Hyper-V or VMware guest, bonding ALB and Round-Robin is not supported. Please use another type of bonding.

=== Continuous writing in VMware guest can cause that deleting VMware snapshot can take long time ===

     Using ODPS on zvol/dataset with VMware guest where many I/O operations are performed can cause that the process of deleting VMware snapshot can take long time. Please take this into consideration while you set up the scheduler for Off-site Data Protection Service task.

=== Enabling quota on dataset can cause file transfer interrupt ===

     Enabling quota functionality on a dataset can cause file transfer interrupt. Before using it in production environment, please enable quota on dataset, or make sure that no file transfers are active.

=== Nodes connected to the same AD server must have unique Server names ===

     If JovianDSS nodes are connected to the same AD server, they cannot have the same Server names.

=== Share can not be named the same as Zpool ===

     In case of share with the same name as Pool connections problem will occur. Please use different names.

=== No persistent rules for network cards in virtual environment ===

     Changing settings of virtual network cards (delete, changing MAC, etc.) can cause unstable system behaviour. Please do not change settings on production system. This issue will be fixed in next releases.

=== Downgrade to up17 or earlier is not possible ===

     Starting from up18 bootable medium has always SW RAID structure. Attempt to come back to earlier version is impossible. If you need come back to earlier version, you must reinstall version again.

=== System cannot be installed on cciss based controllers ===

     This issue will be fixed in next releases.

=== Interrupt the process of adding second disk to SW RAID (bootable medium) can cause run system from disk with uncompleted data ===

     Performing operation like: reboot, shutdown, power off, etc. during mirroring data on new added disk can cause that system will be booted from new disk which has incomplete data. In this case, SW RAID function shows empty status and wrong number of RAID members. To resolve this issue, please plug off disk which has incomplete data, boot system, plug in disk and add it once again to SW RAID.

=== SAS-MPIO cannot be used with Cluster over Ethernet ===

     It is strongly not recommended to use Cluster over Ethernet with SAS-MPIO functionality. Such a configuration can lead to a very unstable cluster behavior.

=== On- & Off-site Data Protection backward compatibility problem ===

     In case of using On- & Off-site Data Protection functionality in up21 or earlier, it is strongly recommended to remove all backup tasks created by CLI API and re-create it using GUI.

=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===

     In FC Target HA environment, power cycle of both nodes simultaneously may lead to a situation when VMware is not able to restore proper state of the storage devices. In vSphere GUI LUNs are displayed as Error, Unknown or Normal,Degraded. Moving affected pools to another node and back to its native node should bring LUNs back to normal. A number two option is to restart the Failover in Jovian’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.

=== Problem with maintenance in case of disk failure ===

     In case of disk failure, please remove the damaged disks from the system, before starting administrative work to replace the disk. The order of actions is important.

=== Separated mode after update from JovianDSS up24 to JovianDSS up25 ===

     In HA cluster environment after updating of one node from JovianDSS up24 to JovianDSS up25 the other node can fall into separated mode and the mirror path might indicate disconnected status. In such a case go to Failover Settings and in the Failover status section select Stop Failover on both nodes. Once this operation is finished select Start Failover.

=== Different Write Cache default setting for zvols in early beta versions of Jovian DSS up25 ===

     In the early beta versions of JovianDSS up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of Jovian up25 the Log bias is set to “Write log device (Latency)”.<br/>Please note, that “In Pool (Throughput)” setting may cause a drop in performance in environments with a lot of random access workloads which is a common factor for a majority of production environments.

=== Target alias name is required while configuring HA FC Target in case of adding two or more ports to one FC group ===

     If we want to have more then one port in each FC group (in HA FC configuration) it is necessary to type in Target alias name for every port. Otherwise an error message “Target alias is already used” can show up while setting up remote port mapping for FC targets in (pool name) -> Fibre Channel -> Targets and initiators assigned to this zpool. This issue will be resolved in the future release.

=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===

     In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of Jovian up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open Jovian TUI and use CTRL+ALT+W key combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select qla2xxx_scst QLogic Fibre Channel HBA Driver and make sure the value of this parameter is set to “exclusive”.<br/><br/>Please note that in order to change this parameter Failover must be stopped first.

=== Very low performance of FIO/WT in case of mixed FIO/WT and FIO/WB zvol configurations over Fiber Channel ===

     In case of the mixed FIO/WT and FIO/WB zvol configurations over FC one can observe significantly decreased performance on FIO/WT.

=== More than one zvol with FIO/WB mode can cause instability of the Fiber Channel connection ===

     If there's more than one FIO/WB zvol or a FIO/WB zvol is coexisting with other types of zvols it can cause an instability of the FC connection with client machines. As a result client machines may unexpectedly lose FC connected resources.

=== In certain situations system page cache is not able to flush File I/O errors by itself and cache flushing has to be performed manually ===

     Under certain conditions (like overfilling zvol and then expanding its size) some File I/O errors may be held by the system page cache and it requires manual flushing (in GUI use Storage -> Rescan).

=== Updating nodes of the Jovian cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===

     There is a significant difference in FC configurations in up24 and earlier versions. Those versions allowed the FC ports to be configured in initiator mode only, while later versions allow both target and initiator mode with target as default, so in case of using storage connected via FC initiator, FC port(s) must be manually corrected in GUI of the updated node.

=== Updating Metro Cluster node with NVMe disks as read cache from JovianDSS up26 or earlier can cause the system to lose access to the NVMe disks ===

     The process of updating of Metro Cluster node from JovianDSS up26 or earlier is changing NVME disk IDs. In consequence moving pool back to updated node is possible but the read cache is gone (ID mismatch). In order to bring read cache back to the pool we recommend to use console tools in the following way: press Ctrl+Alt+x -> “Remove ZFS data structures and disks partitions”, locate and select the missing NVMe disk and press OK to remove all ZFS metadata on the disk. After this operation click Rescan button in GUI -> Storage. The missing NVMe disk should now appear in Unassigned disks at the bottom of the page which allows to select that disk in pool’s Disk group’s tab. Open Disk group tab of the pool, press the Add group button and select Add read cache. The missing disk should now be available to select it as a read cache.

=== Synchronization of a large LDAP database can last for a long time (e.g. 10h for 380K users) and can be associated with high system load ===

     This problem will be solved in future releases.

=== Long time of a failover procedure in case of Xen client with iSCSI MPIO configuration ===

     In a scenario where Xen client is an iSCSI initiator in MPIO configuration, the power-off of one node starts the failover procedure that takes a very long time. Pool is finally moved successfully but there are many errors showing up in dmesg in meantime. In case of such an environment we recommend to add the following entry in the device section of the configuration file: /etc/multipath.conf:

'''no_path_retry queue'''

<br/>The structure of the device section should look as follows:
<pre>device {
vendor "SCST_FIO|SCST_BIO"
product "*"
path_selector "round-robin 0"
path_grouping_policy multibus
rr_min_rio 100
no_path_retry queue
}
</pre>
=== In case of large number of disks, zpool move can take a long time ===

     In certain environments in case of large number of disks (about 100 and more) the zpool move operation can take a long time.

=== No support for VMD option in BIOS leads to a problem with listing PCI devices ===

     On some servers, an enabled VMD option in BIOS causes that PCI devices are not listed properly. If this is the case please disable the VMD option in BIOS. This problem will be solved in the future release.

=== Rolled back data are not properly refreshed both in Windows and Vmware systems ===

     Before using rollback operation on zvol please detach iSCSI or FC target, perform rollback operation and reattach target.

=== User gets deleted from share access list after changing its username on AD server ===

     If the AD user is assigned to a share and later the username is changed we should let JDSS know about it. Using the "Synchronize and update shares configurations" operation on JDSS leads to a situation where the changed user gets deleted from the share’s access list. The new username needs to be added to the share’s access list manually.

=== QLogic 32Gbit FC HBA is no longer supported ===

     Starting from JovianDSS up29 we no longer support QLogic 32Gbit FC adapters.

=== Certain 16Gbit FC HBAs are no longer supported ===

     Starting from JovianDSS up29 we no longer support certain 16Gbit FC adapters. If you are using a 16Gbit FC adapter based on the Qlogic chipset using the qla2xxx_scts driver, please refer to our online hardware compatibility list (HCL) to verify if that particular adapter is supported.

Our HCL is available at this link: [https://www.open-e.com/support/hardware-compatibility-list/open-e-jovian-dss/ https://www.open-e.com/support/hardware-compatibility-list/open-e-jovian-dss/]

=== E-mail password cannot contain special non-ASCII characters ===

     The following special characters # : + cannot be used in a password used in an e-mail notification feature. They can break the authentication process.

=== LSA e-mail notifications does not work with SMTP servers requiring SSL/TLS authentication ===

     E-mail alert configuration in LSI Storage Authority Software does not work with SMTP servers which require SSL/TLS authentication

=== Moving IP address of the NFS share’s IP read only access list to read/write access list cannot be performed in one step ===

     If an IP address is already present on the NFS access list and you would like to move it to another access list, it has to be performed in two steps. First delete the IP address from the current list and apply the changes. Next edit the NFS share again and add the IP address to the other access list.

=== If the used space on zpool reaches more than 80%, the system may generate high load and become unstable ===

     If the used space on the zpool reaches more then 80%, the system is trying to utilize the available space to the maximum. As a result, the system load may increase, especially waiting I/O and cause its unstable work. Expanding the pool size space is recommended.

=== In certain situations WebGUI is not showing the current state of the system ===

     There are situations when the system is performing actions taking too long for the WebGUI to refresh the values in the web browser. In such a case the system is showing the old value taken directly from cache memory. We recommend using the F5 key to refresh the WebGUI.

=== An ongoing O&ODP process involving small zvol block size or dataset record size generate high load and render the system unstable ===

     O&ODP backup tasks involving small zvol block sizes as well as small dataset record sizes (4KB - 16KB) are known to generate very high load rendering the system unstable. We recommend using at least 64KB sizes for zvols and datasets.

=== Runtime UPS calibration in the client-server configuration unexpectedly shutdowns JovianDSS ===

     In the client-server configuration of the UPS, the runtime UPS calibration process returns an improper value interpreted by JovianDSS as being on battery. When it timeouts it shuts the system down.

=== Starting from up29 (including updating from previous version), system cannot boot up in UEFI mode if your boot medium is controlled by LSI SAS 9300 HBA with outdated firmware ===

     Make sure your LSI SAS 9300 HBA has the latest firmware installed. A quick workaround is changing the booting mode from UEFI to Legacy.

=== Bonded Mellanox network cards show negative values on the network usage chart ===

     This issue will be solved in the future release.

=== In case of hundreds of thousands of LDAP users system starts very slowly ===

     LDAP database is stored on the boot medium. If you have that large LDAP database we recommend using ultra fast NVMe disk for boot medium.

=== After update to JovianDSS up29 write back cache on some hardware RAID volumes can be unintentionally disabled ===

     Starting from JovianDSS up29 we disable write-back cache on all HDD disks by default, but we do not disable write-back cache on SSD drives and hardware RAID volumes. It can happen however that the write-back cache on some RAID volumes can be turned off. Hardware RAID volume performance can be heavily impacted by the lack of the write-back cache, so please make sure it's enabled after update. Open TUI and invoke Extended tools by pressing CTRL+ALT+t, then select Disk write-back cache settings.

=== Restarting or disconnecting JBOD with the write-back cache enabled on disks can lead to the data inconsistency ===

     If write-back cache is enabled on disks in JBOD then restarting or disconnecting JBOD can lead to data inconsistency. Starting from Jovian up29 we disable write-back cache on HDD disks by default during bootup procedure. We do not disable write-back cache on SSD drives and hardware RAID volumes.

=== Snapshots are not displayed after a system reboot if there are more than a few thousands of snapshots ===

     In case there is a large number of snapshots (more than a few thousands) there might be a significant delay in listing them in WebGUI after a system reboot. Depending on how big the number of snapshots is, it may take a few minutes or up to several dozen minutes to populate the list in WebGUI.

=== It is not recommended to use the gzip-9 compression algorithm. ===

     In case of using the gzip-9 compression algorithm the system can behave unstable when copying the data to storage. It is possible to use this compression algorithm only in environments where very efficient processors are being used.

=== It is not recommended to use more than 500 zvols. ===

     In case of using more than 500 zvols in the system, the responsiveness of the Web-GUI may be low and the system may have problems with the import of zpools.

=== It is recommended to use Fibre Channel groups in Fibre Channel Target HA Cluster environments that use the Fibre Channel switches. ===

     In case of using the Fibre Channel switches in FC Target HA Cluster environments, it is recommended to use only Fibre Channel groups (using the Fibre Channel Public group it is not recommended).

=== Manual export and import of zpool in the system or deactivation of the Fibre Channel group without first suspending or turning off the virtual machines on the VMware ESXi side may cause loss of access to the data by VMware ESXi. ===

     Before a manual export and import of a zpool in the system or deactivation of the Fibre Channel group in Fibre Channel Target HA Cluster environment, you must suspend or turn off the virtual machines on the VMware ESXi side. Otherwise, the VMware ESXi may lose access to the data, and restarting it will be necessary.

=== In Fibre Channel Target HA Cluster environments the VMware ESXi 6.7 must be used instead of VMware ESXi 7.0. ===

     In case of using the VMware ESXi 7.0 in Fibre Channel Target HA Cluster environment, restarting one of the cluster nodes may cause the Fibre Channel paths to report a dead state.

=== Sometimes cluster nodes hang up during boot of Open-E JovianDSS. ===

     In case one of the cluster nodes hangs up during Open-E JovianDSS boot, it must be manually restarted.

=== Sometimes when using the ipmi hardware solutions, the cluster node may be restarted again by the ipmi watchdog ===

     In this case, it is recommended to wait 5 minutes before turning on the cluster node after it was turned off.

=== Sometimes restarting one of the cluster nodes may cause some disks to be missing in the zpool configuration. ===

     In this case, click the “Rescan storage” button on the WebGUI to solve this problem.

=== The Internet Connection Check functionality has been removed. ===

     In order to check the internet connection, try to get the date and time from the NTP server using the Web-GUI (System Settings -> System -> Time and date settings).

=== After upgrading the system to a newer version, the event viewer reported an error message: An unexpected system reboot occurred. ===

     After upgrading the system to a newer version, the event viewer reported an error message: "An unexpected system reboot occurred. Run the 'Scrub scanner' on all pools to check the system integrity. Analysis of logs and previous events can help to find the cause of this problem and prevent the issue in the future. For more information, refer to the help article.". This information should be ignored.

=== Self-Encrypting Drives (SED) feature is supported for only specific devices. ===

     At this moment the Self-Encrypting Drives (SED) functionality is only supported for Samsung PM1643a devices only.

[[Category:Release Notes]]

Delete zpool

2022-02-21T15:49:23Z

Ma-W: Created page with "This functionality is available in: Storage > Pool > Options This option allows you to delete a zpool. The whole structure will be unmounted and then deleted. Note that all d..."

This functionality is available in: Storage > Pool > Options

This option allows you to delete a zpool. The whole structure will be unmounted and then deleted. Note that all data will be lost from the selected zpool. To delete a zpool:

#Go to the Storage section.
#Go to the Pool subsection.
#Click the '''Options''' button.
#Click '''Delete Zpool'''.
#Enter the word "delete".
#Click the '''Delete''' button.

You can also clean metadata from cache using Text-based User Interface (TUI). To do so:

#Activate TUI.
#Press '''Ctrl''' + '''Alt''' + '''X'''.
#In the window that appears, click '''Yes'''.
#In the window that appears, enter administrator password.
#Select '''Remove ZFS data structures and disks partitions'''.
#Choose '''Select'''.
#Press '''Enter'''.
#In the window that appears, enter administrator password.
#Select disks to clear from the list.
#Choose '''OK'''.
#Press '''Enter'''.

[[Category:Help topics]]

Main Page

2021-04-12T11:30:29Z

Ma-W:

'''''Release Notes:''''' {{
#tag:DynamicPageList|
category = Release Notes
ordermethod = categorysortkey
order = descending
}}

----

'''''Help topics:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = Help topics
count=40
ordermethod = categorysortkey
order = ascending
}}

|
{{
#tag:DynamicPageList|
category = Help topics
offset = 40
count= 40
ordermethod = categorysortkey
order = ascending
}}

| style="vertical-align: top" |
{{
#tag:DynamicPageList|
category = Help topics
offset = 80
count=40
ordermethod = categorysortkey
order = ascending
}}

|}

----

'''''ZFS and data storage articles:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = ZFS and data storage articles
count=60
ordermethod = sortkey
order = ascending
}}

|}

----

'''''Video tutorials:'''''

'''''<span style="color:#696969"><span><span>Open-E JovianDSS Video Tutorials</span></span></span>''''' {{
#tag:DynamicPageList|
category = Open-E JovianDSS Video Tutorials
ordermethod = sortkey
order = ascending }}<br/>''<span style="color:#696969"><span><span><span style="color:#696969">'''<span>Setting up a Failover service for Open-E JovianDSS</span>'''</span></span></span></span>'' {{
#tag:DynamicPageList|
category = Setting up a Failover service for Open-E JovianDSS
ordermethod = sortkey
order = ascending
}}

SNMP settings

2021-03-08T14:16:27Z

Ma-W:

This function enables you to configure access over the '''SNMP''' protocol in versions 2 or 3.

With SNMP enabled, you receive a wealth of information (CPU usage, system load, memory info, ethernet traffic, running processes).<br/>System location and system contact are only for your information.  For example, when you connect from an SNMP client, you will see your location and name.

SNMP, version 3 has an encrypted transmission feature as well as authentication by username and password.<br/>SNMP, version 2 does not have encrypted transmission, and authentication is done only via the community string.

The community string you set can contain up to 20 characters, while the password needs to have at least 8 characters.

Links to SNMP clients:

:<span style="font-size:larger">[http://www.muonics.com http://www.muonics.com] </span><br/>
:<span style="font-size:larger">[http://www.mg-soft.com http://www.mg-soft.com] </span>
:<span style="font-size:larger">[http://www.manageengine.com http://www.manageengine.com]</span>

{{Note|
Our storage system supports the SNMP protocol in MIB-II standard.  List of MIBs:

*- mib-2.host

*- mib-2.ip

*- mib-2.tcp

*- mib-2.udp

*- mib-2.interfaces

*- mib-2.at

*- system
}}

JovianDSS offers additional SNMP values to monitor Pool and ZFS attributes.<br/>It is necessary to query specific OIDs in order to receive those attributes.

For basic ZFS parameters NYMNETWORKS-MIB mib is included [[:Media:NYMNETWORKS-MIB.txt|NYMNETWORKS-MIB]]

<br/>snmpwalk -v 2c -m NYMNETWORKS-MIB -c community 192.168.251.79 .1.3.6.1.4.1.25359.1<br/>NYMNETWORKS-MIB::zfsFilesystemName.1 = STRING: "Pool-0"<br/>NYMNETWORKS-MIB::zfsFilesystemName.2 = STRING: "Pool-1"<br/>NYMNETWORKS-MIB::zfsFilesystemAvailableKB.1 = Gauge32: 15861464<br/>NYMNETWORKS-MIB::zfsFilesystemAvailableKB.2 = Gauge32: 15861672<br/>NYMNETWORKS-MIB::zfsFilesystemUsedKB.1 = Gauge32: 4327720<br/>NYMNETWORKS-MIB::zfsFilesystemUsedKB.2 = Gauge32: 4327512<br/>NYMNETWORKS-MIB::zfsPoolHealth.1 = INTEGER: online(1)<br/>NYMNETWORKS-MIB::zfsPoolHealth.2 = INTEGER: online(1)<br/>NYMNETWORKS-MIB::zfsFilesystemSizeKB.1 = Wrong Type (should be INTEGER): Gauge32: 20189184<br/>NYMNETWORKS-MIB::zfsFilesystemSizeKB.2 = Wrong Type (should be INTEGER): Gauge32: 20189184<br/>NYMNETWORKS-MIB::zfsFilesystemAvailableMB.1 = Gauge32: 15489<br/>NYMNETWORKS-MIB::zfsFilesystemAvailableMB.2 = Gauge32: 15489<br/>NYMNETWORKS-MIB::zfsFilesystemUsedMB.1 = Gauge32: 4226<br/>NYMNETWORKS-MIB::zfsFilesystemUsedMB.2 = Gauge32: 4226<br/>NYMNETWORKS-MIB::zfsFilesystemSizeMB.1 = Gauge32: 19716<br/>NYMNETWORKS-MIB::zfsFilesystemSizeMB.2 = Gauge32: 19716<br/>NYMNETWORKS-MIB::zfsARCSizeKB.0 = Gauge32: 61086<br/>NYMNETWORKS-MIB::zfsARCMetadataSizeKB.0 = Gauge32: 9278<br/>NYMNETWORKS-MIB::zfsARCDataSizeKB.0 = Gauge32: 51808<br/>NYMNETWORKS-MIB::zfsARCHits.0 = Counter32: 229308<br/>NYMNETWORKS-MIB::zfsARCMisses.0 = Counter32: 41260<br/>NYMNETWORKS-MIB::zfsARCTargetSize.0 = Gauge32: 64287<br/>NYMNETWORKS-MIB::zfsARCMru.0 = Gauge32: 59529<br/>NYMNETWORKS-MIB::zfsL2ARCHits.0 = Counter32: 0<br/>NYMNETWORKS-MIB::zfsL2ARCMisses.0 = Counter32: 0<br/>NYMNETWORKS-MIB::zfsL2ARCReads.0 = Counter32: 0<br/>NYMNETWORKS-MIB::zfsL2ARCWrites.0 = Counter32: 0

Additional information, like compression ratio, deduplication ratio, available space (in bytes), age (in seconds) of latest snapshot on volume,<br/>can be obtained with standard NET-SNMP-EXTEND-MIB:

'''Examples:'''<br/><br/>NET-SNMP-EXTEND-MIB::nsExtendOutputFull."deduplication" = STRING:

"deduplication Pool-0 1.00"<br/><br/>NET-SNMP-EXTEND-MIB::nsExtendOutputFull."compression" = STRING:

"compression Pool-0/vol00 1.01<br/>compression Pool-0/clone-vol00 1.00"

NET-SNMP-EXTEND-MIB::nsExtendOutputFull."volumes_list" = STRING:<br/><br/>"available Pool-0/vol00 11981377536<br/>available Pool-0/clone-vol00 11981377536"

NET-SNMP-EXTEND-MIB::nsExtendOutputFull."snapshots_age" = STRING:<br/><br/>"snapshot_age Pool-0/vol00 3<br/>snapshot_age Pool-0/vol01 371"

'''Untranslated OIDs:'''<br/><br/>root@p-GA-880GM-USB3:/home/p# snmpwalk -v2c -c public 192.168.0.80  1.3.6.1.4.1.8072.1.3.2.3<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.1.11.99.111.109.112.114.101.115.115.105.111.110 = STRING: "compression Pool-0/vol00 1.01"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.1.12.115.110.97.112.115.104.111.116.95.97.103.101 = STRING: "snapshot_age Pool-0/vol00 3"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.1.12.118.111.108.117.109.101.115.95.108.105.115.116 = STRING: "available Pool-0/vol00 11981377536"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.1.13.100.101.100.117.112.108.105.99.97.116.105.111.110 = STRING: "deduplication Pool-0 1.00"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.2.11.99.111.109.112.114.101.115.115.105.111.110 = STRING: "compression Pool-0/vol00 1.01<br/>compression Pool-0/clone-vol00 1.00"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.2.12.115.110.97.112.115.104.111.116.95.97.103.101 = STRING: "snapshot_age Pool-0/vol00 3<br/>snapshot_age Pool-0/vol01 371"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.2.12.118.111.108.117.109.101.115.95.108.105.115.116 = STRING: "available Pool-0/vol00 11981377536<br/>available Pool-0/clone-vol00 11981377536"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.2.13.100.101.100.117.112.108.105.99.97.116.105.111.110 = STRING: "deduplication Pool-0 1.00"

[[Category:Help topics]]

File:NYMNETWORKS-MIB.txt

2021-03-08T13:25:53Z

Ma-W:

Open-E JovianDSS ver.1.0 up28 Release Notes

2020-11-17T10:52:51Z

Ma-W:

'''Release date: 2020-01-28'''

'''Build: 37311'''

'''For build 38496 go to: [http://wiki.open-e.com/default/wiki/Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes]'''

{| class="cke_show_border cke_show_border"
|-
| __TOC__

|}

== New ==

=== HA Cluster Ring can be configured as two single connections ===

=== HA cluster Ping-nodes can be configured within any available interfaces and subnetworks ===

=== Static routing configuration is available in Web-GUI ===

=== Custom SSL/TLS certificates can be manually imported in Web-GUI ===

=== ZFS Datasets can get a record size value from range of 4KiB up to 16MiB (default record size value is 1MiB) ===

=== Fibre Channel Target mode is available for ATTO Fiber Channel Adapter (supported only with VMware client) ===

=== Improved performance of LDAP database replication mechanism ===

=== Storage performance test tool is available in TUI (System console -> Ctrl+Alt+t -> Add-ons -> Storage performance tool) ===

=== HPE tools for managing HP Smart Array controllers are available in Web-GUI and TUI ===

=== MacOS Spotlight search support allows to quickly locate the files and search through their contents ===

=== Installer creates 128GB boot medium partition size (more space for further upgrade processes) ===

=== New filtering options for Event Viewer (selection by: error, warning, information and the date ranges) ===

=== Kdump (kernel crash dumping mechanism) ===

=== The default SCSI ID for iSCSI and FC luns can be manually set in Web-GUI ===

=== Deduplication statistics for zpool are available in Web-GUI ===

=== Ethernet cards detailed statistics (amount of data sent and received) are available in the system logs ===

=== Statistics for MPIO devices are displayed in GUI (Diagnostics -> Disk usage) ===

=== Linux iostat and S.M.A.R.T data are available in Checkmk monitoring system ===

== Updated ==

=== Samba 4.9.4 ===

=== Mellanox ConnectX-3 driver (mlx4_core, v4.4-2.0.7) ===

=== Mellanox ConnectX-4/5 driver (mlx5_core, v4.4-2.0.7) ===

=== Intel 10/40GbE driver i40e (i40e, v2.9.21) ===

=== Broadcom BCM5706/5708/5709/5716 driver (bnx2, v2.2.5x) ===

=== Broadcom BCM57710/57711/57711E/57712/57712_MF/57800/57800_MF/57810/57810_MF/57840/57840_MF driver (bnx2x, v.1.715.0) ===

=== ATTO Celerity 16Gb/32Gb Fibre Channel Adapter driver (celerity16fc, v1.76.0f1) ===

=== Microsemi Adaptec RAID and HBA driver (aacraid, v1.2.1.57013src) ===

=== Microsemi Adaptec SmartRAID and SmartHBA driver (smartpqi, v1.2.6-015) ===

=== Broadcom MegaRAID SAS Driver (megaraid_sas, v07.709.08.00) ===

=== Microsemi Adaptec MaxView tool (v3.02-23600) ===

=== Areca SAS/SATA RAID Controller Driver (arcmsr, v1.40.0X.10-20181227) ===

=== Smartmontools 7.0 ===

=== VMware tools v10.3.10.10540 ===

=== Page cache for zvol File I/O mode is reduced to 50% ===

== Fixed ==

=== RSS does not check if gateway is set up and if RSS server is available ===

=== System activation on XEN VSA does not work ===

=== Cannot use XEN drives for Metro Cluster in XEN VSA ===

=== Zvol configured as a destination in OODP still can be set as a LUN for target ===

=== Dataset configured as a destination in OODP still can be used as a location for a Share ===

=== VMware VCenter/VSphere snapshot autoremove mechanism deletes all ESX snapshots ===

=== Listing of OODP snapshots lasts very long ===

=== activation.xml is cleaned while activation server was unavailable e.g. because of firewall settings ===

=== System restart in watchdog for processes which works more than 300 sec. ===

=== Problems with ssh and jumboframes (MTU) ===

=== The SIDs are not mapped to usernames and groups for shares in Windows (fixed for new JovianDSS installations only) ===

=== Unstable working of Intel X710/XL710 and Intel X722 network cards configured as LACP or Balance Round Robin bonding mode ===

== Important notes for JovianDSS HA configuration ==

=== It is necessary to use sync always option for zvols and datasets in cluster  ===

=== It is strongly recommended not to use more than eight ping nodes ===

=== It is strongly recommended to configure each IP address in separate subnetwork ===

=== It is necessary to run Scrub scanner after failover action triggered by power failure (dirty system close) ===

=== It is strongly recommended to use UPS unit for each cluster node ===

=== It is necessary to use static discovery in all iSCSI initiators ===

=== It is strongly not recommended to change any settings when both nodes do not have the same JovianDSS version, for example during software updating ===

=== It is necessary to use different Server names for cluster nodes ===

=== HA cluster does not work properly with Infiniband controllers ===

=== HA cluster does not work stable with ALB bonding mode ===

=== FC Target HA cluster does not support Persistant Reservation Synchronization and it cannot be used as a storage for Microsoft Hyper-V cluster. This problem will be solved in future releases. ===

=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===
<p style="text-align: justify"><span class="toctext">    You can find details below:</span></p><p style="text-align: justify"><span class="toctext">    [https://kb.open-e.com/index.php?View=entry&EntryID=3101 https://kb.open-e.com/index.php?View=entry&EntryID=3101]</span></p><p style="text-align: justify"><span class="toctext">    *Please consult Broadcom vendor for specific firmware that is suitable for your hardware setup.</span></p>
== Performance tuning ==

=== iSCSI Target with VMware ESX performance tuning ===

     In case of low iSCSI Target performance with VMware ESX, a few parameters need to be changed in VMware ESX iSCSI Initiator. Go to Storage Adapters -> iSCSI Software Adapter -> Advanced Options and the change the following settings:
<pre>
MaxOutstandingR2T change the default 1 to 8

FirstBurstLength change the default 262144 to 65536

MaxBurstLength change the default 262144 to 1048576

MaxRecvDataSegLen change the default 131072 to 1048576
</pre>
=== Write cache sync requests performance tuning ===

     Write cache sync requests (sync) set to “always” for zvol is the safest option and is set by default. However, it can cause write performance decreases since all operations are written and flushed directly to the persistent storage. In case of using sync=always, it is strongly recommended using mirrored write log devices (very fast random writes devices).<br/>     Sync=standard or sync=disabled zvol options provide huge performance improvement but the most recent (up to 5 seconds) cached data can be lost in case of a sudden power failure. Use this option only in environments equipped with UPS.<br/>     For NFS shares the Synchronous data record is enabled by default. This option causes performance to be worse, but data can be safely written. In order to improve the NFS performance you can use Asynchronous data record but in such case, it is strongly recommended to use UPS.

== Known issues ==

=== Browser recommendations ===

     It is strongly recommended to use Mozilla Firefox browser to navigate the system’s GUI. When using other browsers some slight problems with displaying content may occur.

=== Web browser’s cache ===

     After updating from previous versions, some problems with WebGUI content and navigation may occur. To resolve this problems, please clear Web browser cache.

=== System as a guest in virtual environments ===

     Hyper-V:<br/>     In case of installing the system as a Hyper-V guest please use the following settings:<br/>       - Number of virtual processors: 4<br/>       - Memory: Minimum 8GB<br/>       - Boot Disk: 20GB IDE Disk<br/>       - Add at least 6 virtual disk

 <br/>     VMware ESXi:<br/>     In case of installing the system as a VMware ESXi guest please use the following settings:<br/>       - Guest OS: Other 2.6.x Linux ( 64bit )<br/>       - Number of Cores: 4<br/>       - Memory: Minimum 8GB<br/>       - Network Adapter: VMXNET 3<br/>       - SCSI Controller Type: Paravirtual or LSI Logic SAS<br/>       - Boot Disk : 20GB Thick Provision Eager Zeroed<br/>       - Add at least 6 virtual disk<br/>       - Edit Settings->Options->Advanced-General->Configuration-> Add row: disk.EnableUUID : TRUE

=== Reclaim deleted blocks on thin-provisioned LUNs in various systems ===

     In case of deleting large amounts of data, reclaimed deleted blocks on thin-provisioned LUNs in Windows 2012 can significantly slow down system performance. If you predict frequent deletions of large amounts of data, we recommend turning off the automatic reclaim function in Windows 2012. This can be done by disabling the "file-delete notification" feature in the system registry. To do so, follow the steps below:<br/>       - start Registry Editor.<br/>       - locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem       <br/>       - double-click DisableDeleteNotification.<br/>       - in the Value data box, enter a value of 1, and then click OK.<br/> <br/>     In order to reclaim the free space in Windows 2012 please change the    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\DisableDeleteNotification key value back to 0 and use "Optimize" tool located in Disc Management->[disk]->Properties->Tools. As the operation can generate a very high load in the system, it is recommended to perform it after-hours.  <br/>In case of VMware ESXi, the automatic reclaim feature is disabled by default. To reclaim the space of deleted blocks on thin-provisioned LUNs, please use vmkfstools. For details, please refer to the VMware Knowledge Base:

For VMware ESXi 5.0: [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849]<br/>For VMware ESXi 5.5 and newer: [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513 https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513]<br/>For VMware ESXi 6.7 and newer: search in Internet for “Space Reclamation Requests from VMFS Datastores” and read vendor documentation.

In case of using Windows 2008 there is no possibility to reclaim the space released by deleted data of thin-provisioned LUNs.

=== Deduplication issues and recommendations ===

     Please be aware that deleting the zvol with deduplication enabled can generate a very high load in the system and lead to unstable behavior. It is strongly recommended to perform such operation only after-hours. To avoid this issue, please use (if possible) single zvol on zpools dedicated for deduplication and delete the zpool which includes the single zvol.<br/>   <br/>     To determine the amount of System RAM required for deduplication, use this formula:<br/> <br/>                                                                                                                    (Size of Zvol / Volume block size) * 320B / 0.75 / 0.25<br/> <br/>Where:<br/>320B - is the size of entry in DDT table<br/>0.75 - Percentage of RAM reservation for ARC (75%)<br/>0.25 - Percentage of DDT reservation in ARC (25%)<br/> <br/>     Example for 1TB data and 64KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 65536B) * 320B / 0.75 / 0.25 = 28633115306.67B<br/>                                                                                                                       28633115306.67B / 1024 / 1024 / 1024 = 26.67GB<br/> <br/>so for every extra 1TB of storage, system needs extra 26.67GB RAM.<br/><br/>     Example for 1TB data and 128KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 131072B) * 320B / 0.75 / 0.25 = 14316557653.33B<br/>                                                                                                                        14316557653.33B / 1024 / 1024 / 1024 = 13.33GB<br/> <br/>so for every extra 1TB of storage, system needs extra 13.33GB RAM.
<div><br/></div><div>     Example for 1TB data and 1MB Volume block size:</div><div><br/></div><div>                                                                                                      (1099511627776B / 1048576B) * 320B / 0.75 / 0.25 = 1789569706,66B</div><div>                                                                                                                        1789569706,66B / 1024 / 1024 / 1024 = 1.66GB</div><div> </div><div>     so for every extra 1TB of storage, system needs extra 1.66GB RAM.</div><div><br/></div>
<br/>'''IMPORTANT: '''The above calculations only apply to the worst case scenario, when data is completely unique and will not be deduplicated. For the deduplicable data, the need for RAM drastically decreases. If SSD based Read Cache is present, part of deduplication table will be moved to the SSD and deduplication will work with good performance using less RAM.

<br/>'''IMPORTANT: '''With SAN (iSCSI) it is CRITICAL to match User-File-System format block size with the zvol volume-block-size. A simple example is a Windows file system NTFS with default format block size 4k and zvol default volume-block-size is 128k. With defaults like this deduplication will mostly NOT match because files can be aligned in 32 (128/4) different positions on the pool. If the NTFS format is increased to 64k and the zvol default volume-block-size is 128k, deduplication match can fail only one time because a file can be aligned to 2 (128/64) different positions on the pool. Every next write will match already as both alignment options already exist on the pool. In order to achieve all files matching and efficient memory usage NTFS must use 64k format block size and the zvol volume-block-size must equal 64k. Another option is that the NTFS=32k and zvol=32k, but in this case the deduplication table will be twice as large. That is why the NTFS=64k and zvol=64k is the most efficient setting for deduplication.

'''IMPORTANT: '''With NAS (NFS, SMB/CIFs) deduplication matching works always due to the data blocks being aligned by ZFS natively.

'''IMPORTANT: '''De-duplication is working on the pool level in the pool-range. This is why zvol-Physical size cannot show de-duplication benefit. In order to prove that deduplication saved space run the scrub and notice the current physical data space on the pool reported by the scrub. Next copy of new data and run the scrub again. Now scrub will show new physical data space. Comparing the data size from storage client side with the data space growth from the scrub will give the deduplication advantage. The exact pool of the deduplication ratio can be found in LOGs in zfs.log.

=== Zvols configuration issues and recommendations ===

     It is strongly recommended to set the client file system block size same as the zvol volume block size. For example, when using 64k zvol volume block size, the Windows Allocation unit size of NTFS should be set to 64k.

=== Target number limit ===

    In case of more than 60 targets, GUI will not be displayed correctly. This issue will be fixed in the next releases.

=== Targets with the same name are not assigned correctly ===

    Having two or more targets with the same name but belonging to various Zpools, will cause that all targets with the same name will be assigned to one Zpool during the import process.

=== Installation on disks containing LVM metadata ===

     There is no possibility to install the system on disks containing LVM metadata. You will need to clear those disks before installation. To do so, use the “Remove ZFS data structures and disks partitions” function located in the Extended tools. To access this function, boot the system from a temporary media like a USB drive or DVD.

=== Import Zpool with broken write log ===

     There is no option to import Zpool with a broken write log disk using the system’s functions. This is why it is STRONGLY recommended to use mirrored disks for write logs. In case it is necessary to import Zpool with a broken write log, please contact technical support.

=== Replacing disks in data groups for larger ones can cause your storage license capacity to be exceeded ===

     In case of replacing damaged disks for larger ones, the size of the entire Zpool will increased. Make sure that the new size will not exceed your purchased storage license.

=== Periodically after some operations, the GUI needs to be manually refreshed ===

     After performing some operations, e.g. resilvering, the GUI will show outdated information. In this case refresh the web page manually by pressing F5 on your keyboard. This issue will be fixed in next releases.

=== Replacing disks in data groups for smaller ones can cause an error and make the disk disappear from the list of available disks ===

     Operation of replacing a disk in a data group for a smaller one will cause an error "zpool unknown error, exit code 255", and the disk will become unavailable. In order to reuse this disk, please use function "Remove ZFS data structures and disks partitions" located in the Extended tools on the Console screen.

=== It is strongly recommended to use 64KB or higher Volume block size ===

     Smaller than 64KB block sizes used with deduplication or read cache will cause very high memory consumption.

=== RAM recommendations for Read Cache ===

     To determine how much System RAM is required for Read Cache, use the following formula:

<br/> <br/>                                                                      RAM needed = (Size of Read Cache - reserved size and labels) * bytes reserved by l2hdr structure / Volume block size<br/> 

     For 8KB Volume block size and 1TB Read Cache:<br/><br/>                                                                           RAM needed = (1099511627776B - 4718592B) * 432B / 8192B = 57981809664B<br/>                                                                                                        57981809664B / 1024 / 1024 / 1024 = 54GB<br/> <br/>Where:<br/>1099511627776B - 1TB Read Cache<br/>4718592B - reserved size and labels<br/>432B - bytes reserved by l2hdr structure<br/>8192B - Volume block size<br/> <br/>                                                                                                  For 64KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 65536B = 7247726208B<br/>                                                                                                       7247726208B / 1024 / 1024 /1024 = 6.75GB<br/><br/><br/>                                                                                                  For 128KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 131072B = 3623863104B<br/>                                                                                                       3623863104B / 1024 / 1024 /1024 = 3.37GB

=== Multiple GUI disk operations may result in an inaccurate available disks list ===

     Multiple operations of adding and detaching disks from groups can cause that the next operation of detaching will fail, but the disk will be shown on a list of available disks. When trying to add this disk to one group it will fail with the following error "[zfslib-wrap-zpool-ZpoolCmdError-1] invalid vdev specification". In this case, detach this disk once again.

=== After removing disks from groups they may not be displayed on a list of available disks ===

     Sometimes after removing disks from groups, Spare/Read Cache/Write Log disks are displayed on a list of unassigned disks, but they are not on a list of available disks. In this case, click the rescan button located in the adding group form.

=== Reusing disks from an exported and deleted Zpool ===

     After deleting an exported Zpool, not all disks which were a part of a Zpool become immediately available. Before you can reuse disks, which were previously used as a Spare or a Read Cache, you must first clean them. Use “Remove ZFS data structures and disks partitions” function located in the “Extended tools”.

=== Negotiated speed of network interfaces may not display correctly ===

     For some network interfaces, the negotiated speed field may display an incorrect value in GUI and Console. This issue will be fixed in next releases.

=== Limited possibility to display a large number of elements by the GUI ===

     After creating multiple snapshots, clones or zvols some forms in GUI work very slow. If you need to create many snapshots, clones or zvols, it is strongly recommended to use CLI in order to perform operations on them.

=== Open-E VSS Hardware Provider system recommendations ===

     It is strongly recommended to use Windows Server 2012. On the other Windows systems, Open-E VSS Hardware Provider Configuration works unstable.

=== Exceeded quota for dataset does not allow to remove files ===

     Files located on datasets with exceeded quota cannot be removed. In this case, please resize quota and then remove unnecessary files.

=== Slow WebGUI with multiple datagroups ===

     Zpool with more than 20 datagroups causes that some forms on WebGUI work very slow. If you need to create many datagroups, it is strongly recommended to use CLI API.

=== Slow WebGUI with multiple datasets ===

     More than 25 datasets cause that WebGUI works slow.

=== ZFS Upgrade ===

     For Open-E JovianDSS users, it is recommended to upgrade Zpools to the latest ZFS file system. Although the file system upgrade is absolutely safe for your data, and takes only few minutes, please be aware that this operation cannot be undone. In order to upgrade a single Zpool, please use "WebGUI -> Zpool options -> Upgrade file system" from Zpool's option menu.

=== Intel® Ethernet Controller XL710 Family ===

     In case of using Open-E JovianDSS with Intel® Ethernet Controller XL710 Family, it is necessary to update firmware’s network controller to the version: f4.33.31377 a1.2 n4.42 e1932.

=== Motherboards with x2APIC technology ===

     In case of using a motherboard with x2APIC technology enabled, it is necessary to disable x2APIC in BIOS. Otherwise, problems with CPU cores will occur.

=== NFS FSIDs and Zpool name ===

     One of the factors that have been taken into account when NFS FSIDs are generated is Zpool name. It indicates that when Zpool name is changed, e.g. during export and import with different names, FSIDs for NFS Shares located on this Zpool will also be changed.

=== High Availability shared storage cluster does not work with Infiniband controllers ===

     Due to technical reasons the High Availability shared storage cluster does not work properly when using the Infiniband controllers for VIP interface configuration. This limitation will be removed in the future releases.

=== Disks with LVM data cannot be used with the created Zpool ===

     Attempt to create Zpool with drives that contain LVM data will fail with the following error:

''"cannot open 'lvm-pv-uuid-R25lTS-kcDc-eiAN-eAlf-ppgi-rAqu-Oxy1Si': no such device in /dev must be a full path or shorthand device name"''

In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.

=== Unexpected long failover time, especially with HA-Cluster with two or more pools ===

     Current failover mechanism procedure is moving pools in sequence. Since up27 release, up to 3 pools are supported in HA-cluster. If all pools are active on single node and failover needs to move all 3 pools, the failover may take longer than 60 seconds which is a default iSCSI timeout in Hyper-V Clusters. In some environments, under heavy load a problem with too long time of cluster resources switching may occur as well. If the switching time exceeds the iSCSI initiator timeout, it is strongly recommended to increase the timeout up to 600 seconds.

     '''In case of using Windows, to increase iSCSI initiator timeout, please perform following steps:'''

1. Run regedit tool and find: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\...\Parameters\MaxRequestHoldTime registry key''

2. Change value of the key from default 60 sec to 600 sec (decimal)

     '''In case of using VMware, to increase iSCSI initiator timeout, please perform following steps:'''

1. Select the host in the vSphere Web Client navigator

2. Go to Settings in the Manage tab

3. Under System, select Advanced System Settings

4. Choose the ''Misc.APDTimeout'' attribute and click the Edit icon

5. Change value from default 140 to 600 sec.

     '''In case of using XenServer, to increase iSCSI initiator timeout, please perform following steps:'''

A. For existing Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Detach and reattach SRs. This will update the new iSCSI timeout settings for the existing SRs.

B. For new Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Create the new SR. New and existing SRs will be updated with the new iSCSI timeout settings.

=== Activation may be lost after update ===

     In some environments, after update to up11 system may require re-activation. This issue will be removed in the future releases.

=== Bonding ALB and Round-Robin do not work in Hyper-V and VMware environments ===

     In case of using JovianDSS as Hyper-V or VMware guest, bonding ALB and Round-Robin is not supported. Please use another type of bonding.

=== Continuous writing in VMware guest can cause that deleting VMware snapshot can take long time ===

     Using ODPS on zvol/dataset with VMware guest where many I/O operations are performed can cause that the process of deleting VMware snapshot can take long time. Please take this into consideration while you set up the scheduler for Off-site Data Protection Service task.

=== Enabling quota on dataset can cause file transfer interrupt ===

     Enabling quota functionality on a dataset can cause file transfer interrupt. Before using it in production environment, please enable quota on dataset, or make sure that no file transfers are active.

=== Nodes connected to the same AD server must have unique Server names ===

     If JovianDSS nodes are connected to the same AD server, they cannot have the same Server names.

=== Share can not be named the same as Zpool ===

     In case of share with the same name as Pool connections problem will occur. Please use different names.

=== No persistent rules for network cards in virtual environment ===

     Changing settings of virtual network cards (delete, changing MAC, etc.) can cause unstable system behaviour. Please do not change settings on production system. This issue will be fixed in next releases.

=== Downgrade to up17 or earlier is not possible ===

     Starting from up18 bootable medium has always SW RAID structure. Attempt to come back to earlier version is impossible. If you need come back to earlier version, you must reinstall version again.

=== System cannot be installed on cciss based controllers ===

     This issue will be fixed in next releases.

=== Interrupt the process of adding second disk to SW RAID (bootable medium) can cause run system from disk with uncompleted data ===

     Performing operation like: reboot, shutdown, power off, etc. during mirroring data on new added disk can cause that system will be booted from new disk which has incomplete data. In this case, SW RAID function shows empty status and wrong number of RAID members. To resolve this issue, please plug off disk which has incomplete data, boot system, plug in disk and add it once again to SW RAID.

=== SAS-MPIO cannot be used with Cluster over Ethernet ===

     It is strongly not recommended to use Cluster over Ethernet with SAS-MPIO functionality. Such a configuration can lead to a very unstable cluster behavior.

=== On- & Off-site Data Protection backward compatibility problem ===

     In case of using On- & Off-site Data Protection functionality in up21 or earlier, it is strongly recommended to remove all backup tasks created by CLI API and re-create it using GUI.

=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===

     In FC Target HA environment, power cycle of both nodes simultaneously may lead to a situation when VMware is not able to restore proper state of the storage devices. In vSphere GUI LUNs are displayed as Error, Unknown or Normal,Degraded. Moving affected pools to another node and back to its native node should bring LUNs back to normal. A number two option is to restart the Failover in Jovian’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.

=== Problem with maintenance in case of disk failure ===

     In case of disk failure, please remove the damaged disks from the system, before starting administrative work to replace the disk. The order of actions is important.

=== Separated mode after update from JovianDSS up24 to JovianDSS up25 ===

     In HA cluster environment after updating of one node from JovianDSS up24 to JovianDSS up25 the other node can fall into separated mode and the mirror path might indicate disconnected status. In such a case go to Failover Settings and in the Failover status section select Stop Failover on both nodes. Once this operation is finished select Start Failover.

=== Different Write Cache default setting for zvols in early beta versions of Jovian DSS up25 ===

     In the early beta versions of JovianDSS up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of Jovian up25 the Log bias is set to “Write log device (Latency)”.<br/>Please note, that “In Pool (Throughput)” setting may cause a drop in performance in environments with a lot of random access workloads which is a common factor for a majority of production environments.

=== Target alias name is required while configuring HA FC Target in case of adding two or more ports to one FC group ===

     If we want to have more then one port in each FC group (in HA FC configuration) it is necessary to type in Target alias name for every port. Otherwise an error message “Target alias is already used” can show up while setting up remote port mapping for FC targets in (pool name) -> Fibre Channel -> Targets and initiators assigned to this zpool. This issue will be resolved in the future release.

=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===

     In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of Jovian up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open Jovian TUI and use CTRL+ALT+W key combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select qla2xxx_scst QLogic Fibre Channel HBA Driver and make sure the value of this parameter is set to “exclusive”.<br/><br/>Please note that in order to change this parameter Failover must be stopped first.

=== Very low performance of FIO/WT in case of mixed FIO/WT and FIO/WB zvol configurations over Fiber Channel ===

     In case of the mixed FIO/WT and FIO/WB zvol configurations over FC one can observe significantly decreased performance on FIO/WT.

=== More than one zvol with FIO/WB mode can cause instability of the Fiber Channel connection ===

     If there's more than one FIO/WB zvol or a FIO/WB zvol is coexisting with other types of zvols it can cause an instability of the FC connection with client machines. As a result client machines may unexpectedly lose FC connected resources.

=== In certain situations system page cache is not able to flush File I/O errors by itself and cache flushing has to be performed manually ===

     Under certain conditions (like overfilling zvol and then expanding its size) some File I/O errors may be held by the system page cache and it requires manual flushing (in GUI use Storage -> Rescan).

=== Updating nodes of the Jovian cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===

     There is a significant difference in FC configurations in up24 and earlier versions. Those versions allowed the FC ports to be configured in initiator mode only, while later versions allow both target and initiator mode with target as default, so in case of using storage connected via FC initiator, FC port(s) must be manually corrected in GUI of the updated node.

=== Updating Metro Cluster node with NVMe disks as read cache from JovianDSS up26 or earlier can cause the system to lose access to the NVMe disks ===

     The process of updating of Metro Cluster node from JovianDSS up26 or earlier is changing NVME disk IDs. In consequence moving pool back to updated node is possible but the read cache is gone (ID mismatch). In order to bring read cache back to the pool we recommend to use console tools in the following way: press Ctrl+Alt+x -> “Remove ZFS data structures and disks partitions”, locate and select the missing NVMe disk and press OK to remove all ZFS metadata on the disk. After this operation click Rescan button in GUI -> Storage. The missing NVMe disk should now appear in Unassigned disks at the bottom of the page which allows to select that disk in pool’s Disk group’s tab. Open Disk group tab of the pool, press the Add group button and select Add read cache. The missing disk should now be available to select it as a read cache.

=== Synchronization of a large LDAP database can last for a long time (e.g. 10h for 380K users) and can be associated with high system load ===

     This problem will be solved in future releases.

=== Long time of a failover procedure in case of Xen client with iSCSI MPIO configuration ===

     In a scenario where Xen client is an iSCSI initiator in MPIO configuration, the power-off of one node starts the failover procedure that takes a very long time. Pool is finally moved successfully but there are many errors showing up in dmesg in meantime. In case of such an environment we recommend to add the following entry in the device section of the configuration file: /etc/multipath.conf:

'''no_path_retry queue'''

<br/>The structure of the device section should look as follows:
<pre>device {
vendor "SCST_FIO|SCST_BIO"
product "*"
path_selector "round-robin 0"
path_grouping_policy multibus
rr_min_rio 100
no_path_retry queue
}
</pre>
[[Category:Release Notes]]

Open-E JovianDSS ver.1.0 up28 Release Notes

2020-11-17T10:50:48Z

Ma-W:

'''Release date: 2020-01-28'''

'''Build: 37311'''

'''For build 38496 go to: [Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes [http://wiki.open-e.com/default/wiki/Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes http://wiki.open-e.com/default/wiki/Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes]]'''

{| class="cke_show_border cke_show_border"
|-
| __TOC__

|}

== New ==

=== HA Cluster Ring can be configured as two single connections ===

=== HA cluster Ping-nodes can be configured within any available interfaces and subnetworks ===

=== Static routing configuration is available in Web-GUI ===

=== Custom SSL/TLS certificates can be manually imported in Web-GUI ===

=== ZFS Datasets can get a record size value from range of 4KiB up to 16MiB (default record size value is 1MiB) ===

=== Fibre Channel Target mode is available for ATTO Fiber Channel Adapter (supported only with VMware client) ===

=== Improved performance of LDAP database replication mechanism ===

=== Storage performance test tool is available in TUI (System console -> Ctrl+Alt+t -> Add-ons -> Storage performance tool) ===

=== HPE tools for managing HP Smart Array controllers are available in Web-GUI and TUI ===

=== MacOS Spotlight search support allows to quickly locate the files and search through their contents ===

=== Installer creates 128GB boot medium partition size (more space for further upgrade processes) ===

=== New filtering options for Event Viewer (selection by: error, warning, information and the date ranges) ===

=== Kdump (kernel crash dumping mechanism) ===

=== The default SCSI ID for iSCSI and FC luns can be manually set in Web-GUI ===

=== Deduplication statistics for zpool are available in Web-GUI ===

=== Ethernet cards detailed statistics (amount of data sent and received) are available in the system logs ===

=== Statistics for MPIO devices are displayed in GUI (Diagnostics -> Disk usage) ===

=== Linux iostat and S.M.A.R.T data are available in Checkmk monitoring system ===

== Updated ==

=== Samba 4.9.4 ===

=== Mellanox ConnectX-3 driver (mlx4_core, v4.4-2.0.7) ===

=== Mellanox ConnectX-4/5 driver (mlx5_core, v4.4-2.0.7) ===

=== Intel 10/40GbE driver i40e (i40e, v2.9.21) ===

=== Broadcom BCM5706/5708/5709/5716 driver (bnx2, v2.2.5x) ===

=== Broadcom BCM57710/57711/57711E/57712/57712_MF/57800/57800_MF/57810/57810_MF/57840/57840_MF driver (bnx2x, v.1.715.0) ===

=== ATTO Celerity 16Gb/32Gb Fibre Channel Adapter driver (celerity16fc, v1.76.0f1) ===

=== Microsemi Adaptec RAID and HBA driver (aacraid, v1.2.1.57013src) ===

=== Microsemi Adaptec SmartRAID and SmartHBA driver (smartpqi, v1.2.6-015) ===

=== Broadcom MegaRAID SAS Driver (megaraid_sas, v07.709.08.00) ===

=== Microsemi Adaptec MaxView tool (v3.02-23600) ===

=== Areca SAS/SATA RAID Controller Driver (arcmsr, v1.40.0X.10-20181227) ===

=== Smartmontools 7.0 ===

=== VMware tools v10.3.10.10540 ===

=== Page cache for zvol File I/O mode is reduced to 50% ===

== Fixed ==

=== RSS does not check if gateway is set up and if RSS server is available ===

=== System activation on XEN VSA does not work ===

=== Cannot use XEN drives for Metro Cluster in XEN VSA ===

=== Zvol configured as a destination in OODP still can be set as a LUN for target ===

=== Dataset configured as a destination in OODP still can be used as a location for a Share ===

=== VMware VCenter/VSphere snapshot autoremove mechanism deletes all ESX snapshots ===

=== Listing of OODP snapshots lasts very long ===

=== activation.xml is cleaned while activation server was unavailable e.g. because of firewall settings ===

=== System restart in watchdog for processes which works more than 300 sec. ===

=== Problems with ssh and jumboframes (MTU) ===

=== The SIDs are not mapped to usernames and groups for shares in Windows (fixed for new JovianDSS installations only) ===

=== Unstable working of Intel X710/XL710 and Intel X722 network cards configured as LACP or Balance Round Robin bonding mode ===

== Important notes for JovianDSS HA configuration ==

=== It is necessary to use sync always option for zvols and datasets in cluster  ===

=== It is strongly recommended not to use more than eight ping nodes ===

=== It is strongly recommended to configure each IP address in separate subnetwork ===

=== It is necessary to run Scrub scanner after failover action triggered by power failure (dirty system close) ===

=== It is strongly recommended to use UPS unit for each cluster node ===

=== It is necessary to use static discovery in all iSCSI initiators ===

=== It is strongly not recommended to change any settings when both nodes do not have the same JovianDSS version, for example during software updating ===

=== It is necessary to use different Server names for cluster nodes ===

=== HA cluster does not work properly with Infiniband controllers ===

=== HA cluster does not work stable with ALB bonding mode ===

=== FC Target HA cluster does not support Persistant Reservation Synchronization and it cannot be used as a storage for Microsoft Hyper-V cluster. This problem will be solved in future releases. ===

=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===
<p style="text-align: justify"><span class="toctext">    You can find details below:</span></p><p style="text-align: justify"><span class="toctext">    [https://kb.open-e.com/index.php?View=entry&EntryID=3101 https://kb.open-e.com/index.php?View=entry&EntryID=3101]</span></p><p style="text-align: justify"><span class="toctext">    *Please consult Broadcom vendor for specific firmware that is suitable for your hardware setup.</span></p>
== Performance tuning ==

=== iSCSI Target with VMware ESX performance tuning ===

     In case of low iSCSI Target performance with VMware ESX, a few parameters need to be changed in VMware ESX iSCSI Initiator. Go to Storage Adapters -> iSCSI Software Adapter -> Advanced Options and the change the following settings:
<pre>
MaxOutstandingR2T change the default 1 to 8

FirstBurstLength change the default 262144 to 65536

MaxBurstLength change the default 262144 to 1048576

MaxRecvDataSegLen change the default 131072 to 1048576
</pre>
=== Write cache sync requests performance tuning ===

     Write cache sync requests (sync) set to “always” for zvol is the safest option and is set by default. However, it can cause write performance decreases since all operations are written and flushed directly to the persistent storage. In case of using sync=always, it is strongly recommended using mirrored write log devices (very fast random writes devices).<br/>     Sync=standard or sync=disabled zvol options provide huge performance improvement but the most recent (up to 5 seconds) cached data can be lost in case of a sudden power failure. Use this option only in environments equipped with UPS.<br/>     For NFS shares the Synchronous data record is enabled by default. This option causes performance to be worse, but data can be safely written. In order to improve the NFS performance you can use Asynchronous data record but in such case, it is strongly recommended to use UPS.

== Known issues ==

=== Browser recommendations ===

     It is strongly recommended to use Mozilla Firefox browser to navigate the system’s GUI. When using other browsers some slight problems with displaying content may occur.

=== Web browser’s cache ===

     After updating from previous versions, some problems with WebGUI content and navigation may occur. To resolve this problems, please clear Web browser cache.

=== System as a guest in virtual environments ===

     Hyper-V:<br/>     In case of installing the system as a Hyper-V guest please use the following settings:<br/>       - Number of virtual processors: 4<br/>       - Memory: Minimum 8GB<br/>       - Boot Disk: 20GB IDE Disk<br/>       - Add at least 6 virtual disk

 <br/>     VMware ESXi:<br/>     In case of installing the system as a VMware ESXi guest please use the following settings:<br/>       - Guest OS: Other 2.6.x Linux ( 64bit )<br/>       - Number of Cores: 4<br/>       - Memory: Minimum 8GB<br/>       - Network Adapter: VMXNET 3<br/>       - SCSI Controller Type: Paravirtual or LSI Logic SAS<br/>       - Boot Disk : 20GB Thick Provision Eager Zeroed<br/>       - Add at least 6 virtual disk<br/>       - Edit Settings->Options->Advanced-General->Configuration-> Add row: disk.EnableUUID : TRUE

=== Reclaim deleted blocks on thin-provisioned LUNs in various systems ===

     In case of deleting large amounts of data, reclaimed deleted blocks on thin-provisioned LUNs in Windows 2012 can significantly slow down system performance. If you predict frequent deletions of large amounts of data, we recommend turning off the automatic reclaim function in Windows 2012. This can be done by disabling the "file-delete notification" feature in the system registry. To do so, follow the steps below:<br/>       - start Registry Editor.<br/>       - locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem       <br/>       - double-click DisableDeleteNotification.<br/>       - in the Value data box, enter a value of 1, and then click OK.<br/> <br/>     In order to reclaim the free space in Windows 2012 please change the    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\DisableDeleteNotification key value back to 0 and use "Optimize" tool located in Disc Management->[disk]->Properties->Tools. As the operation can generate a very high load in the system, it is recommended to perform it after-hours.  <br/>In case of VMware ESXi, the automatic reclaim feature is disabled by default. To reclaim the space of deleted blocks on thin-provisioned LUNs, please use vmkfstools. For details, please refer to the VMware Knowledge Base:

For VMware ESXi 5.0: [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849]<br/>For VMware ESXi 5.5 and newer: [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513 https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513]<br/>For VMware ESXi 6.7 and newer: search in Internet for “Space Reclamation Requests from VMFS Datastores” and read vendor documentation.

In case of using Windows 2008 there is no possibility to reclaim the space released by deleted data of thin-provisioned LUNs.

=== Deduplication issues and recommendations ===

     Please be aware that deleting the zvol with deduplication enabled can generate a very high load in the system and lead to unstable behavior. It is strongly recommended to perform such operation only after-hours. To avoid this issue, please use (if possible) single zvol on zpools dedicated for deduplication and delete the zpool which includes the single zvol.<br/>   <br/>     To determine the amount of System RAM required for deduplication, use this formula:<br/> <br/>                                                                                                                    (Size of Zvol / Volume block size) * 320B / 0.75 / 0.25<br/> <br/>Where:<br/>320B - is the size of entry in DDT table<br/>0.75 - Percentage of RAM reservation for ARC (75%)<br/>0.25 - Percentage of DDT reservation in ARC (25%)<br/> <br/>     Example for 1TB data and 64KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 65536B) * 320B / 0.75 / 0.25 = 28633115306.67B<br/>                                                                                                                       28633115306.67B / 1024 / 1024 / 1024 = 26.67GB<br/> <br/>so for every extra 1TB of storage, system needs extra 26.67GB RAM.<br/><br/>     Example for 1TB data and 128KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 131072B) * 320B / 0.75 / 0.25 = 14316557653.33B<br/>                                                                                                                        14316557653.33B / 1024 / 1024 / 1024 = 13.33GB<br/> <br/>so for every extra 1TB of storage, system needs extra 13.33GB RAM.
<div><br/></div><div>     Example for 1TB data and 1MB Volume block size:</div><div><br/></div><div>                                                                                                      (1099511627776B / 1048576B) * 320B / 0.75 / 0.25 = 1789569706,66B</div><div>                                                                                                                        1789569706,66B / 1024 / 1024 / 1024 = 1.66GB</div><div> </div><div>     so for every extra 1TB of storage, system needs extra 1.66GB RAM.</div><div><br/></div>
<br/>'''IMPORTANT: '''The above calculations only apply to the worst case scenario, when data is completely unique and will not be deduplicated. For the deduplicable data, the need for RAM drastically decreases. If SSD based Read Cache is present, part of deduplication table will be moved to the SSD and deduplication will work with good performance using less RAM.

<br/>'''IMPORTANT: '''With SAN (iSCSI) it is CRITICAL to match User-File-System format block size with the zvol volume-block-size. A simple example is a Windows file system NTFS with default format block size 4k and zvol default volume-block-size is 128k. With defaults like this deduplication will mostly NOT match because files can be aligned in 32 (128/4) different positions on the pool. If the NTFS format is increased to 64k and the zvol default volume-block-size is 128k, deduplication match can fail only one time because a file can be aligned to 2 (128/64) different positions on the pool. Every next write will match already as both alignment options already exist on the pool. In order to achieve all files matching and efficient memory usage NTFS must use 64k format block size and the zvol volume-block-size must equal 64k. Another option is that the NTFS=32k and zvol=32k, but in this case the deduplication table will be twice as large. That is why the NTFS=64k and zvol=64k is the most efficient setting for deduplication.

'''IMPORTANT: '''With NAS (NFS, SMB/CIFs) deduplication matching works always due to the data blocks being aligned by ZFS natively.

'''IMPORTANT: '''De-duplication is working on the pool level in the pool-range. This is why zvol-Physical size cannot show de-duplication benefit. In order to prove that deduplication saved space run the scrub and notice the current physical data space on the pool reported by the scrub. Next copy of new data and run the scrub again. Now scrub will show new physical data space. Comparing the data size from storage client side with the data space growth from the scrub will give the deduplication advantage. The exact pool of the deduplication ratio can be found in LOGs in zfs.log.

=== Zvols configuration issues and recommendations ===

     It is strongly recommended to set the client file system block size same as the zvol volume block size. For example, when using 64k zvol volume block size, the Windows Allocation unit size of NTFS should be set to 64k.

=== Target number limit ===

    In case of more than 60 targets, GUI will not be displayed correctly. This issue will be fixed in the next releases.

=== Targets with the same name are not assigned correctly ===

    Having two or more targets with the same name but belonging to various Zpools, will cause that all targets with the same name will be assigned to one Zpool during the import process.

=== Installation on disks containing LVM metadata ===

     There is no possibility to install the system on disks containing LVM metadata. You will need to clear those disks before installation. To do so, use the “Remove ZFS data structures and disks partitions” function located in the Extended tools. To access this function, boot the system from a temporary media like a USB drive or DVD.

=== Import Zpool with broken write log ===

     There is no option to import Zpool with a broken write log disk using the system’s functions. This is why it is STRONGLY recommended to use mirrored disks for write logs. In case it is necessary to import Zpool with a broken write log, please contact technical support.

=== Replacing disks in data groups for larger ones can cause your storage license capacity to be exceeded ===

     In case of replacing damaged disks for larger ones, the size of the entire Zpool will increased. Make sure that the new size will not exceed your purchased storage license.

=== Periodically after some operations, the GUI needs to be manually refreshed ===

     After performing some operations, e.g. resilvering, the GUI will show outdated information. In this case refresh the web page manually by pressing F5 on your keyboard. This issue will be fixed in next releases.

=== Replacing disks in data groups for smaller ones can cause an error and make the disk disappear from the list of available disks ===

     Operation of replacing a disk in a data group for a smaller one will cause an error "zpool unknown error, exit code 255", and the disk will become unavailable. In order to reuse this disk, please use function "Remove ZFS data structures and disks partitions" located in the Extended tools on the Console screen.

=== It is strongly recommended to use 64KB or higher Volume block size ===

     Smaller than 64KB block sizes used with deduplication or read cache will cause very high memory consumption.

=== RAM recommendations for Read Cache ===

     To determine how much System RAM is required for Read Cache, use the following formula:

<br/> <br/>                                                                      RAM needed = (Size of Read Cache - reserved size and labels) * bytes reserved by l2hdr structure / Volume block size<br/> 

     For 8KB Volume block size and 1TB Read Cache:<br/><br/>                                                                           RAM needed = (1099511627776B - 4718592B) * 432B / 8192B = 57981809664B<br/>                                                                                                        57981809664B / 1024 / 1024 / 1024 = 54GB<br/> <br/>Where:<br/>1099511627776B - 1TB Read Cache<br/>4718592B - reserved size and labels<br/>432B - bytes reserved by l2hdr structure<br/>8192B - Volume block size<br/> <br/>                                                                                                  For 64KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 65536B = 7247726208B<br/>                                                                                                       7247726208B / 1024 / 1024 /1024 = 6.75GB<br/><br/><br/>                                                                                                  For 128KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 131072B = 3623863104B<br/>                                                                                                       3623863104B / 1024 / 1024 /1024 = 3.37GB

=== Multiple GUI disk operations may result in an inaccurate available disks list ===

     Multiple operations of adding and detaching disks from groups can cause that the next operation of detaching will fail, but the disk will be shown on a list of available disks. When trying to add this disk to one group it will fail with the following error "[zfslib-wrap-zpool-ZpoolCmdError-1] invalid vdev specification". In this case, detach this disk once again.

=== After removing disks from groups they may not be displayed on a list of available disks ===

     Sometimes after removing disks from groups, Spare/Read Cache/Write Log disks are displayed on a list of unassigned disks, but they are not on a list of available disks. In this case, click the rescan button located in the adding group form.

=== Reusing disks from an exported and deleted Zpool ===

     After deleting an exported Zpool, not all disks which were a part of a Zpool become immediately available. Before you can reuse disks, which were previously used as a Spare or a Read Cache, you must first clean them. Use “Remove ZFS data structures and disks partitions” function located in the “Extended tools”.

=== Negotiated speed of network interfaces may not display correctly ===

     For some network interfaces, the negotiated speed field may display an incorrect value in GUI and Console. This issue will be fixed in next releases.

=== Limited possibility to display a large number of elements by the GUI ===

     After creating multiple snapshots, clones or zvols some forms in GUI work very slow. If you need to create many snapshots, clones or zvols, it is strongly recommended to use CLI in order to perform operations on them.

=== Open-E VSS Hardware Provider system recommendations ===

     It is strongly recommended to use Windows Server 2012. On the other Windows systems, Open-E VSS Hardware Provider Configuration works unstable.

=== Exceeded quota for dataset does not allow to remove files ===

     Files located on datasets with exceeded quota cannot be removed. In this case, please resize quota and then remove unnecessary files.

=== Slow WebGUI with multiple datagroups ===

     Zpool with more than 20 datagroups causes that some forms on WebGUI work very slow. If you need to create many datagroups, it is strongly recommended to use CLI API.

=== Slow WebGUI with multiple datasets ===

     More than 25 datasets cause that WebGUI works slow.

=== ZFS Upgrade ===

     For Open-E JovianDSS users, it is recommended to upgrade Zpools to the latest ZFS file system. Although the file system upgrade is absolutely safe for your data, and takes only few minutes, please be aware that this operation cannot be undone. In order to upgrade a single Zpool, please use "WebGUI -> Zpool options -> Upgrade file system" from Zpool's option menu.

=== Intel® Ethernet Controller XL710 Family ===

     In case of using Open-E JovianDSS with Intel® Ethernet Controller XL710 Family, it is necessary to update firmware’s network controller to the version: f4.33.31377 a1.2 n4.42 e1932.

=== Motherboards with x2APIC technology ===

     In case of using a motherboard with x2APIC technology enabled, it is necessary to disable x2APIC in BIOS. Otherwise, problems with CPU cores will occur.

=== NFS FSIDs and Zpool name ===

     One of the factors that have been taken into account when NFS FSIDs are generated is Zpool name. It indicates that when Zpool name is changed, e.g. during export and import with different names, FSIDs for NFS Shares located on this Zpool will also be changed.

=== High Availability shared storage cluster does not work with Infiniband controllers ===

     Due to technical reasons the High Availability shared storage cluster does not work properly when using the Infiniband controllers for VIP interface configuration. This limitation will be removed in the future releases.

=== Disks with LVM data cannot be used with the created Zpool ===

     Attempt to create Zpool with drives that contain LVM data will fail with the following error:

''"cannot open 'lvm-pv-uuid-R25lTS-kcDc-eiAN-eAlf-ppgi-rAqu-Oxy1Si': no such device in /dev must be a full path or shorthand device name"''

In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.

=== Unexpected long failover time, especially with HA-Cluster with two or more pools ===

     Current failover mechanism procedure is moving pools in sequence. Since up27 release, up to 3 pools are supported in HA-cluster. If all pools are active on single node and failover needs to move all 3 pools, the failover may take longer than 60 seconds which is a default iSCSI timeout in Hyper-V Clusters. In some environments, under heavy load a problem with too long time of cluster resources switching may occur as well. If the switching time exceeds the iSCSI initiator timeout, it is strongly recommended to increase the timeout up to 600 seconds.

     '''In case of using Windows, to increase iSCSI initiator timeout, please perform following steps:'''

1. Run regedit tool and find: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\...\Parameters\MaxRequestHoldTime registry key''

2. Change value of the key from default 60 sec to 600 sec (decimal)

     '''In case of using VMware, to increase iSCSI initiator timeout, please perform following steps:'''

1. Select the host in the vSphere Web Client navigator

2. Go to Settings in the Manage tab

3. Under System, select Advanced System Settings

4. Choose the ''Misc.APDTimeout'' attribute and click the Edit icon

5. Change value from default 140 to 600 sec.

     '''In case of using XenServer, to increase iSCSI initiator timeout, please perform following steps:'''

A. For existing Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Detach and reattach SRs. This will update the new iSCSI timeout settings for the existing SRs.

B. For new Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Create the new SR. New and existing SRs will be updated with the new iSCSI timeout settings.

=== Activation may be lost after update ===

     In some environments, after update to up11 system may require re-activation. This issue will be removed in the future releases.

=== Bonding ALB and Round-Robin do not work in Hyper-V and VMware environments ===

     In case of using JovianDSS as Hyper-V or VMware guest, bonding ALB and Round-Robin is not supported. Please use another type of bonding.

=== Continuous writing in VMware guest can cause that deleting VMware snapshot can take long time ===

     Using ODPS on zvol/dataset with VMware guest where many I/O operations are performed can cause that the process of deleting VMware snapshot can take long time. Please take this into consideration while you set up the scheduler for Off-site Data Protection Service task.

=== Enabling quota on dataset can cause file transfer interrupt ===

     Enabling quota functionality on a dataset can cause file transfer interrupt. Before using it in production environment, please enable quota on dataset, or make sure that no file transfers are active.

=== Nodes connected to the same AD server must have unique Server names ===

     If JovianDSS nodes are connected to the same AD server, they cannot have the same Server names.

=== Share can not be named the same as Zpool ===

     In case of share with the same name as Pool connections problem will occur. Please use different names.

=== No persistent rules for network cards in virtual environment ===

     Changing settings of virtual network cards (delete, changing MAC, etc.) can cause unstable system behaviour. Please do not change settings on production system. This issue will be fixed in next releases.

=== Downgrade to up17 or earlier is not possible ===

     Starting from up18 bootable medium has always SW RAID structure. Attempt to come back to earlier version is impossible. If you need come back to earlier version, you must reinstall version again.

=== System cannot be installed on cciss based controllers ===

     This issue will be fixed in next releases.

=== Interrupt the process of adding second disk to SW RAID (bootable medium) can cause run system from disk with uncompleted data ===

     Performing operation like: reboot, shutdown, power off, etc. during mirroring data on new added disk can cause that system will be booted from new disk which has incomplete data. In this case, SW RAID function shows empty status and wrong number of RAID members. To resolve this issue, please plug off disk which has incomplete data, boot system, plug in disk and add it once again to SW RAID.

=== SAS-MPIO cannot be used with Cluster over Ethernet ===

     It is strongly not recommended to use Cluster over Ethernet with SAS-MPIO functionality. Such a configuration can lead to a very unstable cluster behavior.

=== On- & Off-site Data Protection backward compatibility problem ===

     In case of using On- & Off-site Data Protection functionality in up21 or earlier, it is strongly recommended to remove all backup tasks created by CLI API and re-create it using GUI.

=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===

     In FC Target HA environment, power cycle of both nodes simultaneously may lead to a situation when VMware is not able to restore proper state of the storage devices. In vSphere GUI LUNs are displayed as Error, Unknown or Normal,Degraded. Moving affected pools to another node and back to its native node should bring LUNs back to normal. A number two option is to restart the Failover in Jovian’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.

=== Problem with maintenance in case of disk failure ===

     In case of disk failure, please remove the damaged disks from the system, before starting administrative work to replace the disk. The order of actions is important.

=== Separated mode after update from JovianDSS up24 to JovianDSS up25 ===

     In HA cluster environment after updating of one node from JovianDSS up24 to JovianDSS up25 the other node can fall into separated mode and the mirror path might indicate disconnected status. In such a case go to Failover Settings and in the Failover status section select Stop Failover on both nodes. Once this operation is finished select Start Failover.

=== Different Write Cache default setting for zvols in early beta versions of Jovian DSS up25 ===

     In the early beta versions of JovianDSS up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of Jovian up25 the Log bias is set to “Write log device (Latency)”.<br/>Please note, that “In Pool (Throughput)” setting may cause a drop in performance in environments with a lot of random access workloads which is a common factor for a majority of production environments.

=== Target alias name is required while configuring HA FC Target in case of adding two or more ports to one FC group ===

     If we want to have more then one port in each FC group (in HA FC configuration) it is necessary to type in Target alias name for every port. Otherwise an error message “Target alias is already used” can show up while setting up remote port mapping for FC targets in (pool name) -> Fibre Channel -> Targets and initiators assigned to this zpool. This issue will be resolved in the future release.

=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===

     In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of Jovian up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open Jovian TUI and use CTRL+ALT+W key combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select qla2xxx_scst QLogic Fibre Channel HBA Driver and make sure the value of this parameter is set to “exclusive”.<br/><br/>Please note that in order to change this parameter Failover must be stopped first.

=== Very low performance of FIO/WT in case of mixed FIO/WT and FIO/WB zvol configurations over Fiber Channel ===

     In case of the mixed FIO/WT and FIO/WB zvol configurations over FC one can observe significantly decreased performance on FIO/WT.

=== More than one zvol with FIO/WB mode can cause instability of the Fiber Channel connection ===

     If there's more than one FIO/WB zvol or a FIO/WB zvol is coexisting with other types of zvols it can cause an instability of the FC connection with client machines. As a result client machines may unexpectedly lose FC connected resources.

=== In certain situations system page cache is not able to flush File I/O errors by itself and cache flushing has to be performed manually ===

     Under certain conditions (like overfilling zvol and then expanding its size) some File I/O errors may be held by the system page cache and it requires manual flushing (in GUI use Storage -> Rescan).

=== Updating nodes of the Jovian cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===

     There is a significant difference in FC configurations in up24 and earlier versions. Those versions allowed the FC ports to be configured in initiator mode only, while later versions allow both target and initiator mode with target as default, so in case of using storage connected via FC initiator, FC port(s) must be manually corrected in GUI of the updated node.

=== Updating Metro Cluster node with NVMe disks as read cache from JovianDSS up26 or earlier can cause the system to lose access to the NVMe disks ===

     The process of updating of Metro Cluster node from JovianDSS up26 or earlier is changing NVME disk IDs. In consequence moving pool back to updated node is possible but the read cache is gone (ID mismatch). In order to bring read cache back to the pool we recommend to use console tools in the following way: press Ctrl+Alt+x -> “Remove ZFS data structures and disks partitions”, locate and select the missing NVMe disk and press OK to remove all ZFS metadata on the disk. After this operation click Rescan button in GUI -> Storage. The missing NVMe disk should now appear in Unassigned disks at the bottom of the page which allows to select that disk in pool’s Disk group’s tab. Open Disk group tab of the pool, press the Add group button and select Add read cache. The missing disk should now be available to select it as a read cache.

=== Synchronization of a large LDAP database can last for a long time (e.g. 10h for 380K users) and can be associated with high system load ===

     This problem will be solved in future releases.

=== Long time of a failover procedure in case of Xen client with iSCSI MPIO configuration ===

     In a scenario where Xen client is an iSCSI initiator in MPIO configuration, the power-off of one node starts the failover procedure that takes a very long time. Pool is finally moved successfully but there are many errors showing up in dmesg in meantime. In case of such an environment we recommend to add the following entry in the device section of the configuration file: /etc/multipath.conf:

'''no_path_retry queue'''

<br/>The structure of the device section should look as follows:
<pre>device {
vendor "SCST_FIO|SCST_BIO"
product "*"
path_selector "round-robin 0"
path_grouping_policy multibus
rr_min_rio 100
no_path_retry queue
}
</pre>
[[Category:Release Notes]]

Open-E JovianDSS ver.1.0 up28 Release Notes

2020-11-17T08:28:04Z

Ma-W:

'''Release date: 2020-01-28'''

'''Build: 37311'''

'''For build 38496 go to: [http://wiki.open-e.com/default/wiki/Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes http://wiki.open-e.com/default/wiki/Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes]'''

{| class="cke_show_border cke_show_border"
|-
| __TOC__

|}

== New ==

=== HA Cluster Ring can be configured as two single connections ===

=== HA cluster Ping-nodes can be configured within any available interfaces and subnetworks ===

=== Static routing configuration is available in Web-GUI ===

=== Custom SSL/TLS certificates can be manually imported in Web-GUI ===

=== ZFS Datasets can get a record size value from range of 4KiB up to 16MiB (default record size value is 1MiB) ===

=== Fibre Channel Target mode is available for ATTO Fiber Channel Adapter (supported only with VMware client) ===

=== Improved performance of LDAP database replication mechanism ===

=== Storage performance test tool is available in TUI (System console -> Ctrl+Alt+t -> Add-ons -> Storage performance tool) ===

=== HPE tools for managing HP Smart Array controllers are available in Web-GUI and TUI ===

=== MacOS Spotlight search support allows to quickly locate the files and search through their contents ===

=== Installer creates 128GB boot medium partition size (more space for further upgrade processes) ===

=== New filtering options for Event Viewer (selection by: error, warning, information and the date ranges) ===

=== Kdump (kernel crash dumping mechanism) ===

=== The default SCSI ID for iSCSI and FC luns can be manually set in Web-GUI ===

=== Deduplication statistics for zpool are available in Web-GUI ===

=== Ethernet cards detailed statistics (amount of data sent and received) are available in the system logs ===

=== Statistics for MPIO devices are displayed in GUI (Diagnostics -> Disk usage) ===

=== Linux iostat and S.M.A.R.T data are available in Checkmk monitoring system ===

== Updated ==

=== Samba 4.9.4 ===

=== Mellanox ConnectX-3 driver (mlx4_core, v4.4-2.0.7) ===

=== Mellanox ConnectX-4/5 driver (mlx5_core, v4.4-2.0.7) ===

=== Intel 10/40GbE driver i40e (i40e, v2.9.21) ===

=== Broadcom BCM5706/5708/5709/5716 driver (bnx2, v2.2.5x) ===

=== Broadcom BCM57710/57711/57711E/57712/57712_MF/57800/57800_MF/57810/57810_MF/57840/57840_MF driver (bnx2x, v.1.715.0) ===

=== ATTO Celerity 16Gb/32Gb Fibre Channel Adapter driver (celerity16fc, v1.76.0f1) ===

=== Microsemi Adaptec RAID and HBA driver (aacraid, v1.2.1.57013src) ===

=== Microsemi Adaptec SmartRAID and SmartHBA driver (smartpqi, v1.2.6-015) ===

=== Broadcom MegaRAID SAS Driver (megaraid_sas, v07.709.08.00) ===

=== Microsemi Adaptec MaxView tool (v3.02-23600) ===

=== Areca SAS/SATA RAID Controller Driver (arcmsr, v1.40.0X.10-20181227) ===

=== Smartmontools 7.0 ===

=== VMware tools v10.3.10.10540 ===

=== Page cache for zvol File I/O mode is reduced to 50% ===

== Fixed ==

=== RSS does not check if gateway is set up and if RSS server is available ===

=== System activation on XEN VSA does not work ===

=== Cannot use XEN drives for Metro Cluster in XEN VSA ===

=== Zvol configured as a destination in OODP still can be set as a LUN for target ===

=== Dataset configured as a destination in OODP still can be used as a location for a Share ===

=== VMware VCenter/VSphere snapshot autoremove mechanism deletes all ESX snapshots ===

=== Listing of OODP snapshots lasts very long ===

=== activation.xml is cleaned while activation server was unavailable e.g. because of firewall settings ===

=== System restart in watchdog for processes which works more than 300 sec. ===

=== Problems with ssh and jumboframes (MTU) ===

=== The SIDs are not mapped to usernames and groups for shares in Windows (fixed for new JovianDSS installations only) ===

=== Unstable working of Intel X710/XL710 and Intel X722 network cards configured as LACP or Balance Round Robin bonding mode ===

== Important notes for JovianDSS HA configuration ==

=== It is necessary to use sync always option for zvols and datasets in cluster  ===

=== It is strongly recommended not to use more than eight ping nodes ===

=== It is strongly recommended to configure each IP address in separate subnetwork ===

=== It is necessary to run Scrub scanner after failover action triggered by power failure (dirty system close) ===

=== It is strongly recommended to use UPS unit for each cluster node ===

=== It is necessary to use static discovery in all iSCSI initiators ===

=== It is strongly not recommended to change any settings when both nodes do not have the same JovianDSS version, for example during software updating ===

=== It is necessary to use different Server names for cluster nodes ===

=== HA cluster does not work properly with Infiniband controllers ===

=== HA cluster does not work stable with ALB bonding mode ===

=== FC Target HA cluster does not support Persistant Reservation Synchronization and it cannot be used as a storage for Microsoft Hyper-V cluster. This problem will be solved in future releases. ===

=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===
<p style="text-align: justify"><span class="toctext">    You can find details below:</span></p><p style="text-align: justify"><span class="toctext">    [https://kb.open-e.com/index.php?View=entry&EntryID=3101 https://kb.open-e.com/index.php?View=entry&EntryID=3101]</span></p><p style="text-align: justify"><span class="toctext">    *Please consult Broadcom vendor for specific firmware that is suitable for your hardware setup.</span></p>
== Performance tuning ==

=== iSCSI Target with VMware ESX performance tuning ===

     In case of low iSCSI Target performance with VMware ESX, a few parameters need to be changed in VMware ESX iSCSI Initiator. Go to Storage Adapters -> iSCSI Software Adapter -> Advanced Options and the change the following settings:
<pre>
MaxOutstandingR2T change the default 1 to 8

FirstBurstLength change the default 262144 to 65536

MaxBurstLength change the default 262144 to 1048576

MaxRecvDataSegLen change the default 131072 to 1048576
</pre>
=== Write cache sync requests performance tuning ===

     Write cache sync requests (sync) set to “always” for zvol is the safest option and is set by default. However, it can cause write performance decreases since all operations are written and flushed directly to the persistent storage. In case of using sync=always, it is strongly recommended using mirrored write log devices (very fast random writes devices).<br/>     Sync=standard or sync=disabled zvol options provide huge performance improvement but the most recent (up to 5 seconds) cached data can be lost in case of a sudden power failure. Use this option only in environments equipped with UPS.<br/>     For NFS shares the Synchronous data record is enabled by default. This option causes performance to be worse, but data can be safely written. In order to improve the NFS performance you can use Asynchronous data record but in such case, it is strongly recommended to use UPS.

== Known issues ==

=== Browser recommendations ===

     It is strongly recommended to use Mozilla Firefox browser to navigate the system’s GUI. When using other browsers some slight problems with displaying content may occur.

=== Web browser’s cache ===

     After updating from previous versions, some problems with WebGUI content and navigation may occur. To resolve this problems, please clear Web browser cache.

=== System as a guest in virtual environments ===

     Hyper-V:<br/>     In case of installing the system as a Hyper-V guest please use the following settings:<br/>       - Number of virtual processors: 4<br/>       - Memory: Minimum 8GB<br/>       - Boot Disk: 20GB IDE Disk<br/>       - Add at least 6 virtual disk

 <br/>     VMware ESXi:<br/>     In case of installing the system as a VMware ESXi guest please use the following settings:<br/>       - Guest OS: Other 2.6.x Linux ( 64bit )<br/>       - Number of Cores: 4<br/>       - Memory: Minimum 8GB<br/>       - Network Adapter: VMXNET 3<br/>       - SCSI Controller Type: Paravirtual or LSI Logic SAS<br/>       - Boot Disk : 20GB Thick Provision Eager Zeroed<br/>       - Add at least 6 virtual disk<br/>       - Edit Settings->Options->Advanced-General->Configuration-> Add row: disk.EnableUUID : TRUE

=== Reclaim deleted blocks on thin-provisioned LUNs in various systems ===

     In case of deleting large amounts of data, reclaimed deleted blocks on thin-provisioned LUNs in Windows 2012 can significantly slow down system performance. If you predict frequent deletions of large amounts of data, we recommend turning off the automatic reclaim function in Windows 2012. This can be done by disabling the "file-delete notification" feature in the system registry. To do so, follow the steps below:<br/>       - start Registry Editor.<br/>       - locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem       <br/>       - double-click DisableDeleteNotification.<br/>       - in the Value data box, enter a value of 1, and then click OK.<br/> <br/>     In order to reclaim the free space in Windows 2012 please change the    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\DisableDeleteNotification key value back to 0 and use "Optimize" tool located in Disc Management->[disk]->Properties->Tools. As the operation can generate a very high load in the system, it is recommended to perform it after-hours.  <br/>In case of VMware ESXi, the automatic reclaim feature is disabled by default. To reclaim the space of deleted blocks on thin-provisioned LUNs, please use vmkfstools. For details, please refer to the VMware Knowledge Base:

For VMware ESXi 5.0: [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849]<br/>For VMware ESXi 5.5 and newer: [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513 https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513]<br/>For VMware ESXi 6.7 and newer: search in Internet for “Space Reclamation Requests from VMFS Datastores” and read vendor documentation.

In case of using Windows 2008 there is no possibility to reclaim the space released by deleted data of thin-provisioned LUNs.

=== Deduplication issues and recommendations ===

     Please be aware that deleting the zvol with deduplication enabled can generate a very high load in the system and lead to unstable behavior. It is strongly recommended to perform such operation only after-hours. To avoid this issue, please use (if possible) single zvol on zpools dedicated for deduplication and delete the zpool which includes the single zvol.<br/>   <br/>     To determine the amount of System RAM required for deduplication, use this formula:<br/> <br/>                                                                                                                    (Size of Zvol / Volume block size) * 320B / 0.75 / 0.25<br/> <br/>Where:<br/>320B - is the size of entry in DDT table<br/>0.75 - Percentage of RAM reservation for ARC (75%)<br/>0.25 - Percentage of DDT reservation in ARC (25%)<br/> <br/>     Example for 1TB data and 64KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 65536B) * 320B / 0.75 / 0.25 = 28633115306.67B<br/>                                                                                                                       28633115306.67B / 1024 / 1024 / 1024 = 26.67GB<br/> <br/>so for every extra 1TB of storage, system needs extra 26.67GB RAM.<br/><br/>     Example for 1TB data and 128KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 131072B) * 320B / 0.75 / 0.25 = 14316557653.33B<br/>                                                                                                                        14316557653.33B / 1024 / 1024 / 1024 = 13.33GB<br/> <br/>so for every extra 1TB of storage, system needs extra 13.33GB RAM.
<div><br/></div><div>     Example for 1TB data and 1MB Volume block size:</div><div><br/></div><div>                                                                                                      (1099511627776B / 1048576B) * 320B / 0.75 / 0.25 = 1789569706,66B</div><div>                                                                                                                        1789569706,66B / 1024 / 1024 / 1024 = 1.66GB</div><div> </div><div>     so for every extra 1TB of storage, system needs extra 1.66GB RAM.</div><div><br/></div>
<br/>'''IMPORTANT: '''The above calculations only apply to the worst case scenario, when data is completely unique and will not be deduplicated. For the deduplicable data, the need for RAM drastically decreases. If SSD based Read Cache is present, part of deduplication table will be moved to the SSD and deduplication will work with good performance using less RAM.

<br/>'''IMPORTANT: '''With SAN (iSCSI) it is CRITICAL to match User-File-System format block size with the zvol volume-block-size. A simple example is a Windows file system NTFS with default format block size 4k and zvol default volume-block-size is 128k. With defaults like this deduplication will mostly NOT match because files can be aligned in 32 (128/4) different positions on the pool. If the NTFS format is increased to 64k and the zvol default volume-block-size is 128k, deduplication match can fail only one time because a file can be aligned to 2 (128/64) different positions on the pool. Every next write will match already as both alignment options already exist on the pool. In order to achieve all files matching and efficient memory usage NTFS must use 64k format block size and the zvol volume-block-size must equal 64k. Another option is that the NTFS=32k and zvol=32k, but in this case the deduplication table will be twice as large. That is why the NTFS=64k and zvol=64k is the most efficient setting for deduplication.

'''IMPORTANT: '''With NAS (NFS, SMB/CIFs) deduplication matching works always due to the data blocks being aligned by ZFS natively.

'''IMPORTANT: '''De-duplication is working on the pool level in the pool-range. This is why zvol-Physical size cannot show de-duplication benefit. In order to prove that deduplication saved space run the scrub and notice the current physical data space on the pool reported by the scrub. Next copy of new data and run the scrub again. Now scrub will show new physical data space. Comparing the data size from storage client side with the data space growth from the scrub will give the deduplication advantage. The exact pool of the deduplication ratio can be found in LOGs in zfs.log.

=== Zvols configuration issues and recommendations ===

     It is strongly recommended to set the client file system block size same as the zvol volume block size. For example, when using 64k zvol volume block size, the Windows Allocation unit size of NTFS should be set to 64k.

=== Target number limit ===

    In case of more than 60 targets, GUI will not be displayed correctly. This issue will be fixed in the next releases.

=== Targets with the same name are not assigned correctly ===

    Having two or more targets with the same name but belonging to various Zpools, will cause that all targets with the same name will be assigned to one Zpool during the import process.

=== Installation on disks containing LVM metadata ===

     There is no possibility to install the system on disks containing LVM metadata. You will need to clear those disks before installation. To do so, use the “Remove ZFS data structures and disks partitions” function located in the Extended tools. To access this function, boot the system from a temporary media like a USB drive or DVD.

=== Import Zpool with broken write log ===

     There is no option to import Zpool with a broken write log disk using the system’s functions. This is why it is STRONGLY recommended to use mirrored disks for write logs. In case it is necessary to import Zpool with a broken write log, please contact technical support.

=== Replacing disks in data groups for larger ones can cause your storage license capacity to be exceeded ===

     In case of replacing damaged disks for larger ones, the size of the entire Zpool will increased. Make sure that the new size will not exceed your purchased storage license.

=== Periodically after some operations, the GUI needs to be manually refreshed ===

     After performing some operations, e.g. resilvering, the GUI will show outdated information. In this case refresh the web page manually by pressing F5 on your keyboard. This issue will be fixed in next releases.

=== Replacing disks in data groups for smaller ones can cause an error and make the disk disappear from the list of available disks ===

     Operation of replacing a disk in a data group for a smaller one will cause an error "zpool unknown error, exit code 255", and the disk will become unavailable. In order to reuse this disk, please use function "Remove ZFS data structures and disks partitions" located in the Extended tools on the Console screen.

=== It is strongly recommended to use 64KB or higher Volume block size ===

     Smaller than 64KB block sizes used with deduplication or read cache will cause very high memory consumption.

=== RAM recommendations for Read Cache ===

     To determine how much System RAM is required for Read Cache, use the following formula:

<br/> <br/>                                                                      RAM needed = (Size of Read Cache - reserved size and labels) * bytes reserved by l2hdr structure / Volume block size<br/> 

     For 8KB Volume block size and 1TB Read Cache:<br/><br/>                                                                           RAM needed = (1099511627776B - 4718592B) * 432B / 8192B = 57981809664B<br/>                                                                                                        57981809664B / 1024 / 1024 / 1024 = 54GB<br/> <br/>Where:<br/>1099511627776B - 1TB Read Cache<br/>4718592B - reserved size and labels<br/>432B - bytes reserved by l2hdr structure<br/>8192B - Volume block size<br/> <br/>                                                                                                  For 64KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 65536B = 7247726208B<br/>                                                                                                       7247726208B / 1024 / 1024 /1024 = 6.75GB<br/><br/><br/>                                                                                                  For 128KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 131072B = 3623863104B<br/>                                                                                                       3623863104B / 1024 / 1024 /1024 = 3.37GB

=== Multiple GUI disk operations may result in an inaccurate available disks list ===

     Multiple operations of adding and detaching disks from groups can cause that the next operation of detaching will fail, but the disk will be shown on a list of available disks. When trying to add this disk to one group it will fail with the following error "[zfslib-wrap-zpool-ZpoolCmdError-1] invalid vdev specification". In this case, detach this disk once again.

=== After removing disks from groups they may not be displayed on a list of available disks ===

     Sometimes after removing disks from groups, Spare/Read Cache/Write Log disks are displayed on a list of unassigned disks, but they are not on a list of available disks. In this case, click the rescan button located in the adding group form.

=== Reusing disks from an exported and deleted Zpool ===

     After deleting an exported Zpool, not all disks which were a part of a Zpool become immediately available. Before you can reuse disks, which were previously used as a Spare or a Read Cache, you must first clean them. Use “Remove ZFS data structures and disks partitions” function located in the “Extended tools”.

=== Negotiated speed of network interfaces may not display correctly ===

     For some network interfaces, the negotiated speed field may display an incorrect value in GUI and Console. This issue will be fixed in next releases.

=== Limited possibility to display a large number of elements by the GUI ===

     After creating multiple snapshots, clones or zvols some forms in GUI work very slow. If you need to create many snapshots, clones or zvols, it is strongly recommended to use CLI in order to perform operations on them.

=== Open-E VSS Hardware Provider system recommendations ===

     It is strongly recommended to use Windows Server 2012. On the other Windows systems, Open-E VSS Hardware Provider Configuration works unstable.

=== Exceeded quota for dataset does not allow to remove files ===

     Files located on datasets with exceeded quota cannot be removed. In this case, please resize quota and then remove unnecessary files.

=== Slow WebGUI with multiple datagroups ===

     Zpool with more than 20 datagroups causes that some forms on WebGUI work very slow. If you need to create many datagroups, it is strongly recommended to use CLI API.

=== Slow WebGUI with multiple datasets ===

     More than 25 datasets cause that WebGUI works slow.

=== ZFS Upgrade ===

     For Open-E JovianDSS users, it is recommended to upgrade Zpools to the latest ZFS file system. Although the file system upgrade is absolutely safe for your data, and takes only few minutes, please be aware that this operation cannot be undone. In order to upgrade a single Zpool, please use "WebGUI -> Zpool options -> Upgrade file system" from Zpool's option menu.

=== Intel® Ethernet Controller XL710 Family ===

     In case of using Open-E JovianDSS with Intel® Ethernet Controller XL710 Family, it is necessary to update firmware’s network controller to the version: f4.33.31377 a1.2 n4.42 e1932.

=== Motherboards with x2APIC technology ===

     In case of using a motherboard with x2APIC technology enabled, it is necessary to disable x2APIC in BIOS. Otherwise, problems with CPU cores will occur.

=== NFS FSIDs and Zpool name ===

     One of the factors that have been taken into account when NFS FSIDs are generated is Zpool name. It indicates that when Zpool name is changed, e.g. during export and import with different names, FSIDs for NFS Shares located on this Zpool will also be changed.

=== High Availability shared storage cluster does not work with Infiniband controllers ===

     Due to technical reasons the High Availability shared storage cluster does not work properly when using the Infiniband controllers for VIP interface configuration. This limitation will be removed in the future releases.

=== Disks with LVM data cannot be used with the created Zpool ===

     Attempt to create Zpool with drives that contain LVM data will fail with the following error:

''"cannot open 'lvm-pv-uuid-R25lTS-kcDc-eiAN-eAlf-ppgi-rAqu-Oxy1Si': no such device in /dev must be a full path or shorthand device name"''

In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.

=== Unexpected long failover time, especially with HA-Cluster with two or more pools ===

     Current failover mechanism procedure is moving pools in sequence. Since up27 release, up to 3 pools are supported in HA-cluster. If all pools are active on single node and failover needs to move all 3 pools, the failover may take longer than 60 seconds which is a default iSCSI timeout in Hyper-V Clusters. In some environments, under heavy load a problem with too long time of cluster resources switching may occur as well. If the switching time exceeds the iSCSI initiator timeout, it is strongly recommended to increase the timeout up to 600 seconds.

     '''In case of using Windows, to increase iSCSI initiator timeout, please perform following steps:'''

1. Run regedit tool and find: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\...\Parameters\MaxRequestHoldTime registry key''

2. Change value of the key from default 60 sec to 600 sec (decimal)

     '''In case of using VMware, to increase iSCSI initiator timeout, please perform following steps:'''

1. Select the host in the vSphere Web Client navigator

2. Go to Settings in the Manage tab

3. Under System, select Advanced System Settings

4. Choose the ''Misc.APDTimeout'' attribute and click the Edit icon

5. Change value from default 140 to 600 sec.

     '''In case of using XenServer, to increase iSCSI initiator timeout, please perform following steps:'''

A. For existing Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Detach and reattach SRs. This will update the new iSCSI timeout settings for the existing SRs.

B. For new Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Create the new SR. New and existing SRs will be updated with the new iSCSI timeout settings.

=== Activation may be lost after update ===

     In some environments, after update to up11 system may require re-activation. This issue will be removed in the future releases.

=== Bonding ALB and Round-Robin do not work in Hyper-V and VMware environments ===

     In case of using JovianDSS as Hyper-V or VMware guest, bonding ALB and Round-Robin is not supported. Please use another type of bonding.

=== Continuous writing in VMware guest can cause that deleting VMware snapshot can take long time ===

     Using ODPS on zvol/dataset with VMware guest where many I/O operations are performed can cause that the process of deleting VMware snapshot can take long time. Please take this into consideration while you set up the scheduler for Off-site Data Protection Service task.

=== Enabling quota on dataset can cause file transfer interrupt ===

     Enabling quota functionality on a dataset can cause file transfer interrupt. Before using it in production environment, please enable quota on dataset, or make sure that no file transfers are active.

=== Nodes connected to the same AD server must have unique Server names ===

     If JovianDSS nodes are connected to the same AD server, they cannot have the same Server names.

=== Share can not be named the same as Zpool ===

     In case of share with the same name as Pool connections problem will occur. Please use different names.

=== No persistent rules for network cards in virtual environment ===

     Changing settings of virtual network cards (delete, changing MAC, etc.) can cause unstable system behaviour. Please do not change settings on production system. This issue will be fixed in next releases.

=== Downgrade to up17 or earlier is not possible ===

     Starting from up18 bootable medium has always SW RAID structure. Attempt to come back to earlier version is impossible. If you need come back to earlier version, you must reinstall version again.

=== System cannot be installed on cciss based controllers ===

     This issue will be fixed in next releases.

=== Interrupt the process of adding second disk to SW RAID (bootable medium) can cause run system from disk with uncompleted data ===

     Performing operation like: reboot, shutdown, power off, etc. during mirroring data on new added disk can cause that system will be booted from new disk which has incomplete data. In this case, SW RAID function shows empty status and wrong number of RAID members. To resolve this issue, please plug off disk which has incomplete data, boot system, plug in disk and add it once again to SW RAID.

=== SAS-MPIO cannot be used with Cluster over Ethernet ===

     It is strongly not recommended to use Cluster over Ethernet with SAS-MPIO functionality. Such a configuration can lead to a very unstable cluster behavior.

=== On- & Off-site Data Protection backward compatibility problem ===

     In case of using On- & Off-site Data Protection functionality in up21 or earlier, it is strongly recommended to remove all backup tasks created by CLI API and re-create it using GUI.

=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===

     In FC Target HA environment, power cycle of both nodes simultaneously may lead to a situation when VMware is not able to restore proper state of the storage devices. In vSphere GUI LUNs are displayed as Error, Unknown or Normal,Degraded. Moving affected pools to another node and back to its native node should bring LUNs back to normal. A number two option is to restart the Failover in Jovian’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.

=== Problem with maintenance in case of disk failure ===

     In case of disk failure, please remove the damaged disks from the system, before starting administrative work to replace the disk. The order of actions is important.

=== Separated mode after update from JovianDSS up24 to JovianDSS up25 ===

     In HA cluster environment after updating of one node from JovianDSS up24 to JovianDSS up25 the other node can fall into separated mode and the mirror path might indicate disconnected status. In such a case go to Failover Settings and in the Failover status section select Stop Failover on both nodes. Once this operation is finished select Start Failover.

=== Different Write Cache default setting for zvols in early beta versions of Jovian DSS up25 ===

     In the early beta versions of JovianDSS up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of Jovian up25 the Log bias is set to “Write log device (Latency)”.<br/>Please note, that “In Pool (Throughput)” setting may cause a drop in performance in environments with a lot of random access workloads which is a common factor for a majority of production environments.

=== Target alias name is required while configuring HA FC Target in case of adding two or more ports to one FC group ===

     If we want to have more then one port in each FC group (in HA FC configuration) it is necessary to type in Target alias name for every port. Otherwise an error message “Target alias is already used” can show up while setting up remote port mapping for FC targets in (pool name) -> Fibre Channel -> Targets and initiators assigned to this zpool. This issue will be resolved in the future release.

=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===

     In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of Jovian up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open Jovian TUI and use CTRL+ALT+W key combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select qla2xxx_scst QLogic Fibre Channel HBA Driver and make sure the value of this parameter is set to “exclusive”.<br/><br/>Please note that in order to change this parameter Failover must be stopped first.

=== Very low performance of FIO/WT in case of mixed FIO/WT and FIO/WB zvol configurations over Fiber Channel ===

     In case of the mixed FIO/WT and FIO/WB zvol configurations over FC one can observe significantly decreased performance on FIO/WT.

=== More than one zvol with FIO/WB mode can cause instability of the Fiber Channel connection ===

     If there's more than one FIO/WB zvol or a FIO/WB zvol is coexisting with other types of zvols it can cause an instability of the FC connection with client machines. As a result client machines may unexpectedly lose FC connected resources.

=== In certain situations system page cache is not able to flush File I/O errors by itself and cache flushing has to be performed manually ===

     Under certain conditions (like overfilling zvol and then expanding its size) some File I/O errors may be held by the system page cache and it requires manual flushing (in GUI use Storage -> Rescan).

=== Updating nodes of the Jovian cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===

     There is a significant difference in FC configurations in up24 and earlier versions. Those versions allowed the FC ports to be configured in initiator mode only, while later versions allow both target and initiator mode with target as default, so in case of using storage connected via FC initiator, FC port(s) must be manually corrected in GUI of the updated node.

=== Updating Metro Cluster node with NVMe disks as read cache from JovianDSS up26 or earlier can cause the system to lose access to the NVMe disks ===

     The process of updating of Metro Cluster node from JovianDSS up26 or earlier is changing NVME disk IDs. In consequence moving pool back to updated node is possible but the read cache is gone (ID mismatch). In order to bring read cache back to the pool we recommend to use console tools in the following way: press Ctrl+Alt+x -> “Remove ZFS data structures and disks partitions”, locate and select the missing NVMe disk and press OK to remove all ZFS metadata on the disk. After this operation click Rescan button in GUI -> Storage. The missing NVMe disk should now appear in Unassigned disks at the bottom of the page which allows to select that disk in pool’s Disk group’s tab. Open Disk group tab of the pool, press the Add group button and select Add read cache. The missing disk should now be available to select it as a read cache.

=== Synchronization of a large LDAP database can last for a long time (e.g. 10h for 380K users) and can be associated with high system load ===

     This problem will be solved in future releases.

=== Long time of a failover procedure in case of Xen client with iSCSI MPIO configuration ===

     In a scenario where Xen client is an iSCSI initiator in MPIO configuration, the power-off of one node starts the failover procedure that takes a very long time. Pool is finally moved successfully but there are many errors showing up in dmesg in meantime. In case of such an environment we recommend to add the following entry in the device section of the configuration file: /etc/multipath.conf:

'''no_path_retry queue'''

<br/>The structure of the device section should look as follows:
<pre>device {
vendor "SCST_FIO|SCST_BIO"
product "*"
path_selector "round-robin 0"
path_grouping_policy multibus
rr_min_rio 100
no_path_retry queue
}
</pre>
[[Category:Release Notes]]

Open-E JovianDSS ver.1.0 up28 Release Notes

2020-11-17T08:27:22Z

Ma-W:

'''Release date: 2020-01-28'''

'''Build: 37311'''

'''For build '''38496 go to: [http://wiki.open-e.com/default/wiki/Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes http://wiki.open-e.com/default/wiki/Open-E_JovianDSS_ver.1.0_up28r2_Release_Notes]''''''

{| class="cke_show_border cke_show_border"
|-
| __TOC__

|}

== New ==

=== HA Cluster Ring can be configured as two single connections ===

=== HA cluster Ping-nodes can be configured within any available interfaces and subnetworks ===

=== Static routing configuration is available in Web-GUI ===

=== Custom SSL/TLS certificates can be manually imported in Web-GUI ===

=== ZFS Datasets can get a record size value from range of 4KiB up to 16MiB (default record size value is 1MiB) ===

=== Fibre Channel Target mode is available for ATTO Fiber Channel Adapter (supported only with VMware client) ===

=== Improved performance of LDAP database replication mechanism ===

=== Storage performance test tool is available in TUI (System console -> Ctrl+Alt+t -> Add-ons -> Storage performance tool) ===

=== HPE tools for managing HP Smart Array controllers are available in Web-GUI and TUI ===

=== MacOS Spotlight search support allows to quickly locate the files and search through their contents ===

=== Installer creates 128GB boot medium partition size (more space for further upgrade processes) ===

=== New filtering options for Event Viewer (selection by: error, warning, information and the date ranges) ===

=== Kdump (kernel crash dumping mechanism) ===

=== The default SCSI ID for iSCSI and FC luns can be manually set in Web-GUI ===

=== Deduplication statistics for zpool are available in Web-GUI ===

=== Ethernet cards detailed statistics (amount of data sent and received) are available in the system logs ===

=== Statistics for MPIO devices are displayed in GUI (Diagnostics -> Disk usage) ===

=== Linux iostat and S.M.A.R.T data are available in Checkmk monitoring system ===

== Updated ==

=== Samba 4.9.4 ===

=== Mellanox ConnectX-3 driver (mlx4_core, v4.4-2.0.7) ===

=== Mellanox ConnectX-4/5 driver (mlx5_core, v4.4-2.0.7) ===

=== Intel 10/40GbE driver i40e (i40e, v2.9.21) ===

=== Broadcom BCM5706/5708/5709/5716 driver (bnx2, v2.2.5x) ===

=== Broadcom BCM57710/57711/57711E/57712/57712_MF/57800/57800_MF/57810/57810_MF/57840/57840_MF driver (bnx2x, v.1.715.0) ===

=== ATTO Celerity 16Gb/32Gb Fibre Channel Adapter driver (celerity16fc, v1.76.0f1) ===

=== Microsemi Adaptec RAID and HBA driver (aacraid, v1.2.1.57013src) ===

=== Microsemi Adaptec SmartRAID and SmartHBA driver (smartpqi, v1.2.6-015) ===

=== Broadcom MegaRAID SAS Driver (megaraid_sas, v07.709.08.00) ===

=== Microsemi Adaptec MaxView tool (v3.02-23600) ===

=== Areca SAS/SATA RAID Controller Driver (arcmsr, v1.40.0X.10-20181227) ===

=== Smartmontools 7.0 ===

=== VMware tools v10.3.10.10540 ===

=== Page cache for zvol File I/O mode is reduced to 50% ===

== Fixed ==

=== RSS does not check if gateway is set up and if RSS server is available ===

=== System activation on XEN VSA does not work ===

=== Cannot use XEN drives for Metro Cluster in XEN VSA ===

=== Zvol configured as a destination in OODP still can be set as a LUN for target ===

=== Dataset configured as a destination in OODP still can be used as a location for a Share ===

=== VMware VCenter/VSphere snapshot autoremove mechanism deletes all ESX snapshots ===

=== Listing of OODP snapshots lasts very long ===

=== activation.xml is cleaned while activation server was unavailable e.g. because of firewall settings ===

=== System restart in watchdog for processes which works more than 300 sec. ===

=== Problems with ssh and jumboframes (MTU) ===

=== The SIDs are not mapped to usernames and groups for shares in Windows (fixed for new JovianDSS installations only) ===

=== Unstable working of Intel X710/XL710 and Intel X722 network cards configured as LACP or Balance Round Robin bonding mode ===

== Important notes for JovianDSS HA configuration ==

=== It is necessary to use sync always option for zvols and datasets in cluster  ===

=== It is strongly recommended not to use more than eight ping nodes ===

=== It is strongly recommended to configure each IP address in separate subnetwork ===

=== It is necessary to run Scrub scanner after failover action triggered by power failure (dirty system close) ===

=== It is strongly recommended to use UPS unit for each cluster node ===

=== It is necessary to use static discovery in all iSCSI initiators ===

=== It is strongly not recommended to change any settings when both nodes do not have the same JovianDSS version, for example during software updating ===

=== It is necessary to use different Server names for cluster nodes ===

=== HA cluster does not work properly with Infiniband controllers ===

=== HA cluster does not work stable with ALB bonding mode ===

=== FC Target HA cluster does not support Persistant Reservation Synchronization and it cannot be used as a storage for Microsoft Hyper-V cluster. This problem will be solved in future releases. ===

=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===
<p style="text-align: justify"><span class="toctext">    You can find details below:</span></p><p style="text-align: justify"><span class="toctext">    [https://kb.open-e.com/index.php?View=entry&EntryID=3101 https://kb.open-e.com/index.php?View=entry&EntryID=3101]</span></p><p style="text-align: justify"><span class="toctext">    *Please consult Broadcom vendor for specific firmware that is suitable for your hardware setup.</span></p>
== Performance tuning ==

=== iSCSI Target with VMware ESX performance tuning ===

     In case of low iSCSI Target performance with VMware ESX, a few parameters need to be changed in VMware ESX iSCSI Initiator. Go to Storage Adapters -> iSCSI Software Adapter -> Advanced Options and the change the following settings:
<pre>
MaxOutstandingR2T change the default 1 to 8

FirstBurstLength change the default 262144 to 65536

MaxBurstLength change the default 262144 to 1048576

MaxRecvDataSegLen change the default 131072 to 1048576
</pre>
=== Write cache sync requests performance tuning ===

     Write cache sync requests (sync) set to “always” for zvol is the safest option and is set by default. However, it can cause write performance decreases since all operations are written and flushed directly to the persistent storage. In case of using sync=always, it is strongly recommended using mirrored write log devices (very fast random writes devices).<br/>     Sync=standard or sync=disabled zvol options provide huge performance improvement but the most recent (up to 5 seconds) cached data can be lost in case of a sudden power failure. Use this option only in environments equipped with UPS.<br/>     For NFS shares the Synchronous data record is enabled by default. This option causes performance to be worse, but data can be safely written. In order to improve the NFS performance you can use Asynchronous data record but in such case, it is strongly recommended to use UPS.

== Known issues ==

=== Browser recommendations ===

     It is strongly recommended to use Mozilla Firefox browser to navigate the system’s GUI. When using other browsers some slight problems with displaying content may occur.

=== Web browser’s cache ===

     After updating from previous versions, some problems with WebGUI content and navigation may occur. To resolve this problems, please clear Web browser cache.

=== System as a guest in virtual environments ===

     Hyper-V:<br/>     In case of installing the system as a Hyper-V guest please use the following settings:<br/>       - Number of virtual processors: 4<br/>       - Memory: Minimum 8GB<br/>       - Boot Disk: 20GB IDE Disk<br/>       - Add at least 6 virtual disk

 <br/>     VMware ESXi:<br/>     In case of installing the system as a VMware ESXi guest please use the following settings:<br/>       - Guest OS: Other 2.6.x Linux ( 64bit )<br/>       - Number of Cores: 4<br/>       - Memory: Minimum 8GB<br/>       - Network Adapter: VMXNET 3<br/>       - SCSI Controller Type: Paravirtual or LSI Logic SAS<br/>       - Boot Disk : 20GB Thick Provision Eager Zeroed<br/>       - Add at least 6 virtual disk<br/>       - Edit Settings->Options->Advanced-General->Configuration-> Add row: disk.EnableUUID : TRUE

=== Reclaim deleted blocks on thin-provisioned LUNs in various systems ===

     In case of deleting large amounts of data, reclaimed deleted blocks on thin-provisioned LUNs in Windows 2012 can significantly slow down system performance. If you predict frequent deletions of large amounts of data, we recommend turning off the automatic reclaim function in Windows 2012. This can be done by disabling the "file-delete notification" feature in the system registry. To do so, follow the steps below:<br/>       - start Registry Editor.<br/>       - locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem       <br/>       - double-click DisableDeleteNotification.<br/>       - in the Value data box, enter a value of 1, and then click OK.<br/> <br/>     In order to reclaim the free space in Windows 2012 please change the    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\DisableDeleteNotification key value back to 0 and use "Optimize" tool located in Disc Management->[disk]->Properties->Tools. As the operation can generate a very high load in the system, it is recommended to perform it after-hours.  <br/>In case of VMware ESXi, the automatic reclaim feature is disabled by default. To reclaim the space of deleted blocks on thin-provisioned LUNs, please use vmkfstools. For details, please refer to the VMware Knowledge Base:

For VMware ESXi 5.0: [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849]<br/>For VMware ESXi 5.5 and newer: [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513 https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513]<br/>For VMware ESXi 6.7 and newer: search in Internet for “Space Reclamation Requests from VMFS Datastores” and read vendor documentation.

In case of using Windows 2008 there is no possibility to reclaim the space released by deleted data of thin-provisioned LUNs.

=== Deduplication issues and recommendations ===

     Please be aware that deleting the zvol with deduplication enabled can generate a very high load in the system and lead to unstable behavior. It is strongly recommended to perform such operation only after-hours. To avoid this issue, please use (if possible) single zvol on zpools dedicated for deduplication and delete the zpool which includes the single zvol.<br/>   <br/>     To determine the amount of System RAM required for deduplication, use this formula:<br/> <br/>                                                                                                                    (Size of Zvol / Volume block size) * 320B / 0.75 / 0.25<br/> <br/>Where:<br/>320B - is the size of entry in DDT table<br/>0.75 - Percentage of RAM reservation for ARC (75%)<br/>0.25 - Percentage of DDT reservation in ARC (25%)<br/> <br/>     Example for 1TB data and 64KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 65536B) * 320B / 0.75 / 0.25 = 28633115306.67B<br/>                                                                                                                       28633115306.67B / 1024 / 1024 / 1024 = 26.67GB<br/> <br/>so for every extra 1TB of storage, system needs extra 26.67GB RAM.<br/><br/>     Example for 1TB data and 128KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 131072B) * 320B / 0.75 / 0.25 = 14316557653.33B<br/>                                                                                                                        14316557653.33B / 1024 / 1024 / 1024 = 13.33GB<br/> <br/>so for every extra 1TB of storage, system needs extra 13.33GB RAM.
<div><br/></div><div>     Example for 1TB data and 1MB Volume block size:</div><div><br/></div><div>                                                                                                      (1099511627776B / 1048576B) * 320B / 0.75 / 0.25 = 1789569706,66B</div><div>                                                                                                                        1789569706,66B / 1024 / 1024 / 1024 = 1.66GB</div><div> </div><div>     so for every extra 1TB of storage, system needs extra 1.66GB RAM.</div><div><br/></div>
<br/>'''IMPORTANT: '''The above calculations only apply to the worst case scenario, when data is completely unique and will not be deduplicated. For the deduplicable data, the need for RAM drastically decreases. If SSD based Read Cache is present, part of deduplication table will be moved to the SSD and deduplication will work with good performance using less RAM.

<br/>'''IMPORTANT: '''With SAN (iSCSI) it is CRITICAL to match User-File-System format block size with the zvol volume-block-size. A simple example is a Windows file system NTFS with default format block size 4k and zvol default volume-block-size is 128k. With defaults like this deduplication will mostly NOT match because files can be aligned in 32 (128/4) different positions on the pool. If the NTFS format is increased to 64k and the zvol default volume-block-size is 128k, deduplication match can fail only one time because a file can be aligned to 2 (128/64) different positions on the pool. Every next write will match already as both alignment options already exist on the pool. In order to achieve all files matching and efficient memory usage NTFS must use 64k format block size and the zvol volume-block-size must equal 64k. Another option is that the NTFS=32k and zvol=32k, but in this case the deduplication table will be twice as large. That is why the NTFS=64k and zvol=64k is the most efficient setting for deduplication.

'''IMPORTANT: '''With NAS (NFS, SMB/CIFs) deduplication matching works always due to the data blocks being aligned by ZFS natively.

'''IMPORTANT: '''De-duplication is working on the pool level in the pool-range. This is why zvol-Physical size cannot show de-duplication benefit. In order to prove that deduplication saved space run the scrub and notice the current physical data space on the pool reported by the scrub. Next copy of new data and run the scrub again. Now scrub will show new physical data space. Comparing the data size from storage client side with the data space growth from the scrub will give the deduplication advantage. The exact pool of the deduplication ratio can be found in LOGs in zfs.log.

=== Zvols configuration issues and recommendations ===

     It is strongly recommended to set the client file system block size same as the zvol volume block size. For example, when using 64k zvol volume block size, the Windows Allocation unit size of NTFS should be set to 64k.

=== Target number limit ===

    In case of more than 60 targets, GUI will not be displayed correctly. This issue will be fixed in the next releases.

=== Targets with the same name are not assigned correctly ===

    Having two or more targets with the same name but belonging to various Zpools, will cause that all targets with the same name will be assigned to one Zpool during the import process.

=== Installation on disks containing LVM metadata ===

     There is no possibility to install the system on disks containing LVM metadata. You will need to clear those disks before installation. To do so, use the “Remove ZFS data structures and disks partitions” function located in the Extended tools. To access this function, boot the system from a temporary media like a USB drive or DVD.

=== Import Zpool with broken write log ===

     There is no option to import Zpool with a broken write log disk using the system’s functions. This is why it is STRONGLY recommended to use mirrored disks for write logs. In case it is necessary to import Zpool with a broken write log, please contact technical support.

=== Replacing disks in data groups for larger ones can cause your storage license capacity to be exceeded ===

     In case of replacing damaged disks for larger ones, the size of the entire Zpool will increased. Make sure that the new size will not exceed your purchased storage license.

=== Periodically after some operations, the GUI needs to be manually refreshed ===

     After performing some operations, e.g. resilvering, the GUI will show outdated information. In this case refresh the web page manually by pressing F5 on your keyboard. This issue will be fixed in next releases.

=== Replacing disks in data groups for smaller ones can cause an error and make the disk disappear from the list of available disks ===

     Operation of replacing a disk in a data group for a smaller one will cause an error "zpool unknown error, exit code 255", and the disk will become unavailable. In order to reuse this disk, please use function "Remove ZFS data structures and disks partitions" located in the Extended tools on the Console screen.

=== It is strongly recommended to use 64KB or higher Volume block size ===

     Smaller than 64KB block sizes used with deduplication or read cache will cause very high memory consumption.

=== RAM recommendations for Read Cache ===

     To determine how much System RAM is required for Read Cache, use the following formula:

<br/> <br/>                                                                      RAM needed = (Size of Read Cache - reserved size and labels) * bytes reserved by l2hdr structure / Volume block size<br/> 

     For 8KB Volume block size and 1TB Read Cache:<br/><br/>                                                                           RAM needed = (1099511627776B - 4718592B) * 432B / 8192B = 57981809664B<br/>                                                                                                        57981809664B / 1024 / 1024 / 1024 = 54GB<br/> <br/>Where:<br/>1099511627776B - 1TB Read Cache<br/>4718592B - reserved size and labels<br/>432B - bytes reserved by l2hdr structure<br/>8192B - Volume block size<br/> <br/>                                                                                                  For 64KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 65536B = 7247726208B<br/>                                                                                                       7247726208B / 1024 / 1024 /1024 = 6.75GB<br/><br/><br/>                                                                                                  For 128KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 131072B = 3623863104B<br/>                                                                                                       3623863104B / 1024 / 1024 /1024 = 3.37GB

=== Multiple GUI disk operations may result in an inaccurate available disks list ===

     Multiple operations of adding and detaching disks from groups can cause that the next operation of detaching will fail, but the disk will be shown on a list of available disks. When trying to add this disk to one group it will fail with the following error "[zfslib-wrap-zpool-ZpoolCmdError-1] invalid vdev specification". In this case, detach this disk once again.

=== After removing disks from groups they may not be displayed on a list of available disks ===

     Sometimes after removing disks from groups, Spare/Read Cache/Write Log disks are displayed on a list of unassigned disks, but they are not on a list of available disks. In this case, click the rescan button located in the adding group form.

=== Reusing disks from an exported and deleted Zpool ===

     After deleting an exported Zpool, not all disks which were a part of a Zpool become immediately available. Before you can reuse disks, which were previously used as a Spare or a Read Cache, you must first clean them. Use “Remove ZFS data structures and disks partitions” function located in the “Extended tools”.

=== Negotiated speed of network interfaces may not display correctly ===

     For some network interfaces, the negotiated speed field may display an incorrect value in GUI and Console. This issue will be fixed in next releases.

=== Limited possibility to display a large number of elements by the GUI ===

     After creating multiple snapshots, clones or zvols some forms in GUI work very slow. If you need to create many snapshots, clones or zvols, it is strongly recommended to use CLI in order to perform operations on them.

=== Open-E VSS Hardware Provider system recommendations ===

     It is strongly recommended to use Windows Server 2012. On the other Windows systems, Open-E VSS Hardware Provider Configuration works unstable.

=== Exceeded quota for dataset does not allow to remove files ===

     Files located on datasets with exceeded quota cannot be removed. In this case, please resize quota and then remove unnecessary files.

=== Slow WebGUI with multiple datagroups ===

     Zpool with more than 20 datagroups causes that some forms on WebGUI work very slow. If you need to create many datagroups, it is strongly recommended to use CLI API.

=== Slow WebGUI with multiple datasets ===

     More than 25 datasets cause that WebGUI works slow.

=== ZFS Upgrade ===

     For Open-E JovianDSS users, it is recommended to upgrade Zpools to the latest ZFS file system. Although the file system upgrade is absolutely safe for your data, and takes only few minutes, please be aware that this operation cannot be undone. In order to upgrade a single Zpool, please use "WebGUI -> Zpool options -> Upgrade file system" from Zpool's option menu.

=== Intel® Ethernet Controller XL710 Family ===

     In case of using Open-E JovianDSS with Intel® Ethernet Controller XL710 Family, it is necessary to update firmware’s network controller to the version: f4.33.31377 a1.2 n4.42 e1932.

=== Motherboards with x2APIC technology ===

     In case of using a motherboard with x2APIC technology enabled, it is necessary to disable x2APIC in BIOS. Otherwise, problems with CPU cores will occur.

=== NFS FSIDs and Zpool name ===

     One of the factors that have been taken into account when NFS FSIDs are generated is Zpool name. It indicates that when Zpool name is changed, e.g. during export and import with different names, FSIDs for NFS Shares located on this Zpool will also be changed.

=== High Availability shared storage cluster does not work with Infiniband controllers ===

     Due to technical reasons the High Availability shared storage cluster does not work properly when using the Infiniband controllers for VIP interface configuration. This limitation will be removed in the future releases.

=== Disks with LVM data cannot be used with the created Zpool ===

     Attempt to create Zpool with drives that contain LVM data will fail with the following error:

''"cannot open 'lvm-pv-uuid-R25lTS-kcDc-eiAN-eAlf-ppgi-rAqu-Oxy1Si': no such device in /dev must be a full path or shorthand device name"''

In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.

=== Unexpected long failover time, especially with HA-Cluster with two or more pools ===

     Current failover mechanism procedure is moving pools in sequence. Since up27 release, up to 3 pools are supported in HA-cluster. If all pools are active on single node and failover needs to move all 3 pools, the failover may take longer than 60 seconds which is a default iSCSI timeout in Hyper-V Clusters. In some environments, under heavy load a problem with too long time of cluster resources switching may occur as well. If the switching time exceeds the iSCSI initiator timeout, it is strongly recommended to increase the timeout up to 600 seconds.

     '''In case of using Windows, to increase iSCSI initiator timeout, please perform following steps:'''

1. Run regedit tool and find: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\...\Parameters\MaxRequestHoldTime registry key''

2. Change value of the key from default 60 sec to 600 sec (decimal)

     '''In case of using VMware, to increase iSCSI initiator timeout, please perform following steps:'''

1. Select the host in the vSphere Web Client navigator

2. Go to Settings in the Manage tab

3. Under System, select Advanced System Settings

4. Choose the ''Misc.APDTimeout'' attribute and click the Edit icon

5. Change value from default 140 to 600 sec.

     '''In case of using XenServer, to increase iSCSI initiator timeout, please perform following steps:'''

A. For existing Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Detach and reattach SRs. This will update the new iSCSI timeout settings for the existing SRs.

B. For new Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Create the new SR. New and existing SRs will be updated with the new iSCSI timeout settings.

=== Activation may be lost after update ===

     In some environments, after update to up11 system may require re-activation. This issue will be removed in the future releases.

=== Bonding ALB and Round-Robin do not work in Hyper-V and VMware environments ===

     In case of using JovianDSS as Hyper-V or VMware guest, bonding ALB and Round-Robin is not supported. Please use another type of bonding.

=== Continuous writing in VMware guest can cause that deleting VMware snapshot can take long time ===

     Using ODPS on zvol/dataset with VMware guest where many I/O operations are performed can cause that the process of deleting VMware snapshot can take long time. Please take this into consideration while you set up the scheduler for Off-site Data Protection Service task.

=== Enabling quota on dataset can cause file transfer interrupt ===

     Enabling quota functionality on a dataset can cause file transfer interrupt. Before using it in production environment, please enable quota on dataset, or make sure that no file transfers are active.

=== Nodes connected to the same AD server must have unique Server names ===

     If JovianDSS nodes are connected to the same AD server, they cannot have the same Server names.

=== Share can not be named the same as Zpool ===

     In case of share with the same name as Pool connections problem will occur. Please use different names.

=== No persistent rules for network cards in virtual environment ===

     Changing settings of virtual network cards (delete, changing MAC, etc.) can cause unstable system behaviour. Please do not change settings on production system. This issue will be fixed in next releases.

=== Downgrade to up17 or earlier is not possible ===

     Starting from up18 bootable medium has always SW RAID structure. Attempt to come back to earlier version is impossible. If you need come back to earlier version, you must reinstall version again.

=== System cannot be installed on cciss based controllers ===

     This issue will be fixed in next releases.

=== Interrupt the process of adding second disk to SW RAID (bootable medium) can cause run system from disk with uncompleted data ===

     Performing operation like: reboot, shutdown, power off, etc. during mirroring data on new added disk can cause that system will be booted from new disk which has incomplete data. In this case, SW RAID function shows empty status and wrong number of RAID members. To resolve this issue, please plug off disk which has incomplete data, boot system, plug in disk and add it once again to SW RAID.

=== SAS-MPIO cannot be used with Cluster over Ethernet ===

     It is strongly not recommended to use Cluster over Ethernet with SAS-MPIO functionality. Such a configuration can lead to a very unstable cluster behavior.

=== On- & Off-site Data Protection backward compatibility problem ===

     In case of using On- & Off-site Data Protection functionality in up21 or earlier, it is strongly recommended to remove all backup tasks created by CLI API and re-create it using GUI.

=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===

     In FC Target HA environment, power cycle of both nodes simultaneously may lead to a situation when VMware is not able to restore proper state of the storage devices. In vSphere GUI LUNs are displayed as Error, Unknown or Normal,Degraded. Moving affected pools to another node and back to its native node should bring LUNs back to normal. A number two option is to restart the Failover in Jovian’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.

=== Problem with maintenance in case of disk failure ===

     In case of disk failure, please remove the damaged disks from the system, before starting administrative work to replace the disk. The order of actions is important.

=== Separated mode after update from JovianDSS up24 to JovianDSS up25 ===

     In HA cluster environment after updating of one node from JovianDSS up24 to JovianDSS up25 the other node can fall into separated mode and the mirror path might indicate disconnected status. In such a case go to Failover Settings and in the Failover status section select Stop Failover on both nodes. Once this operation is finished select Start Failover.

=== Different Write Cache default setting for zvols in early beta versions of Jovian DSS up25 ===

     In the early beta versions of JovianDSS up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of Jovian up25 the Log bias is set to “Write log device (Latency)”.<br/>Please note, that “In Pool (Throughput)” setting may cause a drop in performance in environments with a lot of random access workloads which is a common factor for a majority of production environments.

=== Target alias name is required while configuring HA FC Target in case of adding two or more ports to one FC group ===

     If we want to have more then one port in each FC group (in HA FC configuration) it is necessary to type in Target alias name for every port. Otherwise an error message “Target alias is already used” can show up while setting up remote port mapping for FC targets in (pool name) -> Fibre Channel -> Targets and initiators assigned to this zpool. This issue will be resolved in the future release.

=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===

     In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of Jovian up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open Jovian TUI and use CTRL+ALT+W key combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select qla2xxx_scst QLogic Fibre Channel HBA Driver and make sure the value of this parameter is set to “exclusive”.<br/><br/>Please note that in order to change this parameter Failover must be stopped first.

=== Very low performance of FIO/WT in case of mixed FIO/WT and FIO/WB zvol configurations over Fiber Channel ===

     In case of the mixed FIO/WT and FIO/WB zvol configurations over FC one can observe significantly decreased performance on FIO/WT.

=== More than one zvol with FIO/WB mode can cause instability of the Fiber Channel connection ===

     If there's more than one FIO/WB zvol or a FIO/WB zvol is coexisting with other types of zvols it can cause an instability of the FC connection with client machines. As a result client machines may unexpectedly lose FC connected resources.

=== In certain situations system page cache is not able to flush File I/O errors by itself and cache flushing has to be performed manually ===

     Under certain conditions (like overfilling zvol and then expanding its size) some File I/O errors may be held by the system page cache and it requires manual flushing (in GUI use Storage -> Rescan).

=== Updating nodes of the Jovian cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===

     There is a significant difference in FC configurations in up24 and earlier versions. Those versions allowed the FC ports to be configured in initiator mode only, while later versions allow both target and initiator mode with target as default, so in case of using storage connected via FC initiator, FC port(s) must be manually corrected in GUI of the updated node.

=== Updating Metro Cluster node with NVMe disks as read cache from JovianDSS up26 or earlier can cause the system to lose access to the NVMe disks ===

     The process of updating of Metro Cluster node from JovianDSS up26 or earlier is changing NVME disk IDs. In consequence moving pool back to updated node is possible but the read cache is gone (ID mismatch). In order to bring read cache back to the pool we recommend to use console tools in the following way: press Ctrl+Alt+x -> “Remove ZFS data structures and disks partitions”, locate and select the missing NVMe disk and press OK to remove all ZFS metadata on the disk. After this operation click Rescan button in GUI -> Storage. The missing NVMe disk should now appear in Unassigned disks at the bottom of the page which allows to select that disk in pool’s Disk group’s tab. Open Disk group tab of the pool, press the Add group button and select Add read cache. The missing disk should now be available to select it as a read cache.

=== Synchronization of a large LDAP database can last for a long time (e.g. 10h for 380K users) and can be associated with high system load ===

     This problem will be solved in future releases.

=== Long time of a failover procedure in case of Xen client with iSCSI MPIO configuration ===

     In a scenario where Xen client is an iSCSI initiator in MPIO configuration, the power-off of one node starts the failover procedure that takes a very long time. Pool is finally moved successfully but there are many errors showing up in dmesg in meantime. In case of such an environment we recommend to add the following entry in the device section of the configuration file: /etc/multipath.conf:

'''no_path_retry queue'''

<br/>The structure of the device section should look as follows:
<pre>device {
vendor "SCST_FIO|SCST_BIO"
product "*"
path_selector "round-robin 0"
path_grouping_policy multibus
rr_min_rio 100
no_path_retry queue
}
</pre>
[[Category:Release Notes]]

Share group

2020-09-18T08:31:49Z

Ma-W:

This functionality is available in: User Management > Share users/groups > Share users and groups > Share groups > Add group

Here you can configure name for the new group.

'''Note:''' The name should have 1 to 20 characters: a-z A-Z 0-9 - _. It can't start or end with a space or contain several spaces in a row.

You are also able to add users to a group. To do so:

#Specify the name for a group.
#Go to the Group users section.
#Select users to be added to the group.
#Click the '''Apply''' button.

[[Category:Help topics]]

Share user

2020-09-18T08:30:29Z

Ma-W:

This functionality is available in: User Management > Share users/groups > Share users and groups

Here you can configure name and the password for the new user. To add a new user to the system, the Lightweight Directory Access Protocol (LDAP) should be enabled.<br/><br/>'''Name''': The value in the '''Name''' field should have 1 to 20 characters: a-z A-Z 0-9 - _. It can't start or end with a space or contain several spaces in a row.<br/>'''Password''': The minimum length for this field is 6.

To add a new user:

#Go to the User Management section.
#Go to the Share users/groups tab.
#Go to the Lightweight Directory Access Protocol (LDAP) subsection.
#Make sure LDAP is enabled.
#Go to the Share users and groups section.
#Expand Share users subsection.
#Click '''Add user'''.
#In the window that appears, enter the values in the '''Name''', '''Password''', and '''Password confirmation''' fields.
#Click '''Apply'''.

To add a a new group:

#Go to the User Management section.
#Go to the Share users/groups tab.
#Go to the Lightweight Directory Access Protocol (LDAP) subsection.
#Make sure LDAP is enabled.
#Go to the Share users and groups section.
#Expand share groups subsection.
#Click '''Add group'''.
#In the window that appears, enter the value in the '''Name''' field.
#Click '''Apply'''.

[[Category:Help topics]]

CreateNewPool

2020-04-16T13:33:48Z

Ma-W: Redirected page to Zpool wizard

#REDIRECT [[Zpool wizard]]

SetTime

2020-04-16T13:31:55Z

Ma-W: Redirected page to Time and date settings

#REDIRECT [[Time and date settings]]

Snmp Settings

2020-04-16T13:30:43Z

Ma-W: Redirected page to SNMP settings

#REDIRECT [[SNMP settings]]

SnmpConfig

2020-04-16T13:26:41Z

Ma-W: Redirected page to SNMP settings

#REDIRECT [[SNMP settings]]

SnmpConfig

2020-04-16T13:23:12Z

Ma-W: Redirected page to Snmp settings

#REDIRECT [[Snmp settings]]

DefaultGateway

2020-04-16T12:44:29Z

Ma-W: Redirected page to Default gateway

#REDIRECT [[Default gateway]]

CreateNewUser

2020-04-16T11:37:42Z

Ma-W: Redirected page to Discovery CHAP user access

#REDIRECT [[Discovery CHAP user access]]

Data Migration Tool

2020-03-31T11:49:18Z

Ma-W:

Functionality allows user to migrate data from DSSV7 NAS shares to the Open-E JovianDSS.

Below the list of steps that need to be done in order to migrate data:

'''On Open-E JovianDSS:'''

#Create zpool
#Create dataset
#Enable Data Migration Tool in Extended tools under console (CTRL+ALT+X)

<br/>'''On DSSV7:'''

#Create Data Replication Task (DREP) using IP of JovianDSS as a destination IP and selecting source and destination shares from where to where data need to be migrated.
#Start the task and wait till task completes.

<br/>'''Important notes:'''

#While Data Migration Tool is turned on data sharing protocols on JovianDSS will be disabled.
#Any changes made to shares configuration on JovianDSS, while Data Migration Tool is running, will be reflected by the tool after restarting it.
#After completing migration process it is Administrator role to turn off the Data Migration Tool.
#After rebooting the system Data Migration Tool becomes automatically turned off.

[[Category:Help topics]]

Edit fc group properties

2020-03-31T11:49:08Z

Ma-W:

This function allows modifying FC group alias. Alias of a FC group can be modified at any time, it doesn’t have any influence on the physical FC configuration. For more information about FC groups please refer to the FC groups section.

[[Category:Help topics]]

Virtual IPs

2020-03-12T10:37:55Z

Ma-W:

<span id="docs-internal-guid-178eff9a-7fff-bb24-bcf6-670490bfaf23"><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">This option allows you to add a virtual IP to provide services. To add a virtual IP, click the '''Add Virtual IP''' button in the Storage section of the Virtual IP tab. The following data is required:</span></span>
<ul style="margin-top: 0px; margin-bottom: 0px;">
<li><span id="docs-internal-guid-178eff9a-7fff-bb24-bcf6-670490bfaf23"><span style="font-size: 10pt; background-color: transparent; font-weight: 700; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">Virtual IP address </span><span style="font-size: 10pt; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">- the address by which the services will be granted.</span></span></li>
<li><span id="docs-internal-guid-178eff9a-7fff-bb24-bcf6-670490bfaf23"><span style="font-size: 10pt; background-color: transparent; font-weight: 700; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">Name </span><span style="font-size: 10pt; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">- the name used by the virtual IP.</span></span></li>
<li><span id="docs-internal-guid-178eff9a-7fff-bb24-bcf6-670490bfaf23"><span style="font-size: 10pt; background-color: transparent; font-weight: 700; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">Netmask </span><span style="font-size: 10pt; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">- the subnet mask assigned to the virtual IP address.</span></span></li>
<li><span id="docs-internal-guid-178eff9a-7fff-bb24-bcf6-670490bfaf23"><span style="font-size: 10pt; background-color: transparent; font-weight: 700; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">Network interface </span><span style="font-size: 10pt; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">- the network interface used in the local server by the virtual IP.</span></span></li>
<li><span id="docs-internal-guid-178eff9a-7fff-bb24-bcf6-670490bfaf23"><span style="font-size: 10pt; background-color: transparent; font-weight: 700; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">Remote network interface </span><span style="font-size: 10pt; background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">- the remote network interface used in the remote server by the virtual IP.</span></span></li>
</ul>

<span id="docs-internal-guid-178eff9a-7fff-bb24-bcf6-670490bfaf23"><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">Once everything is set, press </span><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-weight: 700; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">Apply </span><span style="font-size: 10pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; font-variant-numeric: normal; font-variant-east-asian: normal; vertical-align: baseline; white-space: pre-wrap">to add a virtual IP.</span></span>

[[Category:Help topics]]

FC target assigned to pool properties

2020-03-12T10:22:32Z

Ma-W:

The article describes how to assign FC target to pool properties when using HA cluster or single node configuration. In general, this function allows modifying target alias and assigning a remote target. In addition, if you would like to learn about FC target replacement, read this article: [http://wiki.open-e.com/default/wiki/FC_target_replacement http://wiki.open-e.com/default/wiki/FC_target_replacement]

== High Availability cluster configuration ==

Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In a cluster environment, when a pool has to be moved to other node, it is is required to know which target should be used there to serve FC groups resources. To properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups.

The cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. The initiator accesses LUNs by using an active path and a standby path is used for a target that doesn’t have access to LUNs. The active path is set for a target, when the pool is present on the same node where the target is. The standby path is used for a target, when a pool is present on the other node. When a cluster moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, the ALUA configuration is not created by a cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs the configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after the cluster is started, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after the assignment of a remote target, please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite the modification of path statuses.

<br/>In summary, to correctly set up targets for a cluster usage, do the following:

*Select a remote target for each target assigned to FC groups.
*Switch a selected remote target on a remote node to a target mode.

== Single node configuration ==

There is no possibility to pair the target with a remote node because ALUA is not used. In case when the pool is imported with an FC configuration from another machine, it is neccessary to assign FC targets to FC ports of the current server. This is due to the fact that the system is unable to determine on which ports it has to share resources.

[[Category:Help topics]]

Static routing

2020-03-12T09:57:44Z

Ma-W:

<span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.8px">By using this manager, you are able to manually enter and remove static routes to/from a routing table. The manager allows configuring routes to a subnetwork or to specific hosts. The order of entries in the routing table is important.</span>

<span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.8px">'''Note:''' Configuring static routes for interfaces that are a part of the cluster is impossible.</span>

[[Category:Help topics]]

MPIO disks

2020-03-12T09:40:48Z

Ma-W:

The MPIO disks function lists all the configured MPIO devices (disks which are available through more than one path will be automatically configured as an MPIO device and will be also listed).

For each MPIO device the available and currently used paths, as well as the MPIO status are visible.<br/>Available MPIO statuses: Pending setup, OK, Unknown.

'''Pending setup''' - postponed until the Pool is exported and later until:

*the Pool is imported
*or the system restarted
*or in case of a cross SAS cluster - for moving the resources (Pool) to the second node and back.

'''Unknown''' - MPIO configuration present in the system but not active<br/>'''OK''' - MPIO device configured and running

MPIO devices can be collectively edited (by selecting specific devices) and using the “'''Edit selected'''” button or separately  by using “'''Edit disk'''” from the form in which “'''Remove failed paths'''”, “'''Disk details'''” and “'''Delete'''” functions are available.

'''Important:'''

It is not possible to delete the MPIO device which has two or more available paths. In order to delete such device it is necessary to remove the paths (to unplug the cables) and then use the "Delete" function.

'''Important:'''

In case of using remote disks for cluster over Ethernet functionality, the MPIO devices configuration will be postponed until the system is restarted.

[[Category:Help topics]]

MPIO available disks

2020-03-12T09:35:53Z

Ma-W:

Available disks function lists the disks which are connected with one path only and that are not configured as a part of MPIO devices.<br/>This function enables a manual configuration of those disks (with one path) as part MPIO devices. It is also possible to check details of individual disks.

'''Important:'''<br/>Disks on which Pools are located are also listed – in this case, the configuration of an MPIO appliance will be postponed as pending setup until the Pool is exported,<br/>and later until:

*the Pool is imported
*or the system restarted
*or when using a cross SAS cluster for moving the resources (Pool) to the second node and back.

'''Important:'''<br/>In case of using remote disks for cluster over Ethernet functionality, the MPIO devices configuration will be postponed until the system is restarted.

'''Important:'''<br/>Listed are also the disks which are available through more than one path and which were deleted from the MPIO devices in the MPIO disks section form - keep in mind<br/>that the MPIO device will be automatically configured after the system restart, as it is for all disks connected to the system through more than one path.

[[Category:Help topics]]

File:Workgroup guest.png

2020-03-02T10:56:58Z

Ma-W: Ma-W uploaded a new version of "File:Workgroup guest.png"

Share groups

2020-02-26T09:21:39Z

Ma-W: Redirected page to Group access

#REDIRECT [[Group access]]

Share users

2020-02-26T08:08:19Z

Ma-W: Redirected page to User access

#REDIRECT [[User access]]

Spotlight service

2020-01-31T15:53:58Z

Ma-W:

The Spotlight service, available only for macOS machines, allows you to search files on the attached share based on name, metadata, and size. The Open-E JovianDSS creates an index and that index is being used by the client's machine. Bear in mind that no local copy of an index on the client's side is being created. Thus, each new user does not have to generate an index for files once the Spotlight service in Open-E JovianDSS has been enabled. The support for Spotlight service has to be enabled. The SMB service has to be restarted after enabling Spotlight. This option is available after enabling SMB for a given share.

The Spotlight's service database and index are updated during an upload or modification of data on datasets. If the pool that was currently used is exported, or could not be used due to the lack of space, the last imported or created pool will be used for the Spotlight service. The index is also placed on the pool. For example:

*Pool-0 is created, Spotlight is enabled and pool-0 database is used.
*Pool-1 is created, Spotlight is enabled and still database from pool-0 is used.
*Pool-0 is exported and the database from pool-1 is used.
*Pool-0 is imported and the database from pool-1 is used.

'''Note''': Once the service has been enabled, a dataset called _spotlight-db-dataset will be added.

[[Category:Help topics]]

Spotlight service

2020-01-31T15:53:28Z

Ma-W:

Repair failed disk

2020-01-31T15:09:09Z

Ma-W:

You will find the list of all available disks in the system. Each disk in the list is represented by  :

*'''Name'''
*'''Serial Number'''
*'''Model'''
*'''Size'''

To select a disk that should be replaced by a new disk, you have to point to the '''indicator.'''

In the main '''Group''' view, you will see the position "replacing-xy", that will contain names of the drives that will be changed. 

[[Category:Help topics]]

Deduplication

2020-01-31T15:05:40Z

Ma-W:

Deduplication is a process that eliminates redundant copies of data and reduces storage overhead. In turn, the deduplication ratio is the measurement of the zpool's data original size versus the data size after removing redundancy. Deduplication can be set on zvols or datasets but the deduplication ratio is displayed per pool instead of single zvols or datasets because they are located on the pool.

'''Note: '''It is not recommended to use deduplication in systems whose primary aim is to provide efficiency and fast data access in case when High Availability cluster is enabled. In certain conditions, the deduplication table may crash and rebuilding it while importing the pool may take a lot of time or even lead to improper functioning of a failover.

== Things to be taken into consideration ==

Before using deduplication, the following matters should be taken into account:

*hardware - deduplication is very memory consuming so if simultaneously the system would have to process the current tasks, it may significantly slow down its efficiency
*need for quick access to the data - when archiving or backing up the data as it saves the disk space. In case when there is a small amount of repetitive data, deduplication can only cause longer write times.

It is also worth to calculate memory requirements in the following way:

*deduplication table (DDT) entry that is equal to about 320 bytes should be multiplied by the number of allocated blocks by 320. For example: DDT size (1.08MB) x 320 = 345,6‬ meaning that this amount of memory is required for deduplication

Once deduplication is enabled, it has an impact on the whole pool since it creates the global DDT array with deduplication indicators. When deduplication is disabled, '''Zpool storage deduplication rate''' is set to 1. If the value is greater than 1, then the deduplication operation has taken place. Disabling deduplication will not cause the value to return to 1.

== Removing deduplicated data ==

Deduplicated data must be rearranged after deduplication has been disabled on zpool by performing the send/ receive operation on the pool. The '''Zpool storage deduplication rate''' will be reset to 1, otherwise old data will be left in deduplication state.

To remove deduplicated data, disable deduplication and transfer data from sources which had deduplication enabled to a different place where deduplication is not enabled.

If the deduplication ratio on the given pool returns to value 1.0 it is possible to assume that there are no deduplicated data on the pool.

[[Category:Help topics]]

Deduplication

2020-01-31T15:04:34Z

Ma-W:

Add Pool Initiator window

2020-01-31T12:35:26Z

Ma-W: Redirected page to FC initiator

#REDIRECT [[FC_initiator]]

Share users list

2020-01-31T12:33:47Z

Ma-W: Redirected page to User access

#REDIRECT [[User access]]

Hardware monitoring

2020-01-31T12:33:05Z

Ma-W: Created page with "<span style="font-size:13px; color:#000000; font-weight:normal; text-decoration:none; font-family:'Arial'; font-style:normal; text-decoration-skip-ink:none">Hardware monitorin..."

<span style="font-size:13px; color:#000000; font-weight:normal; text-decoration:none; font-family:'Arial'; font-style:normal; text-decoration-skip-ink:none">Hardware monitoring</span>

Edit Sensor

2020-01-31T12:30:23Z

<span style="font-size:13px; color:#000000; font-weight:normal; text-decoration:none; font-family:'Arial'; font-style:normal; text-decoration-skip-ink:none">Edit Sensor</span>