@gobenizzle This only means that the backup task was "interrupted" when a backup was in progress. The code assumes that if a backup got arbitrary interrupted (i.e not via the stop button), it is because the box code crashed. That assumption is true most of the time but you probably ran out of disk space and rebooted etc which killed the backup task.
Nothing to worry. If you trigger a new backup, it will go away.
To add to what @BrutalBirdie said, Cloudron is designed for hosting apps (and not databases as such). This means that you can't create databases separately and there is no UI to create/delete databases. It's designed for hosting your app which needs a database. The database is provisioned and updated as needed transparently as part of the app install/update/uninstall process. Very similar to heroku.
Just wanted to point that out, because Cloudron is not a classic style server management panel where one can manage "databases".
I have the .zip file. Cannot figure out why I keep getting "backupFolder path is protected"
You can only create backups to specific paths on the server. Many of the paths are "protected" to make sure that the folders won't get overwritten by updates or are used by the system. This is just a hardcoded list of paths:
(the baseDir above is /home/yellowtent/). You cannot create backups in subdirectories of the above paths.
I understand you are using restore here though and not backup 🙂 The restore logic uses the same validation logic for paths and you have copied the backup to under /home/yellowtent/. Instead, copy the backup in some path like /mnt/backups/ or /srv/backups/ and try to restore, that should work.
@nebulon : interesting about Nextcloud
I used to have 4 x Nextcloud instances in my Cloudron server (different projects). 3 of them about 10Gb of files (other smaller).
My backups were working but slow.
Even after switching to 'better' VPS provider.
So after testing Seafile for a while, I have moved 2 of the Nextcloud instances over to a single Seafile VPS (with different libraries for segregation). The other 2 Nextcloud instances will follow.
I have nothing against Nextcloud and been very happy for it for long time. But if it is really only being used for file collaboration and device syncing, and you don't actually NEED the extra facilities it provides, my personal view is that Seafile is a better solution.
So would be awesome to get Seafile onto Cloudron.
But I'm quite happy running it on a separate VPS.
To conclude this, it was a memory issue. The instance as a whole was a bit overcommited.
If the backup task is idle, it won't consume any memory. Also Cloudron does not reserve memory based on the limits set, neither for backup nor for apps. The limit is just to avoid rouge apps or the backup task to bring kill other apps.
@leggias hm getting a SIGSEGV is odd here. If you like you can enable remote SSH support and send us a mail to email@example.com mentioning your dashboard domain. Then we can take a direct look at your setup to get down to the issue.
Disk snapshots or VPS snapshots don't work well with Cloudron, since backups are per-app and not per-server on Cloudron. This is to be able to rollback/restore individual apps without interfering with the system or other apps running on it.
Still for a secondary fallback backup solution this can still be recommended.
That's what I do. I do Cloudron backups to a Hetzner Storage Box, plus pay Hetzner for their automated backups, plus occasionally do a snapshot too.
Although really I ought to backup to another provider too, to avoid the potential issues @girish once had with DO.
@robi there is a already bunch of "workarounds" for rsync. Empty directories, executable bit of files cannot be stored in most object storage. So, there is fsmetadata.json file that stores this information outside of the files. When restoring, we use that file to restore back the state. I guess we can extend that file to also save and restore timestamps.
If anyone wants this leave a note and I can look into it in the future.