You can use the Cloud Backup platform or the Offsite Server Backup platform. Offering a simple month-to-month licensing model. … luckily you can read this thread where one person was able to get some clarification directly from a CrashPlan rep.ģ3 Reasons why WholesaleBackup is a perfect alternative to CrashPlan for your cloud and server backup solutions
So that they can narrow in on small business backup serviceswhich consist primarily of workstations, laptops, and probably a server or two. Additionally, they are ending consumer-grade backups which were focused on personal computers. While at the same time they are killing support for Servers at the Enterprise level because the solution is not secure enough. The motive behind the CrashPlan changes is to it shift its focus primarily on Business and Commercial grade backup services. Because customers utilizing an Enterprise-grade backup solution should expect secure data backups at a minimum whether it’s on a workstation, laptop, or server. This statement and reasoning were slightly contradicting and bewildering when taking a step back and looking at the big picture… Running the Code42 app on unsupported operating systems may produce undesirable results. Thus Code42 is ending support for Code42 apps on Windows operating systems that are intended to run on servers. They are not intended to back up or secure data on servers. Here’s the quote from the official support page:Ĭode42 applications are designed to back up and secure end-user devices, such as laptops and desktops. Ĭode42 support document explaining the end of life for CrashPlan Enterprise on Windows Servers The other huge issue that has many users and manage service providers scrambling to find a new server backup solution is the Windows Server end of life support for the CrashPlan Enterprise app on Windows Servers. The inability to backup from a mapped driveĬrashplan ending support for Windows Servers from r/sysadminĢ.) CrashPlan ending support of all Windows Servers (including Enterprise). 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