mirror
/
borg
mirror of https://github.com/borgbackup/borg.git
1
0
Fork 0
Code Issues Releases Wiki Activity

docs: minor fixes/update to notes

This commit is contained in:
Thomas Waldmann 2023-07-04 23:36:41 +02:00
parent 84b1ad6948
commit 89cfd083ba
No known key found for this signature in database
GPG Key ID: 243ACFA951F78E01
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/usage/notes.rst
View File

@ -175,9 +175,7 @@ Separate compaction
~~~~~~~~~~~~~~~~~~~
Borg does not auto-compact the segment files in the repository at commit time
(at the end of each repository-writing command) any more.
This is new since borg 1.2.0 and requires borg >= 1.2.0 on client and server.
(at the end of each repository-writing command) any more (since borg 1.2.0).
This causes a similar behaviour of the repository as if it was in append-only
mode (see below) most of the time (until ``borg compact`` is invoked or an
@ -236,7 +234,7 @@ in ``.ssh/authorized_keys``:
command="borg serve --append-only ..." ssh-rsa <key used for not-always-trustable backup clients>
command="borg serve ..." ssh-rsa <key used for backup management>
Running ``borg init`` via a ``borg serve --append-only`` server will *not* create
Running ``borg rcreate`` via a ``borg serve --append-only`` server will *not* create
an append-only repository. Running ``borg rcreate --append-only`` creates an append-only
repository regardless of server settings.
@ -276,7 +274,7 @@ with file 6::
That's all to do in the repository.
If you want to access this rollbacked repository from a client that already has
If you want to access this rolled back 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.