Cloudron Forum

@perler Wow, that is a very good catch! The kind of; "huh, why have I not thought about this one before, yet it seems obvious"... As you say it, the idea comes from an instant need once in front of a specific situation which requires a solution that no one seems to have a previous need. And while reading how you describe it, in pops in mind like; "yeah, that would be master piece to be able to restore the files only, in an app as Nextcloud". So true. There could be others apps as well, but at first thought NC is the very first candidate for such desirable feature, because of the very nature of the app which holds files, and potentially team communications and email boxes as well. And this is where we can see that restoring the whole pack at once, especially for a well active NC app, could produce unexpected outcomes. Depending of course on how the app is used inside an organization. I don't think it would be a required feature for all apps. But then, if it's easier to implement as a general backup feature then why not. I would vote for this. Thanks for the heads-up.

@girish done

There is a bug in the current release that the code crashes when trying to send a notification if a backup failed. This is fixed . I think in the coming releases we can explore more notification options but atleast now you should get an email.

@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!

@scooke I went to each individual app and pointed to the fileshare with the full path "/media/fileshare/2020-07-01-0500/app_backup.tar.gz.enc" and restored those backups. As for the second part, Azure adds the following "actimeo=30" switch to the cifs share that goes in your /etc/fstab file that causes the connection to time out if the backup takes too long. Once that is removed, reboot the server and the new backups will complete without issues.

The doc actually says "The Backup Cleaner checks if entries in the database exist in the storage backend and removes stale entries from the database automatically." I will fix the progress message to match this.

@girish Ah I didn't see this until too late, sorry. I had tried to start over to a degree by destroying the current backup disk and mounting a new disk instead then clearing out the backups history and seeing if that starts working better for me. So far so good, but if the issue comes back I'll certainly send the email out and enable remote support, as I agree there seems like some odd issue for sure.

So I tried mounting the folder from the Synology NAS and then the storagebox again and everything is working fine. I have misnamed the remote directory. Sorry for the unnecessary topic.

@girish said in Delete Local Backups: Documented at https://docs.cloudron.io/backups/#old-local-backups small typo there s/snapshots/snapshot

@girish Ah, thank you. Found them. That freed up 22GB for me

Good point. I checked the services and some of them are yellow (without error, but stalled in loading). I've restarted one app that uses mongodb and now the backup works. But it's very close to the memory limit. If this happens again, I'll increase the memory assigned. Thanks for pointing it out.

@jagadeesh-s2104 Clean backup is a good idea. Thank you!

This is super helpful. I’m hoping we see something like this as a feature baked in though. Like multiple backup sources with different schedules

@scooke I tried "cleaning" but didn't make a difference. Will keep an eye on it.

Since 2022 a lot has changed for backups and will change even further with Cloudron 9. Closing this topic for now.

@WaffleUncle So you are using the Import button in the app section, correct - https://docs.cloudron.io/backups/#import-app-backup ? In your case, it looks like your backups were in the file system and not external. If that is the case, you have to fill up the 'Import Backup' dialog manually: Upload the backup app_client.xxx.tar.gz to somewhere in the server like /tmp/app_client.xxx.tar.gz. In the import UI, Choose Filesystem Put the path as /tmp/app_client.xxx.tar.gz It should import now.

@girish said in Database Access & Backups?: @sarah-white Good, was just checking since your comment got flagged as spam by the forum. Sounds much like replies produced by asking ChatGPT to me!

This was indeed a bug. Fixed in https://git.cloudron.io/cloudron/box/-/commit/2434e813836e7837162c1798794d04655227d9cf . Thanks a lot @avatar1024 . It will be part of 7.1.2

I have clarified the text a bit more now.