akent35 Posted January 6, 2006 Report Share Posted January 6, 2006 On Sunday, 1/1, I used Retrospect 6.x to make a backup of my primary OS X partition on my TI 15.2" Powerbook. I sold the machine the following day, and have purchased a 17" Powerbook (received it today). After partitioning its hard drive (making an 80 Gigabyte "main" partition, and a 20 Gigabyte one, on which I have OS 10.4), I booted from the small partition. When I tried to use Retrospect to restore from the backup mentioned above to the 80 Gig partition, I received the following error: "Sprry, restore preparation failed, error -24161 (catalog version is too new)". Sure seems like a strange error to me. Any suggestions as to how I can proceed? Link to comment Share on other sites More sharing options...
twickland Posted January 6, 2006 Report Share Posted January 6, 2006 Sounds like you may be trying to restore using Retrospect 6.0 from a catalog that was created (or added to) by version 6.1. Try updating the version of Retrospect you're using to 6.1.126. Link to comment Share on other sites More sharing options...
Guest Posted January 8, 2006 Report Share Posted January 8, 2006 I'm trying to help my Father-in-law who is having a similar problem. We think the problem relates to how the backup was done (newer version of Retrospective Express) and the restore is using an older version (rev) that seems to be complaining about the date of the catalog version. I have searched all over, but find nothing to offer any suggestions as to what specific date/item is being compared to see if it is "too new". At this point, ANY suggestion would be helpful. We can't imagine that a slighty different version/rev of the software would stop if from reading and working with the catalog. We arent' talking major version jumps. He has the additional complication that his main system will not re-boot and can only boot off the disk (simple system with the Restore utility). So using the "right" version is more of a problem. Has EMC/Dantz made a bootable disk with the lastest version/rev, he does have 6.1.126 on that main machine. Now the gripe...who writes code that isn't upward compatible for something as important as backup/restore and then doesn't tell anyone this could happen! Need a solution. Kernel Panics aren't a great error message to see either! Link to comment Share on other sites More sharing options...
CallMeDave Posted January 8, 2006 Report Share Posted January 8, 2006 Quote: who writes code that isn't upward compatible... Uh, probably everyone? Here's a test; create a document in Microsoft Word 11 (part of Office 2004) and then bring it over to an old Mac and try and open it in Word 5. What happens? Developers can't be expected to write updward compatible code, unless they can go into a time machine and find out what new API's and features are going to be included in the future. Retrospect is, of course, _backward_ compatible with catalogs; Retrospect 6.1 will happily Restore from catalogs dating as far back as version 4.3. You don't include any specific information about what versions are at issue here. But the error message that you hint at (again without providing the exact message) suggests that this is not a version issue (which would have a "catalog too new" message). There have been reports of date mismatch issues here on the Forum; you might try and search for the message text on this board and see if you find anything. >...and then doesn't tll anyone this could happen! From the Retrospect 6.1 ReadMe file: "Retrospect 6.0 backup sets: {snip} New backup sets created with Retrospect 6.1 cannot be used with Retrospect 6.0." Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.