cancel
Showing results for 
Search instead for 
Did you mean: 

BE16 new tape device not responding

Boris0815
Level 3

Hi,

we run a Win2016 Server x64 with BE16 and a Dell Tape Library TL2000 attached (1 Drive IBM 3580).

After installing Windows Updates, BE suddenly showed 2 Tape Devices. One was named correctly "IBM ULT3580-HH6" like before, but it was not responding any more. With every job starting, it instantly turned offline. Yet all of the library slots are reacting fine so far.

The new one was labeled "Bandlaufwerk001". This one responded to things like cleaning, and details were accessible. But with every job it says "Der Speicher wurde nicht für den Backup Exec-Server konfiguriert." (see screenshot 1). When I try to change details of the backup jobs (which look entirely well and just like before) the attaced screenshot 2 comes up.

How can our Backup jobs access the tape device again?

1 ACCEPTED SOLUTION

Accepted Solutions

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

It appears that the operating system may have detected the tape drive as having changed and plug-n-play has given the device a new identity which has then affected Backup Exec.

Your ADAMM.LOG file may show information as to how the configuration was before the problem and what is being seen now

 As you appear to be using partitions of slots, if you defined specific drives for specific partitions, then you will probably have to delete and recreate the partitions to correct this (which may mean temporarily re-targetting you jobs.)

 

View solution in original post

2 REPLIES 2

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

It appears that the operating system may have detected the tape drive as having changed and plug-n-play has given the device a new identity which has then affected Backup Exec.

Your ADAMM.LOG file may show information as to how the configuration was before the problem and what is being seen now

 As you appear to be using partitions of slots, if you defined specific drives for specific partitions, then you will probably have to delete and recreate the partitions to correct this (which may mean temporarily re-targetting you jobs.)

 

View solution in original post

Thanks Colin, that did the trick!