Open-E JovianDSS Up30 Webinar Followup Package

Thank You for Participating in Our Webinar

We Have A Special Summary for You!

We hope that our event turned out to be inspiring for you! Open-E JovianDSS Up30 is our next step in improving data storage; thus, we are very glad that it generated such interest! If you would like to go back and relive the webinar once again, you can do it by watching the video on our YouTube channel:

But that’s not all! To sum up, all the most important points that Sebastian Reich, our Business Development Representative, referred to during the presentation, we would like to provide you with some helpful resources.

If you would like to explore the presentation freely, you can access it by clicking here.

For those of you who are concerned about Open-E DSS V7 End-of-Life, here are some materials that can help you prepare for this change:

• Open-E DSS V7 End-of-Life Brochure
• Article: Comparing Open-E DSS V7 and Open-E JovianDSS
• Article: Open-E DSS V7 End-of-Life Announcement

If you want to learn more about the two most important features added, be sure to watch our
Open-E JovianDSS Up30 video tutorials:

• How to Set Up ZFS Special Devices - Tutorial for the Open-E JovianDSS Up30 Version!
• How To Create Partitions on NVMe Disks - Tutorial for Open-E JovianDSS Up30 Version!

Your engagement during the event was amazing! Thanks to that, we managed to create a list with answers to the questions you asked during the webinar:

QUESTION: Is the recommendation to select the same redundancy level for the special devices as for the data groups (vdevs)?

ANSWER: No, having the same redundancy level on your data storage and Special Device vdevs is not necessary. For example, you can have your Pool configured on 2-way mirrors and a Special Device group using a 4-way mirror group. It is important, however, to remember to ensure redundancy for your Special Devices, as the loss of Special Device vdev means a complete data loss.

QUESTION: Are there any best practices from Open-E regarding the size distribution - Write Cache / Read Cache / Special Devices (Write Log doesn't have to be that big, you said at the beginning....)?

ANSWER: Write Log size is based on the network speed of storage access interfaces, but you can assume that using disks bigger than 400GB is a waste of space. Special Device vdev should be configured to have a size of approximately 10% of usable storage if it is used only for metadata offload. Read Cache serves as a secondary cache, so the bigger its size the better.

QUESTION: Regarding NVMe partitioning - can read/write cache and special devices be killed with 2x NVM devices?

ANSWER: Yes, in a minimal approach, you can configure two partitions on each NVMe drive, create a mirror on two of them for Write Log, and use the rest for Read Cache.

QUESTION: Do special devices on (SAS-) SSDs make sense, or only with NVMe drives.

ANSWER: Yes, as long as they are faster than the disks used in data group vdevs.