Crashplan backup sw allows backing up to a friend's computer

[jolly_jester]

I had a nightmare getting this to run on my ds1010+ but finaly managed it and also got it to start on startup of my ds1010+.
Most of the scripts only seem to run in bash shell and you have to have all the correct ipkg packages installed and have to modify the startup scripts to run. Not for the faint hearted but possible. Remember it will only run on atom based hardware due to the need to have proper java.
Took me about 6 hours last night to get it going and to get it to autostart.

[ullerdk]

Remember it will only run on atom based hardware due to the need to have proper java.

Arghhh, that is why I can't it installed on my DS508, which is not Atom/x86 based.
Damn, I wish I could have CrashPlan running on my DS508
Now it may be time to upgrade my DS508 to a new DS1511+.
/Ulrik

[Dirac]

Would someone who has this working on startup kindly post all the necessary installation and modification steps in detail?

[jolly_jester]

Note: Every time they release a new version you'll need to reinstall saving the config and bin directories each time, as the autoupdate does not work and breaks the install.

Okay first of all this ONLY WORKS ON ATOM BASED NAS

Here's some more to help people start to install it..sorry i'm doing this from memory but it's a start...

Install IPKG (Check for your model on the forum)

ipkg update
ipkg install cpio
ipkg install bash
ipkg install coreutils

cd /var/tmp

***Note must get lotest binary from http://b3.crashplan.com/consumer/downlo ... s=Linux***
wget http://download.crashplan.com/installs/ ... _Linux.tgz

tar -zxvf CrashPlan_3.0.2_Linux.tgz

cd CrashPlan-install
bash install.sh

I installed to default directories (nearly all left as default apart from backup directory) as it cuts down on modifications needed.

Go into the directory where you have installed it and into the bin directory and modify the CrashplanEngine file to work (Sorry cant remember how i did this but did remove alot)

to run type :-
bash CrashplanEngine start

To configure see this :-
http://support.crashplan.com/doku.php/h ... ess_client

[jolly_jester]

Forgot to say that if you are upgrading crashplan to latest version you have to back up the
conf, log, var , bin and cache directories then delete the install and re-install then restore back these.

It's a pain that the auto update does not work and every version you are forced to upgrade the software. It takes about 15-20 minutes once you know how to do it but stops crashplan working until you've upgraded to the latest.

[Dirac]

It seems to install OK, but I cannot connect to it. I'm not sure the SSH tunneling is working properly (I'm using PuTTY on Win7 x64). I'm trying to connect over my LAN, so nothing remote going on (e.g. firewall issues). CrashPlanEngine is listening on 4242 and 4243 as verified by "netstat -na | grep LISTEN | grep 42".

The only thing that produces anything is opening an SSH session to the DiskStation as root, and issuing "telnet localhost 4242" which gives me an encrypted stream. What am I not doing right?

Thanks for posting those instructions jolly_jester--helped a lot!

EDIT: Turns out the CrashPlanEngine stopped running when I closed the SSH window. (I forgot to mention that it isn't running on startup, and I accepted all the defaults for rc.d and init.d when I installed the package. I also didn't edit the CrashPlanEngine script, but it is obviously starting OK if I can get it to run manually). As long as I leave it open, it keeps running. Now, how do I start CrashPlanEngine on the DiskStation, and keep it running on reboot?

[jolly_jester]

I cheated....I added it to the start and stop scripts of sabnzb which i also run. Seemed the easiest way since i also connected sickbeard and couch potatoe this way...
So nzbstarts and all 3 programs start up as well....when sabnzb stops they all stop as well....

I did have a go at getting it too start by itself but gave up and went for the quick fix instead.

[Dirac]

You installed the .spk for sabnzbd? So I guess you would need to re-edit whenever the .spk is upgraded as well, correct?

I do have transmission running on my NAS, but I'm not sure how to edit, or what file to edit. I am not above cheating.

I thought it would be as simple as putting the crashplan startup script in /opt/etc/init.d/, but that didn't work. I added a debug line (echo "Hello World" >> /volume1/crashplan/test.log) and that works, but the script doesn't start crashplan, so maybe it's syntax. The command "/usr/local/crashplan/bin/crashplan start" runs the script properly. I created a symlink for bash in /bin/ so the script can find it (it's in /opt/bin/).

Any additional help is much appreciated. Perhaps an .spk for crashplan can be created?

EDIT: I am now trying to put the script in /usr/local/etc/rc.d/. Running "/usr/local/etc/rc.d/crashplan.sh start" starts the engine when logged in as root. Why isn't it starting automatically on boot? I have permissions set to 755, and I have tried both admin/users and 500:500 for username/usergroup. I have transmission.sh in the same folder and it is starting. Do I need to edit the crashplan.sh file? I am not very familiar with linux but I'm getting comfortable at the command line.

Here's crashplan.sh as it was set up by the installer.

