NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Crashplan for Dummies, aka Step by Step :)
I have just went through this and have seen several folks post that they wish there was an all inclusive guide, I just bought a Pro 2 and so far I am pleased with what I see under the hood (looks like debian to me, kernel 2.6.37) I'm a *nix guy so I thought I would try to make an all inclusive step-by-step to help anyone that might want to try and install crashplan. So here goes, the normal warning goes here - There are no warranties implied or otherwise, DO THIS AT YOUR OWN RISK! If you find any thing that needs to be updated or doesn't make sense please post and let me know...
I am not the only one to post how to do this see here - http://www.readynas.com/forum/viewtopic.php?f=61&t=18139&start=15#p297737
and here http://support.crashplan.com/doku.php/how_to/configure_a_headless_client
Steps for x86 ReadyNas Only:
Old way,still works but uses java 6, which is out of date:
Updated JAVA install, credit goes to InterClaw :)
The full instructions can be found here - http://minimserver.com/ejre-installer.html I will try to list just the steps for x86 ReadyNas:
1. Go to Oracle and down load the latest embeeded java version l@@k for this version - x86 Linux Small Footprint – Headless - http://www.oracle.com/technetwork/java/embedded/downloads/javase/index.html
*Note you will have to accept Oracles Terms and Conditions and create an account to download the file
2. Download file and copy the java file to /c/backup/ on your ReadyNas
3. Download the EJRE Readynas Addon see the link above for the full instructions, the addon can be found here - http://minimserver.com/downloads/EJREInstaller-0.10-readynas-x86.bin
4. Install EJRE Addon and this will install the java version that you placed in /c/backup/
5. Verify that java is working, time to jump to the command line to finish the installation. Install the Enable Root SSH addon - http://www.readynas.com/download/addons/x86/4.2/EnableRootSSH_1.0-x86.bin Complete installation by rebooting your readynas.
6. You will need to get a ssh client for your desktop/laptop, here is one for winblows (putty) - http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe, nothing to install, just download and place on your desktop or somewhere you can find it.
7. Open putty and SSH into your readynas, enter the IP address and when it prompts for username enter "root" and then your normal raidar/frontpage "password". Once logged in verify java operation by entering the following :
8. Now we can install Crashplan.
- Download the latest linux crashplan version
enter "wget the latest version that is listed on crashplan for linux, see below"
Here is the main download page, just make sure you get the latest version -
http://www.crashplan.com/consumer/download.html?os=Linux, this will download andplace this in your
root directory.
9. Once the diownload has completed lets extract the files which are tarred and zipped.
enter "tar -xvf CrashPlan_3.0.3_Linux.tgz" or whichever version you downloaded, this will extract all of the files
and place them in a folder called "CrashPlan-install".
enter "cd "CrashPlan-install" and then run the installer, enter "./install.sh", this will start the installer
ask for you to accept the terms and conditions and ask questions where to install etc..You can accept the defaults
for most, however when it prompts you for the default crashplan backup directory, you can go with the default or
provide a directory that you have already established for that purpose, e.g., "/crash-backup" whatever your share
that you created without any slashes, this actual is a pointer to "crash-backup -> /c/crashplan-backup"
Here are the questions, most you accept the defaults, in this case I chose to specify a different Directory -
Do you accept and agree to be bound by the EULA? (yes/no) yes
What directory do you wish to install CrashPlan to? [/usr/local/crashplan]
What directory do you wish to link the CrashPlan executable to? [/usr/local/bin]
What directory do you wish to store backups in? [/usr/local/var/crashplan] /crash-backup
What directory contains your SYSV init scripts? [/etc/init.d]
What directory contains your runlevel init links? [/etc/rc2.d]
Your selections:
CrashPlan will install to: /usr/local/crashplan
And put links to binaries in: /usr/local/bin
And store datas in: /crash-backup
Your init.d dir is: /etc/init.d
Your current runlevel directory is: /etc/rc2.d
Is this correct? (y/n) [y] y
10. Configure crashplan on the readynas, in order to do this you need to download and install crashplan on a local PC,
using linux, winblows or Mac - http://www.crashplan.com/consumer/download.html once that has been
done we need to tunnel from the PC to the readynas, the already have this detailed on the crashplan site
called a headless install - http://support.crashplan.com/doku.php/how_to/configure_a_headless_client
*Note while configuring the Crashplan client -the client will show your shares twice - as links (with an arrow as part of the icon)
and under the "C" folder. It won't back up the links, you need to select the folders under the "C" folder. If you try the other way, the
backup "succeeds", but doesn't back anything up. Thanks to StephenB for this update!
Once the configuration is complete you should be good to go.. :)
I'm sure I have left something out or not fully explained something, if so let me knoiw and I will update the posting..
Good Luck :)
I am not the only one to post how to do this see here - http://www.readynas.com/forum/viewtopic.php?f=61&t=18139&start=15#p297737
and here http://support.crashplan.com/doku.php/how_to/configure_a_headless_client
Steps for x86 ReadyNas Only:
Old way,still works but uses java 6, which is out of date:
1. See Step one below
2. See Step two below
3. See Step three below
4. Once logged onto your readynas as "root" your ready to get the the software setup. Keep in mind that when you are running as root, you have elevated priviliges and you can do anything you want, including messing things up, so go slow and take your time :)
- First thing we need to do is edit the sources.list, we are going to use vi which is not a friendly editor
but is installed on any base *nix system and in this case will get the job done. Lets edit the file, at
the prompt - vi /etc/apt/sources.list, arrow down to the last line and then arrow over to the
last letter and hit the "a" button for append and then hit "enter" to get a new line and then paste
"deb http://archive.debian.org/debian-backports etch-backports main non-free" .
- To get out of vi and save the file "shift:" will get you the colon prompt at the bottom, then to save
and exit enter "x", if you made a mistake and you do not want to save your work at the colon enter "q!"
and that will quit without saving any changes. Once you exit and save your sources list should look
like this, "more /etc/apt/sources.list" -
deb http://www.readynas.com/packages 4.2.19/
deb http://archive.debian.org/debian etch main
deb http://archive.debian.org/debian-backports etch-backports main non-free
5. Now we need to update our package list and install Java.
- enter "apt-get update"
- Now we need to modify configuration dialog selection so we can accept the java Terms and conditions.
- enter "dpkg-reconfigure debconf"
This will ask you to select a dialong frontend, select option 1 - Dialog, then it will ask you for
the level, select option 3 - Medium.
- Now lets install java, enter "apt-get install sun-java6-jre", it will download the package and start to
install it where it will ask for you to accept the terms and conditions, select yes and complete the
installation.
- Modify the deb configuration and change it back, enter "dpkg-reconfigure debconf"
This will ask you to select a dialong frontend, select option 6 - Noninteractive, then it will
ask you for the level, select option 3 - Medium (not sure if this was the default).
Updated JAVA install, credit goes to InterClaw :)
The full instructions can be found here - http://minimserver.com/ejre-installer.html I will try to list just the steps for x86 ReadyNas:
1. Go to Oracle and down load the latest embeeded java version l@@k for this version - x86 Linux Small Footprint – Headless - http://www.oracle.com/technetwork/java/embedded/downloads/javase/index.html
*Note you will have to accept Oracles Terms and Conditions and create an account to download the file
2. Download file and copy the java file to /c/backup/ on your ReadyNas
3. Download the EJRE Readynas Addon see the link above for the full instructions, the addon can be found here - http://minimserver.com/downloads/EJREInstaller-0.10-readynas-x86.bin
4. Install EJRE Addon and this will install the java version that you placed in /c/backup/
5. Verify that java is working, time to jump to the command line to finish the installation. Install the Enable Root SSH addon - http://www.readynas.com/download/addons/x86/4.2/EnableRootSSH_1.0-x86.bin Complete installation by rebooting your readynas.
6. You will need to get a ssh client for your desktop/laptop, here is one for winblows (putty) - http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe, nothing to install, just download and place on your desktop or somewhere you can find it.
7. Open putty and SSH into your readynas, enter the IP address and when it prompts for username enter "root" and then your normal raidar/frontpage "password". Once logged in verify java operation by entering the following :
java -version
8. Now we can install Crashplan.
- Download the latest linux crashplan version
enter "wget the latest version that is listed on crashplan for linux, see below"
Here is the main download page, just make sure you get the latest version -
http://www.crashplan.com/consumer/download.html?os=Linux, this will download andplace this in your
root directory.
9. Once the diownload has completed lets extract the files which are tarred and zipped.
enter "tar -xvf CrashPlan_3.0.3_Linux.tgz" or whichever version you downloaded, this will extract all of the files
and place them in a folder called "CrashPlan-install".
enter "cd "CrashPlan-install" and then run the installer, enter "./install.sh", this will start the installer
ask for you to accept the terms and conditions and ask questions where to install etc..You can accept the defaults
for most, however when it prompts you for the default crashplan backup directory, you can go with the default or
provide a directory that you have already established for that purpose, e.g., "/crash-backup" whatever your share
that you created without any slashes, this actual is a pointer to "crash-backup -> /c/crashplan-backup"
Here are the questions, most you accept the defaults, in this case I chose to specify a different Directory -
Do you accept and agree to be bound by the EULA? (yes/no) yes
What directory do you wish to install CrashPlan to? [/usr/local/crashplan]
What directory do you wish to link the CrashPlan executable to? [/usr/local/bin]
What directory do you wish to store backups in? [/usr/local/var/crashplan] /crash-backup
What directory contains your SYSV init scripts? [/etc/init.d]
What directory contains your runlevel init links? [/etc/rc2.d]
Your selections:
CrashPlan will install to: /usr/local/crashplan
And put links to binaries in: /usr/local/bin
And store datas in: /crash-backup
Your init.d dir is: /etc/init.d
Your current runlevel directory is: /etc/rc2.d
Is this correct? (y/n) [y] y
10. Configure crashplan on the readynas, in order to do this you need to download and install crashplan on a local PC,
using linux, winblows or Mac - http://www.crashplan.com/consumer/download.html once that has been
done we need to tunnel from the PC to the readynas, the already have this detailed on the crashplan site
called a headless install - http://support.crashplan.com/doku.php/how_to/configure_a_headless_client
*Note while configuring the Crashplan client -the client will show your shares twice - as links (with an arrow as part of the icon)
and under the "C" folder. It won't back up the links, you need to select the folders under the "C" folder. If you try the other way, the
backup "succeeds", but doesn't back anything up. Thanks to StephenB for this update!
Once the configuration is complete you should be good to go.. :)
I'm sure I have left something out or not fully explained something, if so let me knoiw and I will update the posting..
Good Luck :)
306 Replies
Replies have been turned off for this discussion
- Need some help. I have a ReadyNAS Ultra 4 Plus running the latest Radiator at 4.2.21. I followed the directions to a T except I am running CrashPlan 3.2.1 for linux on my ReadyNAS. The point where I am failing is that I am unable to telnet to localhost on port 4200 from the readynas. I have properly setup my ui.properties file with servicePort=4200. When I try to launch the Desktop Client I get the failure message and if I would like to try the backup. The only problem that I can tell is that when I run the netstat command on my Readynas, I don't see it trying to listen on 4242. It does however listen on 4343. I am on a windows box and made sure I have tunneling setup on my putty settings. I also rebooted both the desktop and readynas. But still it won't listen on 4242. I do however see that it listen on 4243.
*EDIT*
So it turns out that even though I get a connection refused when trying to telnet to localhost on port 4200, the Desktop Client works fine and I can see my Readynas. Has anyone seen this situation? Anyways, it appears to be working and I am going to attempt a backup and see if it works.
*Edit Again*
So it appears all is working well and fine even though the readynas is not listening on port 4242 and the telnet localhost 4200 fails to connect. My last problem seems to be using the desktop client without SSHing first. According to the dummy guide, it says I should be able to close everything out and change my ui.properties back to default and I should be able to use the desktop client without puttying first. while it does connect, it no longer sees my readynas, but now it sees my desktop. Any suggestions? I guess for now I can always just putty first. A little annoying but not a big deal.
I am also running 3.2.1 (both the PC and the ReadyNAS autoupdated when 3.2.1 was released). I am seeing the results in the guide:skim32 wrote: Need some help. I have a ReadyNAS Ultra 4 Plus running the latest Radiator at 4.2.21. I followed the directions to a T except I am running CrashPlan 3.2.1 for linux on my ReadyNAS... The only problem that I can tell is that when I run the netstat command on my Readynas, I don't see it trying to listen on 4242. It does however listen on 4343. I am on a windows box and made sure I have tunneling setup on my putty settings. I also rebooted both the desktop and readynas. But still it won't listen on 4242. I do however see that it listen on 4243.. tcp 0 0 *.4242 *.* LISTEN
tcp 0 0 127.0.0.1.4243 *.* LISTEN
Did you use the same command options that are in the guide? The -na is important.
Yes, this is normal. BTW, make sure you select the shares under the "C" volume for backup, the top level folders you will see are symbolic links (shortcuts) - if you pick them, crashplan will backup the shortcut file, but not the data.skim32 wrote: So it turns out that even though I get a connection refused when trying to telnet to localhost on port 4200, the Desktop Client works fine and I can see my Readynas. Has anyone seen this situation? Anyways, it appears to be working and I am going to attempt a backup and see if it works.
If you change ui.properties back, you can run the desktop client to manage the crashplan server that is locally installed on your PC. This would be important to people who have a multi-PC license. So this behavior is expected.skim32 wrote: According to the dummy guide, it says I should be able to close everything out and change my ui.properties back to default and I should be able to use the desktop client without puttying first. while it does connect, it no longer sees my readynas, but now it sees my desktop. StephenB wrote: Did you use the same command options that are in the guide? The -na is important.
I am now seeing my ReadyNAS listening on port 4242. I dunno why it wasn't before. I ran the same netstat command and only saw it listening on 4243. After I ran the Desktop Client for the first time, I think it started to listen on 4242. A little strange and unexpected but at least it's working.StephenB wrote: Yes, this is normal. BTW, make sure you select the shares under the "C" volume for backup, the top level folders you will see are symbolic links (shortcuts) - if you pick them, crashplan will backup the shortcut file, but not the data.
I am familiar with linux symlinking, but thanks for the tip. Backup is working great and I've already tested a restore. A little strange that the default restore location is the conf folder. But I am able to change that on the fly so it's not a big deal. Anyone know of way to make it default to original location so I don't have to change it everytime?StephenB wrote: If you change ui.properties back, you can run the desktop client to manage the crashplan server that is locally installed on your PC. This would be important to people who have a multi-PC license. So this behavior is expected.
I guess I misunderstood the guide. I was actually using the following link for my guide (http://www.shasam.net/blog/2012/3/21/cr ... s-x86.html). I was under the impression that even after I changed my ui.properties back to the default I should still be able to manage my ReadyNAS without puttying first. I guess I have to putty in everytime. Not a big deal. Besides that, the only other two things that were unexpected from the guide was that my readynas didn't start listening to port 4242 until after I connected with my Desktop Client and i always got a connection refused when telneting to localhost on port 4200. But everything works regardless of those two differences.
I'm on Verizon Fios 25/25 plan and am seeing speeds at around 9Mbps. Anyone know if that's a limitation of Crashplan? Or I wonder if my Fios service isn't living up to it's advertised plan. My speedtest results show around 20Mbps, so I am curious as to what other people are seeing.
I have Verizon Fios 35/35. Speeds vary quite a bit - it depends in part on what is going on with Crashplan Central, and partly on the NAS (and your ISP of course). I've seen it vary from 1.5 Mbps to 18 or so. 9 Mbps is fairly is typical.skim32 wrote: ...I'm on Verizon Fios 25/25 plan and am seeing speeds at around 9Mbps. Anyone know if that's a limitation of Crashplan? Or I wonder if my Fios service isn't living up to it's advertised plan. My speedtest results show around 20Mbps, so I am curious as to what other people are seeing.
I've set the WAN sending buffer size to 2560 KB, and the receiving message buffer size to 512 KB in backup settings. I also have data de-duplication set to "minimal" and compression set to "off" in advanced backup settings. This seems to give pretty good performance.
I've also made a few adjustments to my.service.xml on the NAS which seems to speed up some file types. They certainly helped in the beginning, but I haven't confirmed how much they help with 3.2.1. PM me if you want details on that.
I don't recall the exact performance of my initial backups, but I know I was uploading an average of ~70 GB per day, perhaps more. There is a short performance thread here: viewtopic.php?f=4&t=61412 you might want to add to it.- I followed the guide in the OP and have had CP 3.0.3 running for a while now without issues. Will it auto update the Linux version on our NAS?
A few days ago in my backup status email I noticed that my backup was not complete any more and the next report showed that it was even more behind. When I checked on the history from the CP client it was showing that the CP service was starting and stopping multiple times a min. I am not Linux man so I figured I would try to uninstall CP from the NAS (I did not do the full uninstall where you clear out the config files) and then install 3.2.1. That went without hitch. I rebooted the NAS after that and then connected with the client. It took about 5 hours for the NAS to verify all of the data with what was already backed up to the CP cloud. I have 3 backup sets and it completed 2 of them and then the client dropped. I reconnected and checked the history and this is what I see:
So it looks like it is having a hard time keeping the CP service running on the NAS. I am on RAIDiator 4.2.21, Memory: 4096 MB [4-5-5-18 DDR2], Volume C: Online, X-RAID2, 6 disks, 77% of 7404 GB used. The services I have installed are CP, Nas Monitor 3.3, PHP+Mysql Support 1.4, ReadyNAS Remote, v1.0.9.78, uTorrent 2.2.02 (not running).
Any advice on what to check for? - It appears to auto-update on the NAS.
Have you tried rebooting? - I rebooted the NAS after installing 3.2.1 but have not rebooted it since then.
- I shutdown the readynas and cold booted it. From what it looks like when ever there is a backup job running the CP service keeps restarting. I have 2 backup sets that only run at night and one that is all the time. As soon as the all the time set finished the CP service ran fine until my at night sets started and then the service started restarting again. The CP client gets disconnected when that happens but my Putty connection to the NAS is fine. So this seems to be only affecting CP.
- You might want to engage CrashPlan support (and post on their forum), They won't do much with the headless configuration, but I think your issue is not related to the fact you are headless. I see some cases where the service disconnects in my log, but I am not seeing the continuous "Crashplan Started" entries that you are seeing.
In the meantime, you can look at the logs in /usr/local/crashplan/log. Note there are also some logs in /usr/local/crashplan/bin. Also, if you click on the house in the upper right corner of the client, you will get a list of commands (which you can enter at the top of the window). There is a way to adjust the logging level, but regrettably the usage hint is not informative.
You could also be running out of virtual memory. If you look at /usr/local/crashplan/bin/run.conf you will see an -Xmx512m option. You can try doubling that to -Xmx1024m and see if that helps.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
