Issue

Christopher
Technical Support
StableBit DrivePool
2.3.0.1244 BETA
Windows 10 (64 bit)
Public
Alex

The pool usage statistics (pie charts in UI) always show the actual usage on the current pool. For instance, if you were to attach a drive letter to the pool that you're looking at, then on that drive, what would you see? That's the stuff that is represented by the pie charts.

Let me show you a concrete example. Imagine that you have this pool setup:
  • parent pool ->
    • child pool 1 ->
      • disk 1
      • disk 2
      • disk 3
    • child pool 2 ->
      • disk 1
      • disk 2
      • disk 3
No duplication enabled yet.

Now, you place a file on "parent pool". That file will now be stored on "child pool 1"  (or "child pool 2", but one of them will be picked), which will then store the file on a disk, say disk 1.

So now, things look like this:
  • parent pool ->
    • child pool 1 ->
      • disk 1 => File.BIN
      • disk 2
      • disk 3
    • child pool 2 ->
      • disk 1
      • disk 2
      • disk 3
Then, you go ahead and turn on duplication in "child pool 1" (on the appropriate folder).
  • parent pool ->
    • child pool 1 [DUPLICATED] ->
      • disk 1 => File.BIN
      • disk 2 => File.BIN
      • disk 3
    • child pool 2 ->
      • disk 1
      • disk 2
      • disk 3
At this point, your file is duplicated on child pool 1, and it will be reported as such in the pie chart for that pool.

But why is the parent pool not reporting any duplicated files at this point?

Why because it is actually only storing the file on one underlying storage device!

If you now enable duplication on the parent pool, as such:
  • parent pool [DUPLICATED] ->
    • child pool 1 [DUPLICATED] ->
      • disk 1 => File.BIN
      • disk 2 => File.BIN
      • disk 3
    • child pool 2 ->
      • disk 1 => File.BIN
      • disk 2
      • disk 3
Only then will the parent pool report the file as being duplicated. Because it is now actually storing that file across 2 separate underlying storage devices (and those pools have their own separate duplication rules).

So, to extend this example into the practical:
  • HybridPool [DUPLICATED] ->
    • LocalPool [DUPLICATED] ->
      • disk 1 => File.BIN
      • disk 2 => File.BIN
      • disk 3
    • CloudPool ->
      • Google cloud drive => File.BIN
      • Amazon cloud drive
      • Dropbox cloud drive
You can now have a setup where your files are duplicated locally, while at the same time, stored unduplicated in the cloud. All of this happens in real-time with no background processing required.