[Box Backup] chris-merge - 2GB+ - Get OK - Compare fails?

[Tobias Balle-Petersen]

Hello Chris.

I'm not familiar with the term top-posting, so I might unintentially be doing i again now. Sorry.

The problem with the compare seems to be a with the MS Office files themselves (I only get errors on
MS-files).

I can restore the files from backup, and they have the same content as the original files.
Despite this, the restored and original file have different MD5 sigs. I have found by testing, that
the MD5 sig of office files change everytime they are opened even though they have not been changed
by the user and saved back.

So... No problem it seems.

Thanks,
Tobias



Chris Wilson wrote:
> Hi Tobias,
> 
> Would you mind not top-posting? It makes our discussion difficult to
> read for other list members who haven't read previous messages in detail
> or who are new to the list. Thank you. I've fixed it here:
> 
> On Wed, 3 Oct 2007, Tobias Balle-Petersen wrote:
>> Chris Wilson wrote:
>>> On Wed, 26 Sep 2007, Tobias Balle-Petersen wrote:
>>>
>>>> All the errors are of this format:
>>>>
>>>> file A has different contents to store file file B
>>>>
>>>> The compare ends with:
>>>> [ 0 (of 8) differences probably due to file modifications after the
>>>> last upload ]
>>>> Differences: 8 (0 dirs excluded, 0 files excluded, 2 files not checked)
>>>> Logging off...
>>>> Exception: Connection Protocol_ObjTooBig (7/42)
>>>
>>> Are all the files which failed to compare properly over 2GB, or only the
>>> first one?
>>
>> None of them ar bigger than 2GB.
> 
> OK, that is strange and very worrying. I would very much appreciate your
> help in fixing this.
> 
> First off, please could you remind me what versions of Box Backup you
> are running on the client and the server?
> 
> Secondly, please could you make a copy of one of the files that's
> failing to compare, in the same directory, and check that the copy is
> backed up, and then run a compare and see if the copy fails to compare
> too? That should establish whether the problem is on the client side, or
> with an old client which generated files which now can't be patched.
> 
> Cheers, Chris.