Backup Central

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


This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments.

Thank you.

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.EDU] On Behalf Of Huebner,Andy,FORT WORTH,IT
Sent: 08 06 2012 9:36 PM
To: ADSM-L < at > VM.MARIST.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


This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments.

Thank you.


Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.

Hi,

you definitely don't need any excludes.

normally you don't need any includes, only if you need some special management class for some databases, because they go into another storage pool, will you need any. R/man manages expiration for all log archives and all backups.

On 8 jun. 2012, at 20:36, Huebner,Andy,FORT WORTH,IT wrote:

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


This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments.

Thank you.

--
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post < at > plcs.nl
+31 6 248 21 622

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.EDU] On Behalf Of Grigori Solonovitch
Sent: Friday, June 08, 2012 2:12 PM
To: ADSM-L < at > VM.MARIST.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.EDU] On Behalf Of Huebner,Andy,FORT WORTH,IT
Sent: 08 06 2012 9:36 PM
To: ADSM-L < at > VM.MARIST.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


This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments.

Thank you.


Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.

This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments.

Thank you.

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.EDU] On Behalf Of Grigori Solonovitch
Sent: Friday, June 08, 2012 2:12 PM
To: ADSM-L < at > VM.MARIST.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.EDU] On Behalf Of Huebner,Andy,FORT WORTH,IT
Sent: 08 06 2012 9:36 PM
To: ADSM-L < at > VM.MARIST.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.edu

I am sorry for some broken lines in given example. Correct list is:

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

Of course, this include/exclude list is used by TSM Client to backup AIX flat files (normal file systems), database dumps and databases via RMAN --> TDPO --> TSM Client. In addition, it contains lines for compression and encryption data.
Note I am using two different nodes for file systems and databases like LPAR05 and LPAR05_ORA with dedicated dsm.sys configuration files:
1) for file systems /usr/tivoli/tsm/client/ba/bin64/dsm.sys:

SErvername BKME
COMMmethod TCPip
TCPPort 1500
TCPServeraddress tsmsrv1
passwordaccess generate
resourceutilization 2
largecommbuffer yes
TCPbuffsize 32
TCPnodelay yes
TCPwindowsize 1024
TXNbytelimit 262144
Nodename LPAR05
Encryptiontype AES128
Encryptkey generate
InclExcl /backup/tsm/ba/InclExcl.list
dirmc FSLPAR05
schedmode prompted
User sa27162 sa25577 edp11797 edp18562

2) for databases /usr/Tivoli/tsm/client/api/bin64/dsm.sys:

SErvername BKME
COMMmethod TCPip
TCPPort 1500
TCPServeraddress tsmsrv1
passwordaccess prompt
resourceutilization 2
largecommbuffer yes
TCPbuffsize 32
TCPnodelay yes
TCPwindowsize 1024
TXNbytelimit 262144
NODENAME LPAR05_ORA
Encryptiontype AES128
Encryptkey generate
dirmc DBLPAR05
Inclexcl /backup/tsm/ba/InclExcl.list

In addition, I have TDPO configuration file used by rman like:

DSMI_ORC_CONFIG /backup/tsm/api/dsm.opt
DSMI_LOG /backup/tsm/log
TDPO_FS ifns
TDPO_NODE LPAR05_ORA
TDPO_OWNER oracle
TDPO_PSWDPATH /usr/tivoli/tsm/client/oracle/bin64
TDPO_TRACE_FLAGS ORCLEVEL0
TDPO_TRACE_FILE /home/oracle/admin/tdpo/ifns.trc

Note, TDPO_FS defines file space name for database backups and this file space name is used in include/exclude list similar to normal file system.

So, as you see, it is not so simple.

In addition,

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.EDU] On Behalf Of Huebner,Andy,FORT WORTH,IT
Sent: 09 06 2012 12:48 AM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] RMAN Options Unix

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.EDU] On Behalf Of Grigori Solonovitch
Sent: Friday, June 08, 2012 2:12 PM
To: ADSM-L < at > VM.MARIST.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.EDU] On Behalf Of Huebner,Andy,FORT WORTH,IT
Sent: 08 06 2012 9:36 PM
To: ADSM-L < at > VM.MARIST.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


This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments.

Thank you.


Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.

This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments.

Thank you.


CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.

Just some comments about RMAN expiration process:
1) you need to register each database in RMAN catalog;
2) just to be sure you need to set recovery window for each database as oracle owner user (for example, to have 31 day recovery window):

#!/bin/sh
#
export ORACLE_SID=ifns
export ORACLE_BASE=/home/oracle
export ORACLE_HOME=`grep "ifns:" /etc/oratab | head -n1 | cut -f2 -d":"`
export PATH=$ORACLE_HOME/bin:$PATH
export TNS_ADMIN=$ORACLE_HOME/network/admin
#
# Configure backup policy
rman <<EOF
#
# Connect to Recovery Manager Catalog Database
connect catalog $RC_USER/$RC_PASSWORD < at > $RC_SERVICE;
#
# Connect to target database
connect target;
#
# Set retention policy
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 31 DAYS;
#
EOF

3) perform some daily purging for each database like:

#!/bin/sh
#
export ORACLE_SID=ifns
export ORACLE_BASE=/home/oracle
export ORACLE_HOME=`grep "ifns:" /etc/oratab | head -n1 | cut -f2 -d":"`
export PATH=$ORACLE_HOME/bin:$PATH
export TNS_ADMIN=$ORACLE_HOME/network/admin
#
# Backup database, archived logs and control file
rman <<EOF
#
# Connect to Recovery Manager Catalog Database
connect catalog $RC_USER/$RC_PASSWORD < at > $RC_SERVICE;
#
# Connect to target database
connect target;
#
# To maintain backups
run {
#
# Allocate channel for maintenance
allocate channel for maintenance type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=/home/oracle/admin/tdpo/$1.opt)';
#
# Report unrecoverable data files
report unrecoverable database;
#
# Report data files required backup according to retention policy
report need backup database;
#
# Report number of redundant backups
report need backup redundancy 7 database;
#
# Report number of incremental backups
report need backup incremental=0 database;
#
# Delete obsolete backups
delete noprompt obsolete;
#
# Release TSM channel
release channel;
#
exit
EOF

4) periodically run cross-check procedure against RMAN and TDPO:

#!/bin/sh
#
# Cross-check Recovery Catalog and TSM database
#
# Input parameters:
# 1 - database SID.
#
export ORACLE_SID=$1
export ORACLE_HOME=`grep "$1:" /etc/oratab | head -n1 | cut -f2 -d":"`
export PATH=$ORACLE_HOME/bin:$PATH
export TNS_ADMIN=$ORACLE_HOME/network/admin
#
#######################################################################
# Remove expired datafiles, control files and archived redo log files #
#######################################################################
rman <<EOF
#
# Connect to Recovery Catalog database
connect catalog $RC_USER/$RC_PASSWORD < at > $RC_SERVICE;
#
# Connect to target database
connect target;
#
# Allocate channel for maintenance
allocate channel for maintenance type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=/home/oracle/admin/tdpo/$1.opt)';
#
# Set date and time format
sql 'alter session set NLS_DATE_FORMAT = "YYYY-MM-DD:HH24:MI:SS"';
#
# Resynchronize catalog
resync catalog;
#
# List database incarnations
list incarnation;
#
# List backups
list backup summary;
#
# Crosscheck backups
crosscheck backup;
#
# List expired backups
list expired backup summary;
#
# Delete expired backups
delete noprompt expired backup;
#
# Delete obsolete backups
delete noprompt obsolete;
#
# Release channel
release channel;
#
# Allocate channel for maintenance
allocate channel for maintenance type disk;
#
# Check archived logs on disk
crosscheck archivelog all;
#
# Remove obsolete archived redo logs
delete noprompt expired archivelog all;
#
# Release channel
release channel;
#
exit;
EOF

So, everything is not very simple, but after correct configuration everything is working fine for many years.
Good luck!

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.EDU] On Behalf Of Remco Post
Sent: 08 06 2012 11:47 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] RMAN Options Unix

Hi,

you definitely don't need any excludes.

normally you don't need any includes, only if you need some special management class for some databases, because they go into another storage pool, will you need any. R/man manages expiration for all log archives and all backups.

On 8 jun. 2012, at 20:36, Huebner,Andy,FORT WORTH,IT wrote:

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


This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments.

Thank you.

--
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post < at > plcs.nl
+31 6 248 21 622


Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.