Ability to control which drives are included in "largest free space" pool

[BrettB]

I got 3 drives on my NPVR server that I use for recordings. All 3 have have directories defined in the Extra Recording Directories. 1 of the drives is larger and slower, and I use it for long-term archiving, etc. 2 of the drives are smaller and faster and I use them for all of the active recordings by manually switching the default recording directory back and forth between them. I can't just use the "Record to directory with largest free space option" because then all of the recordings would go to my archive drive which isn't fast enough to handle the multiple simultaneous recordings.

It would be nice to be able to specify which directories/drives should be included in the "largest free space" pool used for that recording directory option.

[johnsonx42]

It used to be setup so that network locations wouldn't be included in the most free space calculation, so the solution for your scenario was to define the archive drive with a unc path even though it was local. However that was feature was broken (or the bug was fixed, depending on which way you looked at it) in one of the recent releases, so now there's no option.

I long ago proposed some way to set flags on recording locations to control usage, such as "Pool" (use automatically based on space), "No Pool" (i.e. don't use unless recording is explicitly set to that location), "Overflow Only" (i.e. use only when other Pool locations are full), etc. along with a minimum free space below which the drive is considered 100% full (implement as a simple bias on the free space calculation). Now that the other work-around is gone, perhaps it's time to implement something along these lines.

[BrettB]

I long ago proposed some way to set flags on recording locations to control usage, such as "Pool" (use automatically based on space), "No Pool" (i.e. don't use unless recording is explicitly set to that location), "Overflow Only" (i.e. use only when other Pool locations are full), etc. along with a minimum free space below which the drive is considered 100% full (implement as a simple bias on the free space calculation). Now that the other work-around is gone, perhaps it's time to implement something along these lines.

Yes, I saw this wishlist request. It would give even more flexibility. And would certainly cover my needs. Hopefully sub will consider some changes along these lines.