Message-Id: <25937.338083@fatcity.com>
From: "Arup Nanda" <orarup@hotmail.com>
Date: Wed, 16 Jul 2003 12:27:52 -0400
Subject: Re: RMAN & SQL Backtrack

This is a multi-part message in MIME format.

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

MessageWow! Heady!!

It's mighty nice of you to include my name in this illustrious list, =
Mladen; but I don't consider myself to be in the same league :) Better =
yet, count yourself in there.

Talking about the business at hand - you are absolutely right; one of =
the "myths" (of the several) is that RMAN is free. It is, as long as you =
don't put it on tape. Once you bring tape to the picture, you are =
talking money, sometimes big money (as in Tivoli), sometimes small (as =
in BrightStor). However, the solution to usedisk could still be relevant =
and applicable in some cases, especially in small companies.=20

Besides the Freeman book, I would also suggest another one - Oracle RMAN =
Pocket Reference by Darl Kuhn and Scott Schulze, ISBN 0-596-00233-5. It =
predates the Freeman book and I learned my ropes from it. It's a pocket =
reference; but it's truly one of those things where size belies the =
content.

Learning curve could be formidable. Remember you need to learn a new =
"language", and it is arcane. When youventure into territories of tuning =
the tape buffers, etc, the process could be quite involved. I just =
finished setting up and tuning a RMAN setup for a 2 TB database using =
IBM Tivoli Storage Manager agent and the details of the process using =
the IBM Red Books was nightmarish!

Regards,

Arup Nanda
  ----- Original Message -----=20
  From: Gogala, Mladen=20
  To: Multiple recipients of list ORACLE-L=20
  Sent: Wednesday, July 16, 2003 11:39 AM
  Subject: RE: RMAN & SQL Backtrack


  I don't have any experience with SQL*Backtrack and I do have some =
experience
  with RMAN. Here are my comments:
  a) RMAN is reliable. Once you write the backup scripts, they are =
executed by operations
      and there no surprises. In order to rely on those scripts, one =
needs to test them, especially
      the recovery part.
  b) RMAN needs a 3rd party backup software to run. Things like =
OmniBackup, Tivoli, Legato or
      SyncSort can be rather expensive. RMAN doesn't write to tapes =
itself. RMAN delegates a
      backup software contacted through the routines from libobk.so (or =
libobk.dll or libobk.sl) to
      do its writing. To get the "libobk.so" from you backup software =
vendor of choice, you generally=20
      have to write a check. That means that RMAN is NOT free.
  c) Before version 9, RMAN was arcane and hard to learn. Thanks to =
Robert Freeman, it is no=20
      longer so. You can learn how to configure and use RMAN and you can =
find a decent book
      to learn RMAN from. It's not very hard and it's fairly logical. =
One reading of the books suffices=20
      for a good general understanding.
  d) Quality of the software: RMAN leaves a lot to be desired. Its =
biggest drawback is the fact that
      it doesn't do any coordination with the underlying backup catalog. =
In other words, you can happily
      declare backup obsolete in RMAN and Legato will not know anything =
about it and vice versa.
      You can even delete backup in Legato and reuse  the tape while =
RMAN knows nothing about it.
       On the other hand, RMAN, in contrast to all other methods, does =
not put tablespaces into the
       backup mode, thus generating floods of redo archives. RMAN =
doesn't backup data blocks that=20
       have never been used ("behind the watermark blocks"), which is =
great if you have a fresh new
       datafile which was added to the tablespace just in case something =
might  run out of space.
  e)  Personnel. Despite the certification process, it is not always =
easy to find a trained personnel
       which knows how to use it and how  to recover the database. I =
consider the ability to recover
       the database a basis for someone to call himself/herself a DBA. =
You would be surprised how
       many people which claim that title do not know how to recover the =
database. Even smaller number=20
       knows how to use RMAN.
  f)   I would suggest Jared Still, Cary Millsap, Rachel Carmichael, =
Jonathan Lewis, Wolfgang Breitling,=20
      Steve Adams, Gaja V., Arup Nanda, Kirti Deshpande and  Anjo Kolk =
