Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 08/10/24 in all areas

  1. It is not listed as a supported operating system. That does not mean it will not work on Windows 7, I just installed it on a Windows 7 machine a few days ago and it works absolutely brilliant. A major upgrade from the pulling part of FlexRAID. Not supported just means that they are no longer providing active support for Windows 7. So if you have a problem, you may not get a lot of help with it. The other thing it means is that they are probably no longer testing new releases on Windows 7, so the next update may no longer work properly if at all. It's nothing to worry about, as long as you can accept these limitations. Ed
    1 point
  2. This applies to full disk array backup. But I chose specific folders to backup in SnapRAID config. So the parity file would be as large as the size of those folders + some overhead due to block size -> I chose here the smallest possible: 32k.
    1 point
  3. The only con/issue that comes to mind is that there's no "one-click" way of splitting an existing pool into two pools let alone into a pool of two pools. If you stick to using the GUI, you have to remove half your drives (problematic if your pool is over half full!), create a new pool using them, then create the new super pool that adds the other two pools, then transfer all your content from the original pool into the super pool (which, because the pools are separate drives as far as Windows is concerned, involves the slow copy-across-drives-then-delete-original process rather than the fast moving-within-a-drive process). But if you don't mind the wait involved in basically emptying half of the drives into the other half and then filling them back up again, it is definitely the simplest procedure. Alternatively, if you're comfortable "opening the hood" and messing with hidden folders, you can manually seed the super pool instead - it is much quicker but also more fiddly (and thus a risk of making mistakes). Note also that nested duplication is multiplicative; if the super pool folder that will show up in your hub pools when setting per-folder duplication is x2 and your super pool is itself x2, your total duplication of files in the super pool will be x4. So I'd suggest setting each hub pool's super pool folder to x1, setting the super pool itself to x2 and only then commencing the transfer of your content from the hub pools to the super pool. I hope that makes sense.
    1 point
  4. I am aware that I can set duplication to be delayed, which sets it to happen at "night". This system is a backup target so most activity happens overnight. Is it possible to schedule the duplication tasks to a specific start time e.g. 8 AM when the system is idle? [edit] I see that the settings.json file located in C:\ProgramData\StableBit DrivePool\Service contains "FileDuplication_DuplicateTime": { "Default": "02:00", "Override": null } Which might be my solution. Thanks.
    1 point
  5. Re 1, DrivePool does not scrub duplicates at the content level, only by size and last modified date; it relies on the file system / hardware for content integrity. Some users make use of SnapRaid to do content integrity. Re 2, DrivePool attempts to fulfill any duplication requirements when evacuating a bad disk from the pool. It appears to override file placement rules to do so (which I feel is a good thing, YMMV). However, your wording prompted me to test the Drive Usage Limiter balancer (I don't use it) and I found that it overrides evacuation by the StableBit Scanner balancer even when the latter is set to a higher priority. @Christopher (Drashna) Re 3, I'd also like to know *hint hint*
    1 point
  6. Hi, I'd guess the answer is that if it seems to be working - e.g. you were able to create a pool and it shows up in Explorer and you copied a file to it okay - then you likely won't have problems (besides having to use Windows). That doesn't guarantee that future updates to the program will work on 7 down the line, so you might want to avoid updating unless it's necessary / carefully check the changelog / be ready to revert.
    1 point
  7. The issue seemed to resolve itself. I did not have any rules set on D:\System Volume Information. But I didn't have to do the troubleshooting steps you recommended either. This is very strange. Anyway, thanks for all your help.
    1 point
  8. I know the chance of this is near zero, but the most recent Windows screenshotting AI shenanigans is the last straw for me. The incredible suite of Stablebit tools is the ONLY thing that has kept me using Windows (seriously, it’s the best software ever - I don’t even think that’s an exaggeration). I will pay for the entire suite again, or hell Stablebit can double the price for Linux, I’ll pay it. Is there ANY chance a Linux version of DrivePool/Scanner would be developed?
    1 point
  9. Hey guys, Drivepool has served me well for over 10 years. Unfortunately, I'm moving over to Unraid. Nothing to do with Drivepool itself; it works fantastic. I just can't get Snapraid to work in conjunction with it, and I need that extra layer of backup. So my question is, I do need to evacuate off of the Drivepool one drive at a time, and I don't have enough room to empty a drive, remove it, and then go to the next drive. I was wondering if it was possible to move files directly off of a particular drive's poolpart folder instead? Will it cause Drivepool to freak out in any way?
    1 point
  10. Due to an unexpected glitch while updating the site, the Contact site is broken. We're working on fixing this issue as quickly as possible. We have fixed the issue with the Contact site. However, if you experience any issues with it, please let us know know right away. You can do so, by contacting me directly at "christopher@covecube.com". Just let us know what the issue with the site is, and what the issue that brought you to the site was. We apologize for any trouble that this may have caused.
    1 point
×
×
  • Create New...