Jump to content
Division-M Community

silkshadow

Members
  • Content Count

    48
  • Joined

  • Last visited

About silkshadow

  • Rank
    Advanced Member
  1. Just replying to keep an eye on this thread. Thinking of taking 8 old SSDs gathering dust and making a DB pool out of them as I am planning on a large LAN upgrade soon.
  2. Sorry for the late reply, I should've come back to check but I got really busy and forgot to. Just want to say thanks Anthony for not abandoning us.
  3. Thank you Anthony! I was planning a 2016 full LAN upgrade this week but I can hold off for a little bit. I know this is always tough, but any chance of a very rough ETA? Can you tell me if it will be before the of the month?
  4. You should buy a license for DB from Anthony if you can. That said, if there is ever a day that it is no longer possible to buy licenses (happened with SageTV and it happened really fast and suddenly), I have a bunch of licenses I will never use. I periodically bought new licenses as a form of donation hoping to help Anthony keep DB alive. Give it some time, but if you or anyone gets really stuck and Anthony hasn't come up with a buyer or any kind of forward plan, send me a PM. I believe it will email me.
  5. ​When I saw the announcement, I was filled with both deep sadness and dread. With one of my storage pools almost at 160TBs now, I am filled with dread for the future. As someone who was anticipating DB from a post over on the Wegotserevred blog, even before the beta test, I am very sad to see things go this way. I expect good things for you in the future Anthony. Except for the 1 incident with the poor decision to use an overly aggressive DRM scheme in the old version, DB has been more stable than even Windows Server for me. So your work is well proven and I am sure opportunities will abound. I only ask do not let DB die or sell to someone that will kill it, please? Just in my home media life, I've already gone through that with Yahoo/Meedio and Google/SageTV. I still haven't fully recovered from the death of SageTV. If I am unable to use DB I am not sure what I will do, how I would migrate all of this data is beyond me. The future of my data is now in your hands, please treat it well. Good luck and thanks for DB!
  6. I have a pool on a HTPC/gaming PC that has less than 10GBs free. Physically the computer has no more SATA ports available. I have a new 1TB SSD to replace a 250GB SSD currently in the pool. I have a USB 3.0 port and a USB 3.0 to SATA bridge/dock. So what would be the best practice here on how to do this? Should I use DB's drive swap function? Will that even work with no space in the array? Should I hook up the 1TB SSD via USB 3.0 and try and dump the contents of the 250GB onto it and then add it to the pool? Will DB freak out during this process as I have duplication on for some folders? Or should I kind of plug in the new SSD via USB 3.0, add it to the pool, wait for that to finish, then do a remove from pool on the 250GB ssd, power down PC, pull 250GB out and put 1TB in its place? Would that even work via USB as I've never added a USB based drive to DB before. Or is there mix and match or better way to do this I haven't thought of yet? Thanks!
  7. Just to answer my own question here, I experienced no problems to existing data that is duplicated or not resident on the failed drive. I opted to pulled the drive and do a pool repair as running in Fault Tolerant/read-only mode was making me way too nervous. However, after the failed drive's removal my existing space was not sufficient to restore all the duplicated data. So some of the data was unavailable to me unless I mounted the drive the duplicated data was resident on, and searched for it in the duplicated folder. Also, I experienced high CPU usage from DB while it tried to restore data that there was no room for. Or I should say I assume that was the cause and it seemed that way when watching the log activity, but I am not sure that was the cause. CPU usage spiked to over 50% for extended periods. We had a typhoon hit us and we had to chopper back to civilization before the storm hit. I was unable to find a 4TB drive replacement though, and my plan was to find a 4TB drive and then restore the sector by sector image I had taken of the failed drive. I was only able to pickup 2 2TB drives. Anyway, I brought it back to our island when it was safe today. I can see that the data that was unable to be restored before is now getting restored. Unless something else happens, it looks like, even after extended time up with a removed drive and limited free space, I suffered no duplicated data loss.
  8. Thanks for addressing this thesmith. Actually it changes my viewpoint on this issue to know that the license system is an off the shelf item. However, the issue is not just the bug, it is a fundamental one. To spell it out, you were willing to treat a paying customer like a criminal with a day and a half of completely unnecessary downtime. So that is to say that I am not convinced. I would look at this system and say never would I implement it. Fundamentally its stupid. You risk 24 hour+ downtimes for your customers (and a business could not afford that) in return you get a failed attempt to stop piracy? That would be unacceptable to my business, but my business is logistics and my customers are too important to me to risk even though pirate problems for me are real pirates with guns. Not kids behind a keyboard cracking software which studies show can actually help sell more copies. With things like Stablebit, Flexraid and MS's own solution improve and put pressure on you, IMO you do not have room to screw with your customers like I was screwed with. Regardless of how you view your customers, we have the ability to impact your bottom line and risking our downtime seems silly. So getting down to brass tax, you will hopefully fix the random license revocation that I experienced. That's a step in the right direction but this: is still a very serious problem. Say you do fix it only to have something else pop up that causes random license revocation? Its an endless cycle. The grace period has(!) to be longer than the longest vacation your support staff takes. At a minimum that should be 3 days to cover weekends ideally 14 days to make sure.
  9. Thanks guys! To be clear, I do not blame DB for taking the system down. I think the bad drive is breaking DB and several services and other apps on this box depend on the DB pool are breaking Windows. Either way the solution is to pull the drive. My concern is running the DB pool in R/O mode for an extended period. I've never had to do that before, so was just checking if anyone knew of any unintended/unforeseen issues apart from the normal R/O issues? Especially in regards to the 10% of data that is duplicated and unique to this box (all pictures and home videos). Thanks!
  10. Sorry I am late to this, but I use a raid expander card with a LSI card to extend my pools to 48 physical drive bays (still have 18 bays free though). DB handles this fine. So depending on your scenario, that may be a better way to go.
  11. Ran the early versions on SBS 2008 R2 and now running on SBS 2011 essentials. On SBS 2008 though, both my SQL and Exchange stores were on a raid array not DB. Lack of VSS support is a significant issue though, so keep that in mind, but it looks to be addressed in a future v2 release.
  12. 2 of the 5 things that I warn about DB when talking about it that I do not see in the proposed changelog. To be clear, at this point, I am forced to give DB a neutral to negative recommendation (depending on the situation) in discussion and social channels because of these issues. As an original beta tester and long time user, man I like this program, but I find these issues to be recommendation breaking. Thankfully you are addressing 3 of them in v2.0 but these 2 are not addressed: 1) Drive removal is terrible. There is no error handling. If a file is on a bad sector, DB will sit there for weeks trying to move it. Needs a time out. Removal process chokes on folder.jpg all the time for me. IDK why, but the removal process ends up sometimes creating a duplicate folder.jpg in the same directory and the drive removal process just stops. After waiting 10+ hours, I then have to manually delete the extra folder.jpg and start over again. Needs a skip prompt and automatic error instructions. See directory opus (a fellow Aussie dev) and how it handles non-prompting file moves. Bottom line: the drive removal process has no error handling. This needs to be addressed. 2) License system. Here is my scenario. Nothing had changed in my system for months. Reboot my server only to find a warning that my license was in trouble and I had one hour to correct it or my pool would go into R/O mode. 1 freaking hour!! Yet you take a day+ to reply to the support ticket? This is why piracy exists and I sometimes get what the pirates claim about making software better. The pirates can go on using their DB but mine was in R/O for more than 24 hours and I lost an entire day. Bottom line: The license system needs to be scrapped or drastically fixed. You piracy paranoid devs don't get that the worse your system is for your actual customers, the more it invites piracy and just ticks off your existing customers who then spread that anger though their networks. For a product like yours whose customers are all the tech leaders of their social and professional circles (ie the tech product recommendation go to), you get the HTC effect x10. At a minimum the grace period should be as long as however long your longest vacation is. Right now I have and will continue to tell anyone looking to use this product for a business to expect their business to be down for 24+ hours because of DB. This is a "do not buy" for business and a breaking bad for consumers decision on your part.
  13. Funny I just had the opposite. A drive died and no smart warnings from sentinel/DB. One of my big gripes with DB as is. Error handling on drive removal is just dumb, as there is none.
  14. Non 10k+ mechanical drives get practically no benefit from sata3 over sata2. The bottleneck there is not the bandwidth but the performance of spinning plates. So really you could make the 2nd pool, but performance wise it won't make much of a difference (if any).
×
×
  • Create New...