@@ -39,7 +39,9 @@ and GUIs for borg also need to get adapted.
39
39
Major new features
40
40
~~~~~~~~~~~~~~~~~~
41
41
42
- - added retries for input files (e.g. if there is a read error or file changed while reading)
42
+ - create: added retries for input files (e.g. if there is a read error or file changed while reading)
43
+ - extract --continue: continue a previously interrupted extraction
44
+ - additionally to ssh: repos, also implement repos via unix domain (ipc) socket
43
45
44
46
- better, more modern, faster crypto
45
47
@@ -70,11 +72,12 @@ Major new features
70
72
- borg rcreate can create "related repositories" of an existing repo, e.g. to use them
71
73
for efficient archive transfers using borg transfer.
72
74
- borg transfer can copy and convert archives from a borg 1.x repo to a related borg 2 repo.
73
- to save time, it will transfer the compressed file content chunks (without compressing them
74
- again).
75
+ to save time, it will transfer the compressed file content chunks without recompressing.
75
76
but, to make your repo more secure, it will decrypt / re-encrypt all the chunks.
76
77
- borg transfer can copy archives from one borg 2 repo to a related other borg 2 repo,
77
78
without doing any conversion.
79
+ - borg transfer usually transfers compressed chunks (avoids recompression), but there is
80
+ also the option to recompress them using a specific compressor.
78
81
79
82
- command line interface cleanups
80
83
@@ -110,6 +113,7 @@ Other changes
110
113
- do not store .borg_part files in final archive, simplify statistics (no parts stats any more)
111
114
- avoid orphan chunks on input files with OSErrors
112
115
- make sure archive name/comment, stuff that get into JSON is pure valid utf-8 (no surrogate escapes)
116
+ - new remote and progress logging (tunneled through RPC result channel)
113
117
- internal data format / processing changes
114
118
115
119
- using msgpack spec 2.0 now, cleanly differentiating between text and binary bytes.
@@ -156,3 +160,6 @@ Other changes
156
160
- removed some code only needed to deal with very old attic or borg repos.
157
161
users are expected to first upgrade to borg 1.2 before jumping to borg 2.0,
158
162
thus we do not have to deal with any ancient stuff any more.
163
+ - Manifest and archive TAMs now are always required.
164
+ Manifest TAMs should be there since borg 1.0.9 upgrade.
165
+ All archives should have TAMs since borg 1.2.5/1.2.6 upgrade.
0 commit comments