Ok, I am just going to go out and ASK this REALLY DUMB question...

 

Based on this: http://lime-technology.com/forum/index.php?topic=4008.msg201385#msg201385

 

Is this package suppose to be in place from the steps I listed above? As in, using this package, what steps should I still be doing? Something like:

 

1. Install the 3 prereqs (openssh, openssl-solibs, GNU cpio)

2. Make sure your root account or an account has a password, later for SSH

3. Install this package (handles all the steps in the link attached 8 thru 18)

4. Run Putty, go to Connections > SSH > Tunnels.  Enter 4200 for the source port, then enter localhost:4243 for the destination and click 'Add'.

5. 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

6. 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'.

7. 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.

8. 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.

 

Sorry, I might be a bit of a beginner to be attempting this I do have it working, but I installed this package, then did all the manual steps and now have like 3 copies of crashplan installed on my cache drive and want to clean up a bit.

Glad its not just me who had some issues :-) I learnt a lot and then did everything fresh once i knew what i was doing (or i should say was less confused than knowing ....)

 

I did not install ssh etc like you did as its installed with the crashplan download now and all works fine, you just have to do /etc/rc.d/rcsshd start

 

The identity file seems to be the key bit if you have lots of stuff set up as without it each new install is like a fresh one and you loose and backups.

 

You could just clear out everything crashplan and reboot - it should then install to the directory you have it set to on  the install tab - this is what i did to tidy up. Do your opening up of the tunnel and connect the client to set up what you need. I had a few issues clearing out some of crashplan on my windows machine due to lack of permission and found using midnight commander to clear out the stuff worked fine (just type MC at the promt in your telnet session)

 

Hope that helps

Ok, so below is a run down for people like me (Linux dolts) of how to use this plugin and update it to the latest version of CrashPlan (version 3.2.1 as of this post).

 

Credits:

- SeeDrs (for this awesome plugin)

- ScoHo (Some instructions I initially followed)

- cleight (for CrashPlan GUI plugin)

- Loch (for catching an error in my ways (Added step 6))

 

1. Browse to your server and setup a password for root, or create a new user with a password (this is needed for SSH)

2. Download the plugin from the http://lime-technology.com/wiki/index.php?title=UnRAID_Plugins (For version 3.0.3 currently)

3. Get the link to the latest Crashplan linux file here: http://www.crashplan.com/consumer/download.html?os=Linux (right click the big grey "Download for Linux" button and Copy Link Location)

4. Rename the extension if your browser names it a .txt or .xml file. Open the .plg file you downloaded with a text editor

