Klaatou, that is unfortunate it wouldn't work for your situation, have you tried Link Shell Extensions for linking? As far as I know, what you want to do, ie: e:\Bluray and f:\Bluray mapped to z:\Bluray will not work unfortunately. I had mine mapped within a main bluray drive and sorted my physical drives based on Bluray A-E, Bluray F-M, etc for organization
Cool1Net6: Thanks for the reply, that's an interesting question/scenario. Back when I first found Drive Bender, I played around with it for a week or so to ensure it would work with Disparity and rebuilds, etc. At that time I was sure all would be fine, 6 months down the road now, I haven't had to manage anythiing related to drives/space/rebuilds so I am not able to easily recall what I came to decide if I ever had to do a rebuild.
Quickly looking at Drive Bender, I believe the plan was to, in this order (we will say E: is the failing/failed drive)
1. Physically install new drive (format and assign new drive letter, even if only temporary until you remove the old letter)
2. Load drive bender manager
3. Select Drives Dashboard on the left
4. Select E: and say "Swap with new drive"
5. Point it to the new/fresh drive
6. Drive bender will try to do whatever it can to copy/move data from the failing drive to the new drive, whether or not it fails to do so we really don't care about as we will be doing a rebuild with disparity
7. Once drive bender is finished, go to disparity and do a rebuild of the failed drive, onto the new drive, just as you would if you weren't running drive bender.
Since you "Swapped" out the drive in Drive Bender, all Pool/storage info (ie: E:\{106DF1D2-3563-4E6B-9065-8508EB9D6677} ) should remain the same for drive bender purposes. Once you run a disparity rebuild on the drive, it will rebuild that drive with the unique code drive bender used, and all files below that structure. We don't want drive bender to do anything with the drive except allow us to replace the failing drive in the "pool" with the new fresh drive, all data rebuilding will be handled by disparity.
In the very worst case, you could "Remove Drive" from the pool, do a rebuild using disparity and then freshly merge it into the pool as if it were a completely new drive as you do each time you have a new drive to add (you might have to move the data from the old E:\{code}\<files> to the new e:\{code} section based on whatever drive bender assigns to keep things straight but that's simple enough
Again, this is just going from what I vaguely recall from 6 months ago and taking a look at options now as to what I would do if faced with a failing drive.
If you wouldn't mind looking at my steps and checking it against your drive bender/disparity setup and seeing if you agree/disagree based on your recent messing around with it, since you will have a fresher idea of it than I do at this point. I believe that should work but I definitely would appreciate your input/feedback.
Thank you all for contributing! I love this!