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

[ridgers]

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]

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]

Hello Jocelyn,Sorry, yes, a Synology If I understand case 310 correctly, using the mapping -v /volume1:/volume1:rw  is not valid but -v /volume1/foo:/volume1/foo:rw or -v /volume1/bar:/volume1/bar:rw is?Regards,Grant @.(647) 241-4925 Sent from an insanely great Apple productOn Nov 3, 2022, at 9:34 PM, Jocelyn Le Sage @.> wrote: 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.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[jlesage]

Yes, you are correct.

[ridgers]

No difference.

I stopped the container I removed the container I recreated the container with this command.

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/TV:/volume1/TV:rw \ -v /volume1/Movies:/volume1/Movies:rw \ -v /volume1/TV:/volume1/TV:rw \ -v /volume1/web/podcastgen/media:/volume1/web/podcastgen/media:rw \ --restart always jlesage/crashplan-pro

In the vnc interface I see the three mounted folders and all sub-folders are checked off het the 32 TB backup set is reported as 10.5 TB





On Nov 4, 2022, at 4:47 PM, Jocelyn Le Sage @.***> wrote:

Yes, you are correct.

— Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-crashplan-pro/issues/391#issuecomment-1304228478, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJDNDIYWBLSGHXT34PSALHTWGVY6TANCNFSM6AAAAAARWSZ3EQ. You are receiving this because you authored the thread.

[jlesage]

• 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]

It seems that users 1026 is my NAS user id (grant).

I can do. A recursive directory scan and see all the files I expect to bak up.

If I randomly drill into folders under manage Files, I see full sets of files for a given folder. I didn’t;t drill into every folder but I check a few.

Forcing a scan returns the same size, with only is 12054 files not sure there is significance o that.

The back up is not VMs they are all video files.

Trying t find a way to see all the files Crashplan is seeing to get to 12054 files so I can see what is excluded and drill deeper.

On Nov 4, 2022, at 6:28 PM, Jocelyn Le Sage @.***> wrote:

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 — Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-crashplan-pro/issues/391#issuecomment-1304309448, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJDNDIZLRP74RJQUYXZHOZDWGWEYHANCNFSM6AAAAAARWSZ3EQ. You are receiving this because you authored the thread.

[ridgers]

Hello Jocelyn,My issue is resolved but it does not appear to be permissions.Referencing issue 274, I added 'fs.inotify.max_user_watches=1048576' to the file /etc.defaults/sysctl.conf.Back up set is the expected size. Just waiting for it to roll through the files, matching what is already in the cloud.Thank you for being there to assit. You can close the issue.Regards,Grant @.(647) 241-4925 Sent from an insanely great Apple productOn Nov 4, 2022, at 9:57 PM, Grant Ridge @.> wrote:It seems that users 1026 is my NAS user id (grant).I can do. A recursive directory scan and see all the files I expect to bak up.If I randomly drill into folders under manage Files, I see full sets of files for a given folder. I didn’t;t drill into every folder but I check a few.Forcing a scan returns the same size, with only is 12054 files not sure there is significance o that.The back up is not VMs they are all video files.Trying t find a way to see all the files Crashplan is seeing to get to 12054 files so I can see what is excluded and drill deeper.On Nov 4, 2022, at 6:28 PM, Jocelyn Le Sage @.***> wrote:

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 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[jlesage]

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