Start the Shell service by entering the following command Press Escape, then return, select ‘a) save changes’ and press return again to exit.Navigate to Jails, highlight the Crashplan jail and click on the Command prompt icon.Įnter the following command to edit the systems configuration information We’ll do most of the upgrade to version 4.6.0 through the shell and to make things easier we will enable the ability to log in with our preferred SSH client. Navigate to Plugins > Installed and enable the Crashplan service by toggling the service status switch. Once we have accepted the EULA, we can start the Crashplan engine. You can close this, we will configure this later on. You should see the EULA displayed, read through it and if you are satisfied with the conditions, proceed to click on ‘Yes, I accept’ at the bottom of the page.Ĭlose the popup that redirects you to a link informing you how to connect to a headless crashplan desktop. Navigate to Plugins (this time in the left hand column) > Crashplan. Highlight Crashplan and click Install at the bottom of the page Accept Crashplan EULAīefore you can start the Crashplan plugin, you need to accept the EULA. Log in to FreeNAS control panel and navigate to Plugins in the top menu bar. Alternative methods such as installing from the ports tree or enabling Linux compatability and downloading the Linux verison direct from Code42 proved to be more convoluted.Īt the end of this guide you will have configured a up to date Crashplan plug in, have enabled encryption and backed up a folder to Crashplans cloud storage space. Updating the earlier v3.6.0 plugin provides the quickest, easiest and least troublesome method I’ve found of installing a reliable Crashplan into FreeNAS. IntroductionĮven though this guide installs the latest 4.6.0 version of Crashplan, we are going to build upon the foundations provided by the older existing FreeNAS Crashplan 3.6.3_1 plugin. Some folks have recommended increasing the number of inotify watches with the commands below this is another thing that I didn’t do, and it seems to be running okay on my RPi 3.FreeNAS Crashplan installation Last revised: 9 April 2016. NB: This script does not cover mounting an external hard drive or configuring it as your CrashPlan backup destination. I was able to connect to the UI via SSH as described in the official CrashPlan Docs I’ve briefly re-tested the script on a blank Raspbian Jessie Lite installation and it seems to work well. I find the systemd scripts much easier to understand and maintain, and I’ve included what I use below (as well as a prompt in the script to download mine if desired). However, it also assumes that you’re using a systemd service file to start CrashPlan (instead of the sysvinit style scripts it ships with). This script assumes you’re choosing the default answers to all the prompts in the CrashPlan installer. You can check out the revision history to see the much simpler version it started with. EDIT: I’ve expanded the script a fair bit to make it a little more user friendly and complete. I never recommend just copying and pasting someone else’s script, especially when it’s this short and basic, so take a look and try to understand what each command is doing. Additionally, all of the setups I found included replacing libjtux.so and libmd5.so with some ARM compiled versions downloaded from somebody’s website without any kind of hash to verify the download integrity - this made me a little nervous, being that this software will likely “see” nearly all of my sensitive documents and materials.Ī few months ago I went ahead and condensed my setup into a GitHub Gist, and with the 4.7.0 update (which again broke my CrashPlan on the Pi installation this month), I thought I’d go ahead and share. However, I find that I don’t need to take all the steps listed there, and much of the helpful material is in a long comment thread. Every time, I end up Googling around and referencing this thread and a few others. Recently, CrashPlan has started automatically upgrading itself every few weeks to months, which breaks my install. I’ve been using a Raspberry Pi as a local backup destination for CrashPlan for a few years now. Bottom Line: My strategy for getting CrashPlan working on the Raspberry Pi (currently on Raspbian Jessie).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |