Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google

Poll

No poll attached to this discussion.

In order to better support our growing community we've set up a new more powerful forum.


The new forum is at: http://community.covecube.com


The new forum is running IP.Board and will be our primary forum from now on.


This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.


Thank you,

basic understanding of folder duplication needed....

edited February 2013 in DrivePool
whs 2011 drivepool.

i created a pool, added 2 3tb drives, the pool shows up as 5.73tb.  ok, so that's 2x 3tb, so to speak.  i want to move server folders to the pool and have duplication enabled for all of them.  it looks to me like i have to enable folder duplication on a folder by folder basis, so as i add folders and enable duplication the total pool capacity will decrease each time i add a folder and enable duplication for that folder, correct?

the reason i ask is i sort of expected to add the 2 drives and enable duplication enmass and have the pool capacity only show up as the capacity of one of the drives, i.e. 3tb.  make sense?

thanks.

Comments

  • Resident Guru
    Hi montejw360. From memory of when this issue first came up way back, there are two reasons for measuring pool capacity as the total available space of the drives that make up the pool, rather than on the amount of free space available if all folders were duplicated.

    The first is that DrivePool cannot predict whether a user is actually going to keep only duplicated content in the pool.

    The second is that if the pool has an odd number of drives and/or drives of differing size, you cannot completely fill the drives with duplicated content because at least one drive will run out of space before the others and/or the "duplicated only" capacity may have multiple possible values depending on the sizes of the files to be stored.

    So since DrivePool has to handle all possible combinations of drives and content, extra code means extra work and the possibility of extra bugs, and it's simple and straightforward enough to just display the actual physical space available, that's what happened. :)
Sign In or Register to comment.