Up until earlier this morning we assumed our backups have been running 100%. While running some reports the backup exec service crashed on our CAS server. Started the service and all of a sudden a ton of Duplicates kicked off. After some digging it appears as though no Duplicates have been written to tape in over a week. Had that service not crashed, we would have been unaware of this until thursday when we pull tapes.
Part of our everday checklist is to check the Scheduled Jobs tab under Job Monitor to ensure no jobs are sitting at Ready:No idle devices. Pre service crash there were zero jobs with that state. Now there are 30+. The only thing we see is that all jobs that are queued up write to our LTO-5 pool. All jobs that write to our LTO-4 pool wrote successfully.
Not sure where to start looking to ensure this wont happen again. Anyone else see this behavior.