If you'd like to use different accounts, so that each computer (user) is the sole owner of his backed up files, this is also possible. Trying to restore such files from another computer (this is called a guest restore in CrashPlan) will require the user to enter the owner's password.
==How Configure CrashPlan (Fedora 19)==On your HDA, [[Open_Terminal_as_root|open a terminal window as root]] and edit the following XML configuration file in your favorite text editor. nano -w /usr/local/crashplan/conf/my.service.xmlSearch for the “serviceHost” parameter and change it from: <serviceHost>127.0.0.1</serviceHost>to configure this instead: <serviceHost>0.0.0.0</serviceHost>Save the file and then restart the CrashPlan daemon: /etc/init.d/crashplan restart This example will show how to reconfigure the CrashPlan Desktop installation on a Windows PC to talk to the CrashPlan Engine instance running on your HDA. * Open the folder where you installed CrashPlan on your Windows PC. By default, this is in C:\Program Files\CrashPlan. Inside, you’ll find a folder called “conf” and inside there, a file called “ui.properties”. Open this file using a decent text editor like Notepad++ and look for the following line: #serviceHost=127.0.0.1 * Change the line to remove the comment character ‘#’ and include the IP address of your CrashPlan server. For example: serviceHost=192.168.1.100 You now should be able to administer CrashPlan using your HDA as the local storage location. ==Configure CrashPlan (Ubuntu)==
<p style="color:red">'''NOTE''' The CrashPlan UI sometimes has issues registering button clicks. If you click a button and it seems to do nothing, hit the ENTER key. That seems to help in such cases.</p>