[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rdiff-backup-users] ACLs
From: |
Grant |
Subject: |
Re: [rdiff-backup-users] ACLs |
Date: |
Sun, 21 Jul 2013 12:07:50 -0700 |
>>>> Will rdiff-backup save and version ACLs? I'm hoping to use rsync
>>>> --fake-super to preserve ownership and permission info in ACLs and
>>>> then create an rdiff-backup repository from the rsynced files.
>>>
>>>
>>> Well it is certainly meant to, but I have always used it with the
>>> --no-acls option. If you don't use this option, it should save
>>> acls, and I presume it does...
>>>
>>
>> Just note (from http://www.nongnu.org/rdiff-backup/features.html):
>>
>> ACL and EA support: If rdiff-backup can find the pylibacl and pyxattr (mac
>> version) modules, and if the file system supports these features,
>> rdiff-backup
>> will preserve Access Control Lists and user-level Extended Attributes.
>> ACLs are
>> not supported, however, on Mac OS X or Windows as those systems do not use
>> standard POSIX.1e access controls.
>
>
> ACLs and extended attributes are stored in separate metadata files in the
> rdiff-backup-data directory and do not depend on the underlying file system
> for the mirror having support for those attributes. You can delete those
> attributes from the mirror, and they will still be restored correctly based
> on the metadata files. _Restoring_ a file with ACLs or extended attributes
> of course depends on the destination file system supporting them.
To be sure I understand, the requirements in the nongnu.org quote
above only apply to restores?
Will ACLs/EAs be written to the files themselves in the case of the
most recent copy in the repository?
- Grant