Jump to content
Division-M Community

Leaderboard

Popular Content

Showing content with the highest reputation since 01/16/2014 in Posts

  1. Anthony

    Beta v3.0.0.0

    Some good news, we have solved the Drive Idle issue... just performing some final tests and should have a new beta out in the next week.
    5 points
  2. Hi All, First up, I would like to apologies for all the recent updates. The last couple of releases (mostly v3.3 and v3.4) of Drive Bender have contained a very allusive "Access Denied" error (this was a timing/cache problem exposed as a result of improving I/O performance). In addition to v3.2 having an problem with the FolderWall module not disabling correctly, and displaying odd errors... In all, we have not covered ourselves in glory 😬 We are confident we are on top of these issues now with v3.6, and will be looking at our regression testing, and making some changes to ensure we are delivering a better product to our faithfully users! For those that had problems... thanks again for your support and, in some case, access to your machines to help diagnose issues 👍
    4 points
  3. Anthony

    Beta v3.0.9.0

    FYI - Offical v3 release is scheduled for the 30th of December Merry Xmas to all...
    4 points
  4. Once you've copied all your relevant files from "K:\" to another drive or PC, you can uninstall DB and just reformat the individual drives in the DB pool like any normal drive.
    3 points
  5. Anthony

    Beta v3.6.5.0

    Release v3.6.5.0 beta 1 (2020/03/31) [ b ] Change in pool size error was causing the pool to switch into a fault-tolerant mode, and not switch back. [ b ] Detecting missing drives ate boot time now works as expected. [ b ] Scheduling task no longer blocks tasks for extended periods. [ u ] Even balancing has been improved on larger drives. Download here
    3 points
  6. Release v3.6.0.0 release (2020/01/22) [ b ] Fixed a potential file looking issue. [ u ] Further performance improvement introduced. Release v3.6.0.0a release (2020/01/23) FolderWall may not process rules containing explicit application entries correctly. Download
    3 points
  7. Release v3.1.0.0 release (2018-12-03) [ b ] Fixed an issue network security errors. [ b ] Fixed an issue with Drive Idle terminating. [ n ] Drive Idle now defaults to disabled. [ n ] Side Channel Protection can now be enabled via the setting. [ b ] Closing the Drive Bender Manager's config window was updating custom setting even when no setting were changed. Release v3.0.9.0 beta (2018-11-09) [ b ] Further improvements on Drive Idle performance. [ b ] A number of bug fixes on the Drive Idle feature. [ n ] Added notification options to the Pool Firewall. [ b ] A number of minor network share related issues. Release v3.0.8.0 beta (2018-10-15) [ n ] Added new "Side Channel Protection" feature. (DB-228) [ b ] Installer not updating all dependencies correctly. (DB-231) [ b ] Network services staring but not seeing mount point, we have needed to restart "server" for network path to appear. (DB-227) [ b ] Drive Idle performance slow, and for some users files missing during file enumeration. (DB-233 & DB-239) [ b ] Mount point name appearing as "Local Disk". (DB-226) [ b ] Empty pool purging is causing an issue on new installs. (DB-229) [ b ] Drive Bender Manager throwing an error when first starting on some systems (DB-230) [ b ] Network shares can display security issues (DB-238) [ b ] File system health check could create folders using a file name (DB-240) Release v3.0.0.0 beta (2018-07-21) [ n ] Added new "Pool Firewall" feature (note disabling the "List" option is currently not available). (DB-216) [ n ] Added file enumeration cache feature (FEC), this is part of the new "Drive Idle' feature. (DB-218 & DB-220) [ u ] Empty pools are purged on restart. (DB-202) [ b ] Improved network share handling, including a number of network share bug fixes. (DB-203) [ b ] Network nodes being restored after having been removed from a pool. (DB-213) [ b ] A pool can fail to mount if a network share failed to connect. (DB-214) [ u ] Some USB based removable drive were not being detected. (DB-215) [ u ] Improved mount point checks and loading times. (DB-204) [ u ] Hard limit on log file usage improved. (DB-219) [ u ] Fixed a number of driver installation issues. (DB-223) [ b ] Fixed several issues with balancing and landing zone clearing. (DB-217) [ u ] Improved balancing performance. (DB-217) [ u ] Thread deadlocking issue resolved, and improved thread marshalling for better performance. (DB-225) [ b ] Fixed a number of server related bugs. Download here Pool firewall configuration - We have posted a "How to" on the Pool Firewall, you can access via support at https://support.division-m.com/hc/en-us/articles/360000366936
    3 points
  8. Anthony

    Beta v3.0.0.0

    Hi all, Just a quick update on the next beta. We are still trying to nail down an issue with Drive Idle... we believe we have sorted the performance problem, however, there is still an issue with files not displaying on occasions. Problem difficult to sort, as it can take days before it shows up. Anyways... stay tuned!
    3 points
  9. Release v2.7.0.0 release (2017-08-31) [ b ] Balancing and landing zone clearing can start at the same time causing the other to abort. [ b ] When files are being balanced, certain conditions can cause this process to hang, resulting in timeout errors and/or file system hangs. [ u ] "Non-pool used space" is now scanned as part of the file health system scan, and is no longer estimated. [ u ] Improved file locking resulting in I/O speed improvements. [ b ] Fixed a number of minor bugs related to worker thread tasks and queues. [ u ] Windows Server Dashboard is now more Server 2016 aware. [ b ] Fixed a number of minor bugs related to the Drive Bender Manager. Download here
    3 points
  10. Anthony

    Beta v3.9.2.0

    Release v3.9.2.0 beta (2021/10/8) [u] Windows 11 compatibility [u] Drive Bender core updated with a number of rewrites [n] Added new "File placement" options to drive nodes, including "Landing zone", "Primary files", "Duplicate files", "Custom target folders" and "Target not preferred". [b] Memory leak of the server when the Drive Bender Manager is running for extended periods. Before installing, please read Unfortunately, during testing, we discovered a number of performance and reliability issues. These are, in some cases quite severe and can impact small file reading and writing. There is also a memory leak which may require a service restart on occasions. Regardless we are providing the beta for Windows 11 users as a short term solution if they have upgraded to Windows 11, and need assess to their pool. For other users, we are recommending you wait for the next beta. Next beta The update to support Windows 11 was quite a major one and was not in our original v4 roadmap. Therefore we have disabled many of the new features and focused on Win11 compatibility for the initial betas. As we had indicated to users that a Windows 11 compatible beta would be released around the 22nd, sadly that slipped while we tried to work around the performance issue. The end result, is we need to re-architect some of the code, which will likely take until the 1st of November. Sorry to all that have been waiting on Win11 support. Download here
    2 points
  11. Having said that, there is now a beta release, but please read the thread thoroughly.
    2 points
  12. I contacted the developer and he has not played with Win11 yet. he is in the process of getting DB v4 going and thinks it should be ready for beta in the next couple of months. He said they wait for the Windows releases to get closer to general availability before they get serious with compatibility work. As we all know beta software is a moving target, but thanks for the heads up.
    2 points
  13. Looks like the permissions/ownership on the pool folders on each drive got corrupt some how. Some where showing "Administrators" as owner and other had something like "s-1-5-1-21-1234567890-1234567890-1234567890-1000" as the owner. I changed ownership of all to "Administrators" for all and rebooted. Problem solved!!!
    2 points
  14. Release v3.7.0.0 release (2020/04/08) [ u ] Some minor performance and reliability improvements. [ b ] Fixed a number of minor service bugs Release v3.6.6.0 beta 2 (2020/04/30) [ b ] An issue with any drive that causes the pool to switch into fault-tolerant mode can cause the Drive Bender service to crash. [ n ] We have added the ability to reset file object permissions across a pool, see - https://support.division-m.com/hc/en-us/articles/360001500816 Release v3.6.5.0 beta 1 (2020/03/31) [ b ] Change in pool size error was causing the pool to switch into a fault-tolerant mode, and not switch back. [ b ] Detecting missing drives ate boot time now works as expected. [ b ] Scheduling task no longer blocks tasks for extended periods. [ u ] Even balancing has been improved on larger drives. Download
    2 points
  15. Yes, the licenses are not Windows OS specific. They should work on Win7 and up.
    2 points
  16. Yeah, Same here. Irreplaceable files were duplicated so the only items lost were Plex media. I can recreate them from scratch but it doesn't make it any more pleasant.
    2 points
  17. As you know, most any drive of any size can be added to the pool as long as it's NTFS formatted. The unknown is drive longevity/reliability and speed. My guess is if it's slower than your existing drives and dup'd data is being written to it, I would guess it would slow down the operation. Can't speak to the Synology question.
    2 points
  18. I had an excellent experience with support and through some careful hunting we found that one of the pooled drive file systems had converted to exFAT from NTFS for some unknown reason. The fix was to copy all the files from the mount point of the exFAT drive to a good NTFS drive in the pool, then force a removal of the bad drive from the pool, reformat the bad drive, add it back in, then rebalance. I have no idea how the drive decided it wanted to be a different file system, and we may never knw the root cause, but I want to thank Division M for the great product and great support.
    2 points
  19. On a clean install, once you start DriveBender, It will see the disks that you previously had in a pool and ask if you want it recreated. You say YES and it'll do it. Nothing needs copying from an old install. I've done this many times over the years.
    2 points
  20. Just did this a couple of weeks ago. I did have to release my license and then re-establish it. Mine was a fresh install rather than a clone. As far as my pool went it made the transition just fine to the newly installed system drive.
    2 points
  21. You'll need to switch on advanced I/O logging for this particular case and then email the logs. All the details should be here: https://support.division-m.com/hc/en-us/articles/333757012755 Have you got an open support ticket? I expect you'll need one if not. To prepare you, these are the questions that were asked of me: What sort of file sizes are we talking about? Do you have enough free space on a/each drive(s) in the pool? Are you able to replicate this easily? How many drives do you have in the pool, and what is the free space on these drives?
    2 points
  22. Personal feeling is I've not really seen a performance difference between versions of DB, they're slower than JBOD copies. That being said you can open a support ticket and ask the question about stopping the copy / updating DB / restarting the copy. https://support.division-m.com/hc/en-us/requests/new I'm guessing you really wanted this in the DB section and not the Anvil section??
    2 points
  23. 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".
    2 points
  24. 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.
    2 points
  25. w3wilkes

    Beta v3.6.5.0

    Problem fixed with info from DB development. I uninstalled 3.6.0.0a and then deleted the pool config from the registry. Then I installed 3.6.5.0 and it realized that it had to look at my physical drives because there was no pool info in the registry. DB found my pool drives and asked if I wanted to restore the pool from the found drives. I said yes and the pool was restored successfully. Did one final reboot and all is good. Just remember that 3.6.5.0 is beta and you might encounter problems if you try it. If you try this version and have problems, be sure to open a trouble ticket with all the detail so that the issue can be corrected prior to the next release going live.
    2 points
  26. Thanks everyone! I've been putting off this migration for months but I finally mustered the courage yesterday to pull the trigger and to my delight, everything went relatively smooth. The following are my experiences specific to Drive Bender: 1. After releasing the license, I got a notification that, in effect, the pool will still be accessible but will be in read-only mode. However, I was still able to create and delete files on the pool. I don't recall seeing anything about this taking effect after a reboot but all things considered, not an issue for me. 2. In the new OS, Drive Bender didn't took long to recognize the existing pool (Drive P:) and brought it up. However, I was surprised that it brought up a 2nd identical mount point (Drive X:). I just removed the redundant mount point and everything was back to where it should be. This may have been a mount point I created but removed a long time ago. DB could've seen its remnants and decided to mount it. Though unexpected, it's a minor aesthetic issue.
    2 points
  27. @oj88 Once you release the licence on your old server, the pool will stay online until you reboot, and even then, it may still run for 60 days, as that is how long the evaluation licence is for. When you install DB on the new server, you will again have 60 days evaluation until you have to apply the full licence. So really, you could set up your new server, move the disks and utilise the 60 days, without having to release the licence on your old server, just in case you need to move back. When all is OK on the new server, then release the key, wait for the support people to release it and then apply to the new server.
    2 points
  28. 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.
    2 points
  29. This is being updated in the next major release... with a re-write of the feature that will also, dramatically improve pool performance.
    2 points
  30. We have released v3.3... head to https://www.drivebender.com/downloads.html This will sort all FolderWall issues, here is a change log [ u ] By default the FolderWall feature (module) is not enabled. Important - This release will disable any pre v3.3 rules in place. [ b ] Fixed an error that some users were experiencing at boot concerning the FolderWall module. [ b ] At startup, a mount point conflict could occur that cause the mount point to be removed and recreated. [ u ] Added ".BVR" to the VIDEO file types.
    2 points
  31. Hi All, First up, sorry to those users that are seeing this issue... we have sorted it for v3.3 which is in test ATM and scheduled for release on the 17th (Tuesday). It is important to note that the message itself has no effect on the pool, and all should run as normal... that said, we have found that, when in this state, modifying the rules can cause read issues for the pool. If you experiencing this, you need to do the following. Open regedit, head to "HKEY_LOCAL_MACHINE\SOFTWARE\Division-M\Drive Bender", here you will see a key, will be a GUID value (for example "{1F804C48-A87A-4C1D-8E58-BCE89B7F6EEF}", yours will be different). This is the pool key, click on this and you see more keys, the mount point key will be the key without the ".VOLUME" extension, click on this and you will see a value called "Mount Firewall", edit this value and remove the value so it is blank... then restart.
    2 points
  32. https://blog.division-m.com/2019/08/12/mid-year-update-more-banging-on-the-anvil-and-free-give-away/
    2 points
  33. Ok I have to admit that ever since the WHSv1 and then WHS2011 days I have looked at Drive Bender (and tested for a short while back in the day) but opted for DrivePool at the time. Now all these years later I have finally seen the light. Drivepool has destroyed my carefully created and non fragmented archive drives for the very last time. Then having messed with Storage Spaces for a few days I abandoned that quickly. So it was time to revisit Drive Bender and I'm extremely happy. "Cascade Mode" is all I have ever been looking for. Thanks Anthony.
    2 points
  34. You have right. Scan for Drives und delete the other Moundpoint solve the problem. Server now finish and works great with drive bender. Thanks for the help.
    2 points
  35. 1- You should release the license for DriveBender on your old server 2- Remove disks and install on new server 3- Install DB software 4- when you reboot after installing DB it should recognize the pool and all should be well 5- reregister your DB license on the new server
    2 points
  36. Check it out - https://blog.division-m.com/2019/01/16/roon-and-smooth-stream-using-drive-bender/
    2 points
  37. w3wilkes

    Beta v3.0.9.0

    Cool. The install of the official looks like it will be my first boot since Nov 16, 2018 - 3.0.9.0 has been solid for me. Merry Christmas!
    2 points
  38. w3wilkes

    Beta v3.0.9.0

    I've had no trouble either, last boot Nov 16, 2018 (3.0.9.0 install date).
    2 points
  39. CBers

    Beta v3.0.9.0

    10 days in and still running OK.
    2 points
  40. Anthony

    Beta v3.0.8.0

    Our main release is being held up by some performance issues with the new Drive Idle feature... seems, for some users, this is causing slow folder enumeration. So we can get the v3.1 release out, we are going to disable this feature by default (users can enable is they like)... then, once we have it performance sorted for all users, we'll do a point release that enables this feature by default. FYI - We are planning one more beta, v3.0.9.0
    2 points
  41. Anthony

    Beta v3.0.8.0

    Release v3.0.8.0 beta (2018-10-15) [ n ] Added new "Side Channel Protection" feature. (DB-228) [ b ] Installer not updating all dependencies correctly. (DB-231) [ b ] Network services staring but not seeing mount point, we have needed to restart "server" for a network path to appear. (DB-227) [ b ] Drive Idle performance slow, and for some users files missing during file enumeration. (DB-233 & DB-239) [ b ] Mount point name appearing as "Local Disk". (DB-226) [ b ] Empty pool purging is causing an issue on new installs. (DB-229) [ b ] Drive Bender Manager throwing an error when first starting on some systems (DB-230) [ b ] Network shares can display security issues (DB-238) [ b ] File system health check could create folders using a file name (DB-240) Download here Pool firewall configuration - We have posted a "How to" on the Pool Firewall, you can access via support at https://support.division-m.com/hc/en-us/articles/360000366936 Important - This beta release has been heavily tested (in fact, the most rigorously test beta we have ever released), and expect new/updated features to be solid. The only "if" we have is around the performance of the Drive Idle feature, something difficult for us to test, as it needs a wide range of hardware. If you experience any performance issues with folder listings, please let us know (you can disable Drive Idle via settings).
    2 points
  42. CBers

    Beta v3.0.0.0

    For people with issues, I would suggest opening Support Tickets, as this is the only way the developers can fix any potential issues.
    2 points
  43. Anthony

    Drive Bender v3

    Drive Bender v3 is coming, check out some of its new feature in our latest blog - https://blog.division-m.com/2018/07/23/the-malware-meltdown/ Let us know what you think and if there is anything else you would like to see in v3! The Drive Bender v3 beta is set for release on the 31st of July. Update: The release date has been pushed to the 3rd of August. Update 2 (2018/8/4): We have an issue with the Drive Idle feature on one of our test machines, and we are having trouble sorting. Once we get it worked out, the beta will be released. Update 3: We still have not resolved the issue with the test machine. The problem is this bug can take 12 – 24 hours to manifest, so sorting it is proving to be time consuming... stay tuned. Update 4: It looks as if we have sorted the issue, and we are just performing finally testing. All being equal, we are planning to release on the 15th of August.
    2 points
  44. Release v2.8.0.0 release (2017-10-26) [ b ] Balancing on pools with multiple mount points may not balance both mount point (only the first), this could also affect landing zone clearing. [ b ] When applying duplication, the Drive Bender Manager/Console could hang. [ b ] Fixed a number on minor bugs. [ u ] Added additional logging for some areas of code to track drive issues. Download here
    2 points
  45. If you are having disk issues, Drivebender can generate a number of alerts (drive missing, drive back, etc) while you are isolating the cause. It would be nice to be able to select multiple notifications and delete them at once instead of click, open, delete, Yes; rinse and repeat.
    2 points
  46. Okay for the purpose of helping others out I have written the following tutorial. If someone sees something I could do better or update please let me know. For this example I will be taking a 4 tb drive and a 500 gb hard drive with data on both and merge them into a new pool. To start this I have a folder on each one called movies. Inside this folder I then have 10 Movies for a total of what will become 20 movies on what appears to be one drive. 1. Open Drive Bender Manager 2. Select Pool Options with the drop down arrow 3. Select Add A New Pool and name it whatever you would like. If you would like to add a description you can. Also leave it as a managed pool as drive bender will tell the OS where files are on which drive versus you having to remember. Then click Create. Then Yes you want to add a new pool. You should see a screen like below 4. Click Create a mount point. Select whatever drive letter you would like along with a volume name. you should see a screen like below. 5. Click the plus next to one of the drives you want to add. So in my example from above I would click the plus sign next to y:\ 6. You will be present with a screen like below and make sure to check the "Merge the existing files into T:\(Or whatever drive letter you gave your drive)" and leaving everything else alone and click "Add". You will be prompted to make sure you want to add this drive to the pool click yes. Be patient as this may take awhile depending on the size of the drive and how many files you are merging. 7. Verify that the drive did get added correctly. Simply go to Windows Explorer and look for the drive letter you set for the mount point. During this time you will see that the drive you added is no longer visible. Select the mount point drive letter and verify your files are there. 8. Repeat steps 5 - 7 for however many drives you want to add to the pool that have data. If all went well you will see one drive now with all your media on it and a screen that looks like this. @jlr19, please let me know if this needs more pictures. I tried to type as detailed as possible but you know what they say. A picture is worth a thousands words.
    2 points
  47. This has been reported and the developer says it will be fixed in release 3.2.0.0
    1 point
  48. w3wilkes

    Primary Utilization?

    Don't know why I'm just noticing these things now that I've rebuilt my pool??
    1 point
  49. Anthony

    Beta v3.0.0.0

    Thanks CBers... The installer will only force an uninstall if the core driver is out of date. v3 is using the same driver as v2.8.x, so I would expect a forced uninstall first. So that leaves an issue with the installer and the service starting, we'll check it out. In the meantime, I note the issue in the original post.
    1 point
  50. Without knowing what else runs on your PC, it's hard to hazard a guess. Check your Task Scheduler and see if anything runs hourly. What setting do you have for a screensaver? Is it set to start after an hour of inactivity? Loads of things could cause disk access. My disks are on 24x7.
    1 point
×
×
  • Create New...