09-01-2015 09:37 AM
Good Morning,
I am running Backup Exec 14.2 with all the lastest updates as of September 1, 2015. We are using to an HP EverStore MSL4048.
When we insert our weekly tapes in our backup rotation, Backup Exec sometimes thinks that some (not all) of them are cleaning tapes. If we do an inventory, Backup Exec always retrives the correct tape numbers and converts them to the correct type. This issue has presisted though a chassis replacement. We would like for Backup Exec to always recognise the tapes on the first try without the need for an inventory. How can we do this?
Thanks,
09-01-2015 10:16 AM
Hi,
If you have barcodes on the tapes you can run a Scan and it will pick up what's in the library. However, without a Scan or Inventory BE will never know what's available, and there is no way to get around this.
Thanks!
09-01-2015 10:27 AM
I understand that you need to tell Backup Exec to check for changes. My issue is that the 1 minute scan returns incorrect information, so I need to run the 40 minute inventory. I would like a way to fix the scan so that it stops incorrectly catagorizing tapes as cleaning.
09-01-2015 11:35 AM
A scan should give a proper report of the bar codes in the library.
How are you changing the tape in the library? Are you using export/import jobs? or are you opening the library and doing a bulk load?
Can you attach a scan job log showing incorrect bar codes, immediately followed by an inventory job log?
09-01-2015 12:29 PM
So if you use barcodes, have you made sure that none of your "production" tapes have CLN as part of the barcode?
What does the library's interface show if you run a scan? Does it show the tapes as cleaning media?
09-01-2015 12:51 PM
It doesn't sound the problem may be repeated each time. However, if you can capture a trace during of a scan that has failed then please attach it on the next post to this thread. There may be a check condition reported by the tape library which could expose the problem.
Using SGMON, follow these steps to start the capture process (prior to running the scan):
Hopefully something will be obvious in the log that may narrow down the problem and/or expose it.