When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. I changed my port mappings for one of my 2 dockers of cloud berry to I could run them at the same time, and about a week or so later, fix common problems complained about this:ĭocker Application Backup_Remote, Container Port 43210 not found or changed on installed application So far so good, I have been running a very large backup (87 GB) with many large files for over 3 hours without stalling. Personally I am using 3 threads, 100mb chunk and 700mb RAM allocated. The formula to calculate the minimum RAM allocation is But you also need to make sure that CloudBerry has enough RAM assigned to support the number of worker threads and chunk size. I read somewhere that Backblaze B2 stores in 100mb chunks or blocks and the recommendation was to try and match the incoming "chunk size" from Coudberry to that of Backblaze. I have since been tweaking the options under the advanced settings. It seems to happen with very large files over 1GB (home video archives). I was hoping this recent update would fix it but my backup stalled again this morning.
Yea my backups to B2 seem to randomly stop as well. The update crashed the docker, so had to reinstall the cloudberry docker, but it works fine now.Įdit: the backup stops after some time, is that just a bug for me or does it happens for others too Im looking at B2 for cold storage too, not as crazy pricing as Amazon S3/glacier.
0 kommentar(er)