to start the Oracle List certification
      process. I would trust that one more then the OCP. I apologize to =
anyone who I might have forgotten.


  Mladen Gogala=20
  Oracle DBA=20
  Phone:(203) 459-6855=20
  Email:mgogala@oxhp.com=20

    -----Original Message-----
    From: Smith, Ron L. [mailto:rlsmith@kmg.com]
    Sent: Wednesday, July 16, 2003 10:59 AM
    To: Multiple recipients of list ORACLE-L
    Subject: RMAN & SQL Backtrack


    We have been using SQL Backtrack for backup and recovery for about 6 =
years now.  We are being pressured to start using RMAN because it is =
free.  Makes sense but I am wondering about reliability, complexity, =
learning curve, etc...

    Has anyone had experience with both products or anyone new to RMAN =
that can give me an idea of what to expect?

    Thanks!

    Ron
    If you are not the intended recipient of this e-mail message, any =
use, distribution or copying of the message is prohibited. Please let me =
know immediately by return e-mail if you have received this message by =
mistake, then delete the e-mail message. Thank you.


------=_NextPart_000_0087_01C34B95.AD8264C0
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><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Wow! Heady!!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It's mighty nice of you to include my =
name in this=20
illustrious list, Mladen; but I don't consider&nbsp;myself to&nbsp;be in =
the=20
same league :)&nbsp;Better yet, count yourself&nbsp;in =
there.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Talking about the business at hand - =
you are=20
absolutely right; one of the "myths" (of the several) is that RMAN is =
free. It=20
is, as long as you don't put it on tape. Once you bring tape to the =
picture, you=20
are talking money, sometimes big money (as in Tivoli), sometimes small =
(as in=20
BrightStor). However, the solution to usedisk could still be relevant =
and=20
applicable in some cases, especially in small companies. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Besides the Freeman book, I would also =
suggest=20
another one - Oracle RMAN Pocket Reference by Darl Kuhn and Scott =
Schulze, ISBN=20
0-596-00233-5. It predates the Freeman book and I learned my ropes from =
it. It's=20
a pocket reference; but it's truly one of those things where size belies =
the=20
content.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Learning curve could be formidable. =
Remember you=20
need to learn a new "language", and it is arcane. When youventure into=20
territories of tuning the tape buffers, etc, the process could be quite=20
involved. I just finished setting up and tuning a RMAN setup for a 2 TB =
database=20
using IBM Tivoli Storage Manager agent and the details of the process =
using the=20
IBM Red Books was nightmarish!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Arup Nanda</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3DMGogala@oxhp.com href=3D"mailto:MGogala@oxhp.com">Gogala, =
Mladen</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DORACLE-L@fatcity.com=20
  href=3D"mailto:ORACLE-L@fatcity.com">Multiple recipients of list =
ORACLE-L</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, July 16, 2003 =
11:39=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: RMAN &amp; SQL=20
  Backtrack</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial =
size=3D2></FONT><BR></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D937141214-16072003>I=20
  don't have&nbsp;any experience with SQL*Backtrack and I do have some=20
  experience</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D937141214-16072003>with=20
  RMAN. Here are my comments:</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D937141214-16072003>a)=20
  RMAN is reliable. Once you write the backup scripts, they are executed =
by=20
  operations</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; and there no surprises. =
In order=20
  to rely on those scripts, one needs to test them,=20
  especially</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; the recovery=20
  part.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D937141214-16072003>b)=20
  RMAN needs a 3rd party backup software to run. Things like OmniBackup, =
Tivoli,=20
  Legato or</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; SyncSort can be rather =
expensive.=20
  RMAN doesn't write to tapes itself. RMAN delegates =
a</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; backup software =
contacted through=20
  the routines from libobk.so (or libobk.dll or libobk.sl)=20
to</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; do its writing. To get =
the=20
  "libobk.so" from you backup software vendor of choice, you generally=20
  </SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; have to write a check. =
That means=20
  that RMAN is NOT free.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D937141214-16072003>c)=20
  Before version 9, RMAN was arcane and hard to learn. Thanks to Robert =
