Re: Going deeper on merge feature

Denis Corbin <[email protected]> Wed, 20 Dec 2023 21:27:28 +0100
Newsgroups gmane.comp.sysutils.backup.dar.support
Message-ID <[email protected]>

On 20/12/2023 17:50, vash-dar.ztzvp--- via Dar-support wrote:
> On Sunday, December 17th, 2023 at 02:49, Denis Corbin - dar.linux at free.fr <[email protected]> wrote:
> 

[...]

> 
> Thank you to have explained it clearly. Actually, that was the status I observed during my tests.
> I still wonder why "-/ Oo" doesn't seem to be the default overwrite policy as it is reported by the documentation.

I've double checked and you're correct: there is an incoherence between 
the man page and the default behavior at both libdar and dar levels, 
which both default to preserving Data and EA/FSA (-/ Pp). The default 
should be overwrite, by coherence to the time the overwriting policy was 
only expressed by -n and -w options. Without any of those, a warning was 
issued before overwriting.

But as nobody complained about this discontinuity in default behavior 
which appeared with release 2.4.0 (released June 2nd, 2011, thus more 
than 12 years ago) I will rather update the man page than changing dar's 
and libdar's behavior.

> 
> [...]
>> Now, if you plan is to make a full backup from the diff backup as if a
>> full backup was done at the time of the diff backup, this is as easy as
>> adding "full-from-diff" in your merge pattern.
> 
> That's exactly what I meant and want to do.
> 
>>
>> I let you first examin the /etc/darrc provided with dar, where the
>> "full-from-diff" definition contains the adhoc overwriting policy and a
>> quick documentation on how to use it.
>>
> 
> Thanks a lot for this precious hint. I applied that policy and actually reached my goal.
> Docs mentions that logical operators must be escaped if they will be typed in a CLI. I realized that only after having done the merge, then I didn't used any of them. Anyway, It seems to be I reached my goal. I'll be more careful next time.
> I didn't know how to treat the "Saved status" but now, I understood that's possible through the "conditions mechanism". That's not really easy to understand to me, but I feel I understood the most of it. I'll do some more test on it just for learning purpose.

yes, that's not easy to understand, I agree... If needed, I can explain 
it in details, let me know.

> 
>> Cheers,
>> Denis
> 
> Thanks a lot.
> --
> vash
> 
> 

Cheers,
Denis
OpenPGP_signature.asc (application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEVeSEpqXFvH9T9/cuqLFBYNNrO6cFAmWDTjAFAwAAAAAACgkQqLFBYNNrO6dM
sg/+KGQNWtEOXEiQ2oCZrQmG7ijTo1jJmS+E5bouqCBrrOvhdohI544P2YO/RwzqcuDvtvJNB0CO
dr6LJc5DC7ZdUlQ1SUohCjbxBUnp+l8/mj2vgb7IB/fQHA31OyTJ2O9SjyBUBZYmUnCEj0Kes/b9
D6VgcPrv46uRuaU6tpW1t+Xq6bO5Mw0mMFJsoBePYycfyfDZoRxY3m5AKWNhgOtUBB7ExY1uXg/j
TgKHfivPORg2pKaEOkRjV/9Ef7CAiaiOqX6XUnJsVJr1uLFNHdaKtvpJjVsnuE1fW75q18BRsSns
/W5bJqZG0JXmiCxV2VtZOQC4sf5eJ0mQv52Q5LmDdxOWDZBdDv5sM/U7on5JsdI7ZnBXta6Xqf8X
YC6J5nlCkaZ+H1ruHun8qHKK8H3N27q3o171WkjhK2kFMvkULc3lNz2pkdo7JuzTXf2qEHUoe9yS
KuxzqQ2fL/tfGBEreqRPX9ztwdPCSIXGXliQr4TlMXGf0JS/D2WyidLyoJTOWVrLG379dptuNu05
JEzMoHFU06UqEBQXlc2IWpKQ2/7S6BjDAI6oVFphs2ItPCsDjlOuZzCf2i6k2teG71UcZloLt/PU
k1oDdlq+TRDN2zGaQPMzRFnOepRwyt2WKFumSmdAIrpN1VqzIUTU3RWaVv0YOMzp9weM8Pa4x8ja
P/4=
=2ccy
-----END PGP SIGNATURE-----