Crashplan is a great backup solution: inexpensive, fast, easy to set up. I have it running under a multi-computer plan for a small home office which uses a NAS as a file server. It runs on each computer fine, but I wanted to also back up all the shared files on the NAS.
Additionally, we recently had a Buffalo TeraStation PRO failure, so I wanted our system to rely less on any one piece of hardware.
Enter the WD MyCloud. Cheap, fast, small, quiet. 4TB for $199 in Dec 2013. VERY easy to set up. Just plug it in. Seriously - if you don't need a lot of customization - this is how computer equipment should work.
Now to set it up took several hours and a lot of debugging. If you follow the instructions below though it should be quick. You can do this. You'll have a NAS accessable across your network which automatically backs itself up to Crashplan without any user intervention.
The instructions below cover ALL of the steps and hopefully don't require knowledge of Unix or Linux commands so feel free to skip if you know what you're doing. The indented items and blue links go into more detail. I used a PC, but instructions should be the same on a Mac though the tools used may be different.
Shoutouts to all who are linked, thank you for the help.
- Plug the device in to power and your network
- Optional: Change the Device Name
- Load your device dashboard
- Click Settings and change Device Name and Device Description. Make sure to click Save.
- Enable SSH on your device & note the username and password given
- Log in to the MyCloud device using SSH (I like PuTTY, it is lightweight, free and has been around for 15 years). IMPORTANT: This voids your warranty. Proceed at your own risk.
- Download putty.exe from this site or wherever you can find it
- Run putty.exe from wherever you downloaded it and click "Session" in the "Category" browser on the left.
- Use your device IP address as the "Host Name (or IP address)" and click "Open" at the bottom
- If a Security Alert pops up, you can click yes to allow connection. This is YOUR server after all.
- Log-in by typing the username and password given on step 3 (Default is "root" and "welc0me" - yes, that's a zero)
- Your PuTTY screen should look like this:
- You may notice that at the end of the 3rd line, we are dealing with an armv71 processor, not an Intel. When we install crashplan in the next step we will have to modify a file to make it able to communicate with the ARM processor.
- IMPORTANT Install Java first (trust me - see this)
- First we need to update apt-get: sudo apt-get update
- Install JRE headless: sudo apt-get install openjdk-6-jre-headless
- The following may be optional, I have not tested without them:
- Get the java version for our OS: sudo apt-get install libjna-java
- Install the Java Runtime Environment (JRE) sudo apt-get install default-jre
- Install Crashplan using these instructions.
- Using my windows machine, I downloaded the installer and then copied to a new folder called "tmp" I created in the Public folder on the MyCloud device
- Then in the PuTTY session from step 4 use the following commands to unzip and run the installer:
- cd /shares/Public/tmp
- tar zxvf CrashPlan_3.5.3_Linux.tgz
- This line may be slightly different depending on the filename of the Crashplan download, just change the part after "tar zxvf" to the filename you downloaded
- cd CrashPlan-install
- sudo ./install.sh
- Follow all the prompts for the Crashplan install. Accept the defaults. If you don't, you probably know what you're doing - just change the below instructions to point to the locations you installed the files. If it asked to install java, cancel and go back to step 7.
- The installer ends by saying the service is started, but if you check the status, after a few seconds it will not be running. We need to fix one file to work with the ARM processor.
- To check the status, run: /etc/init.d/crashplan status
- First, let's increase the number of files the Crashplan client will watch (while you remember how to log in to the MyCloud!). Follow these directions (section 3.2) - copied below.
- To see # of watches: cat /proc/sys/fs/inotify/max_user_watches
- To change the # of watches, run the following:
- sudo echo 1048576 > /proc/sys/fs/inotify/max_user_watches
- sudo nano /etc/sysctl.conf
- Then once the editor opens, add this to the end of the file:
- # Set up inotify kernel module to keep watch on up to 1M files
- Then we need to patch the crashplan files as in step 2 of this tutorial, with some minor changes.
- Modify the crashplan launcher script to point to the new java version
- nano /usr/local/crashplan/bin/CrashPlanEngine
- Change the line starting with FULL_CP to:
- Now we need to change the libjtux.so file to a version that will work with the ARM processor. We will need to download it, fix it and build and compile it. This is the hard part.
- Rename original libjtux.so file to get it out of the way
- mv /usr/local/crashplan/libjtux.so /usr/local/crashplan/libjtux.so.intel
- You can skip all of the following by downloading the file from here and replacing the original one.
- cd /shares/Public/tmp/
- wget https://dl.dropboxusercontent.com/u/21924000/libjtux.so
- cp /shares/Public/tmp/libjtux.so /usr/local/crashplan/libjtux.so
- If you'd rather compile from scratch (maybe the above doesn't work), then follow these directions:
- Download the jtux package to your tmp directory on the share and unzip it:
- cd /shares/Public/tmp
- wget http://www.basepath.com/aup/jtux/jtux.tar.gz
- if you can't find it there, just do a google search for jtux and paste the link after wget
- tar -zxvf jtux.tar.gz
- sudo apt-get install build-essentials, using any packages from here if they don't match the version that is needed. I had to use version 2.17-6. Install them using dpkg -i <package-name>
- To install, download to your drive and then unzip as you did with previous files. Then use dpkg -i on the .deb file that you get after unzipping. I'll go into more detail if there are a lot of questions on this.
- Follow the patch instructions here (don't forget the #include line!)
- Once you have the right version of libjtux.so in place, start the CrashPlanEngine
- /usr/local/crashplan/bin/CrashPlanEngine start
- Check to make sure it is running
- /etc/init.d/crashplan status
- Now follow these Directions for Configuring a Headless Client
- You should be good to go!! Hopefully you have a fast internet connection for the first upload. Good luck!