Greetings all,
I've been pulling my hair out over this for the last couple of days since I installed 9.3, and figured asking for assistance is my next step. Hopefully it's something simple that I'm just not doing correctly!
I ended up having to do a new installation of 9.3 since the upgrade from 9.2.1.9 failed. I don't have a super complex configuration, so I figured it shouldn't be too bad or difficult to start over again, jails included. Fortunately, the pool import worked beautifully and I didn't lose any of my data! I am, however, having a problem with getting the permissions setup correctly for CrashPlan to allow me to receive backups from other machines I own. It worked great on 9.2.X, so I'm sure there's no reason I can't get it working in 9.3.
After importing the volumes and getting my main data stores back, I decided to blow out the old jails data sets that remained from my 9.2 installation so I could start anew. No problem. I was also able to install the CrashPlan plugin with no issues. Pictured below is my volume list. I have a "Backup" dataset that I use to store CrashPlan backups, TimeMachine backups, and backups from an imaging software I have been evaluating called ShadowProtect.
When I started having issues with CrashPlan not working, I cleared out the CrashPlan data set and recreated it, thinking the permissions from the import got a little hosed. Permissions for the CrashPlan data set are now set to root/wheel, and I even set everything to 777 to try to give the jail access to the data set. Eventually I will tune these permissions down once everything is working.
I created a couple of storage shares for the CrashPlan jail. One is '/media/backupFROMnas' to indicate data going out to CrashPlan's servers, and '/media/backupTOnas' for my other CrashPlan machines to store backup sets on my NAS.
Permissions to the storage shares from within the CrashPlan jail. The owner/group is root/wheel:
I kept the permissions of the CrashPlan data set as root/wheel because the CrashPlan process within the jail runs as root. I know other plugins often create non-root accounts to run as, but that doesn't seem to be the case here.
Inside the CrashPlan client (I mapped my GUI to the headless client running in the jail via SSH), I am able to select the storage share to backup my NAS data to CrashPlan's servers (/media/backupFROMnas), and it works well. It's going to take a couple of days to finish comparing data on the servers to the data on the NAS, but at least I don't have to upload 1.6TB again at 5 Mbit/sec! For the inbound backup (storage share /media/backupTOnas), I receive the error "Backup disabled - backup location is not accessible"
Under the inbound backup settings, I am pointing CrashPlan to /media/backupTOnas. The test and test1 folders are folders that I created from within the CrashPlan jail to see if I had permissions to write to the storage share. I do have permissions as root within the jail to read/write/delete data in this folder. CrashPlan doesn't think it does.
At this point, I'm not sure what to pursue next. I don't know if it's possible to run CrashPlan as a different user, and then let me create a matching user/group account in the main FreeNAS. But I figured with user/group of root/wheel in the jail matching root/wheel account in FreeNAS, that doing so probably wouldn't make much of a difference. Plus I have the permissions wide open in the CrashPlan data set.
Has anyone else seen this error, or have had a similar problem?
Thanks for taking the time to read this, and I appreciate any feedback or guidance on how I may further troubleshoot and resolve this issue.
- William
I've been pulling my hair out over this for the last couple of days since I installed 9.3, and figured asking for assistance is my next step. Hopefully it's something simple that I'm just not doing correctly!
I ended up having to do a new installation of 9.3 since the upgrade from 9.2.1.9 failed. I don't have a super complex configuration, so I figured it shouldn't be too bad or difficult to start over again, jails included. Fortunately, the pool import worked beautifully and I didn't lose any of my data! I am, however, having a problem with getting the permissions setup correctly for CrashPlan to allow me to receive backups from other machines I own. It worked great on 9.2.X, so I'm sure there's no reason I can't get it working in 9.3.
After importing the volumes and getting my main data stores back, I decided to blow out the old jails data sets that remained from my 9.2 installation so I could start anew. No problem. I was also able to install the CrashPlan plugin with no issues. Pictured below is my volume list. I have a "Backup" dataset that I use to store CrashPlan backups, TimeMachine backups, and backups from an imaging software I have been evaluating called ShadowProtect.

When I started having issues with CrashPlan not working, I cleared out the CrashPlan data set and recreated it, thinking the permissions from the import got a little hosed. Permissions for the CrashPlan data set are now set to root/wheel, and I even set everything to 777 to try to give the jail access to the data set. Eventually I will tune these permissions down once everything is working.

I created a couple of storage shares for the CrashPlan jail. One is '/media/backupFROMnas' to indicate data going out to CrashPlan's servers, and '/media/backupTOnas' for my other CrashPlan machines to store backup sets on my NAS.

Permissions to the storage shares from within the CrashPlan jail. The owner/group is root/wheel:

I kept the permissions of the CrashPlan data set as root/wheel because the CrashPlan process within the jail runs as root. I know other plugins often create non-root accounts to run as, but that doesn't seem to be the case here.

Inside the CrashPlan client (I mapped my GUI to the headless client running in the jail via SSH), I am able to select the storage share to backup my NAS data to CrashPlan's servers (/media/backupFROMnas), and it works well. It's going to take a couple of days to finish comparing data on the servers to the data on the NAS, but at least I don't have to upload 1.6TB again at 5 Mbit/sec! For the inbound backup (storage share /media/backupTOnas), I receive the error "Backup disabled - backup location is not accessible"

Under the inbound backup settings, I am pointing CrashPlan to /media/backupTOnas. The test and test1 folders are folders that I created from within the CrashPlan jail to see if I had permissions to write to the storage share. I do have permissions as root within the jail to read/write/delete data in this folder. CrashPlan doesn't think it does.


At this point, I'm not sure what to pursue next. I don't know if it's possible to run CrashPlan as a different user, and then let me create a matching user/group account in the main FreeNAS. But I figured with user/group of root/wheel in the jail matching root/wheel account in FreeNAS, that doing so probably wouldn't make much of a difference. Plus I have the permissions wide open in the CrashPlan data set.
Has anyone else seen this error, or have had a similar problem?
Thanks for taking the time to read this, and I appreciate any feedback or guidance on how I may further troubleshoot and resolve this issue.
- William