January 12, 20179 yr I dont think so. How would I check this? Im pretty new to unraid On the Dashboard near the bottom left is a line that shows how full flash / log / docker is. Or go to Tools - Diagnostics and post complete diagnostics zip.
January 12, 20179 yr I dont think so. How would I check this? Im pretty new to unraid On the Dashboard near the bottom left is a line that shows how full flash / log / docker is. Or go to Tools - Diagnostics and post complete diagnostics zip. I got it figured out I deleted docker.img and added all my containers. Crashplan is working great now! Thanks for the help!
January 12, 20179 yr I dont think so. How would I check this? Im pretty new to unraid On the Dashboard near the bottom left is a line that shows how full flash / log / docker is. Or go to Tools - Diagnostics and post complete diagnostics zip. I got it figured out I deleted docker.img and added all my containers. Crashplan is working great now! Thanks for the help! Maybe only temporary unless you figure out how you filled it up and fix that. See the Docker FAQ sticky.
January 24, 20179 yr Newbie here, please go easy on me. What is the best way to backup my unraid server using crashplan? I am looking to save the configuration, VMs, appdata, basically everything unraid except the shares which I am already backing up using a different utility. I am looking for a complete backup solution, example: if there is a fire and the hardware is all melted, what folders/data will i need to rebuild and restore my server? The folders I see in the Crashplan UI are Backup Config Core Data Home Lib64 media mnt ( This is all the disks and shares) nobody root run unassigned Thanks for your help..
January 25, 20179 yr If all the hardware is melted there is nothing to restore.. Your data is what you should backup If you area allready doing that then just install the Community Applications plugin and backup your dockers and VM's from there..
January 28, 20179 yr I have CrashPlan set to autorun upon startup but it remains off and I have to turn it on manually, any idea on why that is? It starts up automatically when I start the array manually, but not when the array is automatically started from a reboot.
January 30, 20179 yr I've just setup the Docker on 6.2.4. I'm processing one of my shares for backup to the cloud service which is 229GB. It's currently stick on "connecting to backup destination". Anyone have any ideas what this might be? Cheers Michael
February 4, 20179 yr I'm running into the same issues that Michaelrwjenkins is describing. Tried solving it by using the code42 documentation of crashplan, but could not get it resolved. Any and all suggestions are greatly appreciated!
February 4, 20179 yr Doublecheck in settings - network if you have the correct interfaces selected.. You can just select them all.. If all else fails repeatedly press "retry" to connect... It does this with me sometimes.. In the end it always connects btw.. always..
February 5, 20179 yr Doublecheck in settings - network if you have the correct interfaces selected.. You can just select them all.. If all else fails repeatedly press "retry" to connect... It does this with me sometimes.. In the end it always connects btw.. always.. Cheers, I did indeed retry like 20 some times and it decided to work
February 5, 20179 yr Do you use network bonding in unraid ? Maybe its ties into that somehow.. Verzonden vanaf mijn iPhone met Tapatalk
February 6, 20179 yr Do you use network bonding in unraid ? Maybe its ties into that somehow.. Verzonden vanaf mijn iPhone met Tapatalk I do not, so that's not it. In a few weeks when I upgrade my network capacity I will, if anything comes up I'll report back. As for now, still not sure what caused it, it's been running fine even after reboots ever since it connected properly.
February 6, 20179 yr Do you use network bonding in unraid ? Maybe its ties into that somehow.. Verzonden vanaf mijn iPhone met Tapatalk I do not, so that's not it. In a few weeks when I upgrade my network capacity I will, if anything comes up I'll report back. As for now, still not sure what caused it, it's been running fine even after reboots ever since it connected properly. Same here...If you do not touch it in the end it will start to function again on its own also..
February 6, 20179 yr This has been asked several times and I don't see any answer. Autostart doesn't work with Crashplan. Logs point to this: openbox-xdg-autostart requires PyXDG to be installed What needs to be done to fix this?
February 6, 20179 yr autostart works fine here.. Hmm. Well why would some people have the same issue with the same error? I don't know of a way to add that package. Sent from my iPad using Tapatalk
February 7, 20179 yr My appologies.. I think I misunderstood "autostart".. I thought you meant that the crahsplan docker did not auto-start.. In retrospect I see this is some kind of other package that I have no idea of what it is..
February 7, 20179 yr My appologies.. I think I misunderstood "autostart".. I thought you meant that the crahsplan docker did not auto-start.. In retrospect I see this is some kind of other package that I have no idea of what it is.. No, you were correct. For me and at least a few others in the thread, Crashplan won't autostart in the docker. It throws that error every time. However starting it manually works every time.
February 8, 20179 yr Add me to the list of people who the Crashplan docker will not auto start. After a server reboot, all of my dockers come up except Crashplan which fails with the error: ERROR: openbox-xdg-autostart requires PyXDG to be installed Manually starting or restarting it works just fine though. Annoying that I have to go manually start it every time the server is rebooted (so far only for UnRAID updates at least)
February 10, 20179 yr Chiming in here as well. No auto-starting the docker. Works perfectly if I start it manually though.
February 10, 20179 yr Just tested.. auto-starts fine... You've already said that so you're one of the lucky ones. Can we get the developer to chime in here or do we need to reach out on GitHub? Sent from my iPad using Tapatalk
February 10, 20179 yr Just tested.. auto-starts fine... You've already said that so you're one of the lucky ones. Can we get the developer to chime in here or do we need to reach out on GitHub? Sent from my iPad using Tapatalk I wanted to be sure.. I might have thought it worked when it didn't... If it the docker itself that does not start then support should be in here.. If it is crashplan itself that is nog starting to backup, then it might be crashplan and/or github...
February 12, 20179 yr I was wondering why you have this step for new installs in post #1 when you already have /mnt/user mapping in by default as the "Backup Source" | "unRAID Share Path"? Map /data (or /mnt) on the container side to /mnt on the host side. Note that whatever path you input on the container side will be the path you access from within the CrashPlan app. If /mnt mapping in to the container should always be included, why don't you simply have this as another default mapping just like you do for "Backup Source" | "unRAID Share Path"? I was a bit confused why I would need to map /data (container) or /mnt (container) to /mnt (host) and how that would work. I see now that if I map /mnt (container) to /mnt (host) I simply get the entire directory tree for /mnt (host) available under /mnt (container) instead of just /mnt/user (host) mapped in to the container side. Is there any danger to adding /mnt to the container and mapping it to /mnt (host) as I've explained above or should I always map /data (container) to /mnt (host)?
February 12, 20179 yr I was previously having the autostart issue, the following workaround has temporarily resolved it for me: 1. SSH into unRAID as root. 2. Determine the container ID docker ps -aqf "name=CrashPlan" 3. This will return a string. 3a. Run the following: docker update --restart=always containerID Hopefully this helps someone else who is having this issue. Kudos to the developer of this great docker, hopefully we can find a more permanent solution to this annoying but minor bug.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.