You need the crashplan client to make sense of it. The files are in crashplans proprietary format and, especially if you're using compression, dedupe or encryption, are very obfuscated. You can't just see the files via the filesystem and manipulate them from there. You'll get another directory, with a byte / block id, for every 4 gigs you back up. Inside each of those directories will be a 4 gigabyte file (and a couple of other bits of metadata) that contains your backup data. So you may end up with something like (numbers made up) : Within that directory it will create a structure based on the Crashplan ID of your machine and then what I think is the 'virtual block / byte range' it uses internally. I assume it will decide where to put things? Will it fill a drive to overflowing before going to the next drive? Or can I just do a similar backup to how it is working with rsync?Ĭrashplan asks you where you want to store incoming backups. I suspect it's single threaded and we all know it's a memory hog!. I don't really think the client is very good. You can throw all the bandwidth locally at it you want but you'll end up gated somewhere and hit a brick wall. Having said that, I have found there is a performance cap in crashplan at some point. This could explain why you're seeing it vary as it will depend on the data type. Compressible or dedupeable files will have the client report a much higher 'file throughput' rate as it's pipelining the data more efficiently. Therefore it would report a lower throughput rate (closer to your actual network transmission speed) on data that it can't compress. What are you using to measure the speed? The Crashplan client doesn't measure 'wire speed' but rather the speed it's churning through the data. Comcast business class looks like about 4Mbps, roughly ten times as long: 600 hours per TB (25 days).Īny ways to boost my local backup performance so I can backup my 15 TB from one box to the other and then take the backup offsite? :-)Īny way to get it to perform both backups at the same time? Seems I can only do cloud or local, can't do both at the same time. Going up to the cloud is obviously much, much slower. Remember that Crashplan encrypts, versions, etc. Not sure why it varies so much, but if you were estimating transfer time I'd estimate about 300 Megabytes per minute should be pretty achievable. Just wanted to share for those that are interested - both wired to a gigabit wireless router I get one backing up to the other at about 40Mbps, sometimes up to 150Mbps. They're pretty standard boxes, copying the hardware of the "Official builds" that Tom provides. To take advantage of CrashPlan, please contact the IT Service Desk.įor troubleshooting this service, please see the knowledge article.After literally several years of waiting and tinkering, I finally have two UnRaid boxes and have Crashplan running on both. If you ever lose the keys, or are separated from the University, campus technical personnel will be able to recover your data (with appropriate authorization). The campus offering differs from other backup services in that you will be able to use your campus Kerberos authentication to access Crashplan, and that the keys used to encrypt the data on your computer prior to transferring it to CrashPlan are stored locally on a UC Davis managed server.
#Crashplan twitter android#
It is also worth noting that there are iOS and Android apps for CrashPlan which allow you to view files in your cloud backup store (it does not backup your smartphone), but be aware that logging in with your smartphone app consumes one of your four licenses. CrashPlan works on vendor supported versions Windows, Macintosh, Linux, and Solaris. If you need to back up more than four devices, you can purchase blocks of four devices at $100 each for the same Kerberos account. Backup occurs to the CrashPlan cloud service and is unlimited in size and unlimited in file versions. The cost for the service is $100 annually for the ability to backup up to four devices. CrashPlan ProE is a campus-wide offering for the backup and restoration of files on personal computers or servers.
0 kommentar(er)
