![]() I figured something was wrong with the permissions, so I completely erased the CrashPlan dataset and started fresh. Unfortunately I couldn't get CrashPlan in 9.3 to write to the aforementioned dataset (giving the "Backup disabled - backup location is not accessible" error). I was hoping that I could "resume" the incoming backups just as you do when you re-install CrashPlan and want to adopt an existing backup. I originally had some data from incoming backups in the /mnt/XenonNAS/Backup/CrashPlan dataset from my previous installation of 9.2.1.9 along with CrashPlan running in a jail. 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. I was also able to install the CrashPlan plugin with no issues. It worked great on 9.2.X, so I'm sure there's no reason I can't get it working in 9.3.Īfter 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. 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. 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. I ended up having to do a new installation of 9.3 since the upgrade from 9.2.1.9 failed. Hopefully it's something simple that I'm just not doing correctly! ![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |