Jump to content
Division-M Community

Leaderboard

Popular Content

Showing content with the highest reputation since 10/26/2020 in Posts

  1. 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
  2. Having said that, there is now a beta release, but please read the thread thoroughly.
    2 points
  3. 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
  4. 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
  5. Yes, the licenses are not Windows OS specific. They should work on Win7 and up.
    2 points
  6. 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
  7. 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
  8. 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
  9. Until DriveBender is officially supported on Windows 11, I would suggest that people stay on Windows 10 for the time being. If you upgrade to Windows 11, you will have issues. Thanks.
    1 point
  10. I was stuck in a miserable rut having cleaned out my Windows Update files. My media server was completely unusable. Luckily I remembered I still had my previous desktop that ran Windows 10 (that I hadn't booted in over 2 years). Fired it up, updated Windows 10 to 20H2 (it was on 1803 smh), I already had drive bender installed and all the configs set up (as it was the predecessor to my current machine stuck on windows 11). All I needed to do was physically connect my drives that formed the pool, enabled network discovery and sharing, shared the pooled drive then on my host machine I mapped the new network drive to the same mount point I used previously. If you're stuck on Windows 11 with Drive Bender out of date and have a spare computer (with Windows 10 still on it) try this: Update Windows Install Drive Bender Move (release) your license from the host machine to the temporary machine On the host and the temporary machine hit the windows key + s, type "Advanced Sharing" and hit enter (should open "Manage Advanced Sharing Settings - Control Panel" Enable discovery for your current network profile (Private, Public/Guest, All) then enable file sharing and printing for your current network profile On the host machine open file explorer and open properties for the drive you'd like to map over the network then click the "Sharing" tab and click "Advanced sharing..." (you may want to change the account access to everyone, and ) Any programs that previously mapped that drive will likely require a UNC path to replace the previously invalid path (As "\\server name\driveletter" i.e. "\\zulu\c" or whatever drive letter you need) If the program runs as an automatic service you may need to hunt down the executable and place it in your startup folder, when modifying the service properties, under the logon tab, you may need to change the user account to your current administrator, not Local System account On the temporary machine, open file explorer and right click on "This PC" on the left hand side bar and select "map network drive" Enter your UNC path to its mount point (as "\\server name\driveletter" i.e. "\\zulu\c") Be sure to mount it on the same drive letter you used previously to reduce complications If you need further help with restoring functionality to Plex Media Server, Sonarr, Radarr and NZBGet using this method, feel free to contact me.
    1 point
  11. Hello I put in a support request about this, emial I received follows Anthony Smith (Division-M - Support) Oct 5, 2021, 18:25 GMT+11 Hi, We are working on a new beta that will support Windows 11, it will be release as soon as possible. Thanks, Anthony Smith - Division-M
    1 point
  12. It might be worth raising a Support Ticket and asking the developer.
    1 point
  13. I have requested this feature in the past. I figure since DB sees all file create and delete within the pool it could easily do something like a SQLite DB type catalog of pool drives and files on those drives. It would then be trivial for a user to view this DB using SQLite Expert Personal. Seems that something like this would probably be a requirement for large commercial type installations.
    1 point
  14. I've brought up how slow Drive Bender is to the developer before. In my case I have my music library on a DB Pool drive and duplicated, 2 2.5" SATA on the motherboard. I also have a copy on my laptop on a single 2.5" SATA internal 2nd drive. The software I use to play and manage my music scans all my music files and builds a database of Artists, Albums, Tracks, Genre, etc. I use the laptop as backup, both the server and laptop use the same software. Here's the stats from a full scan on each. Server; Laptop; As can be seen in the total time (last line of scan details) the scan from the pool drive takes almost 4 times longer than the scan from a non-pool drive. The only thing I can suggest is that you open a support ticket with the developer and you can reference this thread. Submit a request – Division-M - Support
    1 point
  15. WKO

    Release my license

    everyone Thanks for the help Webb
    1 point
  16. Anthony

    Release my license

    Hi Webb, I have responded a number of times to you support requested, and I see I have a couple of more support message that would indicate that you are not receiving my replies. Maybe check your spam folder? I will respond again right now, let me know if you received these.
    1 point
  17. w3wilkes

    Release my license

    If you message Anthony (not a forum post) it is private so you should be able to send the order # via private message. It sounds like you may have recorded your key # incorrectly.
    1 point
  18. @Fozzie Bear Perhaps raise a Support Ticket for the devs to know, even though you've resolved it. Thanks.
    1 point
  19. Have you enabled Drive Idle in the DB settings? This is experimental, but is touted as a power saver so I guess it will down the pool drives when not in use. I understand why not to use the same drive as the system for a regular pool drive. However, Doesn't a LZ drive get cleared on a regular basis to make room for more data? I would think that primary (and duplicate folders/files) are pushed off the LZ to regular drives. There is a file loss exposure if the LZ drive fails, but this is the case regardless of whether it's a partition on the system drive or a dedicated LZ SSD. You can always open a ticket and ask the developer for some specific guidance on using a portion of the system drive as a LZ. Submit a request – Division-M - Support (division-m.com)
    1 point
  20. Uninstall DriveBender, reboot, install DriveBender, reboot. Go into the DriveBender UI and recover the pool from the attached drives. Let us know how it goes. You should never lose any data with DriveBender. Worse comes to the worse, you can move your content on each drive to the root of it, delete the DB folders and create a new pool from scratch, but come back before you start on that path. Thanks.
    1 point
  21. CBers

    release

    A Support Ticket to de-activate your licence key? You have 30 or 60 days to use it as a temporary licence. If you still don't hear back in a few days, let me know. Thanks.
    1 point
  22. Just to follow up, received reply from developer saying Drive Idle will be re-written for version 4.0. No indication of when that might be.
    1 point
  23. Thanks for the reply. The install went incredibly smoothly, and my old unused licence key was accepted, so kudos to Division-M!
    1 point
  24. Damn. I lost a 4Tb drive last year, but didn't lose anything I couldn't recover from elsewhere. I made sure I had my important content duplicated within the pool and/or backed up to my Google Drive.
    1 point
  25. Sorry I'm so late to your party. Have you checked the manual, it's in the DB program Files directory? In my own case the only thing I have on my DB drives is well known so knowing what's where is no big deal for me. It would really be nice if DB kept a "catalog" of files in the pool so that questions like this could be easily answered. I've submitted this as a request before. Maybe if we get more people to suggest it...
    1 point
  26. Sorry this is so late! Sounds like you need to open a support ticket with the dev. Here's the link; Submit a request – Division-M - Support (division-m.com)
    1 point
  27. Been using Plex with Drive Bender for years. I have had NO interoperability issues, whatsoever. As for duplication, you enable it per folder. So if you have 100 files in that folder with duplication turned on, you'll have a copy of each 100 files elsewhere on a different physical disk in the pool. That also means that that folder will be using up twice as much storage from the pool.
    1 point
  28. I presume you opened a ticket as @CBers suggested in reply to your prior post. What was the reply?
    1 point
  29. 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!
    1 point
  30. No known estimate at present, but hopefully before the end of the year.
    0 points
×
×
  • Create New...