Search the Community
Showing results for tags 'stuck'.
Found 3 results
I am currently going through a rebuild from a number of tapes and unfortunately Restrospect seems to be getting stuck when it comes to a certain file. Is there any way of just skipping this single file on rebuild or can I only skip to the next tape to continue the rebuild? Thanks Mac:Lion Retrospect:10.5.0
Don Lee posted a topic in Retrospect bug reportsI sometimes find that I can't change a script. In this case, I had a script that was set up to copy the latest backups from my "old" set to the cumulative "2015" set. The schedule is to do this once every three months for archive purposes. The old script had the "2014" destination set, and all I wanted to do was change the destination to the "2015" set. I would open the script, click the new destination, set the schedule, and hit "save". It would revert to the old destination set. I tried this a bunch of times. It turns out that the schedule is irrelevant. I click on the new destination, hit save, and the destination reverts back. I tried stopping and re-starting both the console and the engine, and made sure nothing was running. I tried deleting and re-creating the destination media set (empty, as of today). The only thing I found that would allow me to change this script was to delete the script, and then re-add the script. THEN it would let me set the destination as I wished. I smell a bug, although I don't know how to reproduce it. I've seen this before, but I can't pick out the pattern (yet!)
Retro 10.5.0(145) on Mac OS X 10.8.5, Mac mini (summer 2013), 16 GB mem My engine is stuck. I have a pro-active script that says "not active", which runs every 1 day. Active every day between 2:30 AM and 9 AM. It has not actually done anything since Nov 1st, though. I tried duplicating the script, and setting the "active" time to 1:pm to 5 PM on Monday (today) of the duplicate - called junk-script.. junk-script says it is (Not yet determined), and has been that way for a couple of hours. No other activities are active. Looking through the log, it looks like *none* of the proactive scripts are running - since Nov 1st. Is there something I can do to crank up the debugging to tell me what the engine is stuck on? I've had this happen before, and I may not notice it for several days, which is Bad Juju. Thanks,