Nowhere does the CrashPlan app show you which files are already backed up and which are still missing. Can I safely eject the external drive during that time and re-attach it later or would this cause the backup info to get lost? I don’t know, and the app doesn’t tell me. Only when that process is finished after a week or two, it will start to recognize that the files I moved to the external drive have already been backed up. Since the app backs up the newest files first (which is generally a good idea), it starts backing up the videos I just downloaded.I start to wonder, did I do anything wrong? Will I have to re-upload these files? To the CrashPlan app, this looks at first as if I am adding hundreds of gigabytes to my backup because it does not recognize immediately that the files are being moved. After the file scan is complete, I move the files I want to the external drive.Downloading 300 gigs of videos takes some time, too, after all. It is not clear whether I can begin moving stuff to the external drive during this time or not. As mentioned earlier, the CrashPlan client now starts to rescan all files in my entire backup set! In my case, this will take 12+ hours.Since I don’t want to lose any of my existing backup, I first have to add the external hard drive to my CrashPlan backup set. If I would just move files that are currently included in the CrashPlan backup to the external drive, CrashPlan would delete them from the backup.So let’s connect an external hard drive and move some stuff to it from my internal disk.
Update crashplan free#
Since there is not enough free space on my internal drive, I need to free some up first.
Update crashplan download#
Let’s take a fairly common scenario: say I want to download and backup the WWDC 2013 videos. Overall, the app too often gave me the feeling that I was not in control of the backup process. If backups occur during this phase, the app does not say so. The app’s UI is not really clear what happens while the synchronization is in progress. Even a simple action such as removing a folder from your existing set of directories to back up causes the CrashPlan app to re-scan everything. The re-scanning also occurs whenever you modify your backup set. When I contacted support about this, they acknowledged that this behavior was not expected, but the recommendation to increase the memory allocation for the app (apparently you have to do this manually for a Java app) to up to 2 GB did not have any effect.
On my machine with my admittedly large backup set (1.3 TB across almost 2 million files 5), this “Synchronizing” process takes forever: anywhere from 12 to 24 hours is common. 3 The app regularly 4 re-scans the directories in your backup set in order to to check for files that have to be backed up (in case the on-the-fly monitoring misses a file that has changed) and to identify files that can be de-duplicated (if you backup multiple identical files, they will only be stored once). The biggest problem of the CrashPlan client is that it seems really slow.
Update crashplan mac#
The CrashPlan folks have been saying on Twitter for more than year that a native Mac client is in the works, but they (wisely) decline to give a release date. Requiring Java for an essential app that is running in the background all the time is not just an inconvenience, it is also another thing that can break. I realize this is already a deal-breaker for many and it probably should be. The problem I have with CrashPlan are mostly related to the CrashPlan client app.
Update crashplan full#
This is a sad realization for me because the (non-monetary) investment I have made in CrashPlan is considerable: the initial upload of my full backup set (> 1 TB) took months and I hate to lose this investment. I’ve simply had too many problems with the service. 1 Now that the time has come for renewal, I have evaluated my experience with CrashPlan and decided to cancel my subscription. I signed up for CrashPlan, the online backup service, almost a year ago, in November 2012.