Re: [Duplicity-talk] duplicity - verify if backup needed

[eleanor]

My situation is the following: I have - let's say - 300MB on the
client, but only 10MB on the server, where the compression is not that
big to make up the difference. The problem is that running with
--dry-run doesn't actually display the files that are not
synchronized. On client I have quite a lot of files that are either
not present of not synchronized on the server.

Why doesn't --dry-run detect that.

On 12/8/11, address@hidden <address@hidden> wrote:
> On 08.12.2011 15:18, eleanor wrote:
>> Hi.
>>
>> I would like to know if there's a way with duplicity to check if
>> backup is required - that is to check if there are any
>> modified/deleted/added files in the chosen directory.
>>
>> The command that I'm using now is:
>>
>> # duplicity --dry-run --ssh-options /home/testing
>> scp://address@hidden/backup/testing
>> GnuPG passphrase:
>> Local and Remote metadata are synchronized, no sync needed.
>> Last full backup date: Thu Dec  8 15:03:51 2011
>> --------------[ Backup Statistics ]--------------
>> StartTime 1323353254.65 (Thu Dec  8 15:07:34 2011)
>> EndTime 1323353273.39 (Thu Dec  8 15:07:53 2011)
>> ElapsedTime 18.74 (18.74 seconds)
>> SourceFiles 93438
>> SourceFileSize 11116428 (10.6 MB)
>> NewFiles 0
>> NewFileSize 0 (0 bytes)
>> DeletedFiles 0
>> ChangedFiles 0
>> ChangedFileSize 0 (0 bytes)
>> ChangedDeltaSize 0 (0 bytes)
>> DeltaEntries 0
>> RawDeltaSize 0 (0 bytes)
>> TotalDestinationSizeChange 0 (0 bytes)
>> Errors 0
>> -------------------------------------------------
>>
>> In this output se can see that the files have not been
>> added/modified/deleted - which is probably written in the local
>> indexing file - used by duplicity.
>
> --dry-run is the option for this use case, duplicity does not have an
> indexing file. what do you mean by that?
>
>> The problem with this is that the local directory has 310MB of data
>> and the data is not synchronized. How can I check whether the data is
>> actually in sync or not.
>>
>
> what is the problem with using --dry-run?
>
> ede/duply.net
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>