Sunday, May 29, 2016

CrashPlan Adoption

I've been using CrashPlan for more than 2 years and it's doing great. When I migrated to "The Trump" I planned to discontinue using Tivoli CDP.  Although I had been successfully using it for 10 years I knew I would have to upgrade it for Windows 10.

But when I moved my data to "The Trump" I used the Windows 10 directory names for Documents and Pictures which are different than the corresponding Windows 7 directory names.

With CrashPlan you define the backup sets using directory names so I was worried that CrashPlan would think that those were different files and back them up all over again.

I shouldn't have worried.

CrashPlan has an excellent guide on changing computers. Basically you keep the directory names and paths the same between the computers if you can but if you can't don't worry about it.

As I'd observed before CrashPlan dedups backups resulting is a much smaller bandwidth usage than you'd expect. Similarly CrashPlan scans a new computer's backup set matching the files with the files it has previously backed up regardless of location.

When I started CrashPlan on "The Trump" the estimate to complete the backup was in DAYS. I almost panicked. Then the estimate started to drop precipitously as it determined that it already had backups of those files. It finished the 300+ GB backup in a couple of hours.


No comments: