Jump to content
Division-M Community


  • Content Count

  • Joined

  • Last visited

  • Days Won


Bonzo last won the day on March 3 2015

Bonzo had the most liked content!

About Bonzo

  • Rank

Profile Information

  • Gender
  • Location
    Ames, Iowa
  1. I am in the process of de-commissioning my WHS 2011 server (DB 2.4) and moving to a new Server 2012 R2 Essentials system. I have 29TB across 8 drives in my pool, and had been hoping to just physically move those drives from one server to the other and then transfer my license (I have DB 2.4 up on the new server in a "trial" version). I found the instructions on this forum for how to move a pool and it seems fairly straightforward. My question has to do with file permissions. On my new server I set up a domain and entirely new user accounts. If I physically move the drives over, will I have problems with file/folder permissions? Will Server 2012 R2E simply over-write the file permissions from WHS with its own? Anyone have any experience with this? I do have sufficient space on USB drives to move all of my files and then wipe my pool drives and start over, but that would take a long time to transfer the files and might be error-prone, so I'd rather just physically move the drives if that will work. Thanks for any guidance.
  2. Has anyone experienced moving from WHS 2011 to Server 2012 R2 Essentials? I've got my R2E server all set up and going and I'm ready to move my pool following the instructions in this thread, but I'm not sure how file permissions will work. Server 2012 R2-E uses the domain model, consequently my user accounts are totally different from my users on WHS 2011. If I just pull the pool out of the old WHS server and try to bring it up on my new server, will I have any problems with file permissions? Or will Server 2012 just ignore whatever permissions were existing and impose it's own?
  3. A few days ago I was removing one of the oldest drives from my pool (a WD7500AACS) to clear space for a new one, but during removal the WHS dashboard had a problem - unfortunately I didn't catch the error message but it was something about "out of memory". Anyway, the dashboard locked up and had to force shutdown of it (after about 24 hours of waiting for the problem to clear). According to the status bar, the disk wasn't fully removed at the time the dashboard crashed, however after re-booting the server and checking the dashboard, the drive I was attempting to remove is no longer shown as part of the pool. Anyone know of a way to confirm that it actually did get fully removed? I'm want to make sure before I replace it so I don't lose anything. Most of my folders are duplicated - is there a way to check for a duplicate that has no primary? Or a primary that has no dup? Or does DB automatically look for these kinds of scenarios? I'm still on DB 1.9.5 - thought I better get this issue resolved before I upgrade. Thanks for any suggestions.
  4. I am interested in setting up email notifications in DB on my WHS 2011 rig. I keep getting an error message that the specified ports require SSL support. I find this odd, since I have Hard Disk Sentinel and my UPS software both configured to send email via SSL. Could this be a firewall issue? I see there is a FAQ about possibly needing to install Open SSL, but if that were the case why would these other server applications have no problem connecting via SSL? Don't really want to install anything I don't need.
  5. Thanks for the suggestion for Winmerge. Looks like it might be worth investigating. I wonder whether it would be better to install it directly on the server or on a client? Also, has anyone used the WHS2011 Plugin "Snoop-de-doop"? It looks like another option but I'm not sure it's worth $15. I might give the trial version a try.
  6. I was trying to recover a pool after a boot drive mishap and ended up "merging" in a drive that I had apparently previously removed. DB is now reporting that I have "multiple primary files detected" and it looks like it has even been so kind as to go through and re-name the duplicates for me, appending a "(1)" to the end of the file name. Two questions: (1) How can I make sure these duplicates are actually bit-for-bit duplicates? Or has DB already done that level of comparison? (2) if two files are bit-for-bit dups, what's the best way to get rid of the duplicate file and free up that space? Thanks!
  • Create New...