Re: problem during archive test phase

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Andy,

Still looking at this point. I tried to reproduce it but could not see
the problem rising. So I guess it is linked to the data saved. I have
still some point to validate about the dar "layers" used at backup and
the ones used reading time when both delta patch and delta signature
are used.

I will probably submit you a modified dar version to run on the same
data, so don't delete this VM disk image to be able to validate the
problem has been fixed or not :)

keep you informed in a few days at most

Regards,
Denis

On 16/01/2020 19:41, [email protected] wrote:
> Denis, don't know if this info is useful, if I try to restore the
> archive I generated with the -at option (logs showed earlier today)
> get the following output:
> 
> #  extracting from archive sequence definition:
> 20200116T070000_incr.darseq #  extracting archive: 20190303T210053 
> dar -x 20190303T210053 -b -R /mnt/usb/WA8/tmp_extr -B
> /home/andy/opt/tools/midar/midar.dcf -w -q #  extracting archive:
> 20200116T070000_incr dar -x 20200116T070000_incr -b -R
> /mnt/usb/WA8/tmp_extr -B /home/andy/opt/tools/midar/midar.dcf -w
> -q
> 
> Error while restoring /mnt/usb/WA8/tmp_extr/openSUSE Leap
> 15.0/openSUSE Leap 15.0-000002.vmdk : Patch data does not match its
> CRC, archive corruption took place All files asked could not be
> restored
> 
> (dar exit flag: 5)
> 
> Regards, Andy
> 
> 
>> Il 16 gennaio 2020 alle 10.32 andycapo--- via Dar-support
>> <[email protected]> ha scritto:
>> 
>> Hello Denis,
>>> Il 15 gennaio 2020 alle 20.06 Denis Corbin <[email protected]>
>>> ha scritto:
>>> 
>>> -----BEGIN PGP SIGNED MESSAGE-----Hash: SHA256 Andy, ignore the
>>> first questions in my previous mail, It seems you alreadyhave
>>> sent all the necessary for I see what feature has been
>>> activatedto get to that bug. Though, if you can redo step 2
>>> adding -at option when creating thedifferential backup and let
>>> me know if the problem still persist attesting time, that could
>>> save me a lot of time if I was looking in the wrong direction.
> 
>> Done, unfortunately the test phase shows the same error, see
>> annexed log file.If you want me to make some other tests, or give
>> you more information about the configuration, I'm ready to
>> support.
> 
> 
>>> If the problem vanished as I expect, could you thentry
>>> restoring in a temporary directory a few files stored as
>>> binarydelta (first restoring the full backup of course). This
>>> wouldvalidate the problem is not with delta signature but with
>>> the escapesequence layer. I'm looking on my side to reproduce
>>> the problem based on the logs youprovided, thanks! 
>>> Cheers,Denis
>> Thank you, Andy. [...]
> 
> 
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEOzEprx3d76WjfYGPCDGwvQPYsYIFAl4kqA8ACgkQCDGwvQPY
sYJUIQ/8DGx3fJfZxltyaSeAlgoGSPYo7i3HTb8NhMn1mU165vdCMwoU0eotUBqB
63QCh5Nrifen4JElEuSETEmQqa4Jq4Rl0JeR5IG4VZa/hIbDeYaytoBIxZ9BMIfS
2SQlJJzZwqqXXGghuq/ydRuBN68/2RjyVt2TcbsZXuIE1yObymlIdDHLK7Kz1P3M
yMVOFscqAcBW3WiyEAdchLSVXR1KJK2H2DTqbOE1tnRUL4RzCWyehP8MpJbzotP8
Fr8fnf7pabViBD88Ln8LvLdxPGo3FUDSYVr0+cH0Y2BklM0isTP00rxKCv+HMLxb
MhQ0EQUO5oBLH0ZgzQKXlQ8jycCA6IOYtkHMDddTqntcyD7k+KDYMSLqDh/fERns
Gxz6UCU3fYzqs0CHbwGkXFE1h9ZsyZlYMSWQ+rYzQ8wKHKMyBDoXcaaLUeLSTDWw
QQy0aPzyRDf38noi3pHZ/x0kuNZPKqbCyEoYaY7Vt4pD8hrHrx8uVnsG/dYN646Z
jvhVwvk8OHZrEuj89ClJwFoW9QX+vp9fPstrHrwN0t23KiQyI1U7o+ajmgjXIhVk
HDTSbodYMlqUfQ04E6Zw1pksFK2DOj0ucJycKYysRKSdXQTGOcI3KvdZriB3UFUR
4Lj44OOFP9yuvuesgRssw4BSG2G8wVJt+JNpZG4d26/FG5d8oy8=
=CxzB
-----END PGP SIGNATURE-----