-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't use rsnapshot so I don't know if it can handle that or not but
doing an mv will not disrupt the hard link structure itself.
On 01/04/2014 03:18 PM, Charles Marcus wrote:
> On 2014-01-01 1:12 PM, Kevin Korb wrote:
>> The easiest solution is to
On 2014-01-01 1:12 PM, Kevin Korb wrote:
The easiest solution is to just do the same chmod on the most recent
backup before running the next backup.
Hi Kevin,
This worked perfectly, and my shiny new server is now live, so thanks
very much.
I have a related question though...
I want to con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/02/2014 09:53 PM, Dan Stromberg wrote:
> First off, thanks much for your suggestions.
...
>> First, a new column for the old cp -al then rsync on top of it
>> method that --link-dest mostly replaced. It is slower since all
>> the hard links get
First off, thanks much for your suggestions.
On Thu, Jan 2, 2014 at 6:19 PM, Kevin Korb wrote:
> First, a new column for the old cp -al then rsync on top of it method
> that --link-dest mostly replaced. It is slower since all the hard
> links get made and then some get replaced or deleted but it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Interesting list. I have a couple of suggestions I can offer...
First, a new column for the old cp -al then rsync on top of it method
that --link-dest mostly replaced. It is slower since all the hard
links get made and then some get replaced or dele
On Wed, Jan 1, 2014 at 10:09 AM, Charles Marcus
wrote:
> If I change the permissions on the source maildirs, will this cause
> everything to be transferred again? Meaning, will rsync see everything as
> 'modified', thus creating a new copy of the entire mail store on the backup
> target?
>
> Or wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yep, if you change 1 you change the hard links in all of them.
On 01/02/2014 06:09 AM, Charles Marcus wrote:
> On 2014-01-01 1:12 PM, Kevin Korb wrote:
>> The files will not be transferred but they will be stored
>> separately as new versions of the
On 2014-01-01 1:12 PM, Kevin Korb wrote:
The files will not be transferred but they will be stored separately
as new versions of the file even if the content is the same.
Ok, so, 'stored separately' = take up additional space? which is what I
want to avoid.
Permissions are per inode not di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The files will not be transferred but they will be stored separately
as new versions of the file even if the content is the same.
Permissions are per inode not directory entry so you can't have old
and new permissions without breaking the hard link rel
