David,
I suggest you to use the hidden "show version" command on your server, that
will allow to list the contents of backed up data on the server.
Just issue : "show version nnnn xxxx nametype=fsid" with nnnn=node_name and
xxxx=filespace_FSID
This is my favorite method !
Cheers.
Arnaud
******************************************************************************
Panalpina Management Ltd., Basle, Switzerland,
CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
******************************************************************************
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David E Ehresman
Sent: jeudi 4 juin 2009 16:10
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM for Oracle
I understand that rman CAN automatically delete old backups. As a TSM Admin, I
am being asked to verify that rman IS deleting old backups. Is there any way
to verify such from the TSM side?
David
>>> Grigori Solonovitch <G.Solonovitch AT BKME DOT COM> 6/4/2009 1:42 AM >>>
I am using RMAN 9i/10g with TSM 5.5 successfully.
RMAN manages data expiry for Oracle databases completely without any manual
intervention, but some configuration efforts are required:
1) dedicated TSM node for Oracle data with management class and copy group;
2) set vere=no limit, verd=0 rete=<N> ret=0 in copy group, where <N> is a
period of time in days to be able to recover database (I am using 31 day);
3) for each database set retention period in RMAN by CONFIGURE RETENTION POLICY
TO RECOVERY WINDOW OF <N> DAYS, where <N> equal to <N> in copy group;
4) run full database backup periodically. I am running full database backup
twice per month with retention period 31 days. All other days run incremental
backup for database;
5) perform " delete noprompt obsolete" from RMAN backup script;
6) schedule at proper time "crosscheck backup" + "delete noprompt expired
backup" + "delete noprompt obsolete" daily for each database (just not to delay
backups);
7) schedule "crosscheck archivelog all" + "delete noprompt expired archivelog
all" daily for each database (just not to delay backups)
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East http://www.bkme.com
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: G.Solonovitch AT bkme
DOT com
Please consider the environment before printing this Email
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David E Ehresman
Sent: Wednesday, June 03, 2009 8:59 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM for Oracle
Do can a TSM Admin verify that the rman clients are deleting their old TSM for
Oracle backups?
David
Please consider the environment before printing this Email.
"This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are not the
named recipient(s), please delete this email after notifying the sender
immediately. BKME cannot guarantee the integrity of this communication and
accepts no liability for any damage caused by this email or its attachments due
to viruses, any other defects, interception or unauthorized modification. The
information, views, opinions and comments of this message are those of the
individual and not necessarily endorsed by BKME."
|
