![]() The software broke after anything changed e.g.) system upgrades, Java updates & CrashPlan version updates – then having to spend hours trying to sort it out.Updates often caused the software to stop working.The software used excessive amounts of resources primarily RAM.Limited support for various backup scenarios.Lack of support for the product, e.g.) Windows Servers.What’s interesting about this scenario (believe it or not) is that many backup service providers and MSPs actually used CrashPlan Home in favor of CrashPlan Pro or Enterprise. or 60 days while you transition elsewhere.They offer 3 options for what your next steps might be. ![]() Screen capture from Code42 / CrashPlan announcing the discontinuation of CrashPlan Home
0 Comments
Leave a Reply. |