Hi Y'all

maybe it is already in the work, but I watched the uncast "Unraid Story" and heard about multiple pools and new features added to the mover like moving data across pools.

 

So i was wondering can we have a third storage option to a share?

like I have nvme as principal storage, a zfs Z1 ssd pool as secondary and the hdd array as third.

so i can move daily from the nvme to the ssd pool and have great speed read/write and then monthly move data from the ssd pool to the array for long term stored files.

 

like i said maybe it is in the work one way or another but that would be awsome

 

thanks team for the good work here 

I also mentioned the need for a third tier option in the mover settings now that we have complete freedom with how our pools are configured.

at the moment i have 2 pools (an NVME ZFS pool and a Sata SSD ZFS pool) and the array with some shares hitting one or the other first, and one share that never touches the array and is moved from one pool to the other but I would love the ability to control multiple tiers built into the mover.

 

 

 

 

 

 

 

 

I would like to extend that to n tier, so everyone is satisfied. There shouldn't be much difference between two, three, four or even more tiers. I don't think it makes sense to run all the tiers in parallel, that isn't the intention of tiers, but to have them chained or run at different times. Three workflows I can think of

• The schedule of the mover hasn't been overwritten
  • Run all the tiers in series
• The times have been overwritten (e.g. tier 2 daily (nvme -> ssd), tier 3 every week (ssd -> hdd))
  • Run them according to the cron jobs
• A mix of overwritten and default
  • Group them according to their times and run serial inside the groups
  • The most dangerous one, the user would have to make sure the groups don't overlap for best results

That could be extended indefinitely.

13 hours ago, Bastian said:

I would like to extend that to n tier, so everyone is satisfied. There shouldn't be much difference between two, three, four or even more tiers. I don't think it makes sense to run all the tiers in parallel, that isn't the intention of tiers, but to have them chained or run at different times. Three workflows I can think of

• The schedule of the mover hasn't been overwritten
  • Run all the tiers in series
• The times have been overwritten (e.g. tier 2 daily (nvme -> ssd), tier 3 every week (ssd -> hdd))
  • Run them according to the cron jobs
• A mix of overwritten and default
  • Group them according to their times and run serial inside the groups
  • The most dangerous one, the user would have to make sure the groups don't overlap for best results

That could be extended indefinitely.

adding my vote for this one too