Starbuckz8

Just wanted to stop by to say thanks. All seems to be going well thus far. 2 days and still indicating full duplication. I do have some bigger drives I plan on putting in, just haven't had the "need" or "will" to do yet. So I'll test it out this month by doing a hard removal.

Sorry for the late reply. Been busier than expected at work lately. Duplication was configured since the beginning and I would be lead to believe it was operating correctly. Didn't test it on the actual build. But the server snapin reported it as such atleast. That would have been...hmm...when did I contact you for licensing problems? February. After the post I was a bit hesitant to to just disable and re-enable it to not put the extra stress on the drives. But I did. Same result as before - duplication is set to 2x but only 4.39GB are duped. Will give the beta build a try and see what happens. If not, are there any logs I can grab? Edit: after installing and rebooting, it immediately started duplicating. The previous install didn't, so I'll hold out hope

OS: Windows Server 2012 R2 Standard Stablebit Version: 2.1.1.561 Total Storage: 11TB Total Data: ~3.5TB Folders within the pool: 11 I've had duplication enabled on the entire pool since I set this up. And this server generally just sits there and rarely remote into it. It, along with stable bit have been very stable. Last week I noticed that duplication was not actively running even though it is set to 2x. Was reporting something around 152GB duplicated. So I disabled duplication, waited for it to clear out. Then re-enabled - again - back to 2x. Took just shy of 24 hours. Today I checked, and even though it still says 2x duplication, it's reporting that 4.38GB are duplicated.

No need to reply. Out of impatience waiting for it to complete, I decided I'd just copy the last few remaining files to desktop and then copy them onto a different drive within the pool. Even though I wasn't sure how well storage pool would handle direct copy into it's hidden folders. That's when I realized that every time it hit one of Microsoft's backup 4GB blocks it would slow down to 0 and then error out as well. As this drive wasn't one directly connected to the motherboard but an Intel SAS expanded I moved ports around and it told me what I already knew - the news is the gravest... The irony, and incredibly funny part is when I added the drive that went bad I said to myself "if I add in more than is need now, I won't get around to this until it's too late". Gots nobody to blame but meself. I just hope it's one of those 4GB files that takes an hour to recover from, instead of 2 days. With MSFT you really, never know... But hey! If we all followed best practices; all the time, half of us probably would have best-practiced ourselves out of a job, right? After it's done repairing the backup database I'll set everything to duplicate. I promise. Yeah - I've also been saying I'm going to CrashPlan Free to the office. I haven't gotten around to that either.

I'm finally getting around to removing the initial 1TB drives with larger. It's been on my to-do list for a while but as there isn't much free space, I had to start out replacing one by one. My current problem, is when I go to remove a 1TB drive, drivepool errors out with "The request could not be performed because of an I/O device error". I currently have 8 drives in the server. At the time of the removal, I can tell it was reading from J:\ - drive to be removed and writing to E:\ - just replaced larger drive. I've since added the cleaned drives back off and am duplicating the entire pool as there is now enough space to handle it. But what I'd like to know; and didn't see logs for, are if the I/O error is from the read or the write. I've set the load balancer on J to nothing to prepare it for removal, but can't tell if I should actually have it set on E