Item: CrashPlan
Rating: 10
Author: Cedric BARNET

Overall Satisfaction with CrashPlan

Use Cases and Deployment Scope

We use CrashPlan for all our managed customers (Mac shops). We use it back up hundreds of users/devices including server or client workstation data, depending on our client needs and budget.

Pros and Cons

Pros

Continuous incremental backup
Reduplication and compression that really limits the storage needs
File level restore

Cons

Dashboard reliability
Client interface
Easier upgrade process

Return on Investment

Great return on investment
Good image impact when we can perform a disaster recovery
Scalable to keep growing revenue and customer base

Alternatives Considered

Carbonite Server Backup and Acronis Backup & Recovery

I like Crashplan's centralized nature and flexibility with support for all platforms. Their support has been the best of all other competitors' solutions.

I recommend CrashPlan to my friends, colleagues, customers and pretty much everybody that has data to back up on a computer or server. Their different plans (including free for local backups) are appealing for any scenario.

CrashPlan Support

Support Rating

Their support is how any customer support should be: friendly, knowledgeable, responsive and efficient. They make it happen like no one else. Every time I called, the first person I talked to in minutes eventually solved the problem.

CrashPlan Customer Support Pros and Cons

Pros	Cons
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response	None

Exceptional Examples of CrashPlan Support

We experienced an issue with a secondary node server. We looked for one hour for the cause with no results. We picked up the phone and the technician was able to isolate the issue very quickly after listening to what steps we had already looked into. He trusted us and was able to check logs, understand them and find a fix using terminal command in minutes. Impressive.

Comments

Please log in to join the conversation

Go champions!