home.social

#kopia — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #kopia, aggregated by home.social.

  1. The command that will show you the errors is `kopia snapshot list --json`. Without --json, it uses colour to tell you which snapshots had errors, information that is lost if you pipe it into something else, and doesn’t list errors. WTF?

    So the least unreasonable way of getting useful information out of Kopia is:

    /path/to/kopia --config-file=path/to/repo.config snapshot list --json | jq 'map( { obj: .rootEntry.obj, startTime, endTime, errors: .rootEntry.summ.errors } )'

    #Kopia #Backup

  2. So the CLI tool is buried in “/Applications/KopiaUI.app/Contents/Resources/server/kopia”. The required config file that the CLI tool cannot find by itself in “~/Library/Application Support/kopia/repository-[some random bullshit numbers].config”. >>
    #Kopia #Backup

  3. RE: tooting.ch/@oscherler/11760827

    So Kopia has a UI, but it’s useless to tell you why it’s hammering you with notifications for failed tasks that are displayed as successful, and when you open them show you errors that you can’t identify because they’re drowned in a truncated log of thousands of useless lines, all of which contain the word “error.”

    Fortunately, there’s a concealed command line tool that lets you obtain that vital information, in the most unintuitive way possible. >>

    #Kopia #Backup

Share on Mastodon

Enter the server where you have an account.