drak0nian_at_yahoo.com (Paul Drake) wrote in message news:<1ac7c7b3.0310201550.58c1f9e4_at_posting.google.com>...
> rgaffuri_at_cox.net (Ryan Gaffuri) wrote in message news:<1efdad5b.0310201048.31b843ed_at_posting.google.com>...
> > Brian Peasland <dba_at_remove_spam.peasland.com> wrote in message news:<3F93E15F.FE796EB_at_remove_spam.peasland.com>...
> > > > This is more of an opinion type question. Im reading the Backup and
> > > > Recovery book from Osborne. It states that its ok to have a recovery
> > > > catalog tablespace in an instance that has other data in it.
> > > >
> > > > This strikes me as a bad idea. I would think that you would want your
> > > > recovery catalog in a seperaet instance, then I would think you would
> > > > 'ideally' want a standby database that feeds off your RMAN catalog.
> > >
> > > Are you assuming that the Recovery Catalog is in the very database that
> > > you are backing up? If so, then that is indeed a bad idea. However, you
> > > can have a Recovery Catalog in a separate database that has other data,
> > > so long as the Recovery Catalog for that database is not in that
> > > database. For instance, I have two databases A and B that get backed up
> > > using RMAN. The RC for database A is in database B. And the RC for
> > > database B is in database A. Database A and B are used for other things
> > > as well. It should be noted that database A and database B are on
> > > separate physical servers.
> > >
> > > HTH,
> > > Brian
> > >
> > >
> > > --
> > > ===================================================================
> > >
> > > Brian Peasland
> > > dba_at_remove_spam.peasland.com
> > >
> > > Remove the "remove_spam." from the email address to email me.
> > >
> > >
> > > "I can give it to you cheap, quick, and good. Now pick two out of
> > > the three"
> >
> >
> > first time i read about rman i thought it would be best to have
> > atleast one dedicated RMAN instance and not put anything in it,
> > strictly from a management standpoint.
> >
> > how do you backup the other data that is in the instance that contains
> > rman? how do you manage the backup of your rman instance? just with
> > archive logs and hot backups?
>
> dude, its a database.
> the rman catalog is a schema in a database.
> when you take a statspack snapshot, you're storing data from an
> instance, as you're hitting dynamic and fixed views which contain data
> that are not stored in the database. they are contained in an
> instance. in memory only.
>
> when you backup a database, you copy blocks of data (rman) or copy
> physical files (hot: ocopy, cold: xcopy or your favorite *nix utility)
> from one file to another.
>
> If you have multiple versions of oracle databases for which you
> maintain catalogs, it is recommended in the literature to maintain a
> separate schema in the rman catalog database for each major version in
> the most recent database version.
>
> you backup the rman catalog database same as any other, with exp, hot
> or cold physical backup sets. I would not use rman to backup an rman
> catalog.
>
> the Oracle RMAN pocket reference is pretty handy for covering this
> kinda stuff.
> Veritas was nice enough to hand them out at RMOUG last March.
> There is also an RMAN reference text from Oracle Press.
>
> Pd
i didnt ask a single question about commands. I can get that out of
the docs. I was looking for information on experiences people have
had. What has worked best for you in practice. Those you cant get out
of the docs.
Received on Tue Oct 21 2003 - 06:55:00 CDT
