Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About marhk

  • Rank
    Occasional Forum Poster
  1. Interestingly, it worked - done once in manual mode. Down the road - we'll see? Before I excluded this file (on all backups not just duplications of Leopard) it would fail. Some other features are that it seems to take 50% longer vs. 10.4.10 for a duplication. Upon starting up from the duplicated drive all went well. The fascinating thing to me is at first trying to decide which disk it actually started from. The right upper corner is no longer respected in Leopard for the startup drive. Time Machine works as expected. Upon opening the Time Machine, all of the old backups of the source drive are there and available. (I have the duplicated drive excluded from TM in the source disk TM prefs) So, these TM files of the source drive can be used if I ever have to jump to the duplicated backup drive. Sounds too simple - I agree - but, so far it works. I still think there should be a simple button in the backup choices of Retrospect to choose this, however. (More Leopard friendly. ;-)
  2. Thanks for the reply! You are so right! My mistake. There obviously is a way to select/exclude a file by name (i.e.; .com.apple.timemachine.supported) I did this and so far a duplication process manually started seems to be going OK. What I’m doing is simply duplicating one internal hard disk to another in a PPC machine. Time Machine is active on the main drive to an external firewire drive. marhk
  3. Under 10.4 I had an auto duplicate operation set up that worked well to provide an alternate bootable disk. After upgrade to 10.5.1 duplicate won’t work because of Time Machine issues. Log = {Can't write file “.com.apple.timemachine.supported”, error -42 (too many files open), path: “Christine/.com.apple.timemachine.supported”. Trouble writing files, error -42 (too many files open).} OK, that has been explained before - but, how do I exclude this file during a duplication procedure? File selection doesn’t work during a duplication process and, unless things have changed recently, I have never been able to achieve a bootable disk using an archive and restore procedure (too involved anyway - duplication is what I need). What is needed is a selector under the OPTIONS button to exclude Time Machine files during a duplication operation. What am I missing? Marhk
  4. What is needed in this app is a straight forward way to restore one computer from another. I recently experienced the sudden unexpected failure of my TiBook hard drive- weird scraping noise, no drive!. Dirt Cheap Drives sent me a new one the next day. The install was easy. But what to do then? I had 2 backups on firewire drives at my desk top computer, but moving the entire drive’s info was something that I haven’t done since OS 9 days. It used to be easy! It should be now! I set the TiBook up as a Firewire Target drive and used the replace all option in the latest version of Retrospect (OS 10.3.5) to move all files to the drive. I had high hopes as the process ended copying the info and seemed to be configuring the files. When it finished I rebooted - no dice! Drive not even seen. Following that I faced about 8 hours of Archive and Install using 10.3 system discs - then reinstall 10.3.5 combo - then reconfigure, find files, reinstall important utilities and finally fully reinstall the TechTool edrive (which wasn’t backed up and actually has proven useful for away-from-home crashes). I see no reason, considering the cost, why Retrospect can’t be engineered to recover from this type of crash in one step. As a small business user this fatal whole-disk type of crash is why I use backup software. I look forward to the new owner‘s efforts toward making this app easier to use and specifically directed at recovery from anticipated situations like I just experienced.