w3wilkes

I did see the "ghost pool" (your drive X:) once a long time ago and like you I just got rid of it and all was good. Glad it went well for you.

For item 3. You should be able to roll back without a problem, again, release the license from the Win2k19. On the other 2 questions. You should open a ticket and ask about your questions 1 and 2.

Is this your first encounter with Drive Bender? You will find the manual for the product in the software install directory. It describes how to set up a pool. Parity is not a feature of Drive Bender. In a nutshell; Follow the instructions in the manual for adding your drives to the pool (they should be empty / formatted) Once the pool is created the 16 drives should appear as a single drive to File Explorer and the original drive letters should not be there for the native drives anymore. As you create directories on the new drive bender drive you should go into the Drive Bender manager and specify which folders you want duplicated or you can set duplication for the entire pool. Data that is copied to folders or the drive you've defined for duplication will be put on 2 physically separate drives in the pool. This way if a drive in the pool fails there will be an additional copy of the files on the failed drive elsewhere in the pool. So your first order of business is "read the manual".

Hopefully you've opened a ticket on your problem. https://support.division-m.com/hc/en-us/requests/new I use WHS2011 with drivebender 3.6.0.0a and have my client computer backup folder in the DB pool and it works fine. I will say that I started with the client computer backup folder in the pool so I wonder if the problem might be related to moving the folder after you had been using it on a native drive.

Did the drive fail or are you just upgrading the drive? Have you tried assigning the drive a letter and manually deleting the file. Then you might be able to get back to the DB drive removal process. Seems like there's a force option, but if the only copy of a file is on the drive being forced I think the file would be lost. You should probably open a support request and seek help from the developer. https://support.division-m.com/hc/en-us/requests/new

This is the only report of this that I've seen since 3.6.0.0a. You should open a trouble ticket with Drive Bender support. https://support.division-m.com/hc/en-us/requests/new

In your upgrading process did you drain each drive that was to be upgraded before you removed it from the pool? If not, the removed drive would be the same as a drive crash and should be handled that way to recover any primaries on the removed drive. I believe the process is defined in the manual which is located in the directory that you installed Drive Bender in, typically "C:\Program Files\Division-M\Drive Bender". There's also documentation on the Division-M website. https://support.division-m.com/hc/en-us/categories/201693583-Knowledge-Base-Drive-Bender If you need more help I would suggest that you open a support ticket; https://support.division-m.com/hc/en-us/requests/new 1971 240Z guy.

I think you need to take ownership. Google is your friend, try this search "windows 10 take ownership drive" without quotes.

Hopefully you meant Windows Home Server 2011. As far as I know there is no WHS 2010. On client computer backup it sounds like you have an error in your backup catalog. Have you tried doing a repair function on the client backup database? Here's a link with instructions for doing a repair. https://books.google.com/books?id=MufqJtL2evkC&pg=PT374&lpg=PT374&dq=whs2011+repair+client+backup+database&source=bl&ots=IzpDSmgVGq&sig=ACfU3U1DoLUc-vMk6dlDiUFzcDnvk2j8zA&hl=en&sa=X&ved=2ahUKEwiNztHU9JTnAhWTK80KHXU1BUcQ6AEwDXoECC4QAQ#v=onepage&q=whs2011 repair client backup database&f=false I have had an occasion a couple of years back where I ended up having to delete the whole client computer backup folder and re-setup the backups for my PC's since I was not able to get a successful repair.

You should open a support ticket and ask the question regarding switching drivers. You should also include the info about DB being much slower and refer to this thread. The place to open a ticket is; https://support.division-m.com/hc/en-us/requests/new Be sure to let us know what DB says.

With this type error I would hope that you've opened a support ticket; https://support.division-m.com/hc/en-us/requests/new They will probably give direction on setting some log levels and have you submit logs with the recorded data. Not an excuse, but the developer is in the Sydney Australia area and may be hampered by the devastating wildfires.

I don't understand what the issue is beyond the message? My pool is fine. I can access all my files in the pool, my music server can play any music from my pool, my PC backups go to the pool on my server, etc.. Other than the error message from 3.2 and 3.3 my pool is working fine.

I've not heard an update yet. Have you opened a support ticket? https://support.division-m.com/hc/en-us/requests/new

Sorry that none of us have any help for you. Hopefully Anthony has responded to your support ticket.

I downloaded again and re-installed. It came up as a Modify...