borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 52 Pull Requests 2 Actions Packages Releases 121 Activity

Add support for "borg check --last N" #2

New Issue
Closed
opened 2018-01-05 05:33:24 +00:00 by import_bot · 2 comments
import_bot commented 2018-01-05 05:33:24 +00:00
Collaborator
Copy Link

Borg backup allows you to only check the last N archives, instead of all of them. That can speed things up when you are running hourly backups with looser settings and will have a few hundred archives.

Imported from Taiga issue 1 (done). Created on 2015-07-26T14:04:09+0000 by Thomas Harold.

Borg backup allows you to only check the last N archives, instead of all of them. That can speed things up when you are running hourly backups with looser settings and will have a few hundred archives. --- Imported from Taiga issue 1 (done). Created on 2015-07-26T14:04:09+0000 by Thomas Harold.
import_bot commented 2018-01-05 05:33:24 +00:00
Author
Collaborator
Copy Link

This appeas to be the first instance of a Borg-only (non-Attic) config file option, as "attic check" doesn't support "--last", so it would need to some logic to ensure it's only supported when Borg is the backend.

Comment on 2015-07-26T15:15:02+0000 by Dan Helfman.

This appeas to be the first instance of a Borg-only (non-Attic) config file option, as "attic check" doesn't support "--last", so it would need to some logic to ensure it's only supported when Borg is the backend. --- Comment on 2015-07-26T15:15:02+0000 by Dan Helfman.
import_bot commented 2018-01-05 05:33:24 +00:00
Author
Collaborator
Copy Link

Implemented in atticmatic 0.1.3 via a new Borg-only "check_last" config file option in the "[consistency]" section.

Comment on 2015-07-28T04:49:52+0000 by Dan Helfman.

Implemented in atticmatic 0.1.3 via a new Borg-only "check_last" config file option in the "[consistency]" section. --- Comment on 2015-07-28T04:49:52+0000 by Dan Helfman.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
spot-check
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   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#2
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?