Jump to content
ggirao

Propogating Permissions Triggers Full Back-Up

Recommended Posts

Open thread in 8, happens the same to me.

 

Today in my diary backup is tries to do full 2,2TB.

Share this post


Link to post
Share on other sites

Changing permissions, attributes, or timestamp of a file causes Retrospect to consider it a new file.

 

Propagating permissions touches the permissions of all files and folders in the directory. Unfortunately, you'll need to wait for this one to complete.

Share this post


Link to post
Share on other sites

I've never quite understood why changing the metadata on a file (permissions, attributes etc) and not the last write time causes the whole file to be backed up, rather than just backing up the new attributes.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×