Copyright (c) 2006-2014 MindTouch Inc.
This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).
At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.
A complete copy of the MSA is available at http://www.mindtouch.com/msa
Have you ever wondered what goes on with CrashPlan behind the scenes? In this article, we'll take a closer look at exactly what happens when CrashPlan is backing up.
Let's start with an example scenario where CrashPlan is using its default settings and is backing up your user home directory.
CrashPlan constantly watches for new and changed files within your home directory with what we call the real-time file watcher. It adds new and changed files to a TO DO list.
Let's say that you created a document called “Letter to Grandma.doc”. The real-time file watcher sees that you've created this document and adds it to the TO DO list for backup.
This is what happens when CrashPlan starts backing up Letter to Grandma.doc:
Data is securely encrypted throughout this process.
The process repeats for the next block within the file until CrashPlan has analyzed and backed up the entire file. In this way, only unique information is backed up, which saves bandwidth and storage, and makes restoring faster
As you're working on your letter and making changes, CrashPlan's real-time file watcher sees that the file has changed and CrashPlan puts the file back into the TO DO list. If your letter is 1 MB, 1 MB is added to the TO DO list. Only the changes are actually sent to the destination, however, not the entire file. The changes are backed up while you work, creating a new version of “Letter to Grandma.doc”.
In this example, you've added a paragraph (highlighted in red):
There are actually two ways that CrashPlan learns about new files or changes to your existing files:
With two methods of identifying file changes, your files are doubly protected—CrashPlan checks for changes twice to make sure your files are backed up.
The real-time file watcher works directly with the tools built into your computer's operating system, which means it is fairly lightweight and can easily work in the background without you noticing.
The scan requires a bit more resources than the real-time file watcher, so to minimize possible impact on your computer, the scan runs at 3 am every day by default, when most people are less likely to be working at the computer.
Of course, you probably have more than one file on your computer that you'd like backed up. CrashPlan can't back up all files simultaneously, so how does it decide what to work on first? We designed CrashPlan to back up the newest and most recently changed files first. This ensures that the most recent versions of your files—what you're working on right now—are backed up as soon as possible. The priority order looks like this:
Whenever a file is added or modified, CrashPlan adds it to its backup to-do list. Changes are added to the backup based on the frequency at which CrashPlan backs up new versions, which by default is every 15 minutes. You can change this default setting under Settings > Backup).
We always recommend that you back up to multiple backup destinations for fastest backup and restore and for best protection, but exactly how does multi-destination backup work?
CrashPlan prioritizes backup activity to ensure all your selected files are completely backed up at one destination before starting backup to another, redundant destination. To accomplish this, CrashPlan backs up to destinations which it determines should complete fastest:
For example, if you are backing up to a local folder and to a friend's computer, CrashPlan completes backup to the local folder before backing up over the Internet to your friend's computer. Once backup to a destination completes (or if that destination becomes unavailable for any reason), CrashPlan backs up to the next destination.
If you choose to enable Backup Sets, you can specify backup priority. The goal is still to back up all your files to at least one destination first. Then, CrashPlan works on redundancy to back up your files to additional destinations. As long as one destination in the set is complete, CrashPlan moves on to back up other, less complete sets. When you have Backup Sets enabled, CrashPlan follows these rules:
The backup process always works the same, whether you have one computer or ten computers in your account.
CrashPlan treats each computer within your account separately and each computer's backup is stored separately at each destination. Each source computer stores its backup in its own folder. The folder name is the source computer's ID.
In this example, John and Michelle are backing up to Chris. This is what it looks like on Chris' computer:
Storing each computer's backup in its own folder enables seeding, which is the process of backing up locally and then physically transporting the backup drive to an offsite destination, such as a friend across town or to our data centers. Seeding is a great way to kick-start a large backup to an offsite destination and saves on bandwidth because the backup does not go over the Internet.
Occasionally, CrashPlan's data de-duplication needs to re-scan your files to see what's already been backed up. When this happens, it looks like CrashPlan is backing up all your files from the beginning, but it is actually reviewing each block to see what's been backed up already. How can you tell that this is the behavior you're seeing?
Verify that the amount of data being stored is a number that is consistent with your file selection size and previous backup completion. From Backup, click the name of the destination to view stats for the chosen destination. Under Space used, verify that this number is an amount of data reasonable for your file selection size and previous backup completion.