[Box Backup] backup timing issues, native windows client boxwin0.09h.exe
on WinXP Home
Stuart Hickinbottom
boxbackup@fluffy.co.uk
Wed, 18 Jan 2006 18:22:16 +0000
I could be wrong, but from memory I think the backup client daemon
avoids uploading changed files right away to prevent you continually
updating the server if you have files on your machine that change very
frequently (eg database files). Imagine if your server is remote over a
slow link - such files might 'starve' other files from being backed up
at all.
I believe the behaviour is something like:
1. bbackupd notices a file has been created
2. bbackupd waits a while (configurable in the client .conf file), and
then uploads it
If, in between 1 and 2, you change that file, it will avoid it having to
be uploaded twice.
If the file is continually changing I'm pretty sure it will be uploaded
after a while anyway, it's just that it won't be uploaded any more
frequently than this interval no matter how volatile the contents.
I seem to remember this is discussed somewhere on the website/wiki, but
I know finding it might not be that obvious.
Stuart
E.W. Peter Jalajas wrote:
> Even with my bbackupd.conf settings at the very short intervals of the
> test bbackupd.conf settings (well below 1 minute; snipped screen
> scrapes below, edited for clarity), my new files are not being backed
> up until exactly 5 hours and 3 seconds later.
>
> This may relate to the bbackupquery timestamp/timezone problem
> mentioned in my other recent thread:
> [Box Backup] bbackupquery.exe issues, native windows client
> boxwin0.09h.exe
>
> I have no idea really, but I think bb may be using timezone adjustments
> inconsistently, either internally to one end (windows client or linux
> server), or during communications between the windows client and the
> linux server, but I'm too lazy to figure out how to figure it all out.
>
> Any ideas on how I can resolve this problem and get my backups stored
> timely?
>
> Thanks,
> Pete
>
> >From ls -alrtF on server store:
> -rw-r--r-- 1 224 2006-01-14 14:53 o44.rfw (2006-01-14T09:50.txt)
> -rw-r--r-- 1 208 2006-01-16 00:32 o48.rfw (2006-01-15T19:29.txt)
> -rw-r--r-- 1 208 2006-01-17 04:40 o4a.rfw (2006-01-16T23:37.txt)
> -rw-r--r-- 1 208 2006-01-18 03:53 o4d.rfw (2006-01-17T22:50.txt)
> -rw-r--r-- 1 224 2006-01-18 06:22 o50.rfw (2006-01-18T01:19.txt)
> -rw-r--r-- 1 6652 2006-01-18 06:22 o02.rfw
> -rw------- 1 0 2006-01-18 10:41 write.lock
> -rw-r--r-- 1 88 2006-01-18 10:41 info.rfw
> drwxr-xr-x 2 4096 2006-01-18 10:41 ./
>
> >From bbackupquery:
> 00000044 f----- 2006-01-14T19:50 00001 2006-01-14T09:50.txt
> 00000048 f----- 2006-01-16T05:29 00001 2006-01-15T19:29.txt
> 0000004a f----- 2006-01-17T09:37 00001 2006-01-16T23:37.txt
> 0000004d f----- 2006-01-18T08:50 00001 2006-01-17T22:50.txt
> 00000050 f----- 2006-01-18T11:19 00001 2006-01-18T01:19.txt
>
> C:\Program Files\Box Backup>net stop boxbackup
> The Box Backup service is stopping.
> The Box Backup service was stopped successfully.
> C:\Program Files\Box Backup>net start boxbackup
> The Box Backup service was started successfully.
> C:\Program Files\Box Backup>bbackupctl reload
> Using configuration file C:\Program Files\Box Backup\bbackupd.conf
> Daemon configuration summary:
> AutomaticBackup = true
> UpdateStoreInterval = 3 seconds
> MinimumFileAge = 4 seconds
> MaxUploadWait = 24 seconds
> Succeeded.
>
> >From cmd of the backuplocation:
> 01/14/2006 09:50 AM 19 2006-01-14T0950.txt
> 01/15/2006 07:29 PM 7 2006-01-15T1929.txt
> 01/16/2006 11:37 PM 7 2006-01-16T2337.txt
> 01/17/2006 10:50 PM 5 2006-01-17T2250.txt
> 01/18/2006 01:19 AM 30 2006-01-18T0119.txt
> 01/18/2006 10:09 AM <DIR> .
> 01/18/2006 10:09 AM <DIR> ..
>
> feeble attempt at keywords: late backups, backups are late
>
> --- Per Thomsen <pthomsen@reedtz.com> wrote:
>
>
>> On 1/13/06 10:59 PM, E.W. Peter Jalajas wrote:
>>
>>> The boxwin query listing seems to report the timestamp as exactly
>>>
> the correct day and minute, but 10
>
>>> hours in the future (or 14 hours in the past?).
>>>
>
>
>> I'm pretty sure the time stamps in bbackupquery are UTC, so you must
>>
> be 10 hours west of Greenwich.
>
> I think I'm set to EST (GMT-5):
> Under cygwin:
> $ date
> Sat Jan 14 09:33:04 EST 2006
> Under cmd:
> C:\PROGRA~1\BOXBAC~1>date /T
> Sat 01/14/2006
> C:\PROGRA~1\BOXBAC~1>time /T
> 09:33 AM
>
>
> _______________________________________________
> boxbackup mailing list
> boxbackup@fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
>
>