Anything in /var/log/crashplan/engine_error.log?
/etc/host.conf: line 2: bad command `hosts' /etc/host.conf: line 3: bad command `dns'
I don't use the Crashplan plugin as I feel it's quite unbaked and since it's headless it sort of defies the point of a GUI system.
Instead I just install Crashplan on a PC (or Mac if you prefer) and then just create a Crashplan directory there.
Now create a symlink to your FreeNAS folders and they will be eligible in your Crashplan system.
On Windows 7/8/10 you could do as admin: "mklink /D c:\Users\[You]\Crashplan //freenasname/Media"
And that would create a link and local install of Crashplan would let you pick your folders (sic, datasets) to include in backup.
2TB... that is just pictures and home videos (small GB) lol... movies etc. not in the back up :) My wife loves her digital pictures...Yes, 2 TB is quite a lot to process and would take well, more than 24 hours which is the normal frequency to run.
This is why I don't backup TV Shows, or Movies. I do strictly Documents (MB), Home Videos (small GB), and Pictures (small GB). If I added in Movies and TV Shows I'd be in TB and in same boat.
Anyway, you can select the Files in Crashplan and each time you make a change it will re-scan your backup targeted folders.
Morten:~ solvstrom$ ssh -L 4200:localhost:4243 crashplan@crashplan_1 -Nv OpenSSH_6.9p1, LibreSSL 2.1.8 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 21: Applying options for * ssh: Could not resolve hostname crashplan_1: nodename nor servname provided, or not known Morten:~ solvstrom$
When I enter the above into shell, I get this:Code (text):
- $ jexec crashplan_1 /bin/tcsh
Code:/etc/host.conf: line 2: bad command `hosts' /etc/host.conf: line 3: bad command `dns'
debug1: Connection to port 4200 forwarding to localhost port 4243 requested. debug1: channel 2: new [direct-tcpip]
I am also having these errors show up in my /etc/host.conf file. The SSH tunnel connects and asks for my password. Once connected and I launch the MacOS CrashPlan GUI, the tunnel reports:
Code:debug1: Connection to port 4200 forwarding to localhost port 4243 requested. debug1: channel 2: new [direct-tcpip]
However the CrashPlan GUI gives me an "Unable to connect, check your network" when trying to enter my CrashPlan credentials or creating a new account.
Step 1 - Stop Crashplan on Windows Machine close any open windows and all services (Ctrl+Alt+Delete) close all services relating to crashplan. Step 2 - Logon to FreeNas server, click on jails, select CrashPlan select Shell then Stop the crashplan service by typing service crashplan stop (followed by enter) Step 3 - ee /var/lib/crashplan/.ui_info (hit enter) (copy key it should look something like :4243,[random characters],127.0.0.1) Step 4 - On the windows side go to the C:\ProgramData\CrashPlan\ and open the ".ui_info" file. paste info from Step 3, but change the 127.0.0.1 to the ip address for your Crashplan jail, mine for example is 192.168.1.2 save and close (I also made this file read only so the system can't change it - but not necessary, you would however have to edit this file from time to time when you don't connect as it for some reason gets changed). Step 5 - Back in the shell on the freenas side type "service crashplan start" Step 6 - Still in the shell type "sockstat -l" and verify to be sure you have port 4243 listening. Step 7 - Verify my.service.xml is setup correct. Step 8 - Launch CrashPlan in windows - it should connect now.
# quit any running instance of crashplan the java gui cd ~/Library/Application\ Support/CrashPlan mv .ui_info .ui_info.local # insert your gid into next line (cb8b1...) echo "4200,c8b1d4c8-4e23-4ef8-a43c-253b011fc405,127.0.0.1" > .ui_info echo "port=4200" >> ui.properties # in another terminal ssh -L 4200:127.0.0.1:4243 crashplan@crashplan_1 -N -v -v # open ~/Applications/CrashPlan.app
So, I just checked my error log and that is still in there. However everything is working just fine (as far as I can tell anyway, the GUI connects and I am 100% backed up with no error or other events in the history tab).
You state that you are using the SSH tunnel above - I don't think anyone (or very few people anyway) are using that. Most modify the .ui_info file on the host maching and change the port to match the port in the .ui_info file on the server machine so that it connects directly. I do anyway, and my reasoning is that my desktop with the GUI and the server are both behind a firewall anyway and the SSH tunnel really isn't needed (plus I never could get it to work).
Incase you want to connect directly, these are the steps I used last time to setup crash plan.
Code:Step 1 - Stop Crashplan on Windows Machine close any open windows and all services (Ctrl+Alt+Delete) close all services relating to crashplan. Step 2 - Logon to FreeNas server, click on jails, select CrashPlan select Shell then Stop the crashplan service by typing service crashplan stop (followed by enter) Step 3 - ee /var/lib/crashplan/.ui_info (hit enter) (copy key it should look something like :4243,[random characters],127.0.0.1) Step 4 - On the windows side go to the C:\ProgramData\CrashPlan\ and open the ".ui_info" file. paste info from Step 3, but change the 127.0.0.1 to the ip address for your Crashplan jail, mine for example is 192.168.1.2 save and close (I also made this file read only so the system can't change it - but not necessary, you would however have to edit this file from time to time when you don't connect as it for some reason gets changed). Step 5 - Back in the shell on the freenas side type "service crashplan start" Step 6 - Still in the shell type "sockstat -l" and verify to be sure you have port 4243 listening. Step 7 - Verify my.service.xml is setup correct. Step 8 - Launch CrashPlan in windows - it should connect now.
root java 92184 98 tcp4 *:4242 *:* root java 92184 99 tcp4 127.0.0.1:4243 *:*