CrashPlan


agw

Recommended Posts

  • 1 month later...
  • Replies 533
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

First off thank you for the instructions, my install went very well.  I was curious though, my backup doesn't appear to ever complete.  It always has a to do of over 10GB, and after running several times that number doesn't really seem to change, and even goes up.  For instance right now it showed 17 GB remaining, with another back up due in a couple of hours.  I forced the start of the backup and it's running but the to do climbed up to 20 GB.  What is going on?  I also back up to an external HDD and it behaves the same way.

 

I'm using Windows  7 64 and I do have a couple of VM's but I excluded them

Link to comment
  • 1 month later...

I'm losing my mind!  I got Crashplan up and running a few months ago, but I knew I had done something.....wrong.  I didn't install the the default directories and instead installed it to my flash drive, what's the difference I figured.....  I connected to it once with the Windows client software through the SSH tunnel and never again.  So I got it configured and everything, got about 200gb backed up and it's been running great. 

 

Then yesterday happened....we had a power outage while I was at work that lasted longer than my UPS.  dang!  now I can't get Crashplan to fire back up.  I mean...it runs on the server, I have everything set the way it should be as far as I can tell....but I can't connect to it with the windows software to configure it again.  it hasn't checked in in like 1.5 days.  :(

 

Instead of cluttering up the thread with pics of my problems here's an album of screenshots I took to show you guys what I'm dealing with and see if anyone has any ideas as to why I can't connect...

 

 

Thanks in advance

Link to comment

You need to look at the crashplan log files in the log/ directory inside your crashplan install.

 

Also don't install crashplan onto your flash drive (though your screenshots show that not to be the case?) - it writes alot of log and cache files into its install space and will likely shorten the lifespan of your flash drive significantly.

Link to comment

ok, ended up just copying all the logs to /boot/templogs.  :)  now I can easily see them in notepad ++.  I've looked through all the logs, and I don't see anything that sticks out as being  a problem.  the service is running (as far as I can tell) i just can't connect to it from my windows desktop to configure it properly. 

 

any idea specifically what log i should be looking at?  and for what?  sorry to be so dense..but...I'm stumped.

Link to comment

ugh..for the love of pete...no wonder I could never get this to work....the directions are a little vague on page 23 at the part that says

 

 

- Once you run Putty, go to Connections > SSH > Tunnels.  Enter 4200 for the source port, then enter 4243 for the destination and click 'Add'.

 

 

the Crashplan instructions are actually clearer on this....taken from: http://support.crashplan.com/doku.php/how_to/configure_a_headless_client

putty2.png

clears it up a little more.  I had ALWAYS put the unraid server's IP:4243 I had no idea it was supposed to be my machine.  I was under the impression that we were forwarding the traffic to unraid right there....anyway, I think that was my problem.  finally....I'm getting there...

Link to comment
  • 2 weeks later...

I have been running the Crashplan plugin for a week now. And I must say that it works very well. Soon all my digital photos are backed up!

 

I didn't succeed in getting the Windows client to connect to the headless Crashplan-client. Followed the guides on the forum but no luck. But when using the Mac client I got it working. So I am using this setup instead!

 

Regards Jens

Link to comment
  • 4 weeks later...

Hi - been trying to get this working on my machines and i am so near but cannot get the connection to work. I have open posts on another thread but a quick question on the SHH tunnel settings here - my server is called backupsvr for example and in putty i am putting local as 4200 and destination as backupsvr:4243 is this right or must it be localhost:4243??

 

The reason i did it like this is i have 2 unraid servers and want to be sure which i am connecting to

 

Thanks

 

Link to comment

Thanks - i was refering to post 483 where there is the setting for putty. Just want to clarify if i have 2 servers called Bob and Fred do i use localhost 4243 or do i use Bob:4243 and Fred:4243 to differentiate?

 

My problem is i have the tunnel open, crashplan set to look for 4200 but still its not connecting.

 

Also i wanted to clarify the install directory for crashplan as i get errors on boot up, i used /usr/local/crashplan - is that right if i want it to run in memory?

Link to comment

Hi again!

 

I didn't get the tunnel to work with Putty. I am using my Mac to setup the tunnel now with the SSH command.

 

As I understand it, you use the 4200 port locally on your computer for CrashPlan client. The SSH tunnel then routes this traffic to port 4243 on the server.

I think it should be localhost:4243. The adress to the server (Bob or Fred) is given in the "Session" Window of your Putty Configuration.

 

Remember that you can only connect to one server at a time as you use the same port (4200) to connect to the Crashplan server.

 

Link to comment

Thanks for that - i was followign that info and the posts here. i will try when i get home using localhost:4243 as i can see now that which server i want to connect is in the hostname box above, hope that will let me in.

 

If it does then i will only have the problem with the initial install as i get an error loading it to ram - do you have it running in memory and if so what is your install directory for crashplan?

 

