- CrashPlan for Home
The CrashPlan app is certified for use only on the specific systems that meet our system requirements. However, technology enthusiasts have found uses for CrashPlan outside our supported systems and configurations.
This article lists information and external links about several configurations that are not supported by Code42.
The information presented here is intended to offer information to advanced users. However, Code42 does not design or test products for the use described here. This information is presented because of user requests.
Our Customer Champions cannot assist you with unsupported processes, so you assume all risk of unintended behavior. You may want to search our support forum for information from other users.
Pre-release operating systems
CrashPlan is not certified for use on pre-release operating system versions. Code42 can't guarantee that CrashPlan will work, or troubleshoot any problems, on alpha, beta, or other pre-release operating systems. Many users have found that the CrashPlan app runs on these operating systems after completely uninstalling and reinstalling the CrashPlan app, but these operating systems are unsupported.
Even though some versions of the CrashPlan app have been able to run on ARM devices, these devices do not meet the CrashPlan app's processor requirements and are unsupported. Common ARM devices include:
- Raspberry Pi
- Some NAS devices
Network-attached storage (NAS) devices are appliances that act as file servers on networks. These devices often have minimal system resources and run a limited version of Linux without a graphical environment. You might attempt to install a headless computer to remotely back up files on NAS, but using the CrashPlan app on a NAS device is unsupported.
Install the CrashPlan app to a non-default location
Linux distributions that do not support SysVinit
The CrashPlan app for Linux requires SysVinit. The CrashPlan app is not supported for use on an operating system that does not support SysVinit.
Some Linux distributions, such as Arch Linux, do not support SysVinit as an init system. While some users have created third-party packages or scripts that work around the requirement for SysVinit, those configurations are not supported. Our Customer Champions cannot assist you in troubleshooting any issues related to running the CrashPlan app without SysVinit.