Watchman Monitoring alerts you to backup problems on all versions of Code42/Crashplan. Code42 for Enterprise, Crashplan Small Business, and Crashplan Pro are monitored on macOS, Linux, and Windows.
The Monitoring Client sends alerts and warnings if a client has not completed a backup in 7 days (by default), if a PROe server is not responding, or a PROe server is not creating its regularly scheduled backups.
ERROR: "Could not find /Library/Caches/CrashPlan"
This error usually occurs because Java VM/engine is not installed. New Macs do not have Java installed. The CrashPlan client does not work without Java. Launching CrashPlan.app from the applications folder triggers the installation of Java.
Crashplan has posted several articles related to getting Java reinstalled.
Here are some worth noting:
Crashplan reported an "Out of Memory error occurred"
The Monitoring Client will look for, and report on, situations where the Crashplan Client software runs out of memory during its scan.
Code42's article on adjusting app settings for memory usage with large backups explains the issue and offers suggestions.
Searching Code42's support site for "Out of Memory" may also lead to solutions, including increasing the memory allotment.
Crashplan is unable to backup X file(s)
This is a common error where the CrashPlan client application decides that some files cannot be backed up, but does not report this to the GUI.
In almost every case, the files are not important and can be removed with no consequence.
When this error is reported, the best course of action is to review the files listed in
Excess warnings when rotating Crashplan's backup media
CrashPlan does not recommend a workflow that rotates external drives. However, some users will rotate drives used as destinations. In this case, the default settings on the Monitoring Client need to be adjusted to prevent false positives.
In the Settings tab of the PreferencePane, change the days allowed between backup completion to the number of days of the rotation cycle being used plus a few days for the drive to back up.
Reporting after removal of Crashplan
The Monitoring Client may continue to report on Crashplan after the Client has been uninstalled. Code42/Crashplan's uninstall script may leave behind portions of the Client on macOS or Linux.
Running the following commands will stop the client service and prevent it from running in the future.
sudo systemctl stop Code42Service sudo systemctl disable Code42Service
The Crashplan plugin will stop reporting and eventually reporting will go stale.
Linux may require a reboot after stopping and disabling the Code42 Service.
How can this article be improved?
Please sign in to leave a comment.