Jump to content
boegly

All schedules deferred after new year

Recommended Posts

 Apparently as of the new year all schedules have been deferred. Version 14.6.1 on MacOS 10.12.6. I can't find anything where deferred is even an option, much less an option to undo.

Share this post


Link to post
Share on other sites

boegly,

If you read the third paragraph in the OP in this thread, which was the latest one in this Forum before you posted yours, you'll find a link to an older post which may tell you how to solve your problem.  I'm going to try that approach now, since I intend to try to revert to Retrospect Mac 14.6.0.

Share this post


Link to post
Share on other sites

A bug exists in all older Macintosh versions of Retrospect that will make scripts appear deferred.  This is a cosmetic only bug that is fixed in 15.6.1. No backups should fail to run because of this issue. 

You can either ignore the defer warnings or you can upgrade to 15.6.1 and the issue will not appear. http://www.retrospect.com/upgrade or http://www.retrospect.com/updates

Share this post


Link to post
Share on other sites

It appears to not be cosmetic. No scripts are running. I have a number of clients using this version. It seems pretty sketchy to make them all pay for an upgrade because suddenly version 14 won't work. In addition, I've tried several work arounds with rescheduling and nothing keeps a script, whether old or new, from being deferred.

Share this post


Link to post
Share on other sites

Contrary to what the head of Retrospect Tech Support has said above, the issue that causes a script to appear deferred as of January 1st is definitely not just a cosmetic issue. The deferred scripts, when they run, do not backup "client" machines, only local drives.

See this post for the details of a test I did.

P.S.: See this post; i turns out that the issue is cosmetic, and fixable with Console 14.6.2, for Retrospect Mac 12.5-14.6—unless you have the -530 Bug problem I had.  Sorry for testing that indicated otherwise. :(

Edited by DavidHertzberg
Added P.S. saying the issue _is_ cosmetic and fixable for _normal_ 12.5-14.6

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×