Thanks again

 

Link to comment

Probably me being dumb, but I am having trouble running the CrashPlan tar extraction:

root@Hades:/boot/packages# tar -zxfv CrashPlan_3.2.1_Linux.tgz

tar (child): v: Cannot open: No such file or directory

tar (child): Error is not recoverable: exiting now

tar: Child returned status 2

tar: Error is not recoverable: exiting now

 

The file is there and the file name is correct? Do I have to do this from Console or can I be doing it from Putty like I am trying?

Link to comment

Credit this to ScoHo, I am just updating this as some of the instructions were a bit off and caused me some pain (not a linux guy) :)

 

This guide assumes you're using a Windows desktop/laptop, but it probably wouldn't be all that different for a Mac or Linux distro.  For a Mac, prostuff has some scripts in this thread to help with that process.

 

Here we go...

 

1. Get the latest version of unMENU and install it. Wiki I used here:

http://lime-technology.com/wiki/index.php/Configuration_Tutorial#Install_UnMENU_for_Screen_and_eMail_Notifications

unMENU: http://www.lime-technology.com/wiki/index.php?title=UnMENU_documentation

 

2. Once you have unMENU installed, go to http://servername:8080/'>http://servername:8080/ (servername being the name of your unRAID server) in a browser on your Windows desktop.  This takes you to the unMENU web interface.

 

3. Once unMENU loads, click the Pkg Manager menu option at the top.

 

4. Go down to the 'openssh' package and click the button 'Select openssh-5.1p1-i486-1.tgz' (that is the version as of this writing so this may change).  Once installed, click 'Enable Re-Install on Re-Boot' button.  This will ensure SSH gets reinstalled on reboot.

 

5. Go back to the Pkg Manager and find the 'openssl-solibs (OpenSSL shared libraries)' package and click the button 'Select openssl-solibs-0.9.8i-i486-1.tgz' (that is the version as of this writing so this may change).  Once installed, click 'Enable Re-Install on Re-Boot' button.  This will ensure openssl gets reinstalled on reboot.

 

6. Go back to the Pkg Manager and find the 'GNU cpio copies files into or out of a cpio or tar archive' package and click the button 'Select cpio-2.5-i486-3.tgz' (that is the version as of this writing so this may change).  Once installed, click 'Enable Re-Install on Re-Boot' button.  This will cpio gets reinstalled on reboot.

 

Those are the only 3 packages you will need for this (other than the Crashplan client itself).

 

7. Go back to http://servername and under Users setup a password for root if you have not already, this needs to be done. If you want to keep root blank, create a new user/password.

 

8. Now go to your unRAID server terminal either directly on the machine or via your Telnet client of choice (I use PuTTy) and login to your server.

 

9. Time to start SSH so type:

/etc/rc.d/rc.sshd start

 

10. Now create the a public/private key pair by typing:

 

ssh-keygen -t rsa

 

11. Now follow the prompts:

- First you will be prompted for a file name.  I just chose 'cpkey'.

- Next you will be prompted for a password.  Create one, and remember it (although I'm not sure what it's used for).

 

12. Now copy the files that have been created by the install of ssh:

 