5. Replace the old URL (old: http://download.crashplan.com/installs/linux/install/CrashPlan/CrashPlan_3.0.3_Linux.tgz) with the new one you just copied (currently: http://download.crashplan.com/installs/linux/install/CrashPlan/CrashPlan_3.2.1_Linux.tgz) Only 1 location in the file

6. Change the CrashPlan Download MD5 line to: <MD5>4f4442aa4a1467c6ad98d12ae87a1ebc</MD5>

7. Replace the old tgz file name throughout the file: CrashPlan_3.0.3_Linux.tgz (should be 2 places if you did step 3 as well, otherwise 3 places including step 3) with the new file name: CrashPlan_3.2.1_Linux.tgz.

8. Copy the package to /boot/config/plugins

9. Open up telnet (PuTTy) and install the plugin:

installplg /boot/config/plugins/Crashplan-0.2-i468-1atv.plg

10. Assuming no failures, browse back to your server and go to Settings -> Crashplan. Before Enabling it set it up on your cache drive (/mnt/cache/apps/.crashplan) or something like that. Enable and save!

11. Now onto your PC (Assuming your using a PC, steps should be close to the same for MAC) for the rest of the steps.

12. Install if you have not already CrashPlan on your Windows/MAC machine so we can connect to the "headless" install on your unRAID box. Once installed head to your install location (typically C:\Program Files\CrashPlan) and go to the 'conf' folder and open 'ui.properties' with a text editor. Add to the bottom:

servicePort=4200

Save and exit it.

13. Open up your PuTTy and setup an SSH Tunnel:

          a. Go to Connections > SSH > Tunnels

          b. Type 4200 for the SOURCE PORT

          c. Type localhost:4243 for the DESTINATION and click Add

          d. Go to Sessions, enter your unRAID box machine name or IP address in the HOST NAME field. Leave the port to 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'.

          e. Click Open to create the tunnel (login to your server now)

14. Now run CrashPlan and hopefully it should launch, if everything is done correctly.

 

Extras:

Definitely recommend installing the CrashPlan GUI made by cleight here: http://lime-technology.com/forum/index.php?topic=15518.0. Installation instructions are:

 

1. Download the plugin from the http://lime-technology.com/forum/index.php?topic=15518.0

2. Copy the package to /boot/config/plugins

3. Open up telnet (PuTTy) and install the plugin:

installplg /boot/config/plugins/Crashplan_gui-1.0.9-noarch.plg

4. Browse to your server and see it under Utils if all went well.

 

Any issues or questions with the above let me know and I will gladly tweak as needed!

Thanks Thrash.

 

Just upgraded to rc8a. Only thing I would add is that you need to change the MD5 for the new Crashplan.tgz or else it just stops. Otherwise great directions.

 

For those upgrading with prior Crashplan installs, once you remote in to the unRaid Crashplan you put in your credentials and you can "adopt" your old system so I believe your existing back-ups should be unharmed (i'd hate to have to resync 100s of GBs of data)

Thanks Thrash.

 

Just upgraded to rc8a. Only thing I would add is that you need to change the MD5 for the new Crashplan.tgz or else it just stops. Otherwise great directions.

 

For those upgrading with prior Crashplan installs, once you remote in to the unRaid Crashplan you put in your credentials and you can "adopt" your old system so I believe your existing back-ups should be unharmed (i'd hate to have to resync 100s of GBs of data)

 

Good catch, I updated the info... Strangely enough, mine worked without this though...

Checking in to see if anyone has any thoughts as to why out of the blue my crashplan engine crashes every few minutes? It was working fine for about 14 days then it stopped working.

 

I 10/13/12 06:47PM Backup scheduled to always run

I 10/13/12 06:47PM [Default] Scanning for files to back up

I 10/13/12 06:47PM [Default] Starting backup to CrashPlan Central: 484 files (358.70GB) to back up

 

It just repeats over and over.

Ok, so everyone knows how I have it configured (and it previously working) I used my steps here:

http://lime-technology.com/forum/index.php?topic=15921.msg201627#msg201627

 

When I try to connect I get this error now:

7578: Oct 17 20:15:38 Hades sshd[19382]: error: connect_to localhost port 4243: failed.

does anyone have this plug in actually working? Maybe I am messing something up?

I just upgraded from 4.7 to 5 RC8a and since I was using crashplan with 4.7, I'm trying this plugin.

 

I modified the plugin file to use crashplan to use the latest version:

<URL>http://download.crashplan.com/installs/linux/install/CrashPlan/CrashPlan_3.4.1_Linux.tgz</URL>

<MD5>444ba4d6e5194472791dd377f561f00c</MD5>

 

and the plugin install looks OK.

 

What buggs me is that the plugin seems to install openSSH but I can't connect with my PuTTY SSH session.

 

What am I missing here?  Do I need to configure something to be able to connect?

 

Thanks

 

G

These two plugins for Crashplan 3.2.1 do not install OpenSSH:

- Crashplan_gui-1.0.9-noarch.plg

- Crashplan-0.2-i468-1atv.plg

 

When I tried installing these, I just installed openSSH by itself as a plugin (opensshd-0.4-i486-rj.plg) where I was able to configure the SSH port, username, and password in the unraid http://tower/Settings described here: http://lime-technology.com/forum/index.php?topic=20848.0

 

If you are talking about installing the new merged versions of crashplan plugins for version 3.4.1 posted by ThrashMagazine, you should probably post in this thread: http://lime-technology.com/forum/index.php?topic=24875.0

 

In this case, OpenSSH is installed as a package not as a plugin, so I'm guessing the data such as username and password would not be retained after a system reboot. Therefore it might still be best to install the OpenSSH plugin and retry to install the set of crashplan plugins that correspond to your own crashplan version (probably 3.4.1 which is shown right when you open the program). When I installed ThrashMagazine's plugins for 3.4.1, my OpenSSH username and password were maintained, and the Crashplan plugins also automatically started up after a system reboot that I did today.

Thaks for the reply, I'll probably install SSH as a separate plugin.  I did use these two plugins:

- Crashplan_gui-1.0.9-noarch.plg

- Crashplan-0.2-i468-1atv.plg

edited slightly to bring it up to the latest of the crashplan install binaries.

 

I did not keep my console output but if I look in the engine plugin, it installs these packages on top of crashplan pkg: openssh-5.8p1-i486-1.txz, openssl-0.9.8r-i486-3.txz and cpio-2.11-i486-1.txz

 

I hadn't even spotted the merged plugin.  I don't see the difference though.  it's still two plugins and the installed package seem to be the same.

 

Anyway, I'll install the SSH plugin and if it works I'll shut up and be happy

 

G

 

 

FYI, for the 3.4.1 version of these plugins you can use here:

http://lime-technology.com/forum/index.php?topic=24875.0

 

As I get time I plan to merge the two. Post any issues you find in that topic.

Hi I am new to UNRAID, but have succesfully set up a number of plugins, Crashplan, Plex, Dropbox, SNAP etc...

 

However when I run Crashplan (which works excellently initially) I have an issue where eventually (usually within 24 hours) my disks stop being accessible over SMB, and I have to restart the server.

 

I have narrowed this down to Crashplan presumably taking up too much memory and UNRAID ditching SMB. I have messed with Crashplan's settings to try and make it less memory intensive, ie. only try and backup overnight etc... but this does not help

 

The problem is I can't work out where I should look for a log to confirm my suspicions about memory, perhaps the server (HP Microserver 8GB) simply cannot run Plex, SNAP and Crashplan at once, and just does not have enough memory? Or maybe I could force it to always maintain SMB, or restart it automatically.

 

Is there a clue in that it happens within 24 hours, possibly a memory leak or something particularly memory intensive which happens at a certain time?

 

Thanks for your advice.

 

 

Perhaps your installation location or backup location was placed in RAM?  My installation is on my cache drive (i.e., unRAID Main, Settings, Crashplan, Install Directory = /mnt/cache/.crashplan). Then check your Crashplan settings and make sure the backup directory is set correctly.  I vaguely recall that it is blank by default which will cause it to backup into RAM instead of one of our unRAID disks/shares.

 

hey I was hoping someone could just clarify for me what exactly this plugin does.  Does it allow you to backup your computers to your unraid server using crashplan or does it allow you to backup the contents of your unraid server to crashplan?  sorry if thats a dumb question - I just want to make sure I understand it before i install it.

hey I was hoping someone could just clarify for me what exactly this plugin does.  Does it allow you to backup your computers to your unraid server using crashplan or does it allow you to backup the contents of your unraid server to crashplan?  sorry if thats a dumb question - I just want to make sure I understand it before i install it.

 

It does both. Once you've installed crashplan it acts as a both a client (to backup to other crashplan instances or crashplan central) and a server (to allow you to point other crashplan clients at it to receive backups).

oh very cool!  I am more interested in backing up the contents of my unraid to crashplan central.  I am doing that now from the crashplan client on my mac mini.  What woudl be the advantage of doign it directly from my unraid as opposed to from the client on my mac?

oh very cool!  I am more interested in backing up the contents of my unraid to crashplan central.  I am doing that now from the crashplan client on my mac mini.  What woudl be the advantage of doign it directly from my unraid as opposed to from the client on my mac?

 

It would take the resources needed to run the client off your mac and onto unraid. And if your unraid is 24/7 you can just leave it ticking away in the background.

 

Notionally though - no real difference, your data will end up backed up as it is now.

 

You might find that the fuss involved in getting it running (and keeping it maintained) under unraid alongside the possible complexities in avoiding having to completely rebackup all your data from scratch under the new install not really worth the effort if you already have all the data backed up - and can't really see any benefits yourself from putting the client on unraid itself.

ok makes sense - I appreciate the clarification.

 

Crashplan was updated to 3.5.3. for anyone that wants to update their plugins.

My Crashplan seems to have quit working today.  It always reads "Waiting for backup" and I can't get it to backup to either the cloud or my other Unraid running Crashplan.

 

Would this be because of a Crashplan update?  My Windows client shows 3.5.3.  Not sure how to find out what version is on my Unraids?  Or how to upgrade them.

 

If this isn't the issue - any other ideas?

 

Thanks,

 

Russell

Depending on how you installed it, you might be able to go to unRAID Main, click Utils tab, then click Crashplan icon under User Applications.  Crashplan had automatically updated itself to 3.5.3.  But I had to reboot my unRAID box for Crashplan to start working again.

If you're using the Crashplan plugin built for unMenu, you need to go to User Scripts and click "Tar Crashplan File". This needs to be done when Crashplan updates, to make sure the installation files for Crashplan on your /boot update. If you're using the 5.x plugin, this is the "Backup Crashplan" button. If you don't do this, Crashplan will reinstall with the older version when you reboot, and have to update itself again.

Hi Guys,

 

Thanks for the tips.  I'm no linux guy - but I take good notes of what I did.  Here's how I got it running (I have more steps, these are summarized):

 

1.  Clean Flash drive with Unraid and my license file.

2.  Got UnMenu installed.

3.  Using UnMenu, got OpenSSL and OpenSSH installed.

4.  Copied CrashPlan.tgz (from the Crashplan download) to my packages folder on my flash drive.

5.  Using Putty, connected and ran a few commands:

    a.  cd /boot/packages/

    b.  tar -zxvf CrashPlan_3.4.1_Linux.tgz --owner root --group root --no-same-owner

    c.  cd CrashPlan-install

    d.  install.sh

 

I then did the stuff to connect my Windows client to the Engine running on Unraid.

 

Does that help?

 

Thanks,

 

Russell

 

P.S.  I tried the Unmenu option to "Tar Crashplan File" after stopping it - then I started it again, but it didn't fix it.  Thanks for the idea.  I have done a complete reboot already also.

Hey,

 

I downloaded 3.5.3 and "refollowed" those steps, using the 3.5.3 instead of the 3.4.1, of course... and it worked!

 

Thanks again for the help,

 

Russell