randomrage

I'm pretty sure the backups aren't corrupted. They worked when they were on the root folders of one of the pool drives (not in the pool), and they work now that the offending external drive has been removed. The new drive is a 3TB external drive. I forgot that 3TB drives are tricky so I would have mentioned that earlier. Is it possible that had anything to do with it? I also don't know how much troubleshooting I'll be able to do as I've got to take the drive back while I'm still within the return window.

I was able to narrow the problem down to a new external drive. Here's what happened in order: 1) Old external drive died. 2) Booted into system without drive connected. Removed from drivepool. 3) Added new external HDD. Let Drivepool balance (entire pool duplicated). 4) Upgraded to v320 And that's when client backup stopped working. I removed the new external drive today and was able to successfully create manual backups on two separate machines, both pointing at the pool. The new external HDD seems to be okay, it's passing chkdsk scans (don't have a more complicated way to scan). I'll be happy to share any error logs or anything else if you guys want to tell me where to get them.

I'm having the exact same problem. Running WS2012e and I've had all my server folders in a drivepool for a while. Recently, however, one of the pool hard drives died (I replaced it without incident and since everything was duplicated -- in theory without loss). Since around the same time, client backups aren't working. I moved client backups to one of the pool drive root folders and they worked again, and I was able to backup successfully. So I moved them back to the pool, and I can't back up client computers again. I'm running v2.0.0.320.