Jump to content


  • Posts

  • Joined

  • Last visited

jwarthman's Achievements


Newbie (1/14)



  1. Dave & Russ, That's very good feedback, thank you! Fortunately, my backup set & catalog are intact on an external Firewire drive, so a catalog rebuild shouldn't be needed. The comment about preflighting the Restore Entire Disk is also right-on. I've discovered that I can do this rather than wast time doing a restore, only to discover some of the expected files are missing. Tonight when I get home I'll look more closely at snapshots. The difference between a snapshot and a session isn't clear. This backup set has 56 sessions and two snapshots. Honestly, I'm not sure what I did that "caused" the snapshots! But I now understand from your comments that the most recent snapshot probably omits some key files, for some reason. So I need some way of identifying all files on the backup set that are NOT part of that snapshot. Hopefully it's a small number, and won't include all the old versions of all the files in the backup set. :-) Thanks! -- Jim
  2. After re-reading my post, I see that I can simplify my question. Does the "Files Chosen" list show all files available to backup, with check marks to indicate the ones that were selected? If that's the case, then why would some files appear in the list when doing "Search for Files and Folders" but not when doing "Restore Entire Disk"? Thanks! -- Jim
  3. While I've made progress, I still have not gotten a successful restore. I think we've had several threads intermingled here, resulting in some confusion. Let me add some detail that will help you understand what I've done (and am doing). * Powermac G5 with OSX 10.4.7 (not 10.4.6 as posted earlier). * Retrospect 6.1.126 / RDU * Nightly backup to a backup set (56 sessions) on external Firewire drive To restore my corrupt boot drive, I followed a procedure that used to be recommended by Dantz, but seems to no longer be recommended. That is, I boot from a separate drive, reformat the corrupt hard drive, reinstall the OS and upgrade to the version that was last backed-up with Retrospect. After several restarts (some of which involve booting to the volume with the newly-installed OS) I restart once again on the separate drive and launch Retrospect to do a restore. As far as I can tell, I am NOT doing a live restore. Here's where the confusion (and problems) begin. Retrospect offers several choices for how to restore the entire hard drive, and the documentation is unclear about which to choose. It seems likely that several of these choices do the same thing: Restore > Restore Entire Disk > Restore Entire Disk Restore Entire Disk > Replace Corresponding Files Restore Entire Disk > Retrieve Files and Folders Restore Files from a Backup > Restore Entire Disk Restore Files from a Backup > Replace Corresponding Files Restore Files from a Backup > Retrieve Files and Folders et al. When I use Restore > Restore Entire Disk > Restore Entire Disk, some files are NOT restored! For instance: com.apple.dock.plist loginwindow.plist These were obvious omissions because they cause my dock to revert to default, and no applications launch at startup. I suppose many other files are not being restored. Okay, I was able to confirm that these two .plist files ARE on the backup set. I used Restore > Search for Files and Folders, and easily located the files. Not only that, I was able to restore these files the same way. But I didn't keep that restore because I'm still searching for a method to restore everything, so I don't need to wonder what other files might be missing. The thing is, when I view the "files chosen" for restore, none of the other restore methods listed above contain these .plist files! Why would these files show up with Search for Files and Folders, but not, for instance, with Restore Entire Disk? Long story short, I have not restored my drive as yet, since I cannot know what files will be missing. On an earlier attempt, I simply reformatted the corrupt boot drive and, while booted on the separate drive, used Retrospect to restore the entire disk. The results were the same - some files (notably com.apple.dock.plist) were not restored. I'm willing to try this method again and keep more detailed notes. Regarding Snapshots... I have two snapshots on the Backup Set, and have been using the more recent. It's not clear to me if all these Restore methods treat snapshots the same. In any case, if anyone can shed light on why these .plist files only SOMETIMES show up in my list of files to restore, I'd love to hear about it! Best Regards, -- Jim
  4. First of all, thanks *very much* to the folks here, and to Dr. Smoke on the Apple forums for pointing me in the right direction! * I booted on my "backup system". * Great news: I looked at my backup set and found many versions of the .plist files (loginwindow.plist and com.apple.dock.plist). * I restored the most recent versions using Restore > Search for Files & Folders > Replace Corresponding Files. * I restarted, and my dock & startup applications were back to normal! Again, thank you, thank you, thank you! But now to the troubling questions. I mentioned that my dock and my startup items were two issues that I noticed right away after restoring my hard drive. I've just demonstrated that the backup *does* contain the relevant .plist files, and I was able to correct the problem. The key questions now are: 1. Why didn't those files get restored the first time 'round? 2. What other files haven't been restored due to the same factor(s)? I really, really want to identify the root cause of this problem, then perform one more *successful* restore so I don't need to worry about the integrity of my system, and about potentially lost data. So, I'm open to further suggestions regarding why these .plist files (and who-knows-what other files) didn't get properly restored. Or perhaps they DID get restored, but for some reason couldn't be used and got replaced with generic default versions. But then, my partial restore tonight succeeded.... *sigh* Enjoy! -- Jim P.S. - Apologies if this bothers anyone, but I plan to cross-post this to the Apple forum, since it appears to get a somewhat different set of users.
  5. Dave, Thanks much! Okay, for a bit more clarification... The Retrospect User Guide says, on p. 53: Quote: Replace corresponding files copies the marked files to the destination volume into the same folders. Corresponding files are overwritten, even if they are newer. Retrospect leaves files untouched if they are identical to files marked for restore or if the file names do not match those marked for restore. At first blush this seems clear. But upon closer scrutiny, don't the phrases "corresponding files are overwritten" and "Retrospect leaves files untouched if they are identical" seem to conflict? If someone knows what's really happening, I'd love to hear about it! Thanks! -- Jim
  6. Quote: Retrospect will Match files in the Destination that it sees as being identical to the ones in the Source. Matched files will be left in place. Dave, Thanks for the clarification. Quote: The idea of installing an OS first is for when you have to boot into that OS; what you're doing does not require that step, and I wouldn't recommend it. I understand. And yet, when I've done this in the past it has worked flawlessly. But yesterday when I tried just reformatting the drive then restoring from the backup, weird things happened. I'd still appreciate some thought as to what might not have been (properly) restored that would cause my Dock to revert to default. Thanks! -- Jim
  7. Coincidentally, I'm wrestling with a similar issue. My boot drive became corrupt, and I had confidence that I could put things back the way they were using Retrospect. (I've done it several times before.) But for some reason, this time isn't going so smoothly. I should add that I'm running Retrospect 6.1.126 under OSX 10.4.6. My backup set is on an external Firewire drive, and I'm running from a separate drive that has Retrospect installed. First attempt, I reformatted the corrupt drive, re-installed the OS and applied updates. (One anomaly, I think I didn't specify exactly the same user name when the installer set up my account). I did the restore using "Replace corresponding files", but when I restarted I could NOT login! Oops! Probably an operator headspace malfunction. Second attempt, after reading through the user guide, it seemed like, as long as I can boot on a volume that has Retrospect (similar to the emergency Retrospect CD), I can just do the restore. I did, using "Restore entire disk", and it seemed to go well, except that when I boot on the restored volume, many preferences are gone!!! For instance, my Dock is no longer customized, and neither is the menu bar. So my first question is, what things could cause the Dock et al. to revert to some default condition? (In the past, the restore has restored my Dock.) Second question, won't a "Restore Entire Disk" overwrite ALL of the OS files, and delete whatever isn't part of the backup set? If so, what's the point of re-installing OSX first? So, if I've reinstalled OSX, exactly which restore strategy should I use (I'm booted from a separate volume that has Retrospect)? I'm in the midst of trying to get things back to normal, so I really appreciate your feedback! Enjoy, -- Jim
  8. Indeed, I share the sentiments of the first and last posters in this thread. I have enthusiastically recommended Retrospect for the Mac for years. But now, it's as if the company is just milking a good thing, paying lip service to new features but making no investment - or so it seems. It's very disappointing. Perhaps someone in authority will comment. -- Jim
  9. Nate, Thanks for the reply. I have a TiBook that's nearly 3 years old, but the clock/calendar haven't had any problems. After a restart, they're still showing the correct date & time - and yet Retrospect launches twice when the timed backup happens. I don't believe it's a problem with my pram battery. Best Regards, Jim
  10. Well, I thought I'd found an important aspect to this issue, but still no comments from Dantz. Clearly others are having the same issue, yet Dantz appears silent. This is disappointing.
  11. Okay, it's been two weeks since I posted my experience, and still no answers. I have a bit more information. I have observed that, for me, this problem ONLY happens the first time Retrospect runs a scheduled backup after the Mac is restarted. To recap, Retrospect launches and starts its backup, and then a second copy of Retrospect launches (with a second icon on the dock), and both copies of Retrospect seem to read/write into one log file. That is, the log file seems to contain interleaved lines from the two copies of the program. See my posting, above, for an example. Clearly this is a problem that multiple people are having. I hope Dantz is working on this. Thanks! -- Jim
  12. I'll chime in as another (long-time Retrospect user) who is having this problem. I have a script scheduled to run at 12:01 AM. I have my Unattended preference set to "Stay in Retrospect" so I can see what happened in the morning. Often (but not always!) I have two copies of Retrospect running in the dock in the morning. When this happens, I get the "catalog is locked error". Here's an example from this morning's log: ? Retrospect version 6.0.193 automatically launched at 8/15/2004 12:01 AM ? Retrospect version 6.0.193 automatically launched at 8/15/2004 12:01 AM + Retrospect Driver Update, version 5.2.101 + Normal backup using Primary Backup at 8/15/2004 12:01 AM To backup set Macintosh HD Backup… - 8/15/2004 12:01:46 AM: Copying Macintosh HD… + Retrospect Driver Update, version 5.2.101 + Normal backup using Primary Backup at 8/15/2004 12:01 AM Can't add to backup set Macintosh HD Backup: The catalog is locked. 8/15/2004 12:01:54 AM: Execution incomplete. 8/15/2004 12:52:47 AM: Comparing Macintosh HD… Notice that two copies of Retrospect started, and one appeared to perform the backup, the other failed with the error. Log entries from both copies are interspersed, which is interesting. I'm running on a TiBook 667, OS X 10.3.5, and Retrospect version 6.0.193. I'm anxious to solve this problem, and welcome all questions and comments! Enjoy! -- Jim
  13. Once again, this isn't going well. I was able to partition the internal 80 GB drive into a big and a small partition. Then I installed 10.2.3 on the small partition, followed by Retrospect 5.0.whatever. I made sure the big partition was wiped clean, and used Retrospect to "Restore Entire Disk". The restore went fine, and finished after about 4.5 hours with no errors or warnings. I used the Sytem Preferences to select the big partition as the startup device, and rebooted. Unfortunately, I get the same symptom: Shortly after the chime, with the spinning thing in the bottom center part of the screen, it stops spinning and I get a "prompt in the upper left corner of the screen. The prompt says "sh-2.005a#". So, it appears that Retrospect is doing something wrong, either when it backed up my 10.2.8 system to start with, or when it restores it. I was hoping the problem was a glitch of some sort when Retrospect tried to overlay the restored OS "next to" the currently running OS, but apparently this wasn't the problem. The good news is, I can boot on the smaller partition and examine the files and directories on the big partition. Can anyone suggest what might be corrupted here, or how to fix it? I suppose I could once again do an "Archive and Install", but I'd really prefer to make this work without that, since I know from earlier today that my system won't be totally "back to normal" if I do that. I wonder if a different "flavor" of installing 10.2.8 with the Combo Updater would just "refresh" the OS on my big partition, but leave my settings in-place? Best Regards, Jim
  14. Dave, Great reply, thank you! Yes, I noticed the strange "performance" numbers too. And it happened both times. Yet, when I watched the restore, I was seeing performance ~100 MB/sec as you suggested. Go figure. I do have a bunch of large TIFF files in the backup set, so perhaps they're skewing the numbers. I just finished trying something suggested in a different forum. I did an Archive & Install (and discovered it's 10.2.3, not 10.2.6) and it seemed to work after a fashion. It seemed to retain my applications and my data, yet Entourage lost track of my identity, and many (not all) of my Dock icons and settings were lost. In any case, I think next I'll follow your advice, with a twist. I'll install OS X to a separate partition on the TiBook's internal drive, and then "restore entire disk" to a "clean" partition. Does that make sense? It might be a bit slower than booting from an external FW drive, but Probably not dramatically slower. As soon as Retrospect 6 is shipping, I'll probably purchase the upgrade. Thanks! -- Jim
  15. I thought I might have issues with the OS 10.2 installs, so I decided to try again. I was very careful this time, but Retrospect still failed to properly restore my startup drive. When I boot, it automatically drops into "single user mode", and I get a prompt. I installed 10.2.6 (?), then restarted and ran Disk Utility to set file permissions. Then I restarted into single user mode and ran fsck. Then I installed 10.2.8 using the Combo updater. Again I restarted, ran Disk Utility to repair file permissions, and restarted into single user mode to run fsck. Next I installed Retrospect 5.0.238. Once again I ran Disk Utility to repair file permissions. Then I told Retrospect to "restore entire disk". Again, it took over 4 hours and completed with no errors or warnings: + Executing Restore from Backup at 1/23/2004 10:28 PM To volume Macintosh HD… - 1/23/2004 10:28:26 PM: Restoring from Backup Set A1… 1/24/2004 3:00:54 AM: Execution completed successfully. Completed: 144499 files, 33.0 GB Performance: 0.1 MB/minute Duration: 04:32:28 (07:02:33 idle/loading/preparing) I took a couple screen shots and copied & pasted the retrospect log into a file using TextEdit. I saved all three files to my external Firewire drive, just in case. I noted one strange thing. After I saved the file from TextEdit to my FireWire drive, and quit TextEdit, I seem to have "lost" all my fonts. For instance, all my menus were "blank". I couldn't get the TiBook to restart, so I ended up holding down the power button. I may have mentioned that Dantz doesn't want to discuss this unless I pay $70. They *did* suggest that I try downloading the trial version of Retrospect 5.1 and see if that helps. Unfortunately, the buttons for downloading 5.1 don't seem to work. Now, I've been a Dantz customer for years and years - probably since Retrospect 1.0. I have bought many Dantz products, and currently own the "Workgroup" version. I'd like to think I've been a good customer and an advocate of Retrospect on various message boards. I guess that's part of my disappointment here. Anyway, I'd certainly like to discover and correct "the problem" using single user mode, so I don't have to go through the many hour exercise that I described above. If anyone has suggestions, I'm all ears! Enjoy! -- Jim
  • Create New...