Search the Community
Showing results for tags 'Tips'.
Found 2 results
To clarify what I mean here: If you want to ensure that one copy of a duplicate file is on a CloudDrive, but you don't care where the other copy is (or it can be on any local disk). This can be confusing and a bit counterintuitive. Additionally, this will cause your system to want to continually rebalance, as the balancing ratio will always be off. To start off with, you'll need to micromanage the pool a bit. You'll need to create a rule for the folders that you want duplicated (or use "\* " for the entire pool). In this rule, select ONLY the CloudDrive disk. Hit "Ok". You may want to disable the automatic balancing, or at least disable the "Allow balancing plug-ins to force immediate balancing" option. This should help reign in the balancing, so that it's not always attempting to do so. We do plan to add a "duplication grouping" option to handle this entire process natively, specifically for better synergy/integration between StableBit CloudDrive and StableBit DrivePool. However, we don't have an ETA on that, as it may be very complicated to implement.
Because we've already have had a couple of questions about this, in their current forms, StableBit DrivePool works VERY well with StableBit Cloud Drive already. The StableBit CloudDrive drive disks appear as normal, physical disks. This means that you can add them to a Pool without any issues or workarounds. Why is this important and how does it affect your pool? You can use the File Placement Rules to control what files end up on which drive. This means that you can place specific files on a specific CloudDrive. You can use the "Disk Usage Limiter" to only allow duplicated data to be placed on specific drives, which means you can place only duplicated files on a specific CloudDrive disk. These are some very useful tricks to integrate the products, already. And if anyone else finds some neat tips or tricks, we'll add them here as well.