Veritas-bu

[Veritas-bu] OTM with MSSQL

2001-02-16 16:15:41
Subject: [Veritas-bu] OTM with MSSQL
From: Bob Bakh bbakh AT veritas DOT com
Date: Fri, 16 Feb 2001 13:15:41 -0800
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0985D.9E132850
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Exclude your DataBase Files. They can not and should not be backed up =
using
OTM, there is a Microsoft API that NBU uses to backup MS SQL.  It's the =
MS
SQL extension for NetBackup.
=20
Thanks,
=20
Bob

-----Original Message-----
From: Fr=E9d=E9rick Coutret [mailto:frederick.coutret AT par.sita DOT int]
Sent: Friday, February 16, 2001 12:23 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] OTM with MSSQL


Hi,
=20
I tried several times to backup NT systems with MSSQL using OTM and I =
always
got problems.
Veritas support just told me I can't backup NT systems with MSSQL using =
OTM
but I tried and found some workaround
by changing OTM parameters.
=20
But now, the old problems are coming back on some NT servers.
Is there is right way to use OTM without any 11 status code ( 1005 or =
1001
errors on OTM ) ?
=20
Thanks,
Frederick
=20


------_=_NextPart_001_01C0985D.9E132850
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D276331521-16022001>Exclude your DataBase Files. They can not =
and should=20
not be backed up using OTM, there is a Microsoft API that NBU uses to =
backup MS=20
SQL.&nbsp; It's the MS SQL extension for NetBackup.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D276331521-16022001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D276331521-16022001>Thanks,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D276331521-16022001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D276331521-16022001>Bob</SPAN></FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Fr=E9d=E9rick =
Coutret=20
  [mailto:frederick.coutret AT par.sita DOT int]<BR><B>Sent:</B> Friday, =
February 16,=20
  2001 12:23 PM<BR><B>To:</B>=20
  veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] OTM =
with=20
  MSSQL<BR><BR></DIV></FONT>
  <DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>I tried several times to backup NT =
systems with=20
  MSSQL using OTM and I always got problems.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Veritas support just told me I can't =
backup NT=20
  systems with MSSQL using OTM but I tried and found some=20
workaround</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>by changing OTM =
parameters.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>But now,&nbsp;the old problems are =
coming back on=20
  some NT servers.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Is there is right way to use OTM =
without any 11=20
  status code ( 1005 or 1001 errors on OTM ) ?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Thanks,<BR>Frederick</FONT></DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C0985D.9E132850--



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