mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-03-04 02:28:34 +00:00
Code Issues Releases Wiki Activity

docs: extend append-only repo rollback docs, fixes #3579

Browse source
This commit is contained in:
Thomas Waldmann 2018-03-09 23:27:31 +01:00
parent fcf4145222
commit 451b22ee51
1 changed files with 16 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
docs/usage/notes.rst
View file

@ -201,15 +201,28 @@ copy just in case something goes wrong during the recovery. Since recovery is do
deleting some files, a hard link copy (``cp -al``) is sufficient. deleting some files, a hard link copy (``cp -al``) is sufficient.
The first step to reset the repository to transaction 5, the last uncompromised transaction, The first step to reset the repository to transaction 5, the last uncompromised transaction,
is to remove the ``hints.N`` and ``index.N`` files in the repository (these two files are is to remove the ``hints.N``, ``index.N`` and ``integrity.N``files in the repository (these
always expendable). In this example N is 13. files are always expendable). In this example N is 13.
Then remove or move all segment files from the segment directories in ``data/`` starting Then remove or move all segment files from the segment directories in ``data/`` starting
with file 6:: with file 6::
rm data/**/{6..13} rm data/**/{6..13}
That's all to it. That's all to do in the repository.
If you want to access this rollbacked repository from a client that already has
a cache for this repository, the cache will reflect a newer repository state
than what you actually have in the repository now, after the rollback.
Thus, you need to clear the cache::
borg delete --cache-only repo
The cache will get rebuilt automatically. Depending on repo size and archive
count, it may take a while.
You also will need to remove ~/.config/borg/security/REPOID/manifest-timestamp.
Drawbacks Drawbacks
+++++++++ +++++++++