LOGO

Control CrashPlan Backup Remotely - How To Guide

September 29, 2016
Control CrashPlan Backup Remotely - How To Guide

Controlling CrashPlan Remotely: A Detailed Guide

The CrashPlan backup application is remarkably straightforward to set up and manage directly on the machine where it’s installed. However, managing it across a network requires accessing some less obvious configurations.

A Reader's Challenge

A reader contacted us with a plan to reduce costs by purchasing a single-user CrashPlan account instead of a family plan. Their intention was to install CrashPlan on an older desktop computer and use it as a central backup repository for all other computers on the network.

The core issue was the inability to remotely control the CrashPlan client on the dedicated backup server. Despite installing CrashPlan on a home office computer, only the local instance was manageable. The question was: is there a method to control the CrashPlan engine running on the older, repurposed desktop?

Acknowledging the Strategy

This approach to backup streamlining is one we’ve explored ourselves. However, it’s important to note a potential limitation before proceeding.

CrashPlan’s software will operate on a home server, but it won’t back up CrashPlan archives created on other machines. This is a built-in safeguard within the client, designed to prevent redundant data uploads. For instance, running clients on both a desktop PC and a server, then backing up the desktop to the server, would result in the same data being uploaded twice – an inefficient use of bandwidth for both the user and CrashPlan.

If centralizing backups remains the goal, utilizing a different application to create backups on the central server is advisable.

Hidden Configuration Options

As discovered, the CrashPlan client lacks any readily visible settings for connecting to a remote backup engine. These settings do exist, but they are concealed within configuration files and are not accessible through the standard user interface.

This isn't necessarily a criticism of CrashPlan, as the proposed setup – running the client on a headless and/or remote machine – represents a specialized use case that most users won't encounter.

Modifying the ui.properties File

To redirect the CrashPlan client to a new backup engine, you must locate and edit the ui.properties file. On Windows systems, this file is typically found in C:\Program Files\CrashPlan\conf\.

On other operating systems, search for a similarly structured \CrashPlan\conf folder to find the file.

Open the file using a text editor. All lines will initially be commented out, indicated by a hashtag (#) symbol. Locate the line #serviceHost. Remove the hashtag to uncomment the line, and then enter the IP address of your remote backup machine after the equals (=) sign.

ask-htg-how-can-i-control-crashplans-backup-app-from-another-computer-1.jpg

Save the modified file and restart the CrashPlan client on your computer. It will now connect to the backup engine on the remote machine (as specified by the IP address) instead of the local engine.

To revert to controlling the backup engine on your local computer, simply re-add the hashtag at the beginning of the edited line in the properties file.

Security Considerations

If you plan to connect to and control the remote backup engine from outside your home network, we strongly recommend configuring SSH and changing the service port in the ui.properties file to enhance security. Detailed instructions on how to do this can be found in this CrashPlan support article.

Do you have a challenging tech question? Send us an email at ask@howtogeek.com, and we’ll do our best to provide a solution.

#CrashPlan#remote control#backup#data protection#remote access#manage backups