Why hasn't anyone updated the CrashPlan plugin?

[jadz]

I am in the same boat as many people who use CrashPlan on FreeNAS where CrashPlan upgrades periodically and breaks.

I believe the current accepted method for new users or for users who have a broken environment and want to re-build from scratch is to use the older plugin, and then try to get CrashPlan to auto-upgrade, fixing the things that break during the upgrade procedure.

I don't know much about creating PBI, so I'm wondering if there is a reason that someone hasn't updated the CrashPlan PBI? Alternatively, I'm wondering if it might be easier to have an install guide that would walk users through the CrashPlan linux installer instead of using the PBI?

I'm willing to do some research into either of these two methods, but I wanted to ensure that I wasn't wasting my limited time if there was some good reason that no one else has done this.

 

[Robert Trevellyan]

I don't know the answer to your main question, but I'm pretty sure plugins in their current form will be obsolete in version 10, so that might be a factor.

 

[Paul W.]

Can you comment on the nature of the system that will take the place of the plugin? Will it potentially be a little easier to install an maintain vs. the current non-functional Crashplan implementation? My freenas box was purchased via primary spousal approval in order that it back up our burgeoning picture collection... which it's not currently doing :).

 

[depasseg]

It should support linux which is a little better supported by crashplan. But honestly, the issues are because of crashplan. They make it incredibly difficult to run headless and on freebsd. Go to the Crashplan support site and vote for an official freenas plugin from them.

 

[Robert Trevellyan]

Can you comment on the nature of the system that will take the place of the plugin?

http://www.freenas.org/whats-new/2015/10/announcing-freenas-10-alpha.html

 

[Paul W.]

Fabulous. Will be looking forward to it.

 

[jadz]

Fabulous. Will be looking forward to it.

This doesn't mean there will be a new CrashPlan plugin. It means that the plugin environment is changing. It may mean that we lose the existing plugin if no one updates it.