Parmstig

I think the unify-controller when setup gets identified with the specific network adapter, if you make changes to network settings in the container then that network adapter is not present anymore, maybe try with Bridged network so it can access the same network as unraid.

Thank you for a quick reply

This may not be the best solution, please advice if that is the case - but this would be fun so i would like to make it work. The setup: *Array (tv and movie storage) 18TB * sys_hot (domains, isos, system) 1TB nvme * media_hot (docker like nzbget, sonarr, radarr and others) 2TB nvme * movie_warm (movie storage) 2x 8TB disk * tv_warm (tv storage) 2x 4TB disk So my idea of the flow between my shares would be. 1. downloads, unpacking, crc-checks on *Media_hot 2. Store finished downloads both TV and MOVIE on *Media_hot 3. mover: When media_hot is 80% full move TV to tv_warm and MOVIE to *movie_warm 4. mover: When tv_warm is 80% full move TV to Array 5. mover: When movie_warm is 80% move MOVIE to Array My background thinking for this is that my *media_hot can store stuff for a little while. It is a very fast nvme so its good for rsync to other devices. Since its only 2TB it will not hold for long but must transer TV and MOVIE to their specific ZFS Pools for a decent read-speed. Much later it will be transfered to array and saved for all eternity *maybe* 1. Hot: very fast drive 2. Warm: ZFS raid pool with two devices 3. Cold: only one 18TB but will be updated with another 18TB drive later on All mentions of specific software is only for educational purposes and i dont have a parity drive since i dont believe in failures. Is it possible to setup shares with primare -> secondary to achieve this?