Backup Central

Hi Gang -

While I'm awaiting a call back from Veritas support, I'm wondering if
anyone knows what I can start looking at to troubleshoot this problem. We
are having more strangeness occurring in our environment, but I'm not sure
if this could be my system, or network or a combination of the two. Our
environment consists of an e250 Sun Master Server running Solaris 7 and NBU
5.0 attached to a Quantum ATL Library, an e250 Sun Media Server running
Solaris 8 attached to a Storagetek L700e w/7 drives. We are running
remote-NDMP jobs to a NetApp Filer, and an EMC Celerra system. For some
reason, both of these jobs are failing with a 52 error - Media Manager timed
out trying to mount a volume. And then it eventually fails with a 219
error: the Required Storage Unit is Unavailable.

We have had this happen once before in December, and a power cycle of
the media server and tape library fixed the problem. What I witnessed
happening while this was going on is that when the job tries to mount a tape
in one of the NDMP assigned drives, drives 5 & 6 will go into a DOWN-TLD
state. When I bring those drives back up, drive 5 will go down, but 6 will
stay up. When I bring drive 6 up, they both go down again. And this cycle
repeats until the job is cancelled. I power-cycled the library and media
server yesterday, but the problem persists.

Has anyone seen this and know what might be happening? Should I get my
network people looking at this?

Thanks so much!

Jennifer

------=_NextPartTM-000-a8aafdb0-e40e-45bf-aefd-82ce4261c499
Content-Transfer-Encoding: quoted-printable

I have experienced a similar problem that was traced back to the way the
tape drives were setup. In my case, the engineer from the vendor daisy
chained my tape drives (shared the scsi bus) and Netbackup had a hard
time locating the correct drive etc. After we gave each drive their own
channel, remove the drives from Netbackup, and then setup each drive in
Netbackup everything started working again. I would start with Robtest
to see if I can mount a tape, rewind, & eject the tape from each drive.=20

=20

________________________________

From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Jennifer
Hooper
Sent: Tuesday, February 01, 2005 11:11 AM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: [Veritas-bu] More strangeness

=20

Hi Gang -=20

=20

While I'm awaiting a call back from Veritas support, I'm wondering
if anyone knows what I can start looking at to troubleshoot this
problem. We are having more strangeness occurring in our environment,
but I'm not sure if this could be my system, or network or a combination
of the two. Our environment consists of an e250 Sun Master Server
running Solaris 7 and NBU 5.0 attached to a Quantum ATL Library, an e250
Sun Media Server running Solaris 8 attached to a Storagetek L700e w/7
drives. We are running remote-NDMP jobs to a NetApp Filer, and an EMC
Celerra system. For some reason, both of these jobs are failing with a
52 error - Media Manager timed out trying to mount a volume. And then
it eventually fails with a 219 error: the Required Storage Unit is
Unavailable.

=20

We have had this happen once before in December, and a power cycle
of the media server and tape library fixed the problem. What I
witnessed happening while this was going on is that when the job tries
to mount a tape in one of the NDMP assigned drives, drives 5 & 6 will go
into a DOWN-TLD state. When I bring those drives back up, drive 5 will
go down, but 6 will stay up. When I bring drive 6 up, they both go down
again. And this cycle repeats until the job is cancelled. I
power-cycled the library and media server yesterday, but the problem
persists.

=20

Has anyone seen this and know what might be happening? Should I get
my network people looking at this?

=20

Thanks so much!

=20

Jennifer

=20

Heheeh... this was even stranger. It looks like a tape cartridge got
damaged, and was 'stuck' in the drive. But it wasn't IN the drive, it was
in the Cartridge In position. After pulling the tape out, fixing it,
cleaning the drives, and power cycling the whole shaboodle... we're back up
and running. Thank *goodness* it was that easy. I keep patting this
system and telling it to hold on just a liiiiittle while longer until I can
get the new library implemented.

Thanks guys... I have the warning signs to look for now! :)

Jennifer

_____

From: David Turner [mailto:Dturner < at > manh.com]
Sent: Tuesday, February 01, 2005 11:38 AM
To: Jennifer Hooper; veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] More strangeness



I have experienced a similar problem that was traced back to the way the
tape drives were setup. In my case, the engineer from the vendor daisy
chained my tape drives (shared the scsi bus) and Netbackup had a hard time
locating the correct drive etc. After we gave each drive their own channel,
remove the drives from Netbackup, and then setup each drive in Netbackup
everything started working again. I would start with Robtest to see if I can
mount a tape, rewind, & eject the tape from each drive.



_____

From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Jennifer
Hooper
Sent: Tuesday, February 01, 2005 11:11 AM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: [Veritas-bu] More strangeness



Hi Gang -



While I'm awaiting a call back from Veritas support, I'm wondering if
anyone knows what I can start looking at to troubleshoot this problem. We
are having more strangeness occurring in our environment, but I'm not sure
if this could be my system, or network or a combination of the two. Our
environment consists of an e250 Sun Master Server running Solaris 7 and NBU
5.0 attached to a Quantum ATL Library, an e250 Sun Media Server running
Solaris 8 attached to a Storagetek L700e w/7 drives. We are running
remote-NDMP jobs to a NetApp Filer, and an EMC Celerra system. For some
reason, both of these jobs are failing with a 52 error - Media Manager timed
out trying to mount a volume. And then it eventually fails with a 219
error: the Required Storage Unit is Unavailable.



We have had this happen once before in December, and a power cycle of
the media server and tape library fixed the problem. What I witnessed
happening while this was going on is that when the job tries to mount a tape
in one of the NDMP assigned drives, drives 5 & 6 will go into a DOWN-TLD
state. When I bring those drives back up, drive 5 will go down, but 6 will
stay up. When I bring drive 6 up, they both go down again. And this cycle
repeats until the job is cancelled. I power-cycled the library and media
server yesterday, but the problem persists.



Has anyone seen this and know what might be happening? Should I get my
network people looking at this?



Thanks so much!



Jennifer