Search the Community
Showing results for tags 'stops'.
From time to time, I realize that I've seen no emails reporting backup successes or failures. I go to Retrospect (11.5.2 right now) and see that no scheduled backups are running when they *should* be, and they haven't run for a few days or a few weeks. Why does the engine fail so catastrophically? This is a *very serious issue*! I see a couple files in Console named RetroEngine_2014-11-18-233330_Tube.cpu_resource.diag and RetroEngine_2014-12-18-233356_Tube-2.cpu_resource.diag (the 2nd one was just generated after I rebooted my Mac Pro and forced the backups to start again by pausing and then resuming all jobs (because for some reason they wouldn't start automatically like they should've at 23:30). And now both backups are stuck at "Preparing to execute" even after 20 minutes. I've attached both logs. Anything else I can provide? I'm running 10.10.1, and I just turned off Instant Scan before the reboot, because I'd previously turned it off in an older version of Retrospect because I hate how much CPU and disk i/o it uses when I need it. Archive.zip
I have Retrospect 9.0.1 installed on a Windows 2012 Server. I have 30 clients to be backed up, MACs and Windows machines. I have not gotten a successfull backup of all the machines since 9.0.1 was installed. The backup simply stops on the clients. It will be with 1, 2, or 3 files remaining. If I manually backup the client, it works fine. These are all scheduled scripts that run in the evening. I'm starting to get frustrated with that constant hangs. This product is much too expensive for this type of behaviour. Has anybody else experienced this?