Code: Select all

#!/bin/sh
# Linux Standard Base comments
### BEGIN INIT INFO
# Provides:          CrashPlanEngine
# Required-Start:    $local_fs $network $remote_fs
# Required-Stop:     $local_fs $network $remote_fs
# Should-Start:
# Should-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: CrashPlan Engine
# Description:       CrashPlan backup service engine
### END INIT INFO

#############################################################
# Init script for CrashPlanEngine
#############################################################

# Defaults
SCRIPTNAME=/usr/local/crashplan/bin/CrashPlanEngine

case "$1" in
start)
   $SCRIPTNAME start   
   ;;
stop)
   $SCRIPTNAME stop
   ;;
restart)
   $SCRIPTNAME restart
   ;;
force-reload)
   $SCRIPTNAME force-reload
   ;;
status)
   $SCRIPTNAME status
   ;;
*)    
   echo "Usage: $0 <start|stop|restart|force-reload|status>" >&2
   exit 3
   ;;
esac
exit 0


[jolly_jester]

Try changing the first line to :-
#!/opt/bin/bash



Remember scripts have to run under bash

[Dirac]

Still not running at startup. The only way I've gotten it to work is to run the script manually as root with

Code: Select all

/usr/local/etc/rc.d/crashplan.sh start

inside of a linux "screen" so I can detach and log off, and it will keep running.

I'm not sure why it will run from the command line, and not at startup. I've also reached the limit of my linux knowledge, and learned a few things along the way (like the screen command).

[maxxfi]

Have you tried to run it from /etc/rc.local ?
(i.e. add one line "/usr/local/crashplan/bin/crashplan start" in rc.local)

You wrote that:

I thought it would be as simple as putting the crashplan startup script in /opt/etc/init.d/, but that didn't work. I added a debug line (echo "Hello World" >> /volume1/crashplan/test.log) and that works, but the script doesn't start crashplan, so maybe it's syntax. The command "/usr/local/crashplan/bin/crashplan start" runs the script properly. I created a symlink for bash in /bin/ so the script can find it (it's in /opt/bin/).

Sorry, I did not understand where you added the debug line.

[Dirac]

Have you tried to run it from /etc/rc.local ?
(i.e. add one line "/usr/local/crashplan/bin/crashplan start" in rc.local)

It does not appear to be starting this way either. I suppose it could be starting and terminating immediately after, but if it is, I can't tell.

Sorry, I did not understand where you added the debug line.

I essentially had a "startcp" script in /opt/etc/init.d/ that had the following two lines:

Code: Select all

/usr/local/crashplan/bin/crashplan start
echo "Hello World" >> /volume1/crashplan/test.log


I tried a few other names including "S01crashplan", based on some help pages I found.

I added the second line so I could tell the script was running at startup. Entering the first line at the command prompt when logged in as root would start the CrashPlan engine properly (so I didn't think it was a syntax issue). But I still could not get CrashPlan to start at boot.

I have since moved the crashplan script I put in the code environment a couple of posts ago (the one from the CrashPlan installer) into /usr/local/etc/rc.d/ and renamed it crashplan.sh in the hopes that it would automatically run at startup. It meets the Synology startup script requirements of having the .sh extension, taking "start" and "stop" arguments, and having rwx attributes 755. It is also in the right directory as far as I can tell from Synology's documentation on third-party software. I can start it manually and keep it running in a detached screen, but it is not starting after I exit and restart the NAS.

I appreciate everyone's help and troubleshooting suggestions.

[maxxfi]

I essentially had a "startcp" script in /opt/etc/init.d/ that had the following two lines:

Code: Select all

/usr/local/crashplan/bin/crashplan start
echo "Hello World" >> /volume1/crashplan/test.log


Ok, so if with your debug you found that the command has been really executed,
there must be something missing in the environment that make crashplan fail at startup.
Then, wherever you try to run the script write it like this:

/usr/local/crashplan/bin/crashplan start &> /volume1/crashplan/start.err

That should save in the start.err file both stdout and stderr (i.e. regular output, and error messages)
of the startup command.

[Dirac]

Could not get this to work. It ran when I started it manually, but ultimately through troubleshooting I found that my 710+ did not have the horsepower to fill the upload pipe. I ended up mapping the relevant shares in Win 7 and installing CrashPlan Desktop for Win x64 and things are working great, except having to leave my desktop computer on 24x7 for the initial seed.

[JohnD76]

I am keen to install this myself, but it sounds like a bit of a mission....

Would it be possible to start the Crashplan Engine using Crontab?

For those that have done this, approximately how often do you have to backup/uninstall/install the new client/engine?

Edit: Just subscribed to the RSS feed on crashplan and it looks like there have been 3 minor releases this year already so we are looking at possibly having to 'upgrade' every month which would be a bit of a pain.....

Thanks,

John.