Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Back Up Set missing 2/3 of the data after an update #391

Open
ridgers opened this issue Nov 3, 2022 · 8 comments
Open

Back Up Set missing 2/3 of the data after an update #391

ridgers opened this issue Nov 3, 2022 · 8 comments

Comments

@ridgers
Copy link

ridgers commented Nov 3, 2022

Hello,

I have a 32TB back ups et on CrashPlan

After recently updating the docker, the application now tells me my backup set is 10TB not 32TB.

I can't understand what I did wrong when I last updated. When I review the folders on the volume I want backed up they are all check as they were before.

Here's the start up command used for the docker.

sudo docker run -d --name=crashplan-pro -e USER_ID=1026 -e GROUP_ID=101 -e CRASHPLAN_SRV_MAX_MEM=16G -e SECURE_CONNECTION=0 -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1:/volume1:rw --restart always jlesage/crashplan-pro

@jlesage
Copy link
Owner

jlesage commented Nov 4, 2022

I'm assuming you are running the container on a Synology NAS. Note that mapping /volume1 directly to the container no longer works properly. See #310. I would first try to fix that and see if it helps.

@ridgers
Copy link
Author

ridgers commented Nov 4, 2022 via email

@jlesage
Copy link
Owner

jlesage commented Nov 4, 2022

Yes, you are correct.

@ridgers
Copy link
Author

ridgers commented Nov 4, 2022 via email

@jlesage
Copy link
Owner

jlesage commented Nov 4, 2022

  • Is it possible that some files have incorrect permission that prevent the user/group 1026/101 to read them ?
  • Are you able to identify the missing files ? You can click on Manage Files and dig into folders.
  • You could try to force a files scan: click 4 times on the code42 logo, then enter the backup.scan command.
  • Does your backup include some VM images, or artifact of other backup systems ? CrashPlan ofter update their exclusion list and maybe the last update affected your files. See https://support.crashplan.com/hc/en-us/articles/8864842960909

@ridgers
Copy link
Author

ridgers commented Nov 5, 2022 via email

@ridgers
Copy link
Author

ridgers commented Nov 5, 2022 via email

@jlesage
Copy link
Owner

jlesage commented Nov 7, 2022

Usually the lack of inotify watches doesn't prevent CrashPlan from seeing all the files... But great if it's now working for you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants