Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Stopped apps not getting backed up, is this intentional?

  • Hello,

    I have one app which serves as my new WordPress template to clone from for new clients and such. I leave it "stopped" since it's never really needed to run unless I'm making further changes to it and then I stop it again once I've made those changes. I noticed that even though it's set to automatically backup, it doesn't happen whenever it's stopped, only when it's running.

    Is this a defect or is this intentional? If intentional, I think this needs to be added to the documentation and perhaps the UI as well so that a user knows when it's stopped that backups will not be taken of the app even when set to auto-backup. That should probably be on the app interface as well as the Backups interface where it lists apps setup to not auto-backup, perhaps it could include stopped apps.

    And if this is a defect then hopefully this will be fixed in the near future. 🙂


  • @d19dotca I guess it must be a defect or recent change as in the UI (just above the stop button) it says:

    "Start / Stop

    "Apps can be stopped to conserve server resources. They will continue to be backed up but won't be updated."

  • @jdaviescoates Good catch! Yes, indeed it looks like a defect in that case. I hope this can be fixed in the next release, as I think most fo us consider backups to be a critical part of the infrastructure.

  • Staff

    Nothing has changed in behavior or code afaik. Let me check tomorrow if something is broken here.

  • @girish Yes, that'd be perfect. Thank you. If it's not a defect for anyone else, then I guess I'm alone for some reason. haha. I could use your help either way though, so if you want remote access just let me know. I can say that my backups are scheduled to run every 6 hours and are successful as I can see all the backups on all other apps that are running. But the stopped app so far today still has the latest backup as "yesterday", and that was a manual one I took. There's basically been no backups on it at all that were auto-created.

  • @d19dotca @girish I can confirm that my stopped apps don't appear to be getting backed up either.

  • Staff

    I forgot to update this topic yesterday. Yes, I can reproduce this myself as well. Looking into if this is a UI regression or something in the backend. It's most likely a UI issue, because we have not intentionally changed anything on this part of code.

  • Staff

    @d19dotca @jdaviescoates This was indeed a regression. And one that would have bit us hard when we update to Focal (since we rely on backups to upgrade). Thanks for reporting, I have made a fix for the next release. From what I can make out, it's been broken since 5.0 (so past 3 months or so).

    In the meantime, you can apply this yourself if you like, it's a one-liner (just remove the === apps.HEALTH_HEALTHY part) in /home/yellowtent/box/src/backups.js and then systemctl restart box.

  • @girish I'm not sure what Focal is, but you're welcome I guess? haha. Thanks for fixing it so quickly! 🙂

  • Staff

    @d19dotca that's the new Ubuntu LTS release. Usually it brings in new db versions. To migrate automatically to new db versions, we work with db dump files that are created as part of the backup flow

Log in to reply