Crashplan backup performance to esata drive

Status
Not open for further replies.

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
My freenas box has 4 2TB drives (ZFS mirrored), running 9.2.1.7. Although mirrored, I wanted an off-site backup in case anything happens to the box (or the house) and to have a backup in the first place (home foto's/videos that are irreplaceable).
Since this data is not very volatile, I can live with manual backups after special occasions (vacations) where the backups are essentially copies (no need for timestamps).
I ended up choosing chrashplan backing up to a local 3T esata disk (formatted NTFS for more flexibility if I lose the freenas box) that I store with a friend in our area.
Where I am struggling is that the backup is only 1.2TB yet takes nearly a day. The backup averages (acc to the crashplan console) somewhere between 145 and 170Mbps. Freenas reporting tells me that the NTFS drive writes at 20MB/sec where the 4 source drives provide around 5-10MB in read each and the CPU performance not exceeding 40% (even tho crashplan is configured to go to 100%).
I used iostat to get a feel for the drives's throughput. Running iostat on the target NTFS drive bumped write up to 50MB/s on the freenas console (ie it is not maxed out under crashplan). Weirdly enough, the read performance on the source disk hardly go above the 10MB/s when I run iostat on them.

It sounds a bit odd to me that the read performance on the internally mirrored disks would be the bottleneck.
[EDIT] just noticed that the read performance is much higher as sabnzbd bumped it up to nearly 60 MB/s so it should definitely not be the bottleneck.

Really appreciate you insight.
 
Last edited:

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
If crashplan is single threaded (which I am starting to suspect it is) then the backup process will only max one core. I have a simple celeron 1037U which has 2 cores @ 1.8GHz. It probably makes sense that freenas reports the total CPU performance so 40% really is 1 core running at 80% utilisation ie a CPU bottleneck (caused by crashplan).
 

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
Just checked with code24 and crashplan is indeed single threaded. If you want to use crashplan for backing up to a local disk then make sure you have enough CPU power or enough time ;).
 
Status
Not open for further replies.
Top