pest

Yea I couldn't find if it was truly only single file or single file to a single drive, where in my case there are multiple files and multiple drives to be utilized. Not sure how many others use multiple temp drives so maybe I'm a fringe case.

I've tried to read up on balancing limitation but I am either still missing something or my setup is not configured/working correctly. NAS Configuration: Folder duplication on the entire drive pool (including temp). NAS Hardware: 2x 500GB NVME WD Black drives (temp SSD optimizer storage with rules to auto balance) 6x WD RED's varying (3x10TB, 1x6TB, 2x4TB) I'm able to transfer from workstation to NAS > 1000MB/s over 10gbe to the NVME temp. When the NAS has MULTIPLE files to balance, it only migrates (and maxes out) 1 HDD at a time (see attached). My attachment is transferring ~10 files of ~40GB from my temp drives to the spinning rust archives. At least 4 out of 5 HDD have open space to transfer to based on the 90% fill rule. Currently it moves from 1 NVME to 1 HDD at a time, maxing out the HDD speed for each drive. Shouldn't this hit AT LEAST 2 HDD (1 for each NVME) or better yet max with multiple HDD per NVME given available multiple file transfers. In this example, my 2 NVME drives can saturate 5 HDD throughput of 10 files of 40GB at the same time. What am I missing? Does the single thread limitation still apply for multiple files from multiple drives to multiple sources (lol) ?

This might have been a better question for the general section, sorry. But I think I can accomplish what I want with the following settings 512GB nvme m.2 split into two partions, ~68gb OS and ~400GB cache. Real time duplication turned off Balance immediately turned on (with sub setting of "not more than" disabled) ssd optimizer installed 400 gb cache partion be the only flagged ssd fill ssd drives up to 0% With these setting every time a file is copied to the pool it lands on the nvme first then is migrated completely off the nvme duplicated in the pool itself. I don't believe I have any file lock concerns as I won't be accessing the new files until they've been duplicated in the pool and I don't run any kind of DBs. I might look into turning background balancing off to speed the copies to the pool as well (yes, server performance hit while occurring).

Thanks for the response Umfriend! Honestly, I'd never even considered their could be issues or specific settings needed to make plex work with DP. I'll definitely look into this to understand if I need to expect to do anything special. As for the immediate/delayed backup, there is a DP flag somewhere to disable the immediate duplication requirement that is turned on by default. I looked into this before I realized how old/slow the ssd in my server was for write speeds (130MB/s). Ok I just found one reference to disabling real time duplication here: I did not remember the file lock comment or one time a day statement. Guess I'll have to look into it more, I might have previously found an updated comment from someone if they improved it. Perhaps my memory of when I previously looked into it betrayed me. Atleast I plan of having both servers setup concurrently at first so I could tinker briefly with these kinds of options.

Hey guys, I'll preface by saying thanks for any responses. I'm in the process of basically overhauling my entire home network (cat6A wiring & ubiquity ecosystem immediately - 10G switch later this year), main workstation, and server (due to trickle down economics of workstation upgrade). My current server has met my needs for the past 5 years or so, but is a very basic (aging) win10 box with only spinners for mass storarge (30TB currently) and an old SSD OS drive that doesn't write any faster than the spinners, so I've not implimented ssd write caching (and am maxed out on SATA ports). The new server has 2 main goals, switch to a plex implementation for transcoding/remote viewing and take advantage of 10G home network (ssd write caching) for faster video transfers. My current workstation has a 512GB 950 Pro m.2 nvme drive that I've outgrown in capacity for my main workstation and will be replacing for my next build. I'd like to know if I can carryover this 950 pro drive as I transition my current workstation into my new home server to use as both the OS drive and the write cache for the server? I'm aware of the immediate duplication setting I will need to change. I'm not concerned about the time it takes to move data off the write cache to the duplicated drivepool. Can I use the 950 as an OS drive and the single write cache for my pool to maximize transfer speed for my future 10g network? If so should I plan on separating the OS from the write cache with different partitions or any other tips? Future Sever (mostly current WS parts): Intel 6700k, Asus Maximus VII Gene MB, 32 GB Ram (plan to use 1/2 for ram disk for plex transcoding), need to purchase 1660 super or p2000 for transcoding, used supermicro server chassis w/ x16 hot swap ordered, LSI SAS 9207-8i HBA, and migrate 30TB drivepool plus toss in a couple of random spinners that I have lying around and I didn't have room for before. No virtual machines or anything else taxing planned. Am I neglecting to see something? Thanks again for the help and suggestions!