mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-02-22 06:01:54 +00:00
Code Issues Releases Wiki Activity

Merge pull request #6257 from ThomasWaldmann/upgrade-docs

Browse source 
docs: add borg 1.2 upgrade notes, fixes #6217
This commit is contained in:
TW 2022-02-06 23:17:21 +01:00 committed by GitHub
commit 8c95dd46e3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 33 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
docs/changes.rst
View file

@ -217,19 +217,42 @@ The best check that everything is ok is to run a dry-run extraction::
Change Log Change Log
========== ==========
Version 1.2.0rc1 (2022-02-05) Version 1.2.0 (not released yet)
----------------------------- --------------------------------
Please note: Please note:
This is code released for testing (== helping us find bugs). This is the first borg 1.2 release, so be careful and read the notes below.
It is not suitable to run against your production backup repositories! Upgrade notes:
So, if you want to help testing, please run this code additionally to your Strictly taken, nothing special is required for upgrading to 1.2, but some
normal backup and use a separate, fresh repository for it. things can be recommended:
See there for feedback: https://github.com/borgbackup/borg/issues/4360 - do you already want to upgrade? 1.1.x also will get fixes for a while.
- be careful, first upgrade your less critical / smaller repos.
- first upgrade to a recent 1.1.x release - especially if you run some older
1.1.* or even 1.0.* borg release.
- using that, run at least one `borg create` (your normal backup), `prune`
and especially a `check` to see everything is in a good state.
- check the output of `borg check` - if there is anything special, consider
a `borg check --repair` followed by another `borg check`.
- if everything is fine so far (borg check reports no issues), you can consider
upgrading to 1.2.0. if not, please first fix any already existing issue.
- if you want to play safer, first **create a backup of your borg repository**.
- upgrade to latest borg 1.2.x release (you could use the fat binary from
github releases page)
- run `borg compact --cleanup-commits` to clean up a ton of 17 bytes long files
in your repo caused by a borg 1.1 bug
- run `borg check` again (now with borg 1.2.x) and check if there is anything
special.
- check the compatibility notes (see below) and adapt your scripts, if needed.
- if you run into any issues, please check the github issue tracker before
posting new issues there or elsewhere.
If you follow this procedure, you can help avoiding that we get a lot of
"borg 1.2" issue reports that are not really 1.2 issues, but existed before
and maybe just were not noticed.
Compatibility notes: Compatibility notes:
@ -270,6 +293,9 @@ Compatibility notes:
if you have scripts expecting rc == 2 for a signal exit, you need to update if you have scripts expecting rc == 2 for a signal exit, you need to update
them to check for >= 128. them to check for >= 128.
Version 1.2.0rc1 (2022-02-05)
-----------------------------
Fixes: Fixes:
- repo::archive location placeholder expansion fixes, #5826, #5998 - repo::archive location placeholder expansion fixes, #5826, #5998