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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Ability to create custom backup retention schedule presets

    Feature Requests
    3
    5
    179
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • robi
      robi last edited by

      Please allow to enter an own retention schedule and not only their few presets. Or if easier, at least add a few more that make sense, which are not covered.

      Such as keeping...

      • Yearly's for X years, monthly per year, daily per month
      • Half-yearly's for X years, bi-weekly per Y months, daily per Z days.

      I found this to be common practice in various companies I was working in.

      Life of Advanced Technology

      ruihildt 1 Reply Last reply Reply Quote 3
      • ruihildt
        ruihildt @robi last edited by

        Been advocating that for years. 🙂

        1 Reply Last reply Reply Quote 2
        • infogulch
          infogulch last edited by

          How valuable would this be in practice? I.e. how often and in what cases would you need to restore very old spaced out backups like this?

          Not that the features are mutually exclusive, but personally I think I would prefer the ability to pin specific app or full backups on demand instead of having a more complex retention schedule like this. That way I could save the backup right before an upgrade, or the one before and after making big changes in the app. Such backups would be much more useful than hoping that the backup you needed was retained at the right point in the schedule without data loss.

          ruihildt robi 2 Replies Last reply Reply Quote 0
          • ruihildt
            ruihildt @infogulch last edited by

            @infogulch If you think about a small number of service, you can adopt a case by case basis approach like you mention.

            When you change the scale or host third parties, it's much easier to not have to rely on your judgement and the human, and systemize the process of backing up, with multiple close to the present, and space out more and more as the time passes.

            1 Reply Last reply Reply Quote 1
            • robi
              robi @infogulch last edited by

              @infogulch a hybrid of both would be best, but let's start with this one.

              If CL is going to be more adopted in the enterprise, it will need better audit & retention capabilities before things go to archive.

              Life of Advanced Technology

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Powered by NodeBB