![]() ![]() If you do migrate, you should know that "adoption" of one computer by another with a different filesystem does not necessarily trigger a brand-new backup - see this: Any of these approaches is very likely to remain workable post-10.x. To get automatic CP updates and avoid all the monkeying around with a headless arrangement, it seems a lot easier either to run Linux CrashPlan on Linux running in jail (e.g., VirtualBox) or run it anywhere you like outside of FreeNAS. With 9.10 I can no longer get the plugin to work, and certainly all bets are off for 10.x. The conclusion I (and others) came to was that using using the CrashPlan plugin is no longer worth the trouble. In case you haven't already seen it, see this parallel thread related to this topic: I realize you aren't complaining, I'm just mentioning it. Either accept it for what is (hard and a PITA to learn if you've never done CLI before) or simply don't use it. It's not supposed to be easy, and there is no way to make it easier. Even some FreeBSD experts said that if they were to create a server using even 1/2 the features that FreeNAS has, what you can do in 15 minutes on FreeNAS would take a BSD expert several days to implement.Īlso, jails are considered an advanced function. If you've never had to setup CIFS or NFS yourself by editing conf files, you have no way of even gauging how incredibly difficult it can be.įreeNAS is advertised as easy (and relative to doing it yourself, it is easy beyond understanding). From the FreeNAS GUI Restart the CrashPlan JailĪfter doing this you can see how the version numbers increase withĬonsidering how nearly impossible most of the forum users would be if they were told to make a FreeBSD system, keep it up to date, create a working zpool using recommended best practices, then get CIFS and NFS working and stable, FreeNAS is so turnkey it's laughable. The update may take some time, so you may want to wait a while before you continue.ġ. Unknown to me, during this time, my FreeNAS plugin decided it was going to update itself. This is where things got interesting for me. To change your backup directory, in Crashplan, go to Settings>General Tab and click the Configure button to the right of "Inbound backup from other computers" near the bottom, you can change the default backup location. When configuring your headless server, be sure to configure the directory where you want to store your backups. I was able to log in and configure the headless server. ![]() This process in incremental, that means that the crasplan plugin will restart itself many times, until reaching the latest version. Immediatly after you login the UI will exit and the crasplan plugin will start the update process. Launch the modified Crashplan UI on the desktop (my laptop). Step 8: Connect with Crashplan UI and update. Locate the Crashplan service and click restart. Restart the Crashplan service by typing services.msc into the Start Menu search box. To login to jail when no sshd is available in it you must either a) use jexec command on FreeNAS console or b) use the jail console in FreeNAS WebUI.Ī) Connect to jail. Below is an overview of the connection that lets us use another machines GUI to configure the server running inside headless jail. The jail has no user interface, only text console. To configure the Crashplan running inside a FreeNAS jail we need to use another machine that has graphical user interface. Install Crashplan Step 2 : Accept TOS Step 3 : Enable Crashplan plugin Step 4 : Create a sshd user for the Crashplan jail, enable TCP forwarding Install CrashPlan 3.6.3 on your computer you want backed up but do not log in once the installation is complete. Since the newest version of CrashPlan is actually 4.4.1, this causes an issue when trying to connect to a headless CrashPlan installation on FreeNAS.īig thanks to sirkkalap for his write up where most of this came from. It turns out that due to the fact the current version of the CrashPlan plugin, as of FreeNAS-9.3-STABLE-201511040813 is CrashPlan 3.6.3_1. After playing around and messing with it for the better part of the day I figured it out. While this is true none of these guides take into account the uniqueness of the dated FreeNAS CrashPlan plugin.Īfter following countless guides online, I was still unable to fully configure my laptop to backup to a CrashPlan installation running on my FreeNAS machine. You might be saying, there are already guides out there to do this. Just a little background on why I am even taking the time to write this. ![]()
0 Comments
Leave a Reply. |