How does CrashPlan perform on high latency networks like satellite or cellular?
CrashPlan works extremely well and remains quite usable on high latency networks. There are many reasons for this, but mainly because: CrashPlan assumes the worst – It makes no assumptions about quality of link and is quite patient. CrashPlan is extremely efficient – Our binary protocol rides on top of TCP and doesn’t waste a bit. CrashPlan is a streaming protocol – It does not rely on acknowledgements (ACK) from server when sending data. Data is streamed as fast as possible. The only ACK is a TCP ack in the underlying protocol. CrashPlan recovers – Backing up a large file? CrashPlan resumes within the file. So even a 1TB file can be backed up over poor line that keeps dropping. We’ve been used on cellular networks (1G, 2G, 3G), satellites, DSL, Cable, Wireless and wired ethernet – all with great success. Things you may notice in a high latency situation: Long delay when changing desktop preferences. Frequent restarts of backup due to disconnects. It won’t give up in these situations,
