06-18-2009 06:49 AM
i have a few SQL backup jobs where the master job that runs the script never finishes and says active long after the databases have been backed up. each of the database backup jobs ends as Status 0, but the master job doesn't end until i kill it manually
06-18-2009 06:44 PM
06-18-2009 09:00 PM
06-18-2009 10:18 PM
06-19-2009 06:37 AM
06-19-2009 08:03 AM
06-29-2009 07:47 AM
06-29-2009 08:17 AM
07-02-2009 08:05 AM
I have the same issue. it appear that althoght various Default Application jobs run backing up a few large databases taking around 3hrs, the master job always fails after 2hrs and a few seconds.
It fails with
network connection broken(40)
02/07/2009 03:27:27 - Error bpbrm(pid=2776) could not write EXIT STATUS to stderr
Is there a timeout somewhere that could be causing this 2hr aspect or is it a coincidence?
07-02-2009 08:12 AM
07-02-2009 08:26 AM
07-02-2009 09:00 AM