Norm Posted February 5, 2008 Report Share Posted February 5, 2008 I back up my wife's Mac over our ethernet network. We both have non-Intel Powerbook G4s. I'm running 10.4.10. Using Retrospect 6.1.126 My wife just upgraded to Leopard. Since the upgrade the time to Duplicate has gone up considerably. Yesterday, she did not use her Mac at all and the Duplicate was 19974 files, 182 MB, and took 1:24 hours. I have it set so I think it only Duplicates that which changes. Set to "Replace Entire Contents". Is there a reason for the lengthy time and number of files now that she is on Leopard? Thank you for any education on this. Appreciate Quote Link to comment Share on other sites More sharing options...
rhwalker Posted February 5, 2008 Report Share Posted February 5, 2008 Leopard's overhead is higher. Also, FYI, you should update your copy of Retrospect for the Leopard-compatible one. Updates are here: http://www.emcinsignia.com/supportupdates/updates/#UPDATETYPE8 See also: http://kb.dantz.com/article.asp?article=9628&p=2 Russ Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted February 5, 2008 Report Share Posted February 5, 2008 Quote: I back up my wife's Mac over our ethernet network. You don't specify that the Leopard machine is running Retrospect Client software; is it? Note this Note included in the Read Me-Retrospect.html document, that is installed in the same folder as the application: NOTE: 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 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. You should turn of the "Use attribute modification date when matching" option for your Duplicate operations. Dave Quote Link to comment Share on other sites More sharing options...
Norm Posted February 6, 2008 Author Report Share Posted February 6, 2008 Thanks. I'll check that out. Assume I can still use the new version on my Tiger Mac while installing a revised/updated version on the Leopard Mac. I'll read what it says. Hopefully it won't confuse the easily confused. Appreciate that tip. Quote Link to comment Share on other sites More sharing options...
Norm Posted February 6, 2008 Author Report Share Posted February 6, 2008 Yes the Leopard Powerbook is running Retrospect Client software. It shows that it has 6.1.130. I'll go looking for that setting. Not sure where I find it but assume it is in preferences. I remember, well don't remember all of it, a conversation with Retrospect (Dantz then) about how it was preferential in Backups to set it to the new dates. I wasn't convinced but can't remember their reasoning. Here, however, I'm and I believe you are only talking about the Duplicate process. Thanks for the help. Quote Link to comment Share on other sites More sharing options...
Norm Posted February 6, 2008 Author Report Share Posted February 6, 2008 Will I miss anything by turning off: "Use attribute modification date when matching" I don't pretend to know what it means. And I don't know what extended attributes and ACLs are. Thanks for any help. Appreciate Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 7, 2008 Report Share Posted February 7, 2008 If a file's attribute modify date changes, but no other criteria changes, then Retrospect will fail to re-copy the file. In most cases this isn't a big deal. Quote Link to comment Share on other sites More sharing options...
Norm Posted February 10, 2008 Author Report Share Posted February 10, 2008 Thanks. If a file/folder's date actually does change due to a modifcation to that file, will file be Duplicated if I change this preference setting on my wife's Duplicate process? Appreciate the help. Quote Link to comment Share on other sites More sharing options...
Norm Posted March 10, 2008 Author Report Share Posted March 10, 2008 And this would work the same on Tiger? Thanks from a beginner Quote Link to comment Share on other sites More sharing options...
Norm Posted March 10, 2008 Author Report Share Posted March 10, 2008 And the update will work if the Client is on Leopard and Retrospect on Tiger machine? Thanks for info Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 10, 2008 Report Share Posted March 10, 2008 The OS shouldn't matter. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted March 10, 2008 Report Share Posted March 10, 2008 And the update will work if the Client is on Leopard and Retrospect on Tiger machine? There appear to be some unfixed Apple bugs in Leopard that can cause improper operation of Retrospect if ACLs are enabled on a volume for the Universal Binary version of Mac OS 10.4.x (server or non-server) and for Mac OS 10.5.x (server or non-server, because all Mac OS 10.5.x is Universal Binary). If this problem is seen in your configuration, you can work around it until Apple fixes the bug by disabling ACL backup in Retrospect 6.1.138. See: KB article re ACL bug workaround Contrary to what the KB article says, I believe that the problem exists on all Universal Binary MacOS 10.4.x and 10.5.x regardless of platform. The effect of this workaround is that some ACL metadata will not be backed up. Russ Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.