Re: some dar format questions
Denis Corbin <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.dar.support |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 14/02/2019 03:42, Christoph Anton Mitterer wrote: > Hey. > > Thanks for your answers :-) > > On Wed, 2019-01-16 at 13:47 +0100, Denis Corbin wrote: >>> 4) Am I right that "--delta no-patch" disables any use of >>> binary deltas? >> >> Not exactly. Binary delta is disabled by default. If an archive >> contains delta signatures (it has been built with --delta sig >> option) dar/libdar will by default use them during a differential >> backup and store a delta patch in place of the new version of the >> file's data. The delta patched is computed based on the delta >> signature found in the archive and the new version of the data >> found on filesystem. >> >> the option "--delta no-patch" only instruct dar to ignore delta >> signature when present in an archive (or isolated catalogue) and >> to never perform a delta patch (always storing the whole data >> when data changed) > > Well I think that's basically what I've meant above with "disables > any use of bin deltas". > > When a fresh archive is created (i.e. not an > incremental/differential one), either with or without --delta > no-patch, no binary deltas will be used. Correct, --delta no-patch is not intended to be used for full backup, it is completely useless in that case: it does nothing, it neither activates delta signature nor it disables them. > > When creating an archive based on an incremental/differential > one,... with --delta no-patch any binary deltas present in the base > archive, will be "ignored" in the sense that the new archive will > not store a binary delta but the whole file (if there were > changes). correct > While without --delta no-patch, it would, for files that already > have a binary delta in the base archive, create again binary deltas > (if necessary). exact > > Right? yep > > > Cheers, Chris. > Regards, Denis -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEOzEprx3d76WjfYGPCDGwvQPYsYIFAlxlzDcACgkQCDGwvQPY sYIViw/+IoWAzsAL8ltUNhtiQZ/QDkoBennv1c1S7Q+J0/xaeAAb2ugf8lg3Hd2T NzVU4CSBxP3Ov/P5dOjpG6QJ5WOLcoalSdqvsMOk6pirgBCs2sx+7kfWti5Mu5/B c/yRv9UUraVrnJehfF2gAx0LU0KUYyP8WfHQmecOD9QaAPVfN5+zf91DAG+lLu25 C0w9AG+nudf4nmobtYak4bW0AUtTDYnbyaXsCBKsc/SbVddiRJSWWzUATgmMpSxc a6CBFjcfFpfhu3DgpbsLcVW6A8qgqfjF5fe98CVN8IFcVk/R72NzoxV7DN85SnTw Q0u79SsdIsHRKPyaMTgNEd0EimPXkR9opg+KGXx9NH75DoiHtjnWkaP4FQFwsjK4 eJ+xxuFAbO2V097XP1F7dmA0X06KetOBVy0zxARFYVa7HvdTfkyWP0JK+rs/e8E1 sGh+ap5AAG1Br/vokBuwXSyi7YpFrbxC2UhlkGIJMpzUfGiY/in51rHeEzyCnWcF l542V5l219rz43xRzM9EYyurut/BI6X0nCONVQSqM1ao+TT5tAVXEDdZL6Pxl0Vw 3OwmZt0zDN8hUHtEBRK22DEtsbAoFp30TeCI/3TQ/4Abc+c3FU7rFwVxBts3vIc/ rxTfLxQMv5t4DZL4M03CjidlF9miSn8otHtC4OBDShK1yv+f+FQ= =vu6e -----END PGP SIGNATURE-----