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
When I trigger the backup manually,
it runs very long (circa 2-3 hours) (longer than needed for a new fresh total backup)
-> then all old backups are deleted.
C. Ideas
It could be because of missing free space on the backup disc.
It happened two times to me. (Circa within the last 3/4 year)
Is that situation known?
It think a warning shoud be displayed before deleting all backups.
@improve-code:
Thanks a lot for reporting your issue. To my knowledge, the described behaviour has not been reported, until now.
The first backup from a fresh OS install to an existing repository is expected to take a long time, since the cache has to be rebuilt.
This behaviour is documented in the borg docs:
Also, in order for the deduplication used by Borg to work, it needs to keep a local cache containing checksums of all file chunks already stored in the repository. This cache is stored in ~/.cache/borg/. If Borg detects that a repository has been modified since the local cache was updated it will need to rebuild the cache. This rebuild can be quite time consuming.
Note, that in this case the time of the cache-rebuild depends on the size of the existing repository, i.e. it does not depend on the amount of data on your client.
Old archives in the existing backups should only be pruned (deleted) from the repository if the prune command is configured accordingly.
If borg/ Vorta runs out of space, the old archives should always stay intact. Did you try to check with borg list if the archives are still in the repository?
I am afraid, that without the log-files it is impossible to understand/ debug what went wrong in your case.
I still have one of the two repositories. It is untouched since then.
borg list [PATH]shows all the backups.
(borgbackup version 1.2.8-1).
Last backup is from Thu, 2025-05-01.
B.
I will not touch the live repository with Vorta. I will need some time to create a copy.
If I remember right, the old archives were not shown in Vorta.
Thanks for confirming that borg list still shows all archives. That means nothing was deleted from the repository; only Vorta's local archive list was wiped.
We found a likely cause. When the archive refresh (borg list --json) exited successfully but returned empty or unparsable output, Vorta treated that as "the repository has no archives" and dropped every archive from its list. 9810f29 fixes this. Vorta now keeps the existing list, logs a warning and shows "Could not read archive list from Borg. Local list kept." The fix will be in the next release.
Without logs we can't be sure this was your case, so I'm leaving the issue open for now. If it happens again on a version with this fix, please attach ~/.local/state/Vorta/log/vorta.log (Linux). After restoring the old installation, clicking Refresh on the Archives tab should bring the list back.
Vorta 0.12.0 includes 9810f29, which preserves the local archive list when Borg returns empty or unreadable output and displays an error instead. Closing with the release of this fix. We could not confirm the original cause without logs; if archives disappear from the list again on 0.12.0, please report it with the Vorta log so we can reopen and investigate.
Activity
goebbe commentedon Feb 26, 2026
@improve-code:
Thanks a lot for reporting your issue. To my knowledge, the described behaviour has not been reported, until now.
The first backup from a fresh OS install to an existing repository is expected to take a long time, since the cache has to be rebuilt.
This behaviour is documented in the borg docs:
Note, that in this case the time of the cache-rebuild depends on the size of the existing repository, i.e. it does not depend on the amount of data on your client.
Old archives in the existing backups should only be pruned (deleted) from the repository if the prune command is configured accordingly.
If borg/ Vorta runs out of space, the old archives should always stay intact. Did you try to check with
borg listif the archives are still in the repository?I am afraid, that without the log-files it is impossible to understand/ debug what went wrong in your case.
improve-code commentedon Feb 26, 2026
@goebbe
Thank you for the answer, it probably helped.
A.
I still have one of the two repositories. It is untouched since then.
borg list [PATH]shows all the backups.(borgbackup version 1.2.8-1).
Last backup is from Thu, 2025-05-01.
B.
I will not touch the live repository with Vorta. I will need some time to create a copy.
If I remember right, the old archives were not shown in Vorta.
C.
borgbackup/borg#8937 seems maybe to be related.
It describes (unsolved) problems when ~/.cache is deleted, maybe caused by an old borg version (1.2.0).
D.
My operating system was both times Debian.
[-]All backups deleted, new installation, run backup[/-][+]All backups (seem) to be deleted in vorta[/+][-]All backups (seem) to be deleted in vorta[/-][+]All backups (seem) to be deleted in Vorta[/+]Keep local archive list when borg list output is unreadable (#2412)
m3nu commentedon Oct 15, 2026
Thanks for confirming that
borg liststill shows all archives. That means nothing was deleted from the repository; only Vorta's local archive list was wiped.We found a likely cause. When the archive refresh (
borg list --json) exited successfully but returned empty or unparsable output, Vorta treated that as "the repository has no archives" and dropped every archive from its list. 9810f29 fixes this. Vorta now keeps the existing list, logs a warning and shows "Could not read archive list from Borg. Local list kept." The fix will be in the next release.Without logs we can't be sure this was your case, so I'm leaving the issue open for now. If it happens again on a version with this fix, please attach
~/.local/state/Vorta/log/vorta.log(Linux). After restoring the old installation, clicking Refresh on the Archives tab should bring the list back.m3nu commentedon Nov 3, 2026
Vorta 0.12.0 includes 9810f29, which preserves the local archive list when Borg returns empty or unreadable output and displays an error instead. Closing with the release of this fix. We could not confirm the original cause without logs; if archives disappear from the list again on 0.12.0, please report it with the Vorta log so we can reopen and investigate.