duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Re: Copied files, all modified now.


From: edgar . soldin
Subject: Re: [Duplicity-talk] Re: Copied files, all modified now.
Date: Sat, 15 Jan 2011 23:59:40 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7

first of all. can you proof that _all_ files are identical? please do so on 
commandline and show the output please.

also, what is duplicity status telling you about the copied repository? is that 
identical to the state against the original repository? please copy and paste 
that here as well.

ede

On 15.01.2011 23:25, Jeff Cook wrote:
> On Sat, Jan 15, 2011 at 3:08 PM, Jeff Cook <address@hidden> wrote:
>> I copied all of my files locally from a Windows server to a Linux
>> server. Duplicity is going through its first run on the Linux server
>> at the moment (with --allow-source-mismatch), but it is marking almost
>> every file modified. Is this because of metadata/chmod type changes?
>> The data is mostly identical, but somewhat big tars are getting
>> uploaded. Would this metadata change throw some stuff off?
>>
>> Also, it may just be that some of these weren't allowed to be uploaded
>> by Windows, so that's part of the problem potentially. But right now
>> I'd just like to minimize the transfer where possible, so I want to
>> know of any potential problems with this.
>>
>> From
>> Jeff
>>
> 
> I've just done a dry-run which shows 25GB in changes (on a 50GB set).
> This is incorrect, as I copied the files and rsync'd them back and
> forth a couple of times between the two local servers. How can I get
> duplicity to only catalog the useful changes, instead of uploading
> 25GB in "changed" files?
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk




reply via email to

[Prev in Thread] Current Thread [Next in Thread]