Cloudron Forum

@girish said in Easy 3-2-1 Data Storage Plan with Cloudron: I really would like to use another Cloudron as an encrypted off-site backup destination Can’t recommend restic with e.g. OneDrive (which you might have 1 TB anyway of if you have a M365 subscription…) for this enough. End-to-end encrypted, fast, browsable with e.g. restoc-browser….

I try to avoid puttting screenshots in our docs because they become obsolete in 6 months. Given the amount of 3rd party services we integrate with, it's impossible for us to track UI changes across all the services. I just link to the docs like in https://docs.cloudron.io/backups/#linode-object-storage If something is really super popular, I make a "guide" with screenshots.

So is this then fixed by now with getting unbound back alive?

@nebulon Thank you for your reply. In the instructions it says that first you have to run the command cd /home/mastodon/live aws s3 sync --acl public-read public/system/ s3://instance-media --endpoint=https://s3.fr-par.scw.cloud To synchronize local data, cache Mastodon media to the S3 bucket. I guess that would have to be a different command here on Cloudron. Now my images load, but the local avatars, server image have disappeared from the instance and the remote images and avatars are not loading. Is it possible that the remote images will load gradually, I don't know. I've been really struggling with this for a few days now and the result is still not good.

@robi On that, I don't have the data or experience to talk. But 100% sure you can't use wasabi latency, I think smb or better NFS should be a better option, but I'm not an expert. and Using so much ram for it, im not big fun about it, but I would have to try it before to have a real feedback

@jdaviescoates said in Backing up multiple Cloudrons to the same backup destination?: And just to be double clear, having different prefixs results in different paths, right? yes!

@stvslkt What is the endpoint URL you are entering? It should be like https://s3.us-west-002.backblazeb2.com or just s3.us-west-002.backblazeb2.com.

@girish said in Backup size: Thanks, I deleted files in the Nextcloud recycle bin. Now, after a reboot, Cloudron System Info shows 4.3 GB for the Nextcloud instance. (I had to delete the nginx config of a stopped app to get the system to reboot.) Thanks, I'll keep both folders. I have no particular goal to remove Discourse or its backups. I measured /var/backups size by adding up the three separate folders that FileZilla showed me, but I now understand that some files are hardlinks. And the Backup data shows only 4.87 GB now, so my disk is small enough for me to move on. Thank you!

@girish that worked. Thanks