snowboardjoe

Getting an error from CP that my system has not backed up in 5 days. Went to the console and I have an errors on the Web GUI stating, "CrashPlan PRO failed to apply an upgrade and will try again automatically in one hour". Appears the client keeps trying to do an internal upgrade and failing and has been doing this for days. It appears it will never attempt another backup until it can get past this upgrade problem.

I'm still trying to see if I can takeover my existing 11TB of data. CPPro still shows the data is there after the migration and I've been struggling to get my new client to attach to it to keep from spending days/week backing it up all over again. I went through the takeover steps, but it still wants to start over from scratch. When I first got it initialized it shows all my shares were missing and guessing this was due to the path changes (using shares instead of storage and using flash instead of boot). The instruction say to just reselect the shares (not remove the old ones), but it still insists on backing up everything all over again. Is there any way around this? Is there something I should be mapping differently to make it all work? I thought the client would have figured out that data had moved and would not back it up again.

Was starting to review steps needed to migrate to PRO and was so happy to see this thread here. A few questions, though: 1. I'm backing up 11TB and Code42 has already indicated it can't migrate anything over 5TB and will need to perform a full backup from scratch. I assume there is no need for me to migrate any data then? Or do I still need to do copy "/mnt/user/appdata/CrashPlan" to CrashPlanPRO? 2. Long ago I had to modify the code/config to avoid deduplication by CP as it bogged down multi-terabyte backups. Will I need to make that modification again with PRO? I need to find in my notes how I did this long ago. With dedupe turned on my backup never would not have finished as it was too aggressive.

OK, I got things going now. It's still in the middle of synchronizing block information and will take it awhile before I start seeing some real results. Here are some notes on my confusion and how I got things running. o Got Docker initialized fine, but it helps to read some of the unRAID information on how it works here. o Make sure you put your Docker container in the right place. o Do not use the instructions at the beginning of this thread—they're outdated as far as I can tell. o You will need the Community Applications plugin to get access to Crashplan containers (server and desktop client). o Verify you have good mappings to your devices (I had to /boot /boot to backup my flash drive). o Volume mappings will be different compared to your old CrashPlan configuration. o Add the new path(s) to your backup sets and let CrashPlan sort out the new mappings without having to back all of it up over again (don't delete any old ones even if they say they are "missing" yet). o Once you have a complete backup you can remove the "missing" entries. o Mac: To access the client you need CoRD and connect to port 3389 (don't use Remote Desktop Connection on Mac). Hope that helps some other new people.

I just upgraded to unRAID 6.0.1 this evening. The main application I need to get running again is CrashPlan. I'm new to Docker here as well. I followed the directions from the first post on this thread: docker run -d -h laffy --name=crashplan -v /mnt/user/crashplan:/config -v /mnt/user:/data -v /etc/localtime:/etc/localtime:ro -p 4242:4242 -p 4243:4243 gfjardim/crashplan Watched it install the components successfully, but then got the following error: root@laffy:~# docker logs crashplan *** Running /etc/my_init.d/config.sh... mv: cannot move '/etc/localtime.dpkg-new' to '/etc/localtime': Device or resource busy *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 57 So, I guess it's running, but not sure. My Mac client is unable to connect to it. When I fire it up after modifying ~/Library/Application Support/Crashplan/ui.properties (as I've done many times in the past for years), the client keeps going back to my local mac client. I have no idea why that's happening. Perhaps it defaults to that if it can't connect to the specified IP? I tried to review the setting in the container, but when I go to the Docker tab in unRAID interface, I don't see any screens like the screenshots I'm seeing here. So, I have no idea what is wrong here and there is very little information to go on in troubleshooting this issue. UPDATE: I removed the entire Docker configuration and started over again. This time I used from the Community plugin and got that much working. At least that much is installed properly now and the interface is working. I'm still unable to connect my Mac client though and that's baffling. Probably need to modify the starting point of this thread that those instructions will not work for a new 6.0.1 installation.