Freeman,=20
  it is no </SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; longer so. You can learn =
how to=20
  configure and use RMAN and you can find a decent =
book</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; to learn RMAN from. It's =
not very=20
  hard and it's fairly logical. One reading of the books suffices=20
  </SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; for a good general=20
  understanding.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D937141214-16072003>d)=20
  Quality of the software: RMAN leaves a lot to be desired. Its biggest =
drawback=20
  is the fact that</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; it doesn't do any =
coordination=20
  with the underlying backup catalog. In other words, you can=20
  happily</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; declare backup obsolete =
in RMAN=20
  and Legato will not know anything about it and vice =
versa.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; You can even delete =
backup in=20
  Legato and reuse&nbsp; the tape while RMAN knows nothing about=20
  it.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp;&nbsp; On the other hand, =
RMAN, in=20
  contrast to all other methods, does not put tablespaces into=20
  the</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp;&nbsp; backup mode, thus =
generating=20
  floods of redo archives. RMAN doesn't backup data blocks that=20
  </SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp;&nbsp; have never been =
used=20
  ("behind the watermark blocks"), which is great if you have a fresh=20
  new</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp;&nbsp; datafile which was =
added to=20
  the tablespace just in case something might&nbsp; run out of=20
  space.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>e)&nbsp; Personnel. Despite the =
certification=20
  process, it is not always easy to find a trained =
personnel</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp;&nbsp; which knows how to =
use it=20
  and how&nbsp; to recover the database. I consider the ability to=20
  recover</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp;&nbsp; the database a =
basis for=20
  someone to call himself/herself a DBA. You would be surprised=20
  how</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp;&nbsp; many people which =
claim that=20
  title do not know how to recover the database. Even smaller number=20
  </SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp;&nbsp; knows how to use=20
  RMAN.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>f)&nbsp;&nbsp; I would suggest Jared Still, =
Cary=20
  Millsap, Rachel Carmichael, Jonathan Lewis, Wolfgang Breitling,=20
  </SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp;&nbsp; Steve Adams, Gaja V., =
Arup Nanda,=20
  Kirti Deshpande&nbsp;and</SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2><SPAN class=3D937141214-16072003>&nbsp; Anjo Kolk to start =
the Oracle=20
  List certification</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;&nbsp; &nbsp;process. =
</SPAN></FONT><FONT=20
  face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D937141214-16072003>I would trust=20
  that one</SPAN></FONT><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
  class=3D937141214-16072003>&nbsp;more then the OCP. I apologize to =
anyone who I=20
  might have forgotten.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D937141214-16072003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <P><FONT face=3DArial size=3D2>Mladen Gogala</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>Oracle DBA</FONT> <BR><FONT face=3DArial size=3D2>Phone:(203) =

  459-6855</FONT> <BR><FONT face=3DArial =
size=3D2>Email:mgogala@oxhp.com</FONT> </P>
  <BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Smith, Ron L.=20
    [mailto:rlsmith@kmg.com]<BR><B>Sent:</B> Wednesday, July 16, 2003 =
10:59=20
    AM<BR><B>To:</B> Multiple recipients of list =
ORACLE-L<BR><B>Subject:</B>=20
    RMAN &amp; SQL Backtrack<BR><BR></DIV></FONT>
    <DIV><FONT face=3DArial size=3D2><SPAN class=3D328505213-16072003>We =
have been=20
    using SQL Backtrack for backup and recovery for&nbsp;about 6 years=20
    now.&nbsp; We are being pressured to start using RMAN because it is=20
    free.&nbsp; Makes sense but I am wondering about reliability, =
complexity,=20
    learning curve, etc...</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D328505213-16072003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D328505213-16072003>Has anyone had=20
    experience with both products or anyone new to RMAN that can give me =
an idea=20
    of what to expect?</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D328505213-16072003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D328505213-16072003>Thanks!</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D328505213-16072003></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial size=3D2><SPAN=20
    class=3D328505213-16072003>Ron</SPAN></FONT></DIV>
    <P><FONT face=3DArial size=3D2>If you are not the intended recipient =