search

jlesage / docker-crashplan-pro

Docker container for CrashPlan PRO (aka CrashPlan for Small Business)
MIT License
301 stars 38 forks source link

My Synology Is Overwhelmed #321

Open RobKnollstech opened 3 years ago

RobKnollstech commented 3 years ago

Hoping you can help me with settings to keep from overwhelming my Synology DS920+. Running crashplan-pro on Docker, two of my disks are almost constantly near 98-99% Drive Utilization and Drive Read Latency is often 2-3 seconds. Since I have almost 2M files I'm backing up (mostly already backed up and static), I increased the Inotify Watch Limit to around 1.9M. FYI, Synology blames me running 12G RAM ... but since I stopped the contained running crashplan-pro, Drive Latency has dropped to 50-250 ms. If there anything I can do to fix this or am I doomed to overload my Synology? Thanks.

jlesage commented 3 years ago

What CrashPlan is doing during that time ? The initial file scan/sync can use a lot of ressources, but this should be temporary.

Thro42 commented 3 years ago

I have the same issue. Since 20 days the container has near 98-99% Drive Utilization. I can not login into consol of the container. Code42 says "no activity since 50 days" :-(

madfusker commented 3 years ago

Make sure the container is up to date with the latest pull. I haven't seen any of these issues with my QNAP NAS docker container with a 4TB backup. I am running a TVS-872XT with 16GB of RAM.

Thro42 commented 3 years ago

I install the Conainer new befor is start the current test. image It is hard tu access my Synology. It is a DS415+ 2GB RAM and i try to backup 3TB

Thro42 commented 3 years ago

some additional information. It appears that the container keeps restarting while it is scanning the file information. In the Log i found this.

02/11/2021 15:09:12 idle keyboard:   turning X autorepeat back on.
[CrashPlanEngine] starting...
02/11/2021 15:36:24 active keyboard: waiting until all keys are up. key_down=37 Control_L.  If the key is inaccessible via keyboard, consider 'x11vnc -R clear_all'
02/11/2021 15:36:26 active keyboard: turning X autorepeat off.
02/11/2021 15:41:25 idle keyboard:   turning X autorepeat back on.
[CrashPlanEngine] starting...
02/11/2021 16:03:10 active keyboard: waiting until all keys are up. key_down=37 Control_L.  If the key is inaccessible via keyboard, consider 'x11vnc -R clear_all'

Alsoin the "log" Folder are many files like "restart.2021-11-02_15.56.30.log" Insite I see 

Tue Nov  2 15:56:32 UTC 2021 : /usr/local/crashplan/bin/restartLinux.sh
Tue Nov  2 15:56:32 UTC 2021 : Stopping CrashPlan Engine ... 
Tue Nov  2 15:56:54 UTC 2021 : Still running, killing PID=11303 ... 
Tue Nov  2 15:56:56 UTC 2021 : OK
Tue Nov  2 15:56:56 UTC 2021 : Waiting for CrashPlan Engine to be restarted automatically ...
Tue Nov  2 15:56:59 UTC 2021 : New CrashPlan Engine process started with PID 12454
Tue Nov  2 15:56:59 UTC 2021 : Exiting restart script