You're very welcome.
Ya, I figured as much while writing my message and thinking about it. But needing 2 SSDs in order to be able to use the Landing Zone is asking a lot; they're not cheap, and motherboard SATA connectors are at a premium too. So far, without having tried either, I prefer DrivePool over DriveBender simply because support is much better here, but DB does not need 2 SSDs for its Landing Zone...
Well, they have dropped in price recently, but yeah, the SATA connectors are a premium still (even if you get controller cards, they can be very expensive, very quickly).
And as I said, if you disable realtime duplication, that should "fix" the issue, although with the mentioned caveats. Not idea, but it works.
Yes, I was going to get there, and ask about locks and duplication at some point, in another thread. So you are saying that Real Time Duplication hooks low enough on the storage stack that you can duplicate even while the file is locked?
Yup, Specifically, with Real Time duplication, any time you write or modify data on the pool, the writes are done to all copies of the file in parallel.
Essentially, the driver works as a proxy for the file system (this is a drastic oversimplification), and with real time duplication enabled, any file system commands (creating/modifying/etc) are sent to all destination disks at the same time. So locking will not affect the software's ability to write the data.
Alex (the developer) has a good post that goes over this feature (from the alpha version years ago), that may be worth taking a read:
And if you disable real time duplication, then this occurs at 2AM normally. However, this can be changed by creating the advanced config file (a "default" version will always be present after installing or updating).
Set the "FileDuplication_DuplicateTime" to a valid time, and this is when it will run a duplication pass.
Also, changing the duplication status should trigger a duplication pass, and the pool condition indicator (at the bottom) should allow you to re-duplicate manually.
Yes of course, if you always fill one disk before the others, content will tend to be grouped by folder, but I was hoping that "Folder Balancing" (for lack of a better term) had been added to DP (it was mentionned in another old thread in this forum). Ideally I'd want to fill disks using the default settings (most empty disk first) but grouped by folder. To repeat the example the other guy used, I'd want all 10 tracks of a music CD on a single physical disk (which 10 files are all in one folder) just to make things simpler when accessing the disks when the pool is offline, while still filling-up disks most-empty-first...
Well, the Ordered File Placement will attempt to do so, but no, it's not guaranteed to do so.
I believe there is a feature request pending for this already (a balancer that will specifically keep the contents of folders together), and once StableBit CloudDrive is released, we (Alex) should at least get to it, whether or not it's implemented.
Though, as I mentioned, the "File Placement Rules" will allow you to do this, albeit completely manually. (though, you can also do neat things like adding a "\Music\*\*.mp3" to force the mp3 files onto a specific disk, while leaving other files to go anywhere... or add another rule for different extensions). But it sounds like it's not quite what you're looking for, though.