You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: faq/index.md
+6-2
Original file line number
Diff line number
Diff line change
@@ -141,17 +141,21 @@ There are rare situations, where Borg repositories can be damaged by e.g. interr
141
141
142
142
Borg is generally good at fixing those issues and missing data will be added during the next backup run.
143
143
144
+
#### Missing Data Segments
145
+
144
146
To fix errors related to missing data or files:
145
147
146
148
1. First run `borg check $REPO_URL`. This will first check the repository files and then one or more archives.
147
149
2. If the first step reveals errors, you should make a local repo copy, unless the data is non-critical.
148
150
3. Next run `borg check --repair $REPO_URL` to ask Borg to fix any errors.
149
151
4. Finally run `borg create ...` to do a full backup run and add potentially missing data.
150
152
153
+
#### Cache Issues
154
+
151
155
To fix errors related to the cache (from [here](https://github.com/borgbackup/borg/issues/3428#issuecomment-380399036)):
152
156
153
-
1. First try to the local cache `borg delete --cache-only $REPO_URL`
154
-
2. If the first step doesn't resolve the issue, try moving or removing the security folder in `~/.config/borg/security/$REPO_ID`. Where the `REPO_ID` can be found using `borg config $REPO_URL id`
157
+
1. First try to delete the local cache `borg delete --cache-only $REPO_URL`
158
+
2. If the first step doesn't resolve the issue, try moving the security folder in `~/.config/borg/security/$REPO_ID`. Where the `REPO_ID` can be found using `borg config $REPO_URL id`
0 commit comments