Jump to content
Covecube Inc.

Rob Manderson

Members
  • Content Count

    19
  • Joined

  • Last visited

  1. I'd be inclined to close out of the warning for now and remeasure the pool first. (Click on the Manage Pool text below the pie chart and select re-measure). If that doesn't resolve it.... hmmm not sure what I'd try next.
  2. I'm pretty sure it's not harmful - I have 4 drives in an enclosure that was originally connected through USB3 and therefore considered external. A few months ago I switched the enclosure to eSata but the drives are still considered external. I assume it's because they were external when added to the pool. Nonetheless, it irks me that they are considered external! :-) But it's not so important that I'd be prepared to remove them one drive at a time and re-add (along with the balancing etc) just to get that internal designation. Anyway, I've seen no problems arising due to the incor
  3. I've been using Mediasonic 4 bay with eSata for about 9 years. I now have six of em and they're rock solid reliable. I use x3 duplication for the entire pool - about 37 TB in total with 26 TB free space (I really love the duplication feature of DP - in 9 years I've had drives fail but never ever lost a file). This is on Windows Server 2019 standard. I did, however, encounter one anomaly. I have 4x 4TB Seagate SMR drives and I had extremely slow transfer times when adding them to the pool and doing a rebalance. At the time I had x2 duplication. I was getting duplication speeds in the
  4. This is just a guess but.... the recycle bin is 'special'. It's not a real folder, it's a virtual folder. Ever noticed that the recycle bin is the one place in Windows where you can have two or more files with the same name in what looks like the same directory? I suspect DP may be getting confused by files having the same name. Or I may just be wrong :-)
  5. Nope - as far as I'm concerned even one bad sector is reason enough to replace the entire drive.
  6. I have the following scenario. I have one pool with x2 duplication turned on for all folders/files. No balancing or file placement rules (stock standard out of the box install with no customisations). Let's call this the Primary Pool. I have another pool which contains a copy of all the files in the first pool but without duplication. Let's call this the Secondary Pool. The file and folder structure exactly matches that of the Primary Pool - in fact it was copied using RoboCopy with the /MIR option. What I'm thinking of doing is creating a new pool and adding the Primary and
  7. You can run the 2016 WSEE (Windows Server Essentials Experience) on 2019 - I upgraded my server this very weekend to 2019 and still have client backup, dashboard etc. See here https://www.theofficemaven.com/news/installing-windows-server-essentials-experience-on-windows-server-2019 for the dirty details. It isn't for the faint hearted though. At the very least you'll need to be able to do a clean 2016 install and stop before configuring the WSEE component in order to grab the unmodified files and registry entries. Then you get to do a 2019 install and copy a bazillion files etc b
  8. That's exactly how it works. Disconnect, install and activate, reconnect drives, install drivepool and Bob's your uncle. I wish other software were as easy to deal with as DrivePool. You *may* have to reactivate the license - depends on whether it notices a sufficiently significant change in the system. However, the trial license will give more than ample time to work through that issue with CoveCube.
  9. Heh - I have triplication turned on - for the same reason you went duplicated. Started out with ~8TB duplicated and went to triplication - it took 3 days and that was without a single one of those damn SMR drives installed. I've given up on the SMR drives - nothing will make them behave. Yep, other peoples experience may differ - I can only go by what I see and what I see is that anywhere between 20 and 100 GB of continuous writes is all they'll take before they slow to ~500KB/s write speeds. Leave them powered up for 24 hours with no further writes and they're *still* sitting at ~500K
  10. Hmmm and now I don't have the Stablebit Scanner entry on the start menu at all. Edit: Cancel that - I was looking at the wrong machine! Doh! I do still have tne start menu entry but I can't see it in the Stablebit GUI. I can't remember if it was there in the 1.x version I was running on WHS2011.
  11. Start Menu, Stablebit Scanner - Tools (Well, at least on WSE2016).
  12. Ah, ok. So you recommend that I add (say two) of these drives to the existing array plus an SSD. My normal writes go first to the SSD and in the background it replicates to the SMR drives. Since those are empty they'll receive the writes until they match the other disks and after that writes will start consuming space on the existing drives? I say two drives because I have duplication turned on (one of the best features of DP). Since I have duplication on do I need to have two SSD's?
  13. Follow up. I think I found the reason why duplication was soooo slow. My legendary cheapness caught me out! My array had consisted of a mixture of 2, 3 & 4TB drives. The new 4tb drive mentioned in the first post above was a Seagate ST4000DM004 drive, which is an SMR drive. Apparently these drives are intended for the archive market and have very slow write speeds if you're pumping a lot of data into them in a short time. This is one reason they're cheap (and why I chose them). Such a pity the Amazon product page makes no mention of this. Indeed I only found out by searching on t
  14. Thanks for the reply. I think I'll live with a monthly reboot of the server.
×
×
  • Create New...