CrashPlan, why we live and die by our backups
June 03, 2016

CrashPlan, why we live and die by our backups

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with CrashPlan

Crash Plan is used across the whole institution for client backups and it addresses the need for user disaster recovery and migration assistance for users moving to new equipment.
  • Works on any network connection type and location, we found the product works whether they are at home, at a local coffee shop provided wireless or working from inside our outside of our corporate network
  • Provides and easy to recover process for clients that have to use a temporary computer because of technical service being provided to the primary computer, we can provide them with a loaner and do not need to migrate their data all to the temporary computer, they can just get the files they need
  • Computer migration is much easier on the IT department as all we need to provide is the base setup for the user, make sure the new Crash Plan client is installed and linked to their previous computers backup and then the user can install all or just a subset of what they want on the new computer without worrying about data loss.
  • increase the speed that files can be recovered, often the bottleneck is the server providing the data stream and not our ability to receive the data, we have a very large network pipe and can handle data transfers greater than most.
  • AD Integration, currently we have run into issues if we have to move a user from AD to non-LDAP because of a password issue, we can not move the user back to LDAP (AD).
  • Ability to force individual users to upgrade their client and not all or none
  • Since we moved to Crash Plan, our faith in believing that our backups are available and recoverable has been proved time and time again. Previous products we had we often lead us to believe our backups were available but when we would try to access them we would find that they did not truly exist or were corrupt
  • We started with hosting the backup environment ourselves and slowly moved to a mixed model with having multiple destinations thereby increasing our data protection and reducing our storage costs by limiting how much we keep internal versus external
  • Having a way to track clients machines from within the console has helped us track down those stray computers we find are missing but are still communicating back to our backup system, thereby assisting us with recovery
Speed, accuracy of data collection and ease of use, Crashplan has met or exceeded all of our previous backup systems to date
This product is well suited for protecting end users data and not as a full disaster recovery system for a bare metal restore. We have found that bare metal recover is best suited for getting the OS done first and then restore the user data other than doing it all as one process. In the process we understand that we are not catching the users modification to their system but often that was the source of the original problem so we only want to restore their data and not their problems also