I did the failed jobs thing to 0. We'll se if that does anything.
Here is a look at the event log. Look at the oldest item in the log. It refers to sql hanging. Is this the BE SQL or what? We don't have a SQL server otherwise.
B.
Application LogNumberEventDateTimeSourceDescriptionServer: SERVER1Backup Exec8/4/2005Information16,283Backup Exec Alert: Media Remove
(Server: "SERVER1") (Job: "Backup 0005") Please remove the media from the drive, and
Respond OK.
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
2:15:35AMBackup Exec8/4/2005Information16,282Backup Exec Alert: Media Remove
(Server: "SERVER1") (Job: "Backup 0005") Please remove the media from the drive, and
Respond OK.
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
2:00:34AMBackup Exec8/4/2005Information16,281Backup Exec Alert: Media Remove
(Server: "SERVER1") (Job: "Backup 0005") Please remove the media from the drive, and
Respond OK.
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
1:45:34AMCi8/4/2005Information16,280Master merge has completed on c:\system volume information\catalog.wci.1:00:40AMMSSQL$BKUP
EXEC
8/4/2005Information16,279This instance of SQL Server has been using a process id of 232 since 7/25/2005 8:08:16 PM
(local) 7/26/2005 1:08:16 AM (UTC).
12:00:00AMSceCli8/3/2005Information16,278Security policy in the Group policy objects has been applied successfully.