Cloudron Forum

Finally managed to get backups stable with backblaze for a ~1TB cloudron with these settings (using encryption and rsync):

Some notes:

• During initial backups, memory was by far the most common failure. The amount needed was higher than I first expected for a given upload size and concurrency. I found (upload part size) x (upload concurrency) x 4 was roughly the amount needed. i.e. (64mb)*(20)*4 = ~5120mb.
• Scheduling backups at a time when server load is low and allotting as much memory as comfortable helped stability a lot. I ended up keeping my memory limit much higher than strictly necessary. This could probably be reduced, but stability is more important to me at the moment.
• In the graph above memory tended to spike once per backup- @girish maybe this is an issue that could be optimized?
• After initial upload, the memory required for subsequent rsyncs dropped off significantly as expected
• Uploading ~1TB of data with the above took approx. 24h

Curious to see what others find from optimizing these further, but glad to have a working baseline in the mean time.

I'm also curious to see what people's monthly bills tally up to. Waiting for the first month's bill to come in but B2 seems more cost effective than Wasabi so far!

For future reference i managed to clear it up by using a slightly modified version of Girish's search command. It seems like the length limit applies to path length not just the filename length

find . -type f -print|awk '{print length($0), $0}' | sort -n

Went into the web interface and deleted / renamed files longer than 156 bytes and finally cleared trashbin/versioned files

(wipes all deleted / old versions of files - careful):

sudo -u www-data php -f /app/code/occ versions:cleanup
sudo -u www-data php -f /app/code/occ trashbin:cleanup

@robi @girish agreed it would be awesome if there was an automated way to handle this in the future

Use case-
Nextcloud updates very frequently, meaning that even if you only intend to keep 1-2 app backups at a time, you can end up with 5 or 6 due to cloudron's 3 week app update policy: https://docs.cloudron.io/backups/#retention-policy

If you have a 1tb nextcloud, this triples the storage costs / box space and adds up really quick. I think this is especially unnecessary when many people will also have a physical drive synced via the nextcloud client as a third backup.

You can delete these backups manually from your storage provider if you remember to, but it would be awesome to have an option to customize this, so people can enable automatic updates+backups of large apps in cloudron without driving too much cost.

Wondering if there are any updates on whether mastodon will be in cloudron?

Would really like to see it

@girish Ubuntu 16.04.4 LTS, ah I just spotted this article: https://docs.cloudron.io/guides/upgrade-ubuntu-20/ will try upgrading and see if the issue persists

Hey All, circling back on this after a while, I don't think it was a permissions issue after all.

I suspect the way calibre desktop and calibre-web handle capitalization is slightly different and changes stored in metadata.db are case sensitive, so when I uploaded my library folder there were for whatever reason changes to the capitalization of author names that caused the issue.

Solved this by renaming folders and files in file manager to match what the error message was expecting, for example if the "Betty Smith" folder wasn't found, I renamed lowercase "betty smith" to "Betty Smith", after which I was able to normally use calibre-web. Had to do this for ~5-10% of books which is a pain but glad to have it working again. If anyone has found a better solution eager to hear it, scanning through the library for books with missing covers was a good indicator of where the broken links were.

Funkwhale looks awesome! Hope one day we can see it or something like it in cloudron and ditch Spotify

Hey all, is there a place this info can be found if your dashboard is down and you don't have access to the system info page / update section? Need to restore but unsure what version I was on around ~apr9th (7.6.___?)