Jump to content
Division-M Community

oj88

Members
  • Content Count

    136
  • Joined

  • Last visited

  • Days Won

    5

oj88 last won the day on June 1 2015

oj88 had the most liked content!

About oj88

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. 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?
  2. 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.
  3. 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!
  4. When you added drive D:\ into the pool, can you still see D:\ in File Explorer?
  5. 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.
  6. 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. Does DB go into trial/eval mode? If so, for how long before it expires? 3. In case I've migrated the pool drives on the new OS but run into problems (non-DB related) and need to rollback to the old OS, will there be an issue accessing the pool drive again in WHS2011? Thanks!
  7. 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.
  8. I'm also waiting for DB to fully support Server 2016.
  9. 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-pool- Note: Edited for brevity.
  10. I assigned letters on mine so I would be able to run Windows' native disk tools like error/surface check, defrag and disk cleanup.
  11. 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 best practice to run a comprehensive surface test using a hard disk utility before putting them into production. If a hard drive turns out to be a dud in the test, it's easier to have it replaced since it's not holding any of your data. I personally use Hard Disk Sentinel Pro.
  12. I'm sorry that didn't work for you. You may need to contact support. You should still be able to get a response within a day or two.
  13. Try this procedure if it fixes your problem. Uninstall DB Reboot Install DB 2.4 Reboot
  14. I ran into a similar issue several years ago. I initiated a drive removal and left it running overnight. The next morning, I got a dialogue box saying that the drive removal process was completed/successful. But then, I noticed that there is still data in the drive that was supposed to have been removed (I kept the drive letters so I will always have access to the individual disks). I clicked on Running Tasks in DB Client and to my surprise, it is indicating that the Disk Removal process is still running (Overall progress at 6%). If I have shutdown and removed the drive, that would have caused a potential data loss. This was version 1.4.5.0 mind you so it may no longer be apples to apples with the current version. I just thought I should share my experience.
  15. I've read somewhere that Handbrake would move files around after conversion. Some people have reported that even after manually setting where the file should go, Handbrake would still move the converted file to the default folder location. It's a shot in the dark but I'd try searching for the file elsewhere in the pool or on your other drives, including the OS partition.
×
×
  • Create New...