cp --preserve=timestamps /etc/ssh/* /boot/custom/etc/ssh

 

13. Now add the following lines of code to your GO script to copy the key files and start SSH on server start.  To update your GO script, I recommend using unMENU.  Just start up unMENU again (http://servername:8080/'>http://servername:8080/) and go the the 'Config View/Edit' menu option.  You will see a dropdown there that includes all of your script/config/system files.  Select '/boot/config/go' from the dropdown and that will load your GO script in readonly mode.  To edit it, just click the 'Edit' button at the bottom.

 

cp --preserve=timestamps /boot/custom/etc/ssh/ssh*key* /etc/ssh
chmod 600 /etc/ssh/ssh*key*
/etc/rc.d/rc.sshd start

 

14. Now install Crashplan on your Windows desktop if it isn't already installed - http://www.crashplan.com/consumer/download.html While you're there, download the Linux client as well since you'll need that to install on your unRAID box.  I recommend setting up your Crashplan account at this point as well.  You can do that when you run the Windows client.

 

15. Now install the Crashplan Linux client on your unRAID server.  First, copy the TGZ file to your packages folder on your flash drive.  This folder may vary by the unRAID version you're using.  For me, it was 'boot/packages'.

 

16. Now go to your unRAID console, cd to the folder of the TGZ file in the previous step, and Tar the install file by typing (e.g. cd /boot/packages/):

 

tar -zxvf CrashPlan_3.2.1_Linux.tgz

*note: Your filename may very depending on version. This was the one I was getting hung up on, originally it had the "v" after the "f", the command can't support that.

 

17. Now run the install file:

 

install.sh

 

18. Now follow the prompts:

- Say yes to the Java Runtime install if asked

- Enter anything for the rc scripts, we won't be using them

- The manifest directory is where your backups will live. You will need to change this later in the client, but for now put one of your data drives so it doesn't start backing up to memory.  You could do something like /mnt/disk1/Backups.  Personally I backup to their cloud so I set that up later in the client.

- Accept the defaults for the rest of the prompts.

- Once finished, Crashplan should now be installed on your unRAID box.

 

19. Now we need to set up your Windows install of Crashplan to connect to the "headless" install on your unRAID box.  So on your Windows desktop, go to your CrashPlan install folder, most likely 'C:\Program Files\CrashPlan', and then go to the 'conf' folder.  Open the 'ui.properties' file for editing, and add the following line to the end of the file and save & close it:

 

servicePort=4200

*note: This is the port we will use in the next step when setting up the tunnel to access the headless install.

 

20. Now we need to set up an SSH Tunnel on your Windows desktop.  I use Putty (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) for this but I'm sure there are other programs that can be used.

 

21. Once you run Putty, go to Connections > SSH > Tunnels.  Enter 4200 for the source port, then enter 4243 for the destination and click 'Add'.

 

22. Now (still in Putty), go back to 'Session' and enter the name or IP address of your unRAID server in the 'Host Name' field.  Leave the port at 22, and select 'SSH' for 'Connection type'.

*note: So you don't have to set this up every time you want to connect to your unRAID headless Crashplan install, give this session a name (how about 'unRAID'?) and click 'Save'.

 

23. Now click 'Open' to open the tunnel.  You should get a terminal with a prompt for username/password.  Enter your unRAID username and password here.

 

24. Now run the Crashplan client on your Windows desktop and enter your (hopefully already created) login credentials.  If all went well, you should establish a connection and you will be connected to the Crashplan engine on your unRAID box.

 

25. If everything looks good, close the Crashplan client in Windows.  Remember if you ever want to connect to the Crashplan engine on your Windows machine you need to comment out that line in the  'ui.properties' file.

 

26. Now we need to make the Crashplan install on your unRAID box persistent on a reboot.  To do that, first stop the Crashplan engine on your unRAID server cleanly:

 

/usr/local/crashplan/bin/CrashPlanEngine stop

 

27. Tar the Crashplan folder which at this point should also include a crucial .identity file that was created when you connected to the Crashplan engine via your Windows desktop.  To do this, type:

 

tar -cvf /boot/packages/crashplan.tar /usr/local/crashplan /var/lib/crashplan

 

28. Now add the following lines to your GO script.  This will install and start the Crashplan engine on startup:

 

# install crashplan
tar -C / -xvf /boot/packages/crashplan.tar
/usr/local/crashplan/bin/CrashPlanEngine start

 

 

That should do it!  I would do a reboot and make sure everything starts up correctly and try connecting to the Crashplan engine via the Windows client again and make sure the connection still works.  Remember to add that line to your ui.properties file to connect to the unRAID engine (if you removed it).  Also remember every time you want to connect to the unRAID Crashplan engine, you will need to start that SSH tunnel session via PUTTY (or the SSH Telnet of your choosing).

 

A few notes:

 

- Make sure you connect to the unRAID engine through your Windows desktop and ensure the backup destination is set properly.  There was a report of someone not doing this and it was storing the data in RAM and eventually crashed.

 

- It's been said on this thread that the Crashplan engine auto-updates and will cause you to not be able to connect to your unRAID Crashplan Engine.  There is a script in unMENU (Under 'User Scripts') called 'Tar Crashplan File' which will re-tar the new version install of Crashplan on your server and should correct the problem.  Make sure you click the 'Stop Crashplan Engine' script button before doing this.  Then after tar, click the 'Start Crashplan Engine' button.

 

- One thing I would like to add to this is how to add the Crashplan stop functionality to the Clean Powerdown script so Crashplan stops cleanly when the server is powered down.  I have no idea how to do that.

 

- Again, credit this to ScoHo, it is just a re-write of his original post with a few minor tweaks.

Link to comment

Great procedure, thanks for documenting it - I'd have been lost without it.  A couple of things which I had to tweak as I'm connecting from a mac (no putty)

 

The command you'll need to enter in the terminal programme to do the port forwarding will look something like this:

 

ssh -L 4200:localhost:4243 user@server

 

I also had to install Jre - Java 2 Platform Standard Edition Runtime Environment from UnMENU - for some reason, the bundled JRE with CrashPlan didn't do the trick for me.

 

Aside from that, all working like a charm now.

Link to comment

I have gone through the entire post and seems like I have followed along.  However, when I get to the step of running CrashPlan on my Windows machine it simply sits there saying "please wait" and never moves forward.  The identity file is never created in /var/library/crashplan either.  Do I need to open up port 4200 on my router to allow ssh access?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.