CrashPlan, revisited

I reported a while ago on a brief test of CrashPlan. I went back and did another test.

I downloaded and installed the app, then set up a 6 TB+ backup.

The speed looked encouraging. I want ahead and signed up for a year’s subscription.

I went to the web to see if any of the files were really there:

Oops. Can’t connect. I decided to wait a while. It sorted itself out. After a day or so, the speed started to drop way down:

After a week or so, it was about the same speed.

 

Every so often, I’d get this:

And then this:

When I went looking for the service, I couldn’t find it:

A reinstallation fixed things. When it was running again, I compared it to an S3 backup that was taking place simultaneously:

The S3 backup is the light brown part, and the Crashplan backup is the dark blue.

Over the next couple of months, it got slower and slower:

Finally, it stopped reporting on speed:

When I looked at the history, I saw that it hadn’t been backing up for a few days:

I upgraded to Release 4.7, and things got worse.

 

This time, no amount of fiddling would get it started again.

I waited for a few days. Now it says it’s working:

But, when I look at the firewall, there’s no traffic from Crashplan:

And no estimate from the progress indicator:

I guess it’s time for tech support.

I went to the CrashPlan web site and filled out a trouble ticket. On 5/19, I received an acknowledgement with some inappropriate generic suggestions. Today is 5/24. I have heard nothing further. I went back to the email. Near the bottom, it says:

If this email does not address your question, we’re sorry for the extra hurdle. Just email us back and we’ll get back to you as soon as we can, according to urgency and order received.

I get I need to email them back to tell them that I really do want to open a trouble ticket.

I did that on 5/24.