gfjardim

[CONTAINER] CrashPlan & CrashPlan-Desktop

Recommended Posts

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.

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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..

Share this post


Link to post
Share on other sites

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..

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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?

 

unraid.png

 

Cheers

Michael

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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..

Share this post


Link to post
Share on other sites

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 :)

Share this post


Link to post
Share on other sites

Do you use network bonding in unraid ? Maybe its ties into that somehow..

 

 

Verzonden vanaf mijn iPhone met Tapatalk

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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..

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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..

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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)

Share this post


Link to post
Share on other sites

Chiming in here as well.

 

No auto-starting the docker.  Works perfectly if I start it manually though.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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...

Share this post


Link to post
Share on other sites

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)?

Share this post


Link to post
Share on other sites

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.

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.