Please Help

I had a backup run and under the job log for that backup it shows me what media was used to run and that was only 1 tape. Now under my devices it shows 2 tapes were used but obviously only 1 was used for the backup. Is there a way to see what information is on each tape in the device tab?

This will open the restore job selection view, with the Tape Label expanded, under which you can further expand the backup sets (which will be listed date wise) and selections to see what that tape contains.

Basically identify the Data and Time at which your last backup ran and try to match it with the backup set's date and time shown in the restore selection.

I see that the tape was used under the device tap. I know that it was used because every night before I leave work all of the tapes are overwriteable that way I dont run into any issues with backups not being able to run because of tape issues. Under the device tab there are now 2 tapes that are overwrite protected and under the backup job that just ran it only shows 1 tape being used. So where does this other tape come from and why is it now overwrite protected when the backup job never used it?

I have found that it belongs to a backup job that failed. The way it is set up is everyday at 5:30pm one backup job runs and another at 8:55pm. The problem last night was the one that runs at 5:30pm stayed on queued the entire night and it supposedly used that 1 tape. Could this mean that the tape is bad because the backup job didnt run?

First we must identify why that job stayed on queued state the entier night. Please check the Alerts tab as i suspect there was a particular device/media alert which may have popped up and since there was no one to acknowledge it at night time, the job may have been waiting in queued state for someone to respond to that alert.

Once we identify the reason why it was in queued state, it'l be easy to know the answers you're trying to find.

Thats what i figured so i checked it out this morning but the only things that occur are at 4am and it is maintenance of application databases on server has started and then a summary. There is nothing that hints at the reason why that was queued all night