Cloudron Forum

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.

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

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

@wisemetalhead whoops, I somehow missed this question. Not sure why the backup listing disappeared, I think we will have to investigate what happened using the logs. But since the backups itself are still there, you can use the CLI tool's cloudron import to restore (if needed).

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

@joesitsolutions said in Restoring app from backup?: 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: const PROTECTED_PREFIXES = [ '/boot/', '/usr/', '/bin/', '/lib/', '/root/', '/var/lib/', paths.baseDir() ]; (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.

@girish Thank's a lot

@scooke @murgero I am working on get my FreeNAS NFS mount working for the backups, but that seems to be a bit difficult to get the permissions working. If you have experience with NFS, you might have an answer on my problem here... https://forum.cloudron.io/topic/5927/cloudron-backups-on-truenas-nfs-mount/3?_=1636891033300 However thanks!

Apparently, there is a proper S3 bucket storage now. [image: 1679073227960-2a1b7338-dbca-49d7-864b-24dca54d3466-image-resized.png]

@savity I can't reproduce this. Do you see any error on the minio side?

@jdaviescoates Awesome, thanks -- I missed that.