Vidéos d'aide de Screencast
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Tape is suddenly in other slot

Created: 04 Mars 2013 | 5 comments

Is it possible that a tape will be moved automaticly from 1 slot to another free slot?

For example, we insert on friday 6 tapes in slot 1,2,4,5,6,7. There is a clean tape in slot8 and slot 3 is empty. 1 and 2 contains Diff tapes and the rest is full.

On monday we find the tape in slot 7 to be in slot 3. For as far as I can see there is nothing to be found in the logs of BE. Just the import on friday.

Can the software do this by itself?

Thanks.

Marcel

Operating Systems:

Commentaires CommentairesAccéder au dernier commentaire

l'image des pkh

Is the tape which was in slot 7 used by any jobs?

l'image des MarcelB

Yes. In the weekend runs a full job. Target is a media set for full tapes and thoose tapes are imported on friday in slot 1 and 2.

Also on friday the other tapes are imported for diff media set, on the other slots (not 3). Diff runs every night.

We have jobs seperated per server so running after each other to same targets.

-

Marcel

l'image des Larry Fine

Backup Exec will never directly move a tape from SlotA to SlotB.

Backup Exec can move a tape from SlotA to Drive1 to SlotB if SlotA has gotten full while the backup was running in Drive1.  This would typically happen if somebody imported a tape into SlotA while the backup was running. 

This could also happen if there was some sort of hardware glitch and the media was dismounted to the first available slot, which happened to be SlotA.  This sort of sounds like your scenario, since it appears that BE put the tape in the first available/empty slot (slot 3).  Please check the bottom of your adamm.log file as it may have clues about a hardware glitch that was recovered from.

So yes, it can happen that tapes are not in the slots you expect, but hopefully you are using BE's media management and it doesn't really matter what tape is in what slot as BE will compensate.

If you find this is a solution for the thread, please mark it as such.

l'image des MarcelB

Larry,

Thanks for the info.

I do find some info in that log. I grabbed some lines from it. I do not see lines pointing me to a change of slot but it does mention errors. The backup contineus fine. Is this what we where looking for?

-snap-

0003:0000:0000:0000  "adpu320", (Port Driver)
0003:0000:0003:0000  "HP      Ultrium 3-SCSI  G38W", (Tape Device), "\\.\Tape0"
0003:0000:0003:0001  "HP      1x8 autoloader  1.46", (Changer Device), \\.\MediumChanger0

-snap-

Scsi Address
Prt :Bus :Tar :Lun   Attributes
-------------------  -------------------------------------------------------------------------------

0003:0000:0003:0001  DeviceIo[01]: "HP      1x8 autoloader  MXA0603045", Cert=Y, "\\.\MediumChanger0"
0003:0000:0003:0000  DeviceIo[02]: "HP      Ultrium 3-SCSI  HU105447AW", Cert=Y, \\.\Tape0

-snap-

 
Scsi Address
Prt :Bus :Tar :Lun   Attributes
-------------------  -------------------------------------------------------------------------------

0003:0000:0003:0000  Device Name             "\\.\Tape0"
                     Secondary Name          "\\?\scsi#sequential&ven_hp&prod_ultrium_3-scsi&rev_g38w#6&1ecf7c07&0&000300#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}"
                     Primary Inquiry         "HP      Ultrium 3-SCSI  G38W"
                     Serial Number           "HP      Ultrium 3-SCSI  HU105447AW"
                     Device Flags            UMD, SCSI, SN(TYPE 0)
                     Device State            3, Online

                     Device IDs              1002, {ACC8DADE-4A00-4F17-9B44-987E6807BC62}
                     Device Name             "HP 1"
                     Device Type             134283265, "LTO 64K (64K,10,0,E,HU)"
                     Device Features         0x001BFA7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,EL,LU,E,SBS,DC,SDC,TA,HU,RR,W
                     Device Element          1003, 0
                     Device Block Limits     512 min, 65536 max
                     Device Hard Errors      7 write, 1 read
                     Device Soft Errors      1216 write, 617 read

0003:0000:0003:0001  Device Name             "\\.\MediumChanger0"
                     Primary Inquiry         "HP      1x8 autoloader  1.46"
                     Serial Number           "HP      1x8 autoloader  MXA0603045"
                     Device Flags            UMD, SCSI, SN(TYPE 0), SN(ELEMENT)
                     Device State            3, Online

                     Device IDs              1003, {C9AB1DA2-EA84-49B6-A3C2-F60AA95D1955}
                     Device Name             "HP 2"
                     Device Type             2131755008, "CHANGER FS=1"
                     Device Features         0x00006000: RMP,RRD
                     1st Slot Number         1
                     Number Of Slots         8
                     Portal Slots            0
                     Import/Export           Manual

                     Drive Element 0         1002, "HP      Ultrium 3-SCSI  HU105447AW"

-snap-

-

Marcel

l'image des Larry Fine

all that looks fine.  I was wondering if there was a SCSI dump from a hardware glitch at the bottom of the adamm.log, but I assume not, as it is hard to miss.

The "soft errors" are recovered errors, so they are generally not a problem.  Not unexpected, especially if you have used this equipment for a few years.  Those soft & hard erros are exposed in the BE GUI in the drive properties.  I would make a not of them every few months.  If you see much change, it bears investigating... could be media, could be drive related.

So, i don't really know why your tape wasn't where you expected it, but unless this becomes a regular issue, I wouldn't worry about it.

If you find this is a solution for the thread, please mark it as such.