In the last week or so, 4 of the last 5 backup jobs have done this. According to the log, the backup goes thru all the files it's supposed to back up successfully. Then, instead of ending the job, it just sits there active until someone cancels it. Once it's been canceled, it's listed in the Job History as "Canceled, timed out", even though the automatic cancellation didn't occur.
I've done some searching here, Google, Veritas, Symantec, & other places and can't seem to find any clues. I suspect something has changed to cause this, but I can't figure out what. At least I can take heart in the fact that we are getting good backups, as long as someone cancels the active job after it finishes so the next night's job will run.
Any ideas are much appreciated. If you need more detail just ask and ye shall receive.
I don't ask questions here very often, so I can afford to be generous with the points, even though this is not urgent (or at least not nearly as urgent as it would be if the backups were actually failing).
Thanks in advance!