Andy,

Using separate TSM nodes for OS backups and RMAN backups is generally
considered a best practice.  Assuming that's how you're doing it, the
RMAN node doesn't need any excludes or includes (other than if you are
overriding management classes for certain databases, as Remco said).

If your server uses filesystems for Oracle data rather than raw volumes,
you will want to exclude those locations from the OS backups on the
non-RMAN node.  If you are using raw volumes (hdisks, partitions, raw
LVs, etc.), those exclusions aren't necessary.

Some of the exclusions Grigori lists may be useful.  Consult with your
DBAs on which Oracle non-database files can be excluded.  Also on which
ones may need policy overrides (e.g. non-standard retention for RMAN
control files).

The use of multiple management classes from TDP for MS SQL doesn't
really apply to RMAN and TDP for Oracle.  MS SQL needs fast access to
the metadata to query the backups, so setting a keep/cache-on-disk
policy for that data improves performance for MS SQL backup queries
and restores.  RMAN (typically) relies on a catalog database or the
control files to query the backups and does not go to TSM for that.

=Dave


Huebner,Andy,FORT WORTH,IT wrote:
>
> That looks more like file system includes and excludes to me, but it
> has some good stuff in it.
>
> What I started with was:
> include /rman/.../* MGMT_DB_Pool_01
>
> My only example was what we do for SQL, which has 3 includes of SQL
> specific objects.
>
>
> Andy Huebner
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Grigori Solonovitch
> Sent: Friday, June 08, 2012 2:12 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] RMAN Options Unix
>
> Hallo Andy,
> You need to use something similar to:
>
> include * AIX                              - actually, no need to have this, 
> but AIX is default management class
> include /.../* FSLPAR05                    - all AIX files (there is no 
> database files, because are using raw logical volume as datafiles)
> include /ifnd/.../* DBLPAR05               - management class for 3 Oracle 
> databases (node is different from node for normal files)
> include /patm/.../* DBLPAR05
> include /ptel/.../* DBLPAR05
> exclude.dir /home/oracle/admin/ifns/adump  - just to exclude Oracle audit 
> files from backups (very big number of files)
> exclude.dir /home/oracle/admin/patm/adump
> exclude.dir /home/oracle/admin/ptel/adump
> exclude.dir /home/oracle/product           - exclude Oracle home from backups 
> (no sense to backup)
> exclude.compression *.Z                    - exclude compression for already 
> compressed files
> include.encrypt /ifns_ifns/.../*           - encrypt database backups (rman 
> backups)
> include.encrypt /patm_patm/.../*
> include.encrypt /ptel_ptel/.../*
> include.encrypt *.dmp.Z                    - encrypt databse dumps
>
> I hope this will help or, at least, will give right direction.
> Rergards,
>
> Grigori G. Solonovitch
> Senior Technical Architect  Ahli United Bank Kuwait  www.ahliunited.com.kw
>
> Please consider the environment before printing this E-mail
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Huebner,Andy,FORT WORTH,IT
> Sent: 08 06 2012 9:36 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] RMAN Options Unix
>
> We are setting up our first Oracle RMAN nodes.
> The part we are not sure about are the include and excludes.  Are
> there any include and excludes we should use?  These are AIX and x86
> Linux Oracle servers.
>
> Andy Huebner
>


--
Hello World.                                David Bronder - Systems Architect
Segmentation Fault                                      ITS-EI, Univ. of Iowa
iore dumped, disk trashed, quota filled, soda warm.   david-bronder AT uiowa 
DOT edu