Welcome to Drobo Forums!(Login — Register)
To start connecting with other customers, experts, and developers in the Drobo community, please login or register for a Drobo Forums account now. To search for answers without registering, visit the knowledge base.

Welcome to Drobo Forums!Our forums will be updated in the near future and are currently in a read-only state. Check back again soon!

You have come to the right place to connect with other users and experts in the Drobo community to get advice and share ideas. Check out our newly-revised knowledge base at http://myproducts.drobo.com/articles and visit Drobo's Technical Support site at www.drobo.com/support for the latest support information.

(04-08-2014 10:53 AM)diamondsw Wrote: The simplest way by far to add more swap space is just to create another swap file; editing the init scripts will be overwritten every time you update the firmware. Taking ricardo's advice in another thread, I whipped up a psuedo DroboApp that simply allocates and activates another GB of swap.

On each of these, you can skip the packaging sections and go straight to installation.

Once you have the DroboApps installed, you need a way to connect the Crashplan GUI on your computer to the Crashplan engine on the Drobo. The only way to do that is via an SSH tunnel, which means another DroboPort - OpenSSH.http://www.droboports.com/app-repository/openssh-6-2p2

I believe it will work out of the box, but configuring users, login, paths, etc - well outside of what I can cover here. Once SSH is working, you need to open a port forward like so:

Code:

ssh -L 4200:localhost:4243 <drobo-ip>

Finally, you need to edit the ui.properties file inside the Crashplan client (location varies by platform) and add the following line:

Code:

servicePort=4200

So, here's what happens...

Crashplan on the Drobo launches via Java 7, and the locale package provides international character support. It can perform backups unattended, but at first will be waiting for a connection from a GUI to configure it.

The SSH tunnel opens a connection from the local computer on port 4200, to your Drobo on port 4243. This means anything you send to port 4200 will be forwarded to the Crashplan engine on the Drobo.

With the edited ui.properties file, the Crashplan client on your computer will connect to port 4200 - which is effectively the copy of Crashplan engine on the Drobo.

You've seen the recent discussions of memory usage. Once you get this working, you'll probably want to load the swap DroboApp I posted a few posts back. This will give your Drobo a much larger working space and avoid (hopefully) some of the out-of-memory problems that plague Crashplan.

On each of these, you can skip the packaging sections and go straight to installation.

Once you have the DroboApps installed, you need a way to connect the Crashplan GUI on your computer to the Crashplan engine on the Drobo. The only way to do that is via an SSH tunnel, which means another DroboPort - OpenSSH.http://www.droboports.com/app-repository/openssh-6-2p2

I believe it will work out of the box, but configuring users, login, paths, etc - well outside of what I can cover here. Once SSH is working, you need to open a port forward like so:

Code:

ssh -L 4200:localhost:4243 <drobo-ip>

Finally, you need to edit the ui.properties file inside the Crashplan client (location varies by platform) and add the following line:

Code:

servicePort=4200

So, here's what happens...

Crashplan on the Drobo launches via Java 7, and the locale package provides international character support. It can perform backups unattended, but at first will be waiting for a connection from a GUI to configure it.

The SSH tunnel opens a connection from the local computer on port 4200, to your Drobo on port 4243. This means anything you send to port 4200 will be forwarded to the Crashplan engine on the Drobo.

With the edited ui.properties file, the Crashplan client on your computer will connect to port 4200 - which is effectively the copy of Crashplan engine on the Drobo.

You've seen the recent discussions of memory usage. Once you get this working, you'll probably want to load the swap DroboApp I posted a few posts back. This will give your Drobo a much larger working space and avoid (hopefully) some of the out-of-memory problems that plague Crashplan.

Thank you SO much for this. I'm going to be following these instructions this weekend hopefully and finally get crashplan up on my 5N. The other data backup services offered through drobo apps are insanely expensive comparatively, and I've been waiting for crashplan support for what seems like ever.

I am having trouble with my Crashplan. The original install worked fine but once I tried to connect to Crashplan Online it wanted to update the install. Now the update is failing and crash plan will not run/update on the Drobo 5N. Has anyone had this problem? Anyone know how to fix?

Noob question here.
In the install directions it talks of setting up a port from my laptop to the Drobo5N?
Does this mean that Crashplan on the Drobo doesn't actually backup from the Drobo directly? Does it need a desktop/laptop to be on for it to work?
Thanks.

I followed these instructions, and even installed that swap app that you posted, but I get to about a TB and a half into scanning the files for backup, and I get the error message "CrashPlan has been disconnected from the backup engine."

I also installed crashplan from the link you posted, but now on my drobo dashboard it's saying there is an update available. I'm going to guess with the issues that people have had, updating this would be a bad idea.

Any clue as to how I can find out what's going on?

EDIT: So I decided to upgrade, and I'm getting this new prompt to set a password for the archive, which, when I try to do, automatically disconnects me from the service. Once it scans the files on the CP server, and begins to scan what's on the Drobo itself, the app crashes, and it disconnects me.

This may be a memory issue. CP recommends roughly 1GB of memory per TB of data, so I changed the count=1k in that swap app to count=3k, as I have roughly 3TB of data. On top of the on-board 880MB, I think that should do the trick. I will update. One question about this, do I also need to change the bs=1M to bs=3M?

This is a moderated community forum for informational purposes only, and may contain typographical errors, technical inaccuracies, and information about configurations which are not officially supported by Drobo, Inc. The content is provided as is, without express or implied warranties of any kind.

This is not a complaint forum. For technical issues related to Drobo products, please visit us on the web at: www.drobo.com/support/contact-support/. Any opinions, comments, solutions or other commentary expressed on this blog are not officially endorsed or recommended by Drobo.

If any of the Administrators or Moderators feel that your post is considered inappropriate for this forum -- we reserve the right to delete or edit as we see fit.