fattipants2016

Anyone using backblaze with their (home) client? Are you pointing the client at the physical disks? Or at your drivepool drive letter? I saw their client doesn't rely on VSS, but I wasn't sure if pointing it at the pool would cause any additional overhead.

It's been enabled by default since I began using DP, and causes scary thrashing noises from some of my older Seagate 8tb's.

Seems to be working after nixing my additional partitions, blowing up my file placement rules and starting from scratch. I don't know if it was the partitions, or a broken rule that was causing the issue. Wish there was a bit more feedback from the software to let me know why it wasn't working, before. That took around 8 hours of file shuffling, and may have had nothing to do with it.

I tested again, and it's still broken, but I think it may have to do with my 2 of my member disks being partitions on the same physical disk. I'm going to rearrange my stuff and try again in a few days.

Not me who created a ticket, actually. Not in some time. It's going to be quite a bit of work right now to recreate the problem, because all of my file placement rules have to change with/without SSD optimizer. This is definitely not the expected behavior, before I try? This is the basic setup: E:\Videos\Movies (disk 1-5) E:\Videos\TV (disk 1) E:\Music (disk 2) E:\Games (disk 3) E:\Videos\*\*.srt (disk 5) E:\Videos\*\*.nfo (disk 5) E:\Videos\*\*.jpg (disk 5) Basically, music and TV are kept isolated on single disks to prevent an album / show stretching across more than 1. Movies go wherever / fill in gaps. Small files (like subtitles and metadata) are kept seperate (disk 5) which is backed up with Acronis. Files written to existing folders seem to follow the rules, while new subfolders and their contents ignore their parent folders rules until I balance the next time.

If, say, E:\Music is placed on drive 1, new files added to this folder are appropriately written to drive 1. If I create a new folder E:\Music\Test, it's written to the most empty drive, ignoring file placement rules (and then moved during balancing.) Is there any work around for this? My backup strategies rely on certain directories only falling on particular disks.

The most foolproof solution I've found is to move your archival storage to a dedicated machine, and create a network share with WORM access. I fooled around with Windows 10 'Controlled Folder Access' and it was a constant headache, having to constantly add allowances for new software. I re-purposed an ageing Gigabyte Brix mini-PC as a headless NAS, and it's powerful enough to run DrivePool and a handful of other web-based tools.

You can run snapraidhelper (on CodePlex) as a scheduled task to test, sync, scrub and e-mail the results on a simple schedule. If you like, you can even use the "running file" drivepool optionally creates while balancing to trigger it. Check my post history.

Would it be possible to start storing balancing and file placement settings on the pool disks themselves? Over the year or so I've been using DP, my configuration has grown pretty complex. Small errors in configuration can cause huge amounts of data to be moved around, and cause big problems with snapraid.

1.) Is there any way to override the default 3x duplication for reparse points? They're stored on my C Drive (I know, I know) which is backed up once a week. 2.) Are files verified when they're balanced? Is that why my poor drives are pegged at 100% utilization? Again, any way to turn this off?

Don't you mean 'false,' to make it use foreground IO? I just saw this advice in another thread, as well.

Scratch this question, in 2.2.934 the quota is working exactly as expected. It shows not needing balanced until the GB quota is hit. Don't know if maybe there was something wrong with my balancing settings in the past, or a bug in a previous version. I've never understood how the 'balancing ratio' quota and 'or this much data needs to be moved' GB quota interact. Will having a GB quota set (say, 25GB) ignore the ratio (which nobody seems to understand, entirely) until 25GB needs to be moved? The balancing ratio is basically broken / unusable when file placement rules are being used, because it basically drops to 0 as soon as you violate one.

I run double parity, also. It's 1/2 for peace of mind and 1/2 because I'm a nerd and multiple parity is seriously cool stuff. Worked great! I've simulated a few scenarios in the past by moving files to another disk, but this was the first time I needed it. I couldn't leave well enough alone, though, and finally found a solution that works Even with write-protected folders. From an administrator-level command prompt type: "Robocopy C:\Test C:\Test /B /S /Move" I don't understand exactly why it works, but you're basically moving a folder onto itself, but skipping (deleting) empty folders. /B allows Robocopy to properly set attributes and permissions for system folders like Recycle Bin and .covefs. Bad stuff happens if you don't use it. I wrote a batch to run this script on all 7 of my Drivepool disks, and it completes in under a minute. Good stuff.

I tried this, and it doesn't work. Remove Empty Directories does not support junction points. And Windows 10 constantly nags you about a 'driver error' if you have disks mounted to folders but not letters. Wrong thread? I got to test SnapRAID earlier when a wonky script deleted ~4,000 files before I could stop it, so until someone comes along with something new to try I'm done. And this ^^, BTW, is why anyone using snapRAID without file placement rules is absolutely nuts. If those files had been scattered across different drives there's 0 chance I would have been able to get them back.

That's a fair point. I abandoned mounting my drives to folder paths for reasons I don't entirely remember, but I may revisit this if I can't resolve my "Downloads" permission issue.