Future Unraid Feature Desires

[SpencerJ]

Unraid 6.12 will mainly feature ZFS as a new feature set.

 

What feature(s) are you most excited about for future Unraid stable releases?

 

[carp969]

Multiple Arrays - I have a bunch of SAS SSDs just waiting for a second array. They are too small for my data (2tb) but will make great storage for my exi nfs.

[Agent531C]

No native Docker-Compose option 🥲

[BRiT]

Multiple Unraid Array Pools.

 

It would be beneficial to have a storage product deliver actual storage functionality.

[TheLinuxGuy]

Hybrid or "tiered" storage (NVME + SSD + HDD). Where "hot" data is in NVME, then transitions down the stack. Least used data is on hdd. In other words; a QNAP qtier alternative.

[ocyberbum]

i would like vm snapshots or a way to easily install vmware workstation,  but Multiple Unraid Array Pools sounds good also!!

[hawihoney]

Multiple Unraid Array support.

 

And don't forget to enhance "New config" to work with more than one main Unraid array

 

Edited March 14 by hawihoney

[xSniper]

1. Multiple Unraid Array
2. ZFS
3. Intel Arc

[harshl]

Seems to me that if ZFS is implemented in its entirety, that multiple array pools will also essentially be implemented, no? At least it would be if you chose to use that file system.

 

In any case, I would really like to have VM snapshots implemented in the GUI in some way. It is such a powerful feature, and has been available in VMware products forever.

 

Thanks for a great product!

[JonathanM]

22 minutes ago, harshl said:

Seems to me that if ZFS is implemented in its entirety, that multiple array pools will also essentially be implemented, no? At least it would be if you chose to use that file system.

Multiple pools have been available for a while now. 6.12 adds the ability to use ZFS for those multiple pools.

 

It's the single volume per drive parity based array that is being proposed to have multiple instances. That style of array will likely always be restricted to single file systems on each member drive, thus the multi drive reliant features of ZFS will never be able to be used in the traditional Unraid parity array.

[BRiT]

4 minutes ago, JonathanM said:

Multiple pools have been available for a while now. 6.12 adds the ability to use ZFS for those multiple pools.

They said "multiple array pools", meaning something different than what is currently offered. At least that's how it reads to me.

Edited March 16 by BRiT

[glennbrown]

Native Docker Compose with it properly recognizing when a stack/container has been updated manually or via watchtower.

 

[harshl]

9 minutes ago, JonathanM said:

Multiple pools have been available for a while now. 6.12 adds the ability to use ZFS for those multiple pools.

 

It's the single volume per drive parity based array that is being proposed to have multiple instances. That style of array will likely always be restricted to single file systems on each member drive, thus the multi drive reliant features of ZFS will never be able to be used in the traditional Unraid parity array.

Ah yes, that makes sense!

[enJOyIT]

VM Snapshots like in proxmox ftw. So I can drop proxmox and use unraid on bare metal.

[Tucubanito07]

VM Snapshot please. 

[SLNetworks]

At one point it was possible to open the main "links" on top in a new tab if you held down "Command" on Mac or "Control" on Windows (and likely Linux). Lately when I've tried to do such, it opens in a new tab _and_ the current tab. Would be much appreciated if this was fixed.

 

It would be great if Machine Check Events were easier to observe and use. Updated documentation also.

[Wastl]

I'd really like to see an integrated backup solution for appdata, VMs and shares. And it should not be necessary to stop the containers and VMs for it.

[harshl]

2 hours ago, Wastl said:

I'd really like to see an integrated backup solution for appdata, VMs and shares. And it should not be necessary to stop the containers and VMs for it.

I think this essentially another vote for snapshots. Once the snapshot is taken you can copy that state of the data anywhere you want while everything is online.

Although, I suppose this might go a step further to say, let's not only snapshot, but give us a built in mechanism to copy the snapshot data elsewhere. Regardless, snapshots is key in my mind to enable any of this.

[SLNetworks]

Selective updates - ability to skip one or more container updates if certain containers are busy.

 

Might be pretty tedious to implement..

[night_rider]

multiple arrays for sure 

would also like arm virtualisation 

[KptnKMan]

Please GUI enhancements for VM control, like PCIe control, ReBAR control, PCIe Address management, more VM properties, control over more things without needing to edit XML directly, which gets wiped out if GUI interface is applied anytime after XML changes.

 

Would be the most amazing thing.

 

I already have nightly working running VM snapshots via script and VM Backup plugin.

Furthermore, there is already a working Appdata Backup plugin, these things are already available with existing plugins.

 

Array/share data backups are easy in script (I did it personally already).

Edited March 27 by KptnKMan

[SxC97]

I would like to cast a vote for some kind of clustering or high availability feature.

It probably won't be useful to most people, but I have 3 unraid servers. One networking NUC server thats on a dedicated UPS thats used for the most essential containers and VMs, one storage server that handle most backup and storage tasks, and a hypervisor thats used for running most vms. Having a way to automatically keep the most important VMs and containers up despite the hardware going down for maintenance would be a huge help!

I think VMware and TrueNAS both already have these features for VMs and containers respectively, and I think this would make Unraid a much more "professional" product, even if most of us are just using it at home.

Over time, as hardware gets cheaper and more accessible, I think more people will end up with multiple old computers that they can use for their home lab. Maybe you have 2 old laptops, or a couple of thin clients you bought in bulk on ebay. These machines can be put to better use in a home lab environment if they can be clustered together.

Just my 2 cents!

[KptnKMan]

4 minutes ago, SxC97 said:

I would like to cast a vote for some kind of clustering or high availability feature.

It probably won't be useful to most people, but I have 3 unraid servers. One networking NUC server thats on a dedicated UPS thats used for the most essential containers and VMs, one storage server that handle most backup and storage tasks, and a hypervisor thats used for running most vms. Having a way to automatically keep the most important VMs and containers up despite the hardware going down for maintenance would be a huge help!

I think VMware and TrueNAS both already have these features for VMs and containers respectively, and I think this would make Unraid a much more "professional" product, even if most of us are just using it at home.

Over time, as hardware gets cheaper and more accessible, I think more people will end up with multiple old computers that they can use for their home lab. Maybe you have 2 old laptops, or a couple of thin clients you bought in bulk on ebay. These machines can be put to better use in a home lab environment if they can be clustered together.

Just my 2 cents!

You may want to look into running Kubernetes VMs across your 3 nodes for this, or I'm not sure, if its possible to run K8s on the Unraid systems themselves.

K8s-on-Unraid-host might be something to aim for perhaps, if Unraid itself could be a K8s worker node. That would bring some interesting high-availability scenarios.

[Kwakx]

- Get rid of "array" and "pool", make one consistent with a choice of type and file system 

- Get rid of the requirement of one device in the "array", it just wastes licenses in my case

- Make a real cache e.g. for ZFS, wants to make use of my one nvme drive without compromising data 

[EDACerton]

I would really like two things:

 

1. Filesystem snapshots

2. LRU caching via SSD

Edited March 29 by EDACerton