Re: TDP for Oracle Expiration
2002-08-21 13:50:09
If you are using RMAN and TDPO you need to set the copy group like this:
Policy Policy Mgmt Copy Versions Versions Retain Retain
Domain Set Name Class Group Data Data Extra Only
Name Name Name Exists Deleted Versions Version
--------- --------- --------- --------- -------- -------- -------- -------
ORACLE ACTIVE ORACLE STANDARD 1 0 0 30
All deletes should be handled by RMAN, not by TSM. TSM will expire the data
once RMAN deletes the backup files. The TDPO manual and RMAN have sample
scripts for handling this.
Eric
-----Original Message-----
From: Zig Zag [mailto:veritrash AT yahoo DOT com]
Sent: Wednesday, August 21, 2002 8:26 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for Oracle Expiration
Chris,
I have a DB2 client that wants everything kept for 30
days and nothing more.
Here is my copygroup settings/mgmt class assignments.
Policy Policy Mgmt Copy Versions
Versions Retain Retain
Domain Set Name Class Group Data
Data Extra Only
Name Name Name Exists
Deleted Versions Version
--------- --------- --------- --------- --------
-------- -------- -------
UDBDOM ACTIVE DB2PROD STANDARD 1
0 30 0
The reason I have this set up this way is due to the
File naming convention they use. file.dateandtime
Look at the file naming convention used and determine
what is right for you..
--- "Renke, Chris" <CRenke AT ELLIOT-HS DOT ORG> wrote:
> Backup objects are not expiring. I am using a
> recovery catalog to track the
> rman backups.
>
> Thanks in advance,
> Chris Renke
> Elliot Health System
> 4 Elliot Way Suite 203
> Manchester NH 03103
> 603-663-7459
> crenke AT elliot-hs DOT org
>
>
>
> ------------------------------------------------
>
> AIX: 4.3.3
> TSM 4.1.1
> TDP 2.2.1
> Oracle 8.1.7
>
> Backup Copy Group:
> Versions Data Exists 7
> Versions Data Deleted 0
> Retain Extra Versions 0
> Retain Only Version 0
__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
|
|
|