The CrashPlan app is certified for use only on the specific systems that meet our system requirements.
This article lists some common unsupported configurations. Where possible, we offer troubleshooting resources or recommendations for using the CrashPlan app in a supported manner.
Our technical support team can't assist you with unsupported processes, so you assume all risk of unintended behavior.
Install the CrashPlan app to a non-default location
Run the CrashPlan app on pre-release operating systems
The CrashPlan app is not certified for use on pre-release operating system versions. CrashPlan can't guarantee that the CrashPlan app will work, or troubleshoot any problems, on alpha, beta, or other pre-release operating systems. Many users have found that completely uninstalling and reinstalling the CrashPlan app may allow the application to function on these systems.
Run the CrashPlan app on an ARM processor
ARM devices do not meet the CrashPlan app's processor requirements. Raspberry Pi, Pogoplug, and other systems using ARM architecture may be able to run the CrashPlan app, but the configuration is unsupported. Your results may vary.
Real-time backup for network-attached storage (NAS)
The CrashPlan app can only back up files stored on a NAS when the file verification scan runs. The CrashPlan app doesn't support real-time backup on network-attached drives.
Reassign cache location
Your computer's CrashPlan app cache files contain temporary information about your destinations, the data you have on your computer, details about changes to files, and a number of settings that help the CrashPlan app run efficiently. Depending on the size of your backup selection, these cache files can quickly grow in size.
If you want to free up space on your system drive, moving the cache to a drive with more storage is an unsupported process. Instead, clear your cache to free up space.
Back up a Windows network drive
The CrashPlan app doesn't support backing up mapped drives on Windows, including network drives that are mounted by a user. This is due to a restriction built-in to Windows at the operating system level.