Jump to content
Division-M Community

All Activity

This stream auto-updates     

  1. Yesterday
  2. Can I suggest that you raise a Support Ticket to ask that question. https://support.division-m.com/hc/en-us/requests/new
  3. Can I suggest you raise a Support Ticket, as there may be something MS have changed/added that may conflict with DB. https://support.division-m.com/hc/en-us/requests/new
  4. Last week
  5. I upgraded a PC that had a DriveBender pool to the new Windows version 2004 and accessing the pool is like 100x slower. For instance, if I try to load BattleNet it takes 3-5 minutes to come up and then the app is very unresponsive for another minute or so, after which time I can finally enter my login credentials, and then the app goes into Not-Responding state for awhile. Opening Explorer and actually trying to access a file also goes into the unresponsive state. I had DB 3.6 so I went ahead and installed 3.7, but that did not make any difference.
  6. Does Drive Bender work with WSL2 ? Can I use the pool drive like any other drive from the linux subsystem?
  7. Yes, you can remove it manually. Might be worth raising a Support Ticket so that the devs can ask for any logs surrounding the issue.
  8. When the installer tries to remove the older version it fails. Can I remove it manually safely?
  9. Earlier
  10. Glad to hear you got it running. I was going to suggest you delete the drive configuration from the registry and reboot. Drive bender will tell you it's rebuilding from drives.
  11. Really weird... So I removed the drive, and I guess it removed the old DB3. and then the new one was just... there. I didn't need to re-add it. everything operating normal now.
  12. Can you move this to the Drive Bender support forum?
  13. So I think I was on 2.8 or 3.2 before I upgraded (I don't know there have been so many releases lately). Basically, I had a drive die last year which was a 6TB RED and it was given the label DB3. So I removed the drive, repaired the pool, etc, etc. I bought a bunch of new drives and the label DB3 has been replaced with a 6TB RED PRO. When I upgraded I was notified that the old drive could not be found and the pool was put into read-only. I don't understand why it was looking for that drive, but ok. I restarted and now I am getting a new error that the 6TB RED PRO is offline, even though I can clearly see it in windows disk management. I believe it has something to do with the label DB3 being reserved for the drive that died, which was not recorded as removed from the pool for some reason. I have everything mirrored. So to reconcile should I remove DB3, repair the pool, and then add it back? This sucks and makes me not want to upgrade again by the way.
  14. To those who are using Backblaze (not B2), are you able to backup your pool drive? Right now, my pool drive is on a Windows Server OS, which is unfortunately not supported by Backblaze (for good reason), unless you're on the B2 plan. However, I am willing to re-deploy to Windows 10 just to comply. But the question remains, will Backblaze, running on a supported Desktop OS, recognize the pool drive?
  15. From either the Pool Management tab in WHS Server Folders or Drive Bender Manager after you've added the SSD to the pool click on the "Show detailed information and options for this drive" icon (furthest right from the drive) and in the dialog right under "File Placement" there's a drop down. Select "Landing Zone".
  16. Can some one direct me too documentation on how to enable the landing zone feature ? Thanks so much Stacy
  17. It's been a while since I posted this, but I finally got around to trying the Windows Server Deduplication Role on a duplicated DB pool mount (set up just for this test: no data at stake) and wanted to share the results for anyone who might be curious. In short? Doesn't work, or rather it kinda works but doesn't work properly. I created three copies of a 72GB Acronis backup file on a two-disk duplicated pool mount labeled K:\. We'll call them A, B, and C. All three primary files were written to disk 1 and I confirmed that Drive Bender's hidden duplicates had all been properly created on disk 2. The Windows Server Deduplication Role can't be configured to run on a DB Mount, so I pointed it directly at the underlying disk volumes (which I have mounted as folders in C:\Drive Mounts\) and set the exclusions so that it would only run on the UUID folder for the K:\ mount. Gave it a couple of days to work its magic and when I came back it seemed to have worked! My Pool free space had returned to the level I'd expect if I only had file A and its hidden duplicate on the Pool, meaning files B and C (and their DB dups) had been deflated by the Deduplication Role without interfering with DB's duplication management. But... I couldn't delete them. I couldn't do anything with them. The deflated files had been broken. After doing a little digging, I discovered that the interaction of DB and the Deduplication Role both looking at the underlying disks had messed up the security/ownership of the files so that I couldn't even see ownership information when I tried to access it through Explorer ("B" File->Properties->Security tab->"The requested security information is either unavailable or can't be displayed." If I navigated to C:\Drive Mounts\Disk 1\[K-mount UUID]\"B" file everything seemed normal and the security/ownership info was unaltered, but K:\"B" file and nada. I even ran the test again a second time and, while the results weren't quite as clear-cut (only some of the files were messed up), the conclusion is the same nonetheless. So, there you go, doesn't work. Hopefully sharing this info will save others time and effort!
  18. Glad to hear you all back up and running.
  19. All is well again! I went ahead and reinstalled DB and it indirectly prompted me to replace the old drive with the new one, and afterwards, restored the pool on its own. Another plus is now I am on the latest version. I was dreading this step but it turns out it was the most simplest way forwards. Thank you so much, I really appreciate it.
  20. Installed with no problems. Pool came up without issue. Thanks!
  21. I would uninstall DriveBender, then reboot and start the DB install again. If that still doesn't work, then uninstall and remove all entries in your registry relating to DriveBender, then reboot and reinstall. You can map letters to your drives via Disk Management.
  22. Thank you, it's starting to make a lot of sense. I can see that some of my files are in the folder with some missing documents in sub-folders. I would think that they are in the other drives in the pool under the same sub-folders? I am unable to determine this as my DB client keeps prompting to connect to the server which fails. As a result, I can not access the UI to map a letter to the other drives, would you know how to do this? If I am also able to map drives and access them from explorer, how may I erase the pool if the client is inaccessible at this stage? Would a simple uninstall work coupled with following your procedure above (move all content from folder to root and delete folder + 3 files)? Upon reinstallation of DB, would it allow me to create a new pool since those folders/files were removed? Thanks again CBers.
  23. In days gone by when I had a similar problem I just deleted everything from the client backup folder and started fresh.
  24. Apologies, the GUID folders aren't hidden. In the root of the drive, you should have 1 folder and 3 files. The folder is where your content is stored. You could move everything from that folder to the root of the drive, then delete the folder and files, so all you have in the root of the drive is your content. If you do the same with all of the drives in your pool, then you will be back to before ever creating a pool. Delete the pool from the DB UI and reboot your PC. Then once it's back up, start from the beginning again, create a pool and add the drives one by one to it. This is how I have done it in the past when DB got "corrupted". Hope that helps.
  25. Unfortunately I may not have. I only copied everything including the annotated folders with random strings. I have hidden folders enabled but I honestly did not set out to find them and ensure they were copied. As you can tell, I am a complete newb. Could you please advise how I may find them in the root of the drive? Yes, I will have to do the UI method next time. Would uninstalling DB simply allow the drives to show up in explorer? I always had the idea that files were distributed somewhat between the drives in the pool. If so, would they sort themselves out or am I incorrect in assuming how they work? I have sent my DB log files to support as requested. For now, I will wait on further course of action before resorting to deleting the pool. Thank you CBers.
  26. You copied all of the hidden GUID folders that reside in the root of the drive? This is the manual way of swapping drives: https://support.division-m.com/hc/en-us/articles/214025823-How-do-I-manually-remove-a-drive-from-the-pool- I would first have tried to SWAP the drive via the UI, but looks like you've gone past that. You could delete the pool, move the content on the drives to the root of the drive, remove the hidden GUID folders and then start afresh, by creating a new pool and adding your drives one at a time to the new pool. That's one way of getting it up and running and something I have had to do a few times, but it all depends on how confident you are and know exactly what you're doing.
  27. Thank you for your reply CBers. I apologise, I am unsure of the procedure you are speaking of however I followed these steps as advised by the support team: The conundrum was that I had no more SATA ports to accommodate the straight forward method so was advised to plug in the new drive via USB (original enclosure) and move files over this way. Was it possible to add the new drive to the pool - whilst it was connected through USB - and retain its position in the pool when I exchange it with DB1's SATA port? I did not think to do this, and only mapped the drive and copy its contents over. My first instinct was to put the old drive back and it was unsuccessful unfortunately, although I don't quite recall the results. I will try again tonight and post what occurs shortly. Without the new drive, there are presently 2 drives in the pool. Edit: This is what occurs when I plug the old drive back in.
  1. Load more activity
  • Create New...