Add option to show last successful backup #86

New Issue

Closed

opened 2018-08-15 21:17:57 +00:00 by varac · 12 comments

varac commented 2018-08-15 21:17:57 +00:00

Copy Link

from https://github.com/borgbackup/borg/issues/4047:

I need to integrate a check for successful backups in our monitoring system.

If would be nice if borgmatic could have a command like borgmatic --last-success containing the details (time, archive name) of the last successful backup (excluding checkpoint archives).

I agree with the borg maintainer: it seems like this is rather something for a on-top-of-borg management tool., which is why I'm asking here for implementation.

from https://github.com/borgbackup/borg/issues/4047: I need to integrate a check for successful backups in our monitoring system. If would be nice if borgmatic could have a command like `borgmatic --last-success` containing the details (time, archive name) of the last successful backup (excluding checkpoint archives). I agree with the borg maintainer: `it seems like this is rather something for a on-top-of-borg management tool.`, which is why I'm asking here for implementation.

witten commented 2018-08-16 04:55:40 +00:00

Owner

Copy Link

Will this do it?

borgmatic --list | tail -n 1

Or, if you want to get that in JSON form, and are using using a recent version of jq:

borgmatic --list --json | jq '.[0].archives[-1]'

Will this do it? ```shell borgmatic --list | tail -n 1 ``` Or, if you want to get that in JSON form, and are using using a recent version of [jq](https://stedolan.github.io/jq/): ```shell borgmatic --list --json | jq '.[0].archives[-1]' ```

thomasleveil commented 2018-08-16 05:55:54 +00:00

Contributor

Copy Link

Here's an snippet from a bash script I use for monitoring the age of the last archive with borg:

local repo="/var/borgbackup/some/borg/repo"

last_archive_timestamp=$(borg list "$repo" --lock-wait 30 --last 1 --json | jq --raw-output '.archives[0].time' | date +%s -f -)
age=$(( ( $(date +%s) - ${last_archive_timestamp} ) ))

Here's an snippet from a bash script I use for monitoring the age of the last archive with borg: ```bash local repo="/var/borgbackup/some/borg/repo" last_archive_timestamp=$(borg list "$repo" --lock-wait 30 --last 1 --json | jq --raw-output '.archives[0].time' | date +%s -f -) age=$(( ( $(date +%s) - ${last_archive_timestamp} ) )) ```

varac commented 2018-08-16 22:56:17 +00:00

Author

Copy Link

@witten, $thomasleveil: Using --last 1 will eventually show a checkpoint archive, which I not consider a successful archive.

I now use this to show the last successful backup timestamp in the repo:

borg list --sort timestamp  --format '{time}{TAB}{name}{NEWLINE}'  $REPOSITORY  | grep -v '\.checkpoint$' | tail -1 |  cut -f 1

@witten, $thomasleveil: Using `--last 1` will eventually show a checkpoint archive, which I not consider a successful archive. I now use this to show the last successful backup timestamp in the repo: ``` borg list --sort timestamp --format '{time}{TAB}{name}{NEWLINE}' $REPOSITORY | grep -v '\.checkpoint$' | tail -1 | cut -f 1 ```

witten commented 2018-08-17 04:49:36 +00:00

Owner

Copy Link

Well, I convinced myself it's possible to get the timestamp of the most recent non-checkpoint archive with jq:

borgmatic --list --json | jq -r '.[0].archives | map(select(.name | test("\\.checkpoint$") | not)) | last | .time'

But that's not very ergonomic, so I could see the utility in having a feature like this more baked into borgmatic.

Well, I convinced myself it's possible to get the timestamp of the most recent non-checkpoint archive with jq: ``` borgmatic --list --json | jq -r '.[0].archives | map(select(.name | test("\\.checkpoint$") | not)) | last | .time' ``` But that's not very ergonomic, so I could see the utility in having a feature like this more baked into borgmatic.

varac commented 2018-08-17 07:28:04 +00:00

Author

Copy Link

@witten: Nice! I agree this would be good to integrate into borgmatic.

@witten: Nice! I agree this would be good to integrate into borgmatic.

witten commented 2018-10-14 18:41:04 +00:00

Owner

Copy Link

Mentioned another implementation idea for this ticket in comments on #97. Basically, the "gimme the last successful backup" feature could be in a separate piped command that specializes in dealing with and parsing Borg JSON output. Example:

borgmatic --list | print-only-the-last-successful-archive

Mentioned another implementation idea for this ticket in comments on #97. Basically, the "gimme the last successful backup" feature *could* be in a separate piped command that specializes in dealing with and parsing Borg JSON output. Example: ```bash borgmatic --list | print-only-the-last-successful-archive ```

henfri commented 2018-12-26 07:59:25 +00:00

Copy Link

Hello,

one point that I see as a problem with relying on borg list is, that the backup target may be offline. Thus, I suggest to cache this information. I.e. borgmatic --list would just print the output of the borg list command that is run after each borgmatic run.

Greetings,
Hendrik

Hello, one point that I see as a problem with relying on borg list is, that the backup target may be offline. Thus, I suggest to cache this information. I.e. borgmatic --list would just print the output of the borg list command that is run after each borgmatic run. Greetings, Hendrik

witten referenced this issue from a commit 2019-10-13 23:00:34 +00:00

Add "borgmatic list --successful" flag to only list successful (non-checkpoint) archives (#86).

witten commented 2019-10-13 23:07:08 +00:00

Owner

Copy Link

Just released borgmatic 1.3.24 with a new borgmatic list --successful flag to hopefully satisfy this ask. It simply excludes Borg checkpoint archives from the list. So if you want just the last one, you can do something like this:

borgmatic list --successful --last 1

And then of course you can use --json if you'd like to parse out additional information about a particular archive (like the time).

Let me know how this works for you!

Just released borgmatic 1.3.24 with a new `borgmatic list --successful` flag to hopefully satisfy this ask. It simply excludes Borg checkpoint archives from the list. So if you want just the last one, you can do something like this: ```bash borgmatic list --successful --last 1 ``` And then of course you can use `--json` if you'd like to parse out additional information about a particular archive (like the time). Let me know how this works for you!

witten closed this issue 2019-10-13 23:07:08 +00:00

varac commented 2019-10-14 09:40:26 +00:00

Author

Copy Link

@witten: Awesome !!

@witten: Awesome !!

varac commented 2019-10-14 09:44:03 +00:00

Author

Copy Link

This shows the time the last successful backup was made:

 borgmatic list --successful --last 1 --json | jq .[0].archives[0].time

This shows the time the last successful backup was made: borgmatic list --successful --last 1 --json | jq .[0].archives[0].time

witten commented 2019-10-14 17:31:36 +00:00

Owner

Copy Link

Cool! Docs are here: https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#successful-backups

Cool! Docs are here: https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#successful-backups

witten commented 2019-10-16 16:50:43 +00:00

Owner

Copy Link

witten/borgmatic#224

😞

https://projects.torsion.org/witten/borgmatic/issues/224 :disappointed:

witten referenced this issue from a commit 2024-11-19 04:32:54 +00:00

Add a Pushover monitoring hook.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

No results found.

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels

blocked

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

No Label

Milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

4 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#86

No description provided.