upstream/borgbackup
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2026-03-27 12:54:05 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Merge pull request #3680 from ThomasWaldmann/transaction-rollback-docs

Browse source 
docs: extend append-only repo rollback docs, fixes #3579
This commit is contained in:
TW 2018-03-12 15:13:53 +01:00 committed by GitHub
commit e6978fa2ea
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
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.
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
always expendable). In this example N is 13.
is to remove the ``hints.N``, ``index.N`` and ``integrity.N``files in the repository (these
files are always expendable). In this example N is 13.
Then remove or move all segment files from the segment directories in ``data/`` starting
with file 6::
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
+++++++++