I am experiencing an issue where a catalog job is exhibiting the below symptoms:
Very long run time
Very high byte count
Very large MB jobrate
I end up having to cancel the job.
The tape has been at our offsite archive provider for about 3 years now.
I had it returned yesterday, inserted it into my libary and ran an inventory which ran successfully.
Next I kicked off a catalog job for this tape only.
This catalog job had been running for 4.5 hours before I cancelled it.
The stats at that time showed a byte count of 9,253,837,730,712 and a jobrate of 2,092,944.00 MB/min. Obviously something is wrong.
The actual amount of data on the tape is about 360GB. (LTO2 tape getting 1.9:1 compression)
I then kicked off a catalog job for a tape that had never left my library and its doing the same thing.
In reviewing the job log it appears that the catalog is looping over and over through the backup sets on the tape.
This makes me believe something is not right my catalog feature in Backup Exec
I am running version 12.0 SP2.
Any suggestions on how to remedy this?
