RE: Legato oracle module.

Ron - Couple of points for you to consider:

• If you only have a single Oracle server, you may want to consider using the control file to store the RMAN information.
• Ideally, you will have another system with licensed Oracle to host your RMAN catalog.
• You can host your RMAN catalog in a separate instance on the same server, but you should carefully examine the devices used by each instance so you don't have a single point of failure. You don't want your production instance failure to wipe out your RMAN instance.
• If you only have one production server, and don't plan future expansions, RMAN may be more trouble than it is worth. Its greatest benefit is at sites with many, many instances/servers.
• You might want to consider using RMAN to write to disk as Sujatha suggested so you only have one thing to learn at a time. That was the advice I was given. Dennis Williams DBA Lifetouch, Inc. dwilliams_at_lifetouch.com

-----Original Message-----
Sent: Wednesday, May 29, 2002 7:58 AM
To: Multiple recipients of list ORACLE-L

RMAN Users,
I am just getting started in RMAN and have a question about the recovery catalog that RMAN uses.

   Does it have to be an Oracle database that stores the information about the backup if you do not use the controlfile as the source of backup information? For safety and disaster recovery purposes it should reside on a different server than the database being backed up by RMAN. Does that not mean that the recovery catalog server should also be licensed by Oracle because you are using Oracle on another box? In the case where you have 1 server for Oracle and one for recovery then should you not have 2 licenses?
 I am looking for the reliable and cheap way to use RMAN for backups? Thanks,
Ron
ROR mª¿ªm

>>> Sujatha.Madan_at_cmc.cwo.net.au 05/28/02 08:23PM >>> Hi Mike,

I've been using the Legato/RMAN combination for a couple of years now. The
recovery catalog resides on the Legato Backup server. Once all the database
backups finish, we then do a cold backup of the recovery catalog database
straight to tape.

I don't know what others do, but this if you can afford downtime for your
recovery catalog db this is probably the best way to do it.

If you have enough disk space on your server, you actually don't need the
Legato plugin. Just dump the backups to disk and get the normal Legato Networker server backup pick them up onto tape.

Regards,

Sujatha

-----Original Message-----
Sent: Wednesday, 29 May 2002 12:23 AM
To: Multiple recipients of list ORACLE-L

Hi everybody,

        I've taken responsibility of a couple of Oracle systems on NT
(in

addition to my nice Solaris DBs). I'm setting up Legato to do the backups
online using the Legato Networker Oracle Module. After checking the Legato
docs, it seems that the only way of using this module is by integrating it
with RMAN. is this right?

        Now, I'm sure that RMAN can do a good and flexible job. I've played
with it a little but I don't like the meeesssyyy way of backing up the RMAN
catalog.
In the Legato docs , there's a section that warns you :

" Preparing For Disaster
  .
  Ensure that your RMAN Recovery catalog is being backed up regularly.   ."

        Doesn't this imply that you need to perform the catalog backup outside legato yourself?, so why did we buy it in the first place? I know you could create another catalog to perform cross catalog backups but
that all sounds far to complicated and error prone.

Anyone have any tips for me?

[I'm much happier with my online backup scripts on Unix that I've been using
and tweeking for years.]

Mike.
Database Administrator

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com 
-- 
Author: Jenner Mike
  INET: M.Jenner_at_southampton.gov.uk 

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com 
-- 
Author: Sujatha Madan
  INET: Sujatha.Madan_at_cmc.cwo.net.au 

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Ron Rogers
  INET: RROGERS_at_galottery.org

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: DENNIS WILLIAMS
  INET: DWILLIAMS_at_LIFETOUCH.COM

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).