search

jlesage / docker-crashplan-pro

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

Backup runs terribly slow #318

Open nk111 opened 3 years ago

nk111 commented 3 years ago

I had issues after upgrading the container image. My /volume1 mount was gone and so nothing was selected for backup. The web interface showed me all my files as "deleted".

Then I remembered that I created the initial container with docker compose which included the /volume1 mount command. So I re-created the container using the same docker compose command. Now my /volume1 mapping was there again but the backup told me that it had to backup everything from scratch. In my case that's about 1.4TB.

The first 220GB were completed within a few hours yesterday and the estimated time to complete was about 2 days. But then it suddenly turned extremely slow. It almost doesn't show any progress anymore. Single files take ages to complete. The estimated time for the remaining 1.1TB is 6.6 MONTHS!

I tried to pause and resume and even restarted the container. No success.

Any ideas what could be the reason?

I'm running a DS218+ with 10GB of memory. The CRASHPLAN_SRV_MAX_MEM is set to 3G The crashplan docker image is the latest available. The container runs at 25% CPU and 1.75GB memory atm.

jlesage commented 3 years ago

Has the time estimate improved ? Normally, since all your data is already in the cloud, CrashPlan should not re-upload anything... but it will figure this out while going through you data. I would not be too concerned about this estimate.

jlesage commented 3 years ago

Also, note that mapping /volume1 to the container no longer works properly with recent Synology version. See https://github.com/jlesage/docker-crashplan-pro/issues/310.