Maser Posted December 8, 2005 Report Share Posted December 8, 2005 Is there a way to do this? The reason I ask is that I used Disk Utility to do a "File copy" restore from one OSX Server HD to another. When I reset my ACLs, all those acl-set files wanted to be backed up again. If I restore a previously-acled file that's backed up, an "ls -le" doesn't say the file has any acls on it. Unless I'm doing something wrong here? Is there a way to glean ACL information from backed up files? Link to comment Share on other sites More sharing options...
CallMeDave Posted December 9, 2005 Report Share Posted December 9, 2005 Quote: If I restore a previously-acled file that's backed up, an "ls -le" doesn't say the file has any acls on it. I don't have any experience with ACL's yet, but how you Restore would probably matter. Were you doing "Restore an entire disk" when you tried this? Dave Link to comment Share on other sites More sharing options...
Maser Posted December 9, 2005 Author Report Share Posted December 9, 2005 No -- I just restored a file. Which I didn't think would actually show this, but... Is there a way to view something in a report that shows this? Link to comment Share on other sites More sharing options...
CallMeDave Posted December 10, 2005 Report Share Posted December 10, 2005 Have you read the ACL section of the 6.1 Read Me file? I'm not sure about Attribute Modification Dates; likely something new in HFS+ (and I'm not in a place to research it right now). It's doubtful that any new interface elements have been added to Retrospect to display these (since so little new interface elements have been added to Retrospect since, like, 4.3). "... if you are backing up a file that was backed up previously, and you modify the ACLs on that file (but make no other changes to it), the only way for Retrospect to know that the file is different (and therefore should be backed up again) is by looking at the attribute modification date..." snip This might explain the behavior you saw: "Any time you copy a file with extended attributes or ACLs to a volume (for example during a restore or duplicate operation), the volume incorrectly sets the attribute modification date to the current date and time. This means that Retrospect will copy all files with extended attributes or ACLs during the first backup after a restore and during every duplicate operation, since the attribute modification dates will no longer match. Apple has been notified of this issue and is working to resolve it." Link to comment Share on other sites More sharing options...
Maser Posted December 16, 2005 Author Report Share Posted December 16, 2005 This might explain the behavior you saw: "Any time you copy a file with extended attributes or ACLs to a volume (for example during a restore or duplicate operation), the volume incorrectly sets the attribute modification date to the current date and time. This means that Retrospect will copy all files with extended attributes or ACLs during the first backup after a restore and during every duplicate operation, since the attribute modification dates will no longer match. Apple has been notified of this issue and is working to resolve it." That was it. I used Disk Utility to "restore" a disk image from one disk to the other -- using the "file copy" method as there was some problem with a "block copy". The time stamp on those files *were* changed on this. Unexpected, it was! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.