duplicity-talk
[Top][All Lists]
Advanced

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

Re: [Duplicity-talk] best practices for handling hard links


From: Marc Evans
Subject: Re: [Duplicity-talk] best practices for handling hard links
Date: Mon, 17 Nov 2014 19:12:34 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

Yeah, I did find this thread:

http://lists.nongnu.org/archive/html/duplicity-talk/2008-08/msg00044.html

but alas the zip file it refers to is no longer there, and the wayback
machine does not seem to have it either. Any pack rats out there, or
should I create my own?

It does surprise me that this was a know limitation back in 2008 and it
still may exist in the code base today.

- Marc

On 11/17/14 1:43 PM, Kenneth Loafman wrote:
> A while back someone on the mail list wrote a script to help with this. 
> Some searching may be needed. 
> 
> ...Ken
> 
> On Nov 17, 2014 6:12 AM, "Marc Evans" <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     Hello,
> 
>     I am trying to determine what the current state of hard link handling is
>     for duplicity, and then assuming that my belief is correct, that hard
>     links are not preserved by duplicity, I would like to understand what
>     current best practices are?
> 
>     Background: I have about 26TB of raw data that I am backing up to the
>     cloud via duplicity. Once it is encrypted, etc, it consumes about 48TB
>     in the cloud, which includes 1 full backup plus daily incrementals
>     spanning a 1 month period. With the data is considerable files that are
>     highly compressed as well as thousands of hard-link files.
>     Experimentation is finding that the hard-link files are getting stored
>     multiple times, and further when restored the hard links are not
>     preserved.
> 
>     Based on my reading of the mailing list archives my observations seem to
>     be confirmed, though that is in years-old threads. I see in the code
>     various pieces that are hard link oriented though. I also see discussion
>     of special casing hard link handling at duplicity invocation, such that
>     excludes are used to insure that only one copy is actually backed up and
>     a hard link manifest is generated that can be used by scripts to restore
>     hard links.
> 
>     Given the above, what is the state of hard link handling and what are
>     current best practices for dealing with them?
> 
>     Thanks in advance - Marc
> 
>     _______________________________________________
>     Duplicity-talk mailing list
>     address@hidden <mailto:address@hidden>
>     https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 



reply via email to

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