I've been using Drive Bender since MS EOL'ed Drive Extender, but have never been able to use any of the 2.x versions of it due to random drive disconnects under 2012/2012r2.
A couple of weeks ago I upgraded the MB in my server and put a fresh install of 2016 Essentials on, but the mount point on my trusty old DB 1.9.5 wasn't working so I had to go up to 2.8.
To be honest, it's been nothing but trouble. Drives dropping off (but still showing up under device manager) and system lockups. It got better when I disabled the DB SMART monitoring service, but whenever DB would start an automatic health check the pool would freeze and eventually the system would lock up, not even responding to RDP.
I've been aware of Drive Pool for some time, but assumed (incorrectly) that migrating the pool would be a pain. This morning I finally had it with DB and decided to check out Drive Pool and found the migration post on the forum. The part that took the longest was removing the duplication on the DB pool before moving the file structure on each drive.
I migrated a 19 drive 95TB pool in about 2 hours total and the pool came right up in DP and so far it's very responsive. I like how lightweight it is and I got the license package with Scanner, which seems like a big improvement over HD Sentinal (which had its own issues). It's only about 25% of the way through creating the duplicates, but even with that going on it seems to perform better than DB did when it was just sitting there.
I feel like I should have switched a long time ago....
Thanks, StableBIt and thanks to the community for having all the info I needed on this forum to make an informed purchasing decision (warts and all) and to do the migration itself.
Question
johnnj
I've been using Drive Bender since MS EOL'ed Drive Extender, but have never been able to use any of the 2.x versions of it due to random drive disconnects under 2012/2012r2.
A couple of weeks ago I upgraded the MB in my server and put a fresh install of 2016 Essentials on, but the mount point on my trusty old DB 1.9.5 wasn't working so I had to go up to 2.8.
To be honest, it's been nothing but trouble. Drives dropping off (but still showing up under device manager) and system lockups. It got better when I disabled the DB SMART monitoring service, but whenever DB would start an automatic health check the pool would freeze and eventually the system would lock up, not even responding to RDP.
I've been aware of Drive Pool for some time, but assumed (incorrectly) that migrating the pool would be a pain. This morning I finally had it with DB and decided to check out Drive Pool and found the migration post on the forum. The part that took the longest was removing the duplication on the DB pool before moving the file structure on each drive.
I migrated a 19 drive 95TB pool in about 2 hours total and the pool came right up in DP and so far it's very responsive. I like how lightweight it is and I got the license package with Scanner, which seems like a big improvement over HD Sentinal (which had its own issues). It's only about 25% of the way through creating the duplicates, but even with that going on it seems to perform better than DB did when it was just sitting there.
I feel like I should have switched a long time ago....
Thanks, StableBIt and thanks to the community for having all the info I needed on this forum to make an informed purchasing decision (warts and all) and to do the migration itself.
John
Link to comment
Share on other sites
5 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.