Best Answer larsp , 16 July 2014 - 10:23 AM
I have just migrated from DriveBender and back to DrivePool. I tried DriveBender for a period, but it was just slower than DrivePool. When copying many files to DriveBender (ie starting FileHistory from Windows 8), it just stopped working and I had to restart the server. TV-recordings stored in DriveBender was also very slow and uresponsive in VMC. I never had that kind of problems with DrivePool. I do think that the interface in DriveBender is a little more "fancy" but stability is just more important.
Anyway. To migrate back to DrivePool i did the following (on a window server 2012 essential):
1. Installed DrivePool alongside DriveBender.
2. Release your DriveBender license before uninstalling
3. Set up a duplicate DrivePool on the same disks that DriveBender used.
4. Stopped DriveBender and DrivePool services from services.msc
5. Moved alle folders on physical disks from DriveBender root folder to DrivePool root folder.
6. Used the script below to move the duplicate files from DriveBenders location til DrivePools location (DriveBender stores the duplicate in a subfolder named FOLDER.DUPLICATE.$DRIVEBENDER, so you will have to move all the content in that folder to the folder below).
7. Started DrivePool and uninstalled DriveBender.
8. Used computer management to give DrivePool the same disksletter that DriveBender had.
Bat file to move files stored in FOLDER.DUPLICATE.$DRIVEBENDER to the directory below (hidden files will no longer be hidden as move doesn't move hidden files). This script has to be run on all the physical disks. Stand in the \poolpart.* folder. To try it out, stand in a subfolder where you can't do much harm.
Please note that I give ABSOLUTELY NO GUARANTEE that the script will work for you. Try it out first, and if it seem to work, remove the echo
All in all it took just 1 hour to set up and migrate from DriveBender to DrivePool and I did not have to duplicate 6 tb.Go to the full post