docker-crashplan-pro
docker-crashplan-pro copied to clipboard
jlesage
After upgrade of CrashPlan container, CrashPlan runs very slow
Hi.
I love the CrashPlan container, and it has worked perfectly for over 1 year. Also the upgrade from home edition to pro.
About a week ago, the container stopped to work. I upgraded the container, and not the container is able to run. But it runs VERY slow, and it is impossible to use it. I do get e-mail reports about connection to CrashPlan server, but I have not seen any 100% completed backups yet.
What could cause such an issue?
Best regards (and a Merry Christmas) Martin
I would begin with a network speed and quality test. Then check CPU and memory allocation/weighting to the container as well as overall health of the host, e.g. CPU, swap usage and messages/syslog. Check the files in the logs folder to see if Crashplan is logging issues.
Also, note that after an CP upgrade, data is re-synchronized, meaning that a lot of I/O occurs.
On which kind of device are you running the container?
So I think had this issue you are describing . What I had done for a long time is after downloading a new version I exported the configuration, deleted the current container and and then imported the configuration. After iInoticed the slowness, I created the container using the command line interface command that I had started with. The slowness then stopped.
I only have 1 GB. I have created a new backup set, and now it backups. But the "UI" is still completely useless. So you might be right about the amount of memory. I will have to see, if I can get memory for my synology DS 412+ somewhere... Thanks.
I only have 1 GB. I have created a new backup set, and now it backups. But the "UI" is still completely useless. So you might be right about the amount of memory. I will have to see, if I can get memory for my synology DS 412+ somewhere... Thanks.
I was having similar problems. So I upgraded my memory on my ds216 II+. I went from the standard 1gig to 8gig (http://blog.fedorov.com.au/2016/02/how-to-upgrade-memory-in-synology-ds216.html).
I changed the CRASHPLAN_SRV_MAX_MEM from 1024m to 3072M.
Crashplan is running GREAT. Even while scanning the VNC interface is much, much more responsive then it used to be. Scan completes in a few minutes (300 gig). I noticed with the additional memory the CPU can to max out (98%); it never did that before.
It seems that 1GB of memory is not enough to run CP. See https://github.com/jlesage/docker-crashplan-pro/issues/82
It seems that 1GB of memory is now enough to run CP. See #82
JL - do you mean that 1GB is not enough?
I have just installed new memory in my Synology 412+ (now it has 2 GB), and the UI seems much more responsive. I have updated the container memory limit to 1GB. Now I am crossing my fingers...