Skip to main content
Code42 Support

Beyond The Code: Unsupported CrashPlan Configurations

Applies to:
  • CrashPlan PRO
  • CrashPlan PROe

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 some of the more common uses that go beyond the configurations and systems supported by Code42, and provides additional considerations and resources for running CrashPlan in these unsupported scenarios.

Considerations

These configurations may require a working understanding of the following:

  • Networking, TCP/IP
  • Command line or Terminal
  • SSH
  • Hard and soft links

Unsupported configurations

Unsupported process
Our Customer Champions can't 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.

Run CrashPlan on 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 completely uninstalling and reinstalling the CrashPlan app may allow the application to function on these systems.

Run CrashPlan 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 CrashPlan, but the configuration is unsupported. Your results may vary.

Run CrashPlan on network-attached storage

Network-attached storage (NAS) is an appliance that acts as a file server on a network. These devices often have minimal system resources and run a limited version of Linux without a graphical environment. The instructions for installing a headless computer may allow you to remotely back up files on a NAS. There are specific instructions for installing on a Synology DiskStation available on the Synology Forums.

Real-time backup for network-attached storage (nas)

CrashPlan can only back up files stored on a NAS when the file verification scan runs. CrashPlan doesn't support real-time backup on network-attached drives. If you have issues monitoring files on these devices, we offer some suggestions that may help you troubleshoot your NAS configuration.

Reassign cache location

Your computer's CrashPlan 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 CrashPlan run efficiently. Depending on the size of your backup selection, these cache files can quickly grow in size.

To free up space on your system drive, you can use this unsupported process to move the cache to a drive with more storage.

Back up a Windows network drive

CrashPlan doesn't support backing up mapped drives on Windows, including network drives that are mounted by a user. This is due to a restrictions built into Windows at the operating system level. However, you may find that our unofficial method for backing up a Windows mapped drive works for you. Note that the solution requires advanced Windows knowledge.

Back up encrypted data

(CrashPlan version 4.2 and earlier)

Running CrashPlan on systems with user-level disk encryption or encrypted container files is unsupported. On those systems, CrashPlan may not be able to back up files, especially if the user credentials are not available to CrashPlan.

There are specific instructions available to back up encrypted virtual disks such as TrueCrypt volumes or Windows EFS user accounts, but these configurations are not supported.