[Box Backup] bbackupd crashing

[Ben Summers]

On 8 Jan 2006, at 17:57, Soren Dossing wrote:

>
>
> On Sat, 7 Jan 2006, Ben Summers wrote:
>
>> It looks like your Berkeley inode tracking databases have got  
>> corrupted. Stop bbackupd, delete the contents of /var/bbackupd (or  
>> whatever specified by DataDirectory in bbackupd.conf), and restart  
>> bbackupd.
>
> It worked perfectly. Thanks for the suggestion.

It's a nasty one. Caught me a few times too.

>
>> This is harmless, although if you've been renaming large files it  
>> may result in some unnecessary use of bandwidth and disc space on  
>> the server.
>
> I have not been renaming any files. But it seems like bbackupd  
> uploaded everything again... 'bbackupctl sync' maxed out bandwidth  
> for the past 30 hours.

Is it uploading existing files? Or just stuff it didn't manage to  
upload before? If you've got ExtendedLogging = yes in bbackupd.conf  
it'll tell you what's happening in the logs.

>
>> Berkeley DB v1 does seem to do this occasionally. In the  
>> forthcoming release, we also support a later version which I hope  
>> is more reliable.
>
> Any chance that corruptions could be detected by bbackupd and logged?

Difficult. Remember that the only indication is a sudden crash, by  
which time it's too late. I suppose it could notice that it didn't  
shut down properly last time, and delete them as a precaution.

Ben