Jump to content
Division-M Community

oj88

Members
  • Content Count

    140
  • Joined

  • Last visited

  • Days Won

    9

oj88 last won the day on October 30

oj88 had the most liked content!

About oj88

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. Everything I've done is default or out-of-the-box settings. In case you don't already know, that particular Backblaze plan doesn't support Windows Server OS. The Backblaze app will also not allow you to backup mapped networked drives/NAS. It's likely it won't let you backup the pool drive as well. Though it might backup individual drives in the pool, how it would work with Drive Bender's folder structure, I don't know. That unlimited plan is full of caveats. Better try it out first before committing to it, long term.
  2. 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.
  3. 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.
  4. If it's the boot/system drive you want to clone, there shouldn't be any issues with DB. I've done it a few times through the years, even installing a fresh new OS. DB was able to find and mount my pool drives, no problem.
  5. 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?
  6. I have in the past, put the client backup folder in the pool and have had little to no issues with it. It worked for years until I retired WHS2011 about a month or so ago. I would try running the client backup database repair tool from the Dashboard.
  7. With the recent admission from Western Digital squeezing in Shingled Magnetic Recording (SMR) technology on some of their WD Red NAS drives, among other models, should I worry about them with Drive Bender? I know that SMR drives aren't suitable for RAID volumes and that Drive Bender isn't RAID, I'm still interested to hear from @Anthony if there are use cases where SMR drives might not be a good idea for use with Drive Bender. Thanks!
  8. When you added drive D:\ into the pool, can you still see D:\ in File Explorer?
  9. 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, Driv
  10. I'm creating a checklist to migrate from WHS2011 to Windows Server 2019. Basically, I'm swapping out the old SSD with a new one where Win2k19 will be, but still using the same hardware. This server runs Plex Media Server as well as the UniFi Controller, among others.... which implies that I need to be very cautious with every step as well as familiarize myself with the behavior of each software/app that needs to be moved. Question is, when I release the Drive Bender license from the old OS, what happens to that DB instance? 1. Do I immediately lose access to my pool drives? 2. D
  11. I just opened a ticket. I was wondering why my SSD system drive was running out of space. To my surprise, the DB log files I have total to just a few bytes shy of 60GB! That's dating back to Jan or Feb this year. I asked two things.... 1. Can it be safely trimmed down or removed altogether? 2. Can it be moved to a different, non-SSD drive? And in doing so, will the performance degrade? UPDATE: After receiving a reply from Anthony, I went ahead and deleted all the files under the Logs directory. The server is still up and my SSD can breathe again.
  12. I'm also waiting for DB to fully support Server 2016.
  13. Accessing the physical DB drives directly for purposes of directory or file MADs (modifications, additions, and deletions), etc., should NOT be done. Such operations must be performed through the pool mount point and let DB manage the files. However, for purposes of error-checking or repair of the individual DB disks (a process which does not modify the file or directory structure, other than to repair it) accessing the physical DB drives directly is supported. In fact, this is documented in the FAQ; https://support.division-m.com/hc/en-us/articles/214026403-How-can-I-check-the-drives-in-a-po
  14. I assigned letters on mine so I would be able to run Windows' native disk tools like error/surface check, defrag and disk cleanup.
  15. For something that's brand new, it already has 0xC4 (196 in decimal) Pending Sector Count. This is the number of sectors that has been identified by the drive logic to be weak/unreliable at best, or unreadable at worst. Eventually, these sectors will be marked as Bad and your Reallocated Sector Count will go up. In reading SMART parameters, just take note of the RAW entries. In other words, this typically indicates an impending issue with the drive (ie. weak magnetic media or physical damage on the disk surface). If you can have it replaced, do so now. Tip: On any new hard drive, it is
×
×
  • Create New...