Cool way to indicate retention reasons on backups
-
I recently implemented Kopia to replace Duplicati on some systems in my network. Now that I have more than a week of backups, I have gained appreciation for the retention tags they use in the KopiaUI program.
It does a good job of indicating why this version is being retained while also showing how many copies it is maintaining at each retention level. Really handy.
I just noticed the pin to the right. That lets you pin the snapshot so it won't be removed during cleanup. That's kinda cool to be able to single one out to hang on a bit longer, maybe while investigating something I suspect went wrong after that snapshot.
I'm not shilling for Kopia, I haven't used it enough to be sure I trust it yet. I am hoping XO could blatantly steal this kind of idea for backups, especially delta backups. I often get confused about how to get the retention I want when configuring backups and when I search for answers I see other people are also confused.
I guess for the sake of completeness, this is how KopiaUI lets me configure retention:
-
Adding @lsouai-vates for the ideas on improving the backup UI and features in XO 6 (adding also @clemencebx in the loop and @florent for reference)
-
It is a good suggestion. I have asked for similar in the past too
I think having retetion periods like that is very good practice.I have tried to do something similar by creating multiple backup jobs and assigning tags to them.
It is not perfect, but it is easy to determine what jobs specific VMs belong to. I would love to be able to create a progressive schedule like in your example, as well as being able to create one-off snapshots and backups that stay outside the normal schedules.
-
@CodeMercenary hello and thanks for this idea! We will discuss about it with @clemencebx and see what we can propose on new XO-6 design and workflow.
