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

[Yves Goergen]

Another strange output I get now:

>   Logical volume "root_snapshot" created
> Warning, found the following remote orphaned signature file:
> duplicity-new-signatures.20110716T072808Z.to.20110716T072808Z.sigtar.gpg
> Error librsync error 1 while in delta rs_signature_t builder getting delta 
> for var/lib/mysql/ib_logfile1
> --------------[ Backup Statistics ]--------------
> StartTime 1310916487.57 (Sun Jul 17 17:28:07 2011)
> EndTime 1310917360.00 (Sun Jul 17 17:42:40 2011)
> ElapsedTime 872.43 (14 minutes 32.43 seconds)
> SourceFiles 445078
> SourceFileSize 22569204430 (21.0 GB)
> NewFiles 3512
> NewFileSize 33775097 (32.2 MB)
> DeletedFiles 2886
> ChangedFiles 291
> ChangedFileSize 3700870579 (3.45 GB)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 6689
> RawDeltaSize 560750921 (535 MB)
> TotalDestinationSizeChange 161387152 (154 MB)
> Errors 1
> -------------------------------------------------
> 
>   Snapshot used 2,10%
>   Logical volume "root_snapshot" successfully removed

Note the file name:

duplicity-new-signatures.20110716T072808Z.to.20110716T072808Z.sigtar.gpg

It seems duplicity really got clock issues now!

What would happen if I just delete all my backup files locally and
remotely and start over with a new backup set? What files would I need
to delete other than /backup/all and /backup/tmp?

My commandline arguments are (among others):
TMPDIR=/backup/tmp duplicity --archive-dir /backup --name all

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