Managing Tags & discriptions

Support
1

how to use tags?
kopia snap create E: --tags=portableapps:myname

how to filter by tags
kopia snap list --tags=portableapps:myname

Now how do I remember all my tags? :thinking:
kopia snap list
will only show all snapshots but won’t show tags. or discriptions

how to I list tags and discriptions?

Thanks :slight_smile:
sd

2

Interested in your questions, but I’d to also add:

Can I add a tag to an existing snapshot? I noticed that I can ‘pin’ a snapshot (so it doesn’t get removed by a retention policy), but I’d love to be able to label/tag it so I can remember why I pinned it in the future.

3

You can see the descriptions in the json output.

From there you can filter with jq

For example kopia snap list --json | jq .[0]

It’s quite awkward (I haven’t yet managed to see all snapshots with the descriptions).

I hope it could be implemented directly in the UI (tags and descriptions).

4

For anyone coming across this, it turns out you can ‘tag’ a snapshot, instead you ‘pin’ it. This stops it being deleted by a retention policy and lets you add a name. Like so:
kopia snapshot pin <snapshot ID> --add=nameyouwant

These don’t yet show up in the UI, but hopefully down the track that will be possible.

5

I have a prototype of the UI changes to support pins and descriptions:

Please take a look: https://github.com/kopia/htmlui/pull/33

Feedback is appreciated.

3 Likes
6

Thanks for introducing these changes!
I would be very happy to see them in the next release of KopiaUI

7

Love it :+1: Makes complete sense to me. Excellent work as usual!

8

Is it possible to have snapshot names at the level where snapshot definitions are listed, and not only at the level where individual snapshots are listed?

So if you have some project and need different kinds of snapshots, all starting at the same root, you could differentiate between them by name and optional description for further detail. Sample snapshot names, all starting at /home/fred/BIG_PROJECT:

  • Source code
  • CI/CD logs
  • Object code
  • Documentation

My use case is that I need to have various snapshot definitions with different in/exclude and retention rules, all of which are applied from the same directory, so I have no easy way of differentiating between them at the level of the table which gets displayed when you click on the Snapshots tab in the main UI.