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]
@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.
@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 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.
@opensourced you can update to 7.3.2 which has the fix for this. Settings -> Check For Updates. It will say Unstable but it should be stable (there are a few bugs outstanding but nothing major).
@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!
@nebulon said in Confused about a failed backup being listed in backups:
@jdaviescoates if you hover over the 5 hours ago you should see the exact time to validate this.
It shows 05:54:18 so I guess your theory was correct given the logs I pasted above about the failed backup show 04:00:01 - thanks!
