Jump to content

Propogating Permissions Triggers Full Back-Up

Recommended Posts

  • 3 weeks later...
  • 2 weeks later...

I have noticed this too. Propagating permissions, when I do it, is usually done just for thoroughness, when a user reports he can't access a single file he needs and it turns out to be a permissions issue. So my workaround for Retrospect is to manually fix the individual file, spot check others in the same directory etc., instead of propagating.


If permissions change, I do want Retrospect to record that change, back it up. The problem is that it backs up even cases in which nothing was changed. My guess is that at the OS level the metadata gets a new change timestamp (or whatever) when permissions are propogated regardless of whether anything was actually changed. If that's true there's not much Retrospect can do about it.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...