Veritas-bu

[Veritas-bu] OTM Volume Mount on NetWare 5.x

2002-12-05 10:48:16
Subject: [Veritas-bu] OTM Volume Mount on NetWare 5.x
From: hampus.lind AT rps.police DOT se (Hampus Lind)
Date: Thu, 5 Dec 2002 16:48:16 +0100
This is a multi-part message in MIME format.

------=_NextPart_000_0020_01C29C7E.1BD2B000
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi!

I know this is a world wide problem, with most backup software for =
NetWare. I just want to share my problems and maybe get some information =
about how this work for others.

Now to the problem:
The client OTM setting are okay, and checked but Veritas Support.
The backup is active until the backup windows closes, without writing =
any data, then we have to reboot the netware client, because the OTM =
Volume Mount and bpcd.nlm is unloadable.
The client seems to hang when it has created the virtual OTM volume. We =
have the highest loging level possible, and the logs givs us nothing. =
When have updated the NIC driver and SCSI drivers.=20

It feels like this is a NetWare problem, with problems to create virtual =
volumes.

The funny thing is that the backups with OTM enabled can work fine for =
quite some time, and then for no reasone at all, it starts to fail, and =
when it does that it fails forever....
I`am sure that many Novell gurus recognize this behavior.

Regards Hampus.
------=_NextPart_000_0020_01C29C7E.1BD2B000
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I know this is a world wide problem, =
with&nbsp;most=20
backup software for NetWare. I just want to share my problems and maybe =
get some=20
information about how this work for others.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Now to the problem:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The client OTM setting are okay, and =
checked but=20
Veritas Support.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The backup is active until the backup =
windows=20
closes, without writing any data, then we have to reboot the netware =
client,=20
because the OTM Volume Mount and bpcd.nlm&nbsp;is =
unloadable.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The client seems to hang when it has =
created the=20
virtual OTM volume. We have the highest loging level possible, and the =
logs givs=20
us nothing. When have updated the NIC driver and SCSI drivers. =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It feels like this is a NetWare =
problem, with=20
problems to create virtual volumes.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The funny thing is that the backups =
with OTM=20
enabled can work fine for quite some time, and then for no reasone at =
all, it=20
starts to fail, and when it does that it fails forever....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I`am sure that many Novell gurus =
recognize this=20
behavior.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards =
Hampus.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0020_01C29C7E.1BD2B000--


<Prev in Thread] Current Thread [Next in Thread>