It's Goodbye to Retrospect

[Paul Ripley]

I'm running Retrospect 10.5 using OS 10.8.5.  I backup regularly using two hard disk media sets.

 

Today, for the fourth time in 3 days, I tried to restore an application from a backup.  The restored app had a generic icon, and when opened, it displayed 3 error messages.  The restored app had to be force quit.

 

I no longer have confidence in Retrospect.  If a single application cannot be restored, what will happen if there is a need for a complete restoration of the hard drive?

 

At this point, I am going to delete all Retrospect files and use only clones for backup.

 

It's the end of an era.

 

 

[Don Lee]

It is unlikely that Retrospect is incorrectly restoring the app. It is much more likely that the app is being restored properly, but the permissions on the app are wrong (because of the way it was restored) or supporting files (for instance in /Library/Application Support) are missing.

 

I've had troubles with Retrospect over the years, but I don't think I've ever seen it screw up a restore.

[Lennart_T]

I'm running Retrospect 10.5 using OS 10.8.5.  I backup regularly using two hard disk media sets.

 

Today, for the fourth time in 3 days, I tried to restore an application from a backup.  The restored app had a generic icon, and when opened, it displayed 3 error messages.  The restored app had to be force quit.

 

 

Which app is it?

How do you restore it? (The app is most likely a package. Are you 100% sure you are restoring the entire package? No filter preventing parts from being restored?)

What does the error messages say?

As iCompute points out: Are you restoring any "support" files that the app needs?

 

Your best option would really be to restore the app's installer rather than the app itself.