Comments on Entropy Overload: CrashPlan for Backup on Nexenta

This is sort of a response for Jeff. You can'...

2011-02-12T19:53:08.923Z

This is sort of a response for Jeff. You can't install the local copy of the JRE that the installer wants because it's the linux version and you need to use the Nexenta's java. I was doing a fresh install Nexenta 3.01 and Crashplan 3.02. The Java that gets loaded

apt-get install sun-java6-jdk

would cause the crashplan linux installer to say incompatible java version. To fix this I had to install

apt-get install sunwlibc

this resolved the missing library.

Then follow the steps above and it's working like a charm. If you installed the local one.. make sure you change crashplan's java location.

Jeff - if CrashPlan is installing a local JRE, it&...

2010-11-15T06:13:17.882Z

Jeff - if CrashPlan is installing a local JRE, it'll be the one corresponding to the installer's target platform; if it's the Linux installer, then it'll be a Linux JRE, which of course won't run on a Solaris kernel (as I understand it).

It's very possible they changed their installer's mode of operation since I did my installation.

You definitely don't want to be using a Linux JRE. The JRE from apt-get etc. is, as you note, of the 1.6 flavour, and it does work.

I'll write up a post on roughly how to put it together manually with the current installer.

Great post, and was just what I was looking for wh...

2010-10-18T10:05:45.133+01:00

Great post, and was just what I was looking for when trying to figure out how to install CrashPlan on Nexenta 3.01. I followed your instructions, but ran into some issues. Being a newbie, maybe you might have some advice. First, when running the Linux CrashPlan installer, I get the following error:

"The current version of Java, , is incompatible with CrashPlan.
Please install one of the following version of Sun Java Runtime: 1.5 1.6 1.7

The current installed version of Java is not the Sun Java Runtime Environment.
CrashPlan requires the Sun JRE.

ERROR: Failed to find an acceptable Sun Java Runtime Environment
These paths were searched: /bin /usr/bin /usr/local/bin
Would you like to download the JRE and dedicate it to CrashPlan? (y/n) [y] n

We're sorry, CrashPlan requires a valid Sun Java VM. Please install one and then
rerun this installer. Exiting."

I had already installed Sun Java 6 JDK via sudo apt-get install sun-java6-jdk. I then let CrashPlan install the JRE and swapped out the mentioned files with the Solaris versions. When trying to start the CrashPlan engine, I got the error "Java: Cannot find /lib/ld-linux.so.2." Obviously, this file isn't available on Solaris and Crashplan's engine won't start and run without it. I tried symlinking to /lib/ld.so.1, but it didn't help. Thanks for any help you could provide.

Jon, I'm already running CrashPlan under my ow...

2010-03-15T14:30:13.488Z

Jon, I'm already running CrashPlan under my own account rather than the SYSTEM account because the SYSTEM account doesn't have permission to read all the files I want to back up; also, some files are encrypted, and running the service under my account will let them be read.

But even under my account, which does have mapped network drives, the drives don't show up in the UI. Things aren't made easier by the relative lack of logging provided by the UI - e.g. access denied errors the service runs into when traversing the file system are silently swallowed, rather than raised to the user sooner or later.

CrashPlan does have a workaround for accessing map...

2010-03-15T13:54:07.903Z

CrashPlan does have a workaround for accessing mapped drives. This workaround should also work for Windows EFS:

http://support.crashplanpro.com/doku.php/recipe/back_up_windows_mapped_drives