[Box Backup-dev] observation with client side cached state file

[Ben Summers]

On 25 Jul 2006, at 13:32, G. wrote:

> Nick,
>
>> the server with corruption or whatever, then it can be a little
>> misleading - unless you delete the cache file for it to get it  
>> from the
>> server again, it will not re-backup any file now missing from the  
>> store.
>
> Exactly the same thing will happen even if you disable the cache  
> file, but keep the bbackupd
> running on the client side - it will use its runtime cache until  
> restarted, when that information
> is lost. So, considering the fact that bbackupd is designed to keep  
> running around the clock and
> NOT rely on a complete re-scan when restarted, the problem is there  
> with or without a cache file.
> There is no way for bbackupd to know that store contents have  
> changed, unless either the server
> informs it of this.

The client store marker is the way that the server informs the  
clients of unexpected changes to the store. A recreation of the  
account will change this.

However, if nothing changed on the client, then bbackupd wouldn't  
have contacted the store and so wouldn't have learnt of the change.

What happens if you repeat your experiment, but this time, touch one  
of the test files after the server account has been wiped?

Ben