Jump to content

FarmerDave

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About FarmerDave

  • Rank
    Occasional Forum Poster
  1. I've had poor luck, since this original incident. I can almost guarantee a corrupt storage set if I add to it (do an incremental backup). I've also had more than one instance of doing a brand new backup, that would not restore & boot. Frustrating indeed.
  2. OK, well it worked by making a new backup, and restore. Thanks for that. On the one hand, I'm happy that I can get back to a good boot drive in less than an hour, but on the other, I'm pretty frustrated that Retrospect never gave me any indication the backup was bad. I did 15 or so sessions/snapshots, with verification ON, every time. It always verified, so I had no clue the backup was bad, until I went thru this ordeal of trying to restore. I'm glad I tested it now, because in 6 months when I went to restore, I would have been pretty upset. After this experience, confidence in backups will always be shaky, but at least I know I can get this boot drive back again. Thanks again for the tips, and for checking that my steps were OK. When things aren't going right, it seems like everything can be a potential problem.
  3. Quote: CallMeDave said: Quote: I can't be the only one this is happening to. Why not? It's obvious that the Snapshot of your boot drive is not going to Restore. No idea why, but continuing to try isn't going to change the fact. I think you're right , but I had to go thru the stages to arrive at this conclusion. One would think that retrospect would've informed me of some mismatch somewhere along the way, but it didn't. Quote: As I suggested in my previous post, have you attempted to do a clean, fresh, new backup, to a new File Backup Set, and to use _that_ as the Source for a new Restore test? Steps 1-7 are completely valid. Step 8 is unnecessary, but shouldn't have hurt. I've done this (1-7) scores of times and it works. I'm guessing that something in the process you used to make the backup went wonky. Dave I'll do as you suggested here & before. Thanks for the input on the validity of the steps.
  4. After numerous attempts to restore this drive, I'm at a loss. I can't think of anything else to try. The basics most certainly don't work, so there must be some obscure step I'm missing, or the possibility that retrospect 5.x simply doesn't restore bootable OSX volumes. So with this in mind, I have some questions/thoughts. (Since these aren't documented as being a problem anywhere.) 1 - My backup is of a 10G partition on an internal drive (that is in good working condition), System 10.2.8, to a file (no compression). 2 - My intended destination/restore, is an erased 10G partition on a firewire drive. ** any problem with this so far? This should be doable right, or is the system utterly not transferable? 3 - The backups were made, while actually booted on the drive being backed up. 4 - Retrospect's prefs are at the default (OSX warning for permissions is set to "warn") 5 - The backups were all set to "verify", and verification always came up successful. (not counting the Retrospect Log file itself, which often fails in the verfiy) 6 - Backup filter was set to "All files", so I shouldn't be missing any files. 7 - Permissions were always set to be used, on the drive being restored. 8 - Permissions were repaired on the restored drive. What the heck is wrong with this scenario?? Why is this so impossible? I bought Retrospect to provide security & save time, but it's doing nothing but costing me time & money. So far the backups & restores I've made are useless (apparently), and I'd have to start from scratch with the CD's if my drive broke down, so what's the point? I can't be the only one this is happening to.
  5. OK, just tried it again, same result. 1 - Erased the destination firewire partition with Disk Utility. 2 - Used "restore entire disk". 3 - Restored the snapshot of 10.2.8. (making sure "Ignore privileges" was OFF) 4 - Says restore completed succesfully. System is available to select as a boot disk, but won't boot. I get the gray circle with the line thru it. This is the way it's supposed to be done right?? So what am I missing??
  6. I agree, it does sound like I'm trying too hard, but it's only because I've not been able to EVER restore an OSX System with Retrospect. The steps you mention, are exactly the way I've done this. The backup media is a Mac File, on one of my internal drives. The reason for so many increments in the backup, is in case somewhere along the way, something I'm using is problematic. It goes like this: Snapshots: 1 - Bare 10.2 2 - Bare system, upgraded to 10.2.8 using Software update 3 - A couple of navigational utilities, like Default Folder. 4 - My bare necessity "gotta have to work" apps, and authorizations. 5 - More things I like to use, like Graphic converter, etc. 6 - and so on & so on.... The incremental backup feature is the best thing about Retrospect, and I figure I could use this to minimize backup space, and be able to return to any state of the System "build". It can take hours to get to step 6, so why force myself to redo all that work? If I have a snapshot that can return me to that state, then that's a great way to use the backup. The first restore I tried, was to a freshly formatted drive, and according to retrospect, the restore was successful, but the system wouldn't boot off that drive. It would start, then I'd get the circle with the line thru it, meaning the drive wasn't bootable. So I delved into Retrospect manual, where it says you must first re-install the exact version of the Mac OS you're trying to restore, so I did that from CD, and ran the updates to 10.2.8. Then I did the restore (I was booted on another drive, so I was not restoring to the actual boot drive). I made sure that "ignore privileges" was OFF, on the destination drive. At that stage, the drive would boot, but numerous apps say they're missing system files, see pic: http://www.soundlog.com/ALF.gif I've tried repairing permissions on that drive, but it hangs about 1/3 the way through. Ran Diskwarrior 3 on it, and repairing permissions still hangs. This might be where the problem is, but how do I get around it?? and shouldn't the "Restore Entire Disk" put things back the way they were in the backup anyway?? Does the destination drive need to be named the exact way that the backed-up drive was? Is it a known problem restoring a system to a firewire partition? I know this seems like a lot of busy-work, and on the surface, this should be a simple process, but as you can see, in practice, it simply is a real chore. I think that it should be as simply as "Restore Entire Disk", but somewhere along the way, some critical data is not being put back correctly. It shouldn't be this hard.
  7. I've spent a large part of this week dealing with getting a fresh system install, and now that I have a good install of 10.2.8, plus all my needed apps & authorizations, I want to have a restorable backup of it. During this fresh system install to 10.2.8, I stopped every so often to do an incremental backup of the system using Retrospect 5,1. I'd repair permissions, then do a backup to a file. So at this point I have about 15 stages, with varying apps added to the clean install. I had Retrospect do a "compare", and comparisons verified the backups are accurate. The current 10.2.8 system is working fine, and I wanted to test this backup/restore theory. My boot partition is 10G, and I also have a 10G partition on a firewire drive, so I did a "restore entire disk", per Retrospect's restore instructions. The first time it didn't work, meaning I couldn't boot off the drive. So I installed 10.2 from the CD, and did the update to 10.2.8 (as per Retrospect instructions). Then I did the "restore entire disk" in Retrospect. Now, I can boot from the restored partition, but none of the apps work, saying they're missing "shared library" files of various sorts. So this restore is basically useless. I've seen retrospect recommended by power users, but this clearly isn't working, and I've tried before to restore OSX systems with no luck. I thought if I did everything by the numbers it would work, but it's not working. So I find myself with no restorable backup, which is entirely frustrating. What's the best procedure for making & restoring backups? And I mean FULL backups, with apps & authorizations, etc.. I want to back up this stable 10.2.8 partition, and feel comfortable that I can restore it, since it took several hours to get it back to this state.
  8. >>>>> The drive was being _incorrectly_ reported by the Operating System to be a removable disk drive. This was never a feature in Retrospect and cannot be considered moving backward. <<<< Re: moving backward: Well, in some sense, maybe not, but I never saw any warnings NOT to use Firewire as destination media, and since it worked, very well in my case, it was my sole basis for buying Retrospect 5. A bit presumptuous on my part, I suppose, but hey, there it was, and it worked like a charm! >>>>> In many cases, backing up in this method prevented users from having restorable data. <<<<< I've never had anything but excellent results (not arguing whether others may have encountered problems). It's been MUCH better, for me, than ANY tape mechanism I've used. >>>>> A hard disk is not a removable disk and should not be treated as such. <<<<< I swap Firewire drives between several computers several times a day without rebooting. So, regardless how the operating system reports it, Firewire is removable, and the devices are explicity advertised with this theory in mind, with all the "hot patching", "No reboot required", etc.. Unmount the disk, and unplug it. That's still removable, any way you slice it. At any rate, I'll say that this is a choice users should be allowed to make. In my case, I want to continue to back up to firewire, and as far as I can tell, the only reason the existing Retrospect software prevents me from doing so, is that OSX no longer sees the drive as removable. >>>>> We are looking at ways to span multiple hard drives. This functionality was recently introduced on the Windows product - but is not currently available in the Macintosh product, and there is currently no time estimate as to when or if it will be available. <<<<< Well, the easy suggestion has been made. Lift the requirement that a drive be removable, and we can continue to use it as before, right away. If there is some concern for using disks this way, then by all means put up several dialog "Are you sure?" boxes.
  9. Sorry, I can't get to that link at the moment. I'll try later. Can a file span multiple drives now? If so, then that might work, if not...... I'm talking about backing up multiple drives, currently at least (2) 100G, and (2) 160G, in the same set. Older versions could all see FW drives as backup media, so why should we move backwards? I gave up my tape drive, in favor of backing up (VERY reliably, & quickly) to FW drives. I currently span 6 Firewire drives (destination media) in my current backup set, and this is over a years worth of backing up. I don't want to go backward, and lose capabilites. I'd say if Retrospect is having trouble with removable media in OSX, then lift the requirement for the drive to be "removable", and allow ANY drive to be a destination device. Why not? That should be simple enough for the Dantz programmers, and allow us to maintain our existing backup sets, and also allow for great future use.
  10. Mac OS 10.2.2 Restrospect 5.0.238 Driver Update 3.1.105 I have a backup set (Removable Media) with a Firewire Drive as the destination, that I can't use in OSX anymore. I also have 6 Firewire disks mounted, and it doesn't see any of them as valid backup media. It does see them as source (meaning I can back the firewire disks up - just not use them as destination media). I did use this disk to back up in OSX (Not sure now if it was 10.2.x, or 10.1.5). There error I get now is "Please insert disk 1-iBook BU", which is already mounted, but it just can't see it. The same dialog box also says "No removable media found." This sounds like a Driver Update issue to me. Anyone else having this trouble?
×