twickland Posted January 20, 2016 Report Share Posted January 20, 2016 The past several times I've performed Apple software updates that require a reboot, the Retrospect 12.5 engine has come back up in a condition that is not fully operational. The problems have typically included absent data for one or more media sets and a failure to recognize the correct tape in our LTO drive. Stopping and restarting the engine has always fixed these problems, but I have to remember to do this, or scheduled backups will not be performed. I've encountered this problem only after restarts that are part of updates made via the App Store; if I manually reboot, Retrospect engine always seems to launch and behave properly. Quote Link to comment Share on other sites More sharing options...
Maser Posted January 28, 2016 Report Share Posted January 28, 2016 Yeah -- I saw this with the 10.11.3 delta upgrade as well (I reported this to Robin...) In my case, the proactive backup scripts never ran *until* a scheduled groom script ran a few days after the upgrade -- then everything started working again. Quote Link to comment Share on other sites More sharing options...
twickland Posted March 23, 2016 Author Report Share Posted March 23, 2016 I can confirm that this problem still exists in Retrospect 13.0.0. Quote Link to comment Share on other sites More sharing options...
Maser Posted March 24, 2016 Report Share Posted March 24, 2016 Yeah, I've now just resigned myself to remembering to do two reboots after any OS update. 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.