Cloudron Forum

Closed due to inactivity Note: A lot has changed for backups, if the issue persists please open a new topic

@girish Your question got me wondering what was going on. Turns out, two apps on the volume both had caches that were insane (one due to an old uninstalled WP cache plugin that was removed, but maintained its 12 MILLION cached files, and the other was Mastodon, which needed some manual cleaning for the 800k files it had cached). Turns out there were just SO MANY folders/files that any attempt to backup or read the size would just time out. D'oh!

@doodlemania2 that's exactly what the change fixes! it won't let you save that invalid config anymore (i.e putting a bucket name in the endpoint)

@mononym said in Cleanup Backups failure: I guess the issue is in the settings then? Check Backups -> Schedule and Retention -> Configure

@jayonrails We just started on it, so will take a month probably atleast.

Fixed in 7.5.1

@necrevistonnezr how do you intergrate it in Cloudron for Backups?

I would not do this with backups for all the reasons @girish has mentioned (ie you'd have to restore the objects to standard before you'd be able to use them and this could take a while, not what you want when you need to quickly restore a backup), but what you could do if you really wanted to is to move older backups to Glacier automatically after a certain amount of time using automated lifecycle rules [image: 1676065407656-img_20230210_214239.jpg]

@eddieciou thanks. I can't really make out without logs what's going on. Do you think you can drop us a mail at support@cloudron.io ?

@jayonrails this is not implemented yet. Feature request is at https://forum.cloudron.io/topic/3818/backups-ability-to-add-multiple-storage-provider-location

So, these errors are caused by the remote server. The XML error is returned by the AWS SDK in response to some remote error. Unfortunately, there is nothing much we do on Cloudron side to fix this.

@d19dotca Yes, that sounds good. We also fixed the logs view now in 7.5 to give a history of past logs. The current one is hard to work with when debugging such things.

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

I found the issue. Fixed in https://git.cloudron.io/cloudron/box/-/commit/b2d072f2e6d3c8f1b39842c11b70f29ed2cb1231

@eddowding said in What's the fastest backup and restore method?: I have 175GB and it takes about 12h I guess something is very wrong. Yeah, my backup of about 350GB takes about 2 hours (from a Hetzner Dedicated Server in Finland Helsinki (HEL1) to a Heztner Storage Box in Falkenstein (FSN1)) IMHO your issue is very likely due to those "too good to be true" iDrive offer pricing they had which I guess you went for.

@girish said in Add Pre-Backup and Post-Backup Hooks: Seems to not make sense. That's normal for ERPs, almost all ERPs require full access to their database. This is mostly due to the Modular idea for modern ERP, which implements different DB for each module like a microservice. And communicate between with API or Functions Hooks

@girish awesome! I think what would be helpful is to test the parameters before pressing 'restore', just to validate that both the connection and decryption keys are OK. I found the error messages we have right where more confusing than helpful. I don't really know what I did wrong because to resolve it, I just took a fresh backup and restored it using the same details. All good now though.

@girish said in How to upload/import app backup in Cloudron: Can you make a feature request and link to this post? Filed it here: https://forum.cloudron.io/topic/8359/ability-to-import-backups-from-computer-disk-rather-than-needing-to-scp-files/1

yes, if the backup config has a password set, the UI will expect it to be entered before you can restore. You can use the top right menu to mark this as resolved.

@d19dotca yeah, when files move around, the modules we use for file listing is not very good at handling things. I suspect it will work fine again/tonight. I am reworking the backups code to use a different module since we have had issues with apps like owncast as well which move around files a lot.