Re: [Duplicity-talk] duplicity has clock issues and stopped working

[Yves Goergen]

>>   File "/usr/bin/duplicity", line 474, in incremental_backup
>>     assert dup_time.curtime != dup_time.prevtime, "time not moving forward 
>> at appropriate pace - system clock issues?"

I have now commented out this line because it seems dup_time is used for
no other purposes than displaying something to the user. Here comes the
next error: Even though indicating a full backup with the "full"
parameter, duplicity really did an incremental backup - and complained
about stuff I don't understand.

>   Logical volume "root_snapshot" created
> Unable to locate last file 
> var/cache/apt/archives/linux-image-2.6.32-33-server_2.6.32-33.70_amd64.deb 
> and block 479 in backup set.
> Attempting restart on the next file var/cache/apt/archives/partial.
> Error librsync error 1 while in delta rs_signature_t builder getting delta 
> for var/lib/mysql/ib_logfile1
> --------------[ Backup Statistics ]--------------
> StartTime 1310889352.74 (Sun Jul 17 09:55:52 2011)
> EndTime 1310890023.86 (Sun Jul 17 10:07:03 2011)
> ElapsedTime 671.12 (11 minutes 11.12 seconds)
> SourceFiles 444595
> SourceFileSize 22468900505 (20.9 GB)
> NewFiles 3496
> NewFileSize 129738768 (124 MB)
> DeletedFiles 3451
> ChangedFiles 2769
> ChangedFileSize 3841944590 (3.58 GB)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 9716
> RawDeltaSize 475281294 (453 MB)
> TotalDestinationSizeChange 194285679 (185 MB)
> Errors 1
> -------------------------------------------------
> 
>   Snapshot used 1,81%
>   Logical volume "root_snapshot" successfully removed

The backup is done from an LVM snapshot, so there are no locked files,
or files changed during reading. And usually an incremental backup takes
something around 3 minutes. This one took 11 minutes. (But maybe that
comes from the recent reboot and that the filesystem wasn't entirely in
RAM cache yet. Although I'm not sure a snapshot of the filesystem could
be in RAM cache before it was created. Maybe Linux is so smart.)

So, duplicity still doesn't work correctly. And all I did initially was
rebooting the server just as many times before. Something went wrong
this time.

-- 
Yves Goergen "LonelyPixel" <address@hidden>
Visit my web laboratory at http://beta.unclassified.de