Crashplan on Duo/NV+ v2? [SOLVED + TUTORIAL]

[iearmand]

Ok, I could not wait. The appleal of having Crashplan run natively on my NV+ was too much..

Anyway I managed to get as far as updating the dependencies (apt-get install libjna-java)

It's here I've gottena little stuck. You guys mention editing the service file which in my case is in:

Code: Select all

/c/home/Neil/crashplan/conf/default.service.xml

Is this correct?

If so the file does not seem to contain :

Code: Select all

<serviceUIConfig>
    <serviceHost>0.0.0.0</serviceHost>
    <servicePort>4243</servicePort>
</serviceUIConfig>

I added this and continued witht eh install. However I keep getting the following error in the log.

Code: Select all

/c/home/Neil/crashplan/jre/bin/java: /c/home/Neil/crashplan/jre/bin/java: cannot execute binary file

May need to go thought he process again from scratch...but any help would be appreciated..

[sphardy]

1. The Service file is called "my.service.xml" - also the code you quoted is not correct and does not match the instructions
2. You appear to be running the wrong java installation - you shouldn't be running any java included with the Crashplan installation. Check your path and java environment settings

[iearmand]

Thanks sphardy.

You were correct, I had the wrong java installation. I ran a crashplan update which asked if I want to install and I had done so...knew that would come back to haunt me.
I also had a typo in the path & java environment settings which was not helping.

I have now managed to get Crashplan running without any error in the log before I connect.

However now when connected I am getting the "Connecting to backup destination" but nothing is heppening.
I also get the following in the error.log:

Code: Select all

Exception in thread "W13388796_ScanWrkr" java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager
   at com.code42.jna.inotify.JNAInotifyFileWatcherDriver.<init>(JNAInotifyFileWatcherDriver.java:21)
   at com.code42.backup.path.BackupSetsManager.initFileWatcherDriver(BackupSetsManager.java:392)
   at com.code42.backup.path.BackupSetsManager.startScheduledFileQueue(BackupSetsManager.java:330)
   at com.code42.backup.path.BackupSetsManager.access$1600(BackupSetsManager.java:65)
   at com.code42.backup.path.BackupSetsManager$ScanWorker.delay(BackupSetsManager.java:1035)
   at com.code42.utils.AWorker.run(AWorker.java:158)
   at java.lang.Thread.run(Thread.java:722)
Exception in thread "W21889822_ScanWrkr" java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager
   at com.code42.jna.inotify.JNAInotifyFileWatcherDriver.<init>(JNAInotifyFileWatcherDriver.java:21)
   at com.code42.backup.path.BackupSetsManager.initFileWatcherDriver(BackupSetsManager.java:392)
   at com.code42.backup.path.BackupSetsManager.startScheduledFileQueue(BackupSetsManager.java:330)
   at com.code42.backup.path.BackupSetsManager.access$1600(BackupSetsManager.java:65)
   at com.code42.backup.path.BackupSetsManager$ScanWorker.delay(BackupSetsManager.java:1035)
   at com.code42.utils.AWorker.run(AWorker.java:158)
   at java.lang.Thread.run(Thread.java:722)

I have also tried to run "apt-get install libjna-java" and get:

Code: Select all

libjna-java is already the newest version.
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 openjdk-6-jre-headless : Depends: libcups2 but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Even stranger, If I disconnect, stop then start Crashplan, I now cant connect again....

[sphardy]

Re. the Java error - I too still get that, but it so far does not appear to be affecting CrashPlan functionality. iNotify relates to realtime scanning of the filesystem so unless you plan to backup your NAS to another unit running CrashPlan, I think you can safely ignore it.

libcups2 is a bit of a pain. Netgear appears to have a custom version of the library in their firmware and so you have to force that to be overwritten when installing OpenJDK. Given the v2 devices don't support networked printing anyway I doubt this will cause any real issue.

If the suggested command "apt-get -f install" doesn't work try this:

Code: Select all

dpkg -i --force-overwrite /var/cache/apt/archives/libcups2_1.4.4-7+squeeze1_armel.deb


Then try the install again.

Note: I take no responsibility if this change does break things. Plus there's a strong possibility a firmware update will restore the Netgear version of libcups2 which may then break CrashPlan, requiring libcups2 to be updated again. Philippe's java suggestion may be a better option in this case. The perils of being an early adopter...

[filzip77]

Hello,
I forgot to mention that I created a symbolic link to libjnidispatch.so after the installation of the package libjna-java.

Code: Select all

ln  -s /usr/lib/jni/libjnidispatch.so /c/home/Philippe/crashplan/libjnidispatch.so

If you do not create this link, the front-end will wait forever when you start the backup.

[iearmand]

Thanks filzip77. That fixed the issue and Crashplan is now syncing.
Thanks for all the help guys...I had already conceded that I would never have Crashplan working on my NV+v2, to now having it working is just great.

filzip77 as I was working though your install instructions I made a few mistakes and had to go looking else where for things I did not full understand. They may seem obvious to you guys but they took bit of digging for me....if you update your thread they might help others.

During installation I was confused about what options to set when install crashplan. To keep consistent I used your dir structure:

Code: Select all

Your selections:
CrashPlan will install to: /c/home/Philippe/crashplan
And put links to binaries in: /usr/local/bin
And store datas in: /c/home/Philippe/crashplan/manifest
Your init.d dir is: /etc/init.d
Your current runlevel directory is: /etc/rc2.d

Is this correct? (y/n) [y] y


Location of Service file would help:

Code: Select all

/c/home/Philippe/crashplan/conf/my.service.xml

again thanks a million for you work in getting Crashplan working...

[filzip77]

Following your recommendations, I have updated my instructions.
You could maybe change the title of the thread to indicate that the problem is solved:
Crashplan on Duo/NV+ v2? [SOLVED + TUTORIAL]

[iearmand]

done and updated the top thread with a link to your tutorial post as well.

[iearmand]

Was wondering if you guys were seeing any speed issues?
Normally I get 1.2Meg up but at the moment it does not seem to go over 300k up....have tried a few setting on the Crashplan client but to no avail...

[StephenB]

Was wondering if you guys were seeing any speed issues?
Normally I get 1.2Meg up but at the moment it does not seem to go over 300k up....have tried a few setting on the Crashplan client but to no avail...

Are you CPU bound?

Not sure what you tried, but the normal adjustments are

advanced backup settings

data deduplication=minimal
compression=off

You can also try
network settings

sending message buffer size=2560

though I didn't find it made much difference on the Pro. It did no harm though.

I've also found that performance varies by file type.

BTW, if you want to restart the service after you apply changes, try clicking on the house icon on the upper right of the client. It will open a command box, with a reference list of supported commands. Restart is one of them. Stopping the service (which is also there) is not so useful, since the client can't restart it.

[filzip77]

I kept all default values.
The default upload transfer increased and stabilized around 1.3 Mbps (most of the files are pictures of 5MB).
I decided to limit the upload to 800 Kbps in order to do not slow down too much my internet connection.

Have you check your CPU load? The command is

Code: Select all

top

What are the size of the files you transfer? Remember that the NAS ARM has a CPU much less powerful than in your PC. Computing the hash table (MD5) for a big file may use a lot of CPU time on the ReadyNas ARM.

On my side I did not notice a high CPU load during the transfer.

[StephenB]

On my side I did not notice a high CPU load during the transfer.

This depends on the file size and the file extension. Photos are probably small enough that CPU load is not a factor. DVD or BluRay media files are another matter. Though at 1 mbps it might not be practical to back those up to CrashPlan Central anyway.

The 3.2 engine seems to be better on CPU than the older 3.0 engine though. My pro is uploading at about 8 mbps at the moment, and the CPU load is only 3%. I think it was much higher in early March (with the old engine). Back then I was frequently saturating one of the Pro cores. It is still taking about half the memory though.

[iearmand]

I may have been following a red heron. I was checking through my my.service.xml file looking to change some settings and noticed that my servicehost setting had not been set correctly (0.0.0.0). when I fixed it crashplan started to sync correctly older files rather then upload them.
once the initial sync is done I will take a closer look at the upload speeds I get.
one thing I have noticed is that crashplan does start to slow on PC when you have a vast amount of small files....I'm guessing ths part MD5, part file reading, part de-dup & part compression. I will tale a closer look once the intial sync is complete.

Thanks for the feedback though. will give me plenty to fiddle with.

[disconect]

Really interesting topic ! (flag ...)
thx for the work !

[sphardy]

Has anyone noticed crashplan not auto-starting on boot?

The init script is correctly linked in /etc/rc2.d, and calling it manually starts crashplan proving the script/link are valid. But it doesn't appear to work on boot. I haven't checked more deeply to see if the script is just not called or if crashplan fails for some reason, and I have a cron job that regularly checks crashplan is running as a precaution that works around the issue anyway.

But anyone else seen this?

Also - has anyone figured if this setup survives a firmware upgrade?