Re: RMAN: Partial Backup: Metadata Only in Some Tablespaces and Full Data in Another

Nope.  But creating a table in the wrong tablespace sure would.

If the applications use mutually exclusive sets of data, why not have two
databases?  Backup one with RMAN, and the other with datapump (metadata
only).

By the way, how long will it take to reload that 300GB from files?
Depending on your recovery window, RMAN backups may still be warranted.


On Mon, Feb 22, 2010 at 10:05 PM, Bobak, Mark <Mark.Bobak@xxxxxxxxxxxx>wrote:

>  Seems to me, if you set up a backup with the ‘exclude tablespace’ option,
> and the list of tablespaces to exclude is hardcoded, then adding new
> tablespaces in the future shouldn’t compromise anything….?
>
>
>
> -Mark
>
>
>
> *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
> oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Jared Still
> *Sent:* Monday, February 22, 2010 8:21 PM
> *To:* Chris.Langston@xxxxxx
> *Cc:* oracle-l@xxxxxxxxxxxxx
> *Subject:* Re: RMAN: Partial Backup: Metadata Only in Some Tablespaces and
> Full Data in Another
>
>
>
> On Mon, Feb 22, 2010 at 11:40 AM, Langston, Chris <Chris.Langston@xxxxxx>
> wrote:
>
> I need some help with configuring RMAN for Oracle 10gR2. I’ve been asked to
> submit a request to have our outsourced DBA’s configure our backup to
> exclude the data in certain tablespaces while doing full data backups in
> another tablespace.
>
>
>
> Can it be guaranteed that there will NEVER be a new tablespace added?
>
>
>
> If not, then this is sure to cause problems in the future.
>
>
>
>
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
> Oracle Blog: http://jkstill.blogspot.com
> Home Page: http://jaredstill.com
>



-- 
Cheers,
-- Mark Brinsmead
  Senior DBA,
  The Pythian Group
  http://www.pythian.com/blogs

Other related posts: