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

[Nick Knight]

I cannot remember exactly what I did now, I was doing a lot of playing
around with different sized files to sort out large file issues.

One of the things I did do was delete the contents of the account,
remove is from accounts.txt, then recreate the account, the next time
the client reconnected it didn't do a backup until I deleted the
bbackupd.state file.

-----Original Message-----
From: boxbackup-dev-admin@fluffy.co.uk
[mailto:boxbackup-dev-admin@fluffy.co.uk] On Behalf Of Ben Summers
Sent: 25 July 2006 12:25
To: boxbackup-dev@fluffy.co.uk
Subject: Re: [Box Backup-dev] observation with client side cached state
file


Could you tell us a bit more about the corruption on the server?

Did you run bbstoreaccounts to fix the account? If it changed =20
anything, it would have reset the client store marker which would =20
have caused bbackupd to rescan the entire store next time it connected.

Ben


On 25 Jul 2006, at 12:06, Nick Knight wrote:

> Hello all,
>
> This is an observation I have had over the last day or so, if I set up
> the bbackupd to cache its state in a file, then if you have a =20
> problem on
> 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 =20
> the
> server again, it will not re-backup any file now missing from the =20
> store.
>
> My thoughts on this are for a backup system could be a little =20
> dangerous?
>
> Thoughts?
>
> Regards
>
> Nick
>
>
> _______________________________________________
> Boxbackup-dev mailing list
> Boxbackup-dev@fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev

_______________________________________________
Boxbackup-dev mailing list
Boxbackup-dev@fluffy.co.uk
http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev