When both products were in beta, I picked Drive Bender and have been using it since. However, recently, I'm getting a lot of dropped drives which is greatly frustrating. The idea of running Stablebit Scanner along side Drive Pool has me considering the switch.
However, I have 20 drives totaling 60TB in storage with everything duplicated (a hidden duplicate on various drives) so manually recombining stuff is going to be a pain.
That being said, can someone familiar with both programs answer these questions for me:
1. If a drive drops, is there a manual/automatic tool that will identify which primary files were located on the dropped drive and then find the duplicates remaining in the pool and mark them primary then duplicate them?
2. Is there a caching mechanism? What type of read/write should I expect if a file is being copied twice in parallel? All my drives are green 5400rpm drives yet on tests, I'm still getting around 60megs read/100megs write in my current config.
3. If Stablebit scanner finds errors on a drive - what does it do? Some of my reading says it pulls the drive automatically - but then would it initiate (the answer the question 1?)
4. In the same vein, is there a tool to check the integrity of the duplication? Can I scan for every file in a duplicated directory to confirm that it has a duplicate somewhere else in the pool?
Thanks.
Edit:
Larsp has posted an "unofficial" guide on how to migrate the Drive Bender pool to StableBit DrivePool, include a script to handle reorganizing the duplication into a format that StableBit DrivePool will properly handle.
Question
thepregnantgod
When both products were in beta, I picked Drive Bender and have been using it since. However, recently, I'm getting a lot of dropped drives which is greatly frustrating. The idea of running Stablebit Scanner along side Drive Pool has me considering the switch.
However, I have 20 drives totaling 60TB in storage with everything duplicated (a hidden duplicate on various drives) so manually recombining stuff is going to be a pain.
That being said, can someone familiar with both programs answer these questions for me:
1. If a drive drops, is there a manual/automatic tool that will identify which primary files were located on the dropped drive and then find the duplicates remaining in the pool and mark them primary then duplicate them?
2. Is there a caching mechanism? What type of read/write should I expect if a file is being copied twice in parallel? All my drives are green 5400rpm drives yet on tests, I'm still getting around 60megs read/100megs write in my current config.
3. If Stablebit scanner finds errors on a drive - what does it do? Some of my reading says it pulls the drive automatically - but then would it initiate (the answer the question 1?)
4. In the same vein, is there a tool to check the integrity of the duplication? Can I scan for every file in a duplicated directory to confirm that it has a duplicate somewhere else in the pool?
Thanks.
Edit:
Larsp has posted an "unofficial" guide on how to migrate the Drive Bender pool to StableBit DrivePool, include a script to handle reorganizing the duplication into a format that StableBit DrivePool will properly handle.
http://community.covecube.com/index.php?/topic/511-migrate-from-drive-bender-to-drive-pool/?p=4554
-Christopher, aka Drashna
Edited by Christopher (Drashna)adding migration guide
16 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.