> backup of all the environment for this small backup.
It should have been: for this small database.
Sorry about the mistake.

Yechiel Adar
Mehish
----- Original Message -----
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday, December 04, 2003 6:44 PM


> I do not think you need 2 Rman catalogs.
> Build a small database just for Rman. After the daily backup finished
bring
> it down and do os level backup of all the environment for this small
backup.
> You can then easily restore it in case of disk problems.
>
> Remember: A backup is good only when you can restore from it.
> Test restores.
>
> Yechiel Adar
> Mehish
> ----- Original Message -----
> To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
> Sent: Thursday, December 04, 2003 4:44 PM
>
>
> > We have both 8i and 9i instances, but 'eventually' plan to migrate
> everything to 9i. I'm looking at using RMAN for our backup and recovery.
We
> have many instances but essentially 2 types.
> >
> > 1. Production instances that have both OLAP and OLTP. These must be in
> archive log mode.
> > 2. We have staging instances where we do data loads. We do not put these
> in archive log mode for obvious reasons. We do our backups of these with
> transportable tablespaces and running dbverify.
> >
> > We also have 2 locations. One is remote. Its not practical to store our
> backups from the remote location at our local location or vice versa. So
we
> will need 2 seperate RMAN setups.
> >
> > I have seen that some people like to use two instances that have RMAN.
> Many people will just put the RMAN catalog in an existing instance. Is
that
> really a good idea? The idea behind two instances is that they can back
each
> other up. Is that really enough? You can lose both instances, then your
> backup sets are useless. We have a shared NAS, so each location uses the
> same set of storage. We do backup to tape as well.
> >
> > Any suggestions would be appreciated. I can handle the scripting my
self.
> Im just looking for a viable plan.
> >
> > --
> > Please see the official ORACLE-L FAQ: http://www.orafaq.net
> > --
> > Author: <[EMAIL PROTECTED]
> >   INET: [EMAIL PROTECTED]
> >
> > Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
> > San Diego, California        -- Mailing list and web hosting services
> > ---------------------------------------------------------------------
> > To REMOVE yourself from this mailing list, send an E-Mail message
> > to: [EMAIL PROTECTED] (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.net
> --
> Author: Yechiel Adar
>   INET: [EMAIL PROTECTED]
>
> Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
> San Diego, California        -- Mailing list and web hosting services
> ---------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: [EMAIL PROTECTED] (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.net
-- 
Author: Yechiel Adar
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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).

Reply via email to