Re: show/compare compression algorithm/level
Denis Corbin <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.dar.support |
|---|---|
| Organization | http://dar.linux.free.fr/ |
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 24/06/2019 21:20, Matus UHLAR - fantomas wrote: >>>> On 21/06/2019 19:53, Matus UHLAR - fantomas wrote: >>>>> is it possible when listing dar archive to show the >>>>> compression algorithm and level used for files? >>>>> >>>>> and when merging archives, e.g. creating decremental >>>>> archive, does dar detect the same file even if it's >>>>> compressed using different algorithm/level? > >>> On 21.06.19 23:48, Denis Corbin wrote: >>>> dar -l <archive> -q >>>> >>>> will let you see the compression algorithm used, but not the >>>> compression level. For that you can use for example >>>> '--user-comment %c' at archive creation time (let you refer >>>> to the man page for this option details) and see what was >>>> the command line used to create the archive. > >> On 23/06/2019 20:06, Matus UHLAR - fantomas wrote: >>> so, only one compression scheme can be used per archive? > > On 24.06.19 19:41, Denis Corbin wrote: >> Yes for now: once a compression algorithm has been selected you >> can define which file to compress and which file not to try >> compressing. >> >> The archive format has room to have compression algorithm and >> compression level per file, but so far this has not been founded >> very useful. >> >> What is your use case for such feature? > > for now, I'm interested because I have tried to create different > backups using different compression schemes (no big luck) and I was > curious if it's possible to make decremental archive from them > without recompression. > I see. You are correct, building a decremental backup is specific merging operation. As of today, merging is not able to keep file compressed if the two archives have different compression algorithms. I will raise the priority of this feature for it be part of 2.7.x -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEOzEprx3d76WjfYGPCDGwvQPYsYIFAl0Scl8ACgkQCDGwvQPY sYJfHRAAo0jpSN2dFc45EofkKyLPsAQ/NqDleFnxR8f9up0Bgr5S5pTmP0l5725q eK8dHomCwnLxoL4pKeBzpdD3Uwxja6Qplbe+UoLIZq1hmSI9ipqE8+eVXEwK+uqi St4yS8HmWvAM2BRmrgScqLpWJkRUPGwos0cTSsFwnme1wND0AlTlmE+zmEa7Sy7l kK/RSSJJjMQC2k46dNi6oMZVNadkDsD5l5QmVfa0qLliyORHkf+sirA8jxRltxuJ gVUm9Xc01BiPxWZHQrWplyfyCPN6WMnWigGFcDYHiC4RV1WhBnOPXQOO7JV7kXF1 /N9bBErtMGx3by5FrlyJg/zOcds1jd3pcsNNtr1yh2kkZDINq5ROnjY/RkkDDWcw jBZQtlmtAQnuIhBy9NUQuiXi4tbbMxkbnOtWFMHwwIisvlroXcBbTuDt2Pg7nXMa UeruQCzHnEwQNg0Rxx7r1enST1zWkDj+M2JE7QdwIMZhLd5IoLcV1/1k1/g4zizt cB0cI6LKv1KKUsUgd9Xop21PqifkJvNjBYUKuiackeQPiA0l4SzPhqOtTsyjvV7/ GcqjcHKbrjWNOfOvbeVhh8zyBoH1ybUUqc+PmqgZcc9+iZYV40aTGPH2NOyI0cHU 9Vth7RkLW/XOhnzajDkZW1OZAPuaFkGn+Zn+AND0Ev3OjYDlevE= =ztRQ -----END PGP SIGNATURE-----