sciascia1 Posted May 31 Report Share Posted May 31 Hi There, I have an issue from time-to-time where Retrospect doesn't recognise drives or doesn't have access to them, so I have to forget and re-add them to sources. Up until now, this only happened with external drives but now I see this with Macintosh HD. Retrospect just stopped backing-up the Macintosh HD saying it was missing. But when I checked sources, Retrospect now sees two Macintosh HDs with one of them being offline - see attached. The one highlighted is the new one. To fix, I added the new Macintosh HD and removed the old one from the script - this is the internal drive on a laptop which hasn't been replaced in any way. Does anyone know why this happens and how to fix? Any help much appreciated. Cheers, Ben Quote Link to comment Share on other sites More sharing options...
sciascia1 Posted June 2 Author Report Share Posted June 2 Does this not happen to others or is this normal? I'm still on OS 13.6.7 with Retrospect 19.2.0 (122) incase that matters. Any help much appreciated. Cheers, Ben Quote Link to comment Share on other sites More sharing options...
MikeHutch Posted June 6 Report Share Posted June 6 Retrospect always does this when you do a MacOS update. It seems to modify the main drive when it does an interim or major system update. All you have to do is remove the old drive with the wavey line next to it, add the updated drive, then re-instate your favourite folders (if any) and your script(s) with the 'new' drive, and off you go again. You've mostly done this already. BTW, if you get info on your internal drive, you may see that it has changed it's version number, it often reflects your MacOS's version! Cheers 1 Quote Link to comment Share on other sites More sharing options...
sciascia1 Posted June 6 Author Report Share Posted June 6 @MikeHutch Thanks for that. So does it also do something slightly different that effects external drives as well? I have a an ongoing issue where Retrospect no longer has access to the Catalogue, which lives on an external drive. See that last post in this thread here: At the time of that last post, it was happening regularly, now it happens from time to time. I discover that backups didn't run and have to re-locate the catalogue. Any help or suggestions welcome. Cheers, Ben Quote Link to comment Share on other sites More sharing options...
MikeHutch Posted August 14 Report Share Posted August 14 I have a suggestion regarding how to get constant access to your catalogue on a separate drive, and that is to make an Alias of it, and put the Alias in the folder where Retrospect normally expects to see catalogue files. Usually in your Library / App Support / Retrospect folder. BTW are you compressing your catalogue files? There is on option in your script to do this. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.