It looks like you're new here. If you want to get involved, click one of these buttons!
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,
Hey Alex, awesome work so far.
I was just wondering, do you ever see in the future, the possibility to create more than one pool. I only ask because as you probably notice from the forums lots of people are using DrivePool mainly to aggregate their HD Movie collections. For me at least the ultimate would be to be able to store my movies on one pool and be able to keep the other (almost certainly lower volume) default folders on a separate pool. I know several pools are currently possible in DriveBender, but i do appreciate that DB may be written a totally different way.
Judging by forums at HSS and WGS i think WHS2011 users are tinkerers by nature. Reinstalls for hardware upgrades, reorganising files and folders cos youve just bought another 2 X 3TB hard drives and suddenly decided that you now really do have the volume capacity to duplicate your 8TB of HD Movies. Or even reinstalling cos youre bored one Sunday afternoon. I think the ability to create that secondary pool would be massive for lots of us. Anyway maybe its something that could be added as a premium feature. Personally i would have no problem at all paying extra. Or maybe its just not gonna be doable at all, in which case i understand.
By the way, i always feel progress can be judged by reaction and comments. So on that basis that the forums are pretty quiet recently, even after an update is released, shows that you have a winning product. I really hope that when DrivePool for WHS 2011 is finished, you push ahead with ability to use it on any OS. WHS users are a small relatively small group.Your product deserves a much wider audience.
:-)
Comments
Shane writes ,(a) optimising performance - e.g. if set A has heavy random access (e.g. db/docs/pics) while set B has heavy sustained transfers (e.g. music/video), ideally A and B will never be located on the same disk(s). Multiple pools allow this.
Thanx for the agreement. I hadnt even thought about things from a performance point of view, but yeah the advantages are so obvious.
Shane writes, "The alternative to adding multiple pools is to add the ability to configure specific shares to use a subset of the disks in the pool."
This part would actually probably fill my needs but i agree. Serarate pools would be better.