I am having no luck, now I am getting a error when I run the script and CrashPlan won't launch.  Any chance I email you and have you make it for me?  

 

I can PM you my info and email address

I am having no luck, now I am getting a error when I run the script and CrashPlan won't launch.  Any chance I email you and have you make it for me?  

 

I can PM you my info and email address

 

Go for it.  I have stuff to do outside the rest of the afternoon but should be able to look at it in a couple of hours.

just sent you a PM, thanks for helping

Thanks again Prostuff, I owe you one.

Thanks again Prostuff, I owe you one.

 

Not a problem, glad I could help.

 

When I get a chance I will edit the instruction so they more closely match what needs to be done.

Prostuff, maybe when you get a chance you can make a start script like the stop one you made.

Prostuff, maybe when you get a chance you can make a start script like the stop one you made.

 

There is a start script, at least in my version of unMenu.  Check the unmenu folder on the flash drive and see if you can find it there.

I don't have one, in version 4.5.6

 

Also can you tell me how to setup my server to back up to a certain location?  I created a backup folder on Disk4 that I want to back up to.

 

thanks

Prostuff, maybe when you get a chance you can make a start script like the stop one you made.

 

There is a start script, at least in my version of unMenu.  Check the unmenu folder on the flash drive and see if you can find it there.

It must be a script you created locally, since there is no user-script distributed in unMENU to "start" crashplan

 

 

Prostuff, maybe when you get a chance you can make a start script like the stop one you made.

 

There is a start script, at least in my version of unMenu.  Check the unmenu folder on the flash drive and see if you can find it there.

It must be a script you created locally, since there is no user-script distributed in unMENU to "start" crashplan

 

 

 

Well crap, there is a stop one I figured I included the start one.

 

Ok, it is attached below.

40-unmenu_user_script_start_crashplan.zip

So do I just unzip this in the unmenu folder?

 

So do I just unzip this in the unmenu folder?

 

yes

See if your router supports any of the dynamic dns providers. The management interface will have a section for it if it does.

 

Or you can pick one and use a script from unraid to update, though how easy this is will entirely depend on your networks configuration. From trivial to difficult / impossible.

 

https://www.dyndns.com/ as an example of one such service - though there are many.

 

So I finally configured my Verizon router to use dynamic dns, do I have to login and make sure it's stays updated or does it do this automagicly?

Not knowing anything about your router - if you've given the router your username, password and the provider of dynamic DNS I'd expect it to keep it up to date.

So I haven't used crashplan as much as I thought I would, should I remove it or just let it go?  What would I have to do to remove it?

First of all, thanks to both Prostuff and Boof for pioneering a working solution for Crashplan + unRAID.

 

I followed every step from page 3, and everything works great, except for this part:

- This clearly generates the /var/lib/crashplan/.identity file which is so key

 

I've checked, rechecked, restarted and rechecked, and I have no .identity file on my server.  However, while I'm typing this I am able to get Crashplan to backup while connecting with the windows client over ssh port forwarding.  It is running VERY slow at 300 kb/s, which I can't fathom is correct unless Crashplan is using my wireless laptop connection from the client.  Is that correct?  Connecting over ethernet still results in a 300 kb/s transfer rate.  

 

Here is my current internet speed as tested by speedtest.com:

Any ideas?

 

I also found the STOP and TAR user scripts for Crashplan in unMenu (thanks Joe?).  Is there a clean way to automate these in the go and powerdown scripts?

 

Thanks again you guys.

 

Well I figured out the 300 kb/s issue.  Even though I had seen the throttle settings on the Network tab in the client, I assumed the phrase "ignored over LAN" meant all ethernet.  That was incorrect.    I now have it running at 10 mb/s, just to keep half my bandwidth open for other things.

I also found the STOP and TAR user scripts for Crashplan in unMenu (thanks Joe?). 

I am actually the creator of those scripts (with some input from Joe).  I have a start crashplan one also but it looks to not be included with the newest release of unMenu.

 

Is there a clean way to automate these in the go and powerdown scripts?

To start Crashplan on startup it is only a matter of putting the lines in your go script (which I think is mentioned in the install instructions).  As for the stopping, you can edit the powerdown script yourself to add it, or use the stop button before you shutdown the server.

Thanks Prostuff.  I had a suspicion that might have been your unMenu code, thus the ? in the comment.  Also, I knew about your instructions on the go script, but wasn't sure if it was the same code as using the unMenu stuff.  Thanks for clarifying.  What about the .identity file?  Can I assume that without it, my unRAID Crashplan won't run headless?

Thanks Prostuff.  I had a suspicion that might have been your unMenu code, thus the ? in the comment.  Also, I knew about your instructions on the go script, but wasn't sure if it was the same code as using the unMenu stuff.  Thanks for clarifying.  What about the .identity file?  Can I assume that without it, my unRAID Crashplan won't run headless?

 

if you are trying to find that file via Mac OS X terminal you will not see it by defualt.

 

If you telnet into the server and then type this code one line at a time:

cd /var/lib/crashplan
ls -al

 

If it still does not exist then there is something odd going on.

Ah... the -al is what did it.  It's in there.  I'm using Putty on Windows 7.

 

Now, about the tar / persist after update... how does the re-Tar button in unMenu fit in?  Do it instead of the untar routine, before, after?

Ah... the -al is what did it.  It's in there.  I'm using Putty on Windows 7.

 

Now, about the tar / persist after update... how does the re-Tar button in unMenu fit in?  Do it instead of the untar routine, before, after?

 

Crashplan should auto update with a new version comes out.  Once that happens just hit the Tar Crashplan button and you should be good to go.  The old version is renamed and the new version will takes its place.  A reboot will install the new version instead of the old, though a reboot is not necessary to be running the newest version.  If you don't want to keep the old version just find it in the packages folder and delete it.

What happens with the .identity file that has been tarred?  Is that tar / untar part of a separate process in the go script, outside the control of tarring the newest update?

What happens with the .identity file that has been tarred?  Is that tar / untar part of a separate process in the go script, outside the control of tarring the newest update?

 

The .identity file stays the same even after the upgrade. It is created when you login to the application and is created so that the information is remembered.  If you did not have it you would end up resetting some of your settings when you reinstall on every reboot.  The re-tar of the crashplan app just bundles everything (including .identity file) just in case they change something on the install of a new version.

Ah... so the tarring of the current install is just to create a restore point in case of a bad update.  In the event of an update, I can assume that the .identity file stays intact?