Richard
There is an old sample utility called adsmpipe floating around that uses
the API to backup from stdin and restore to stdout. It also has facilities
to list and delete backups.
A few small changes to the source of this would give you something that
uses the API and mimics TDPO, and could then be used to list and delete
your problem backups.
Regards
Steve.
Steven Harris
TSM Admin, Sydney Australia
Richard Rhodes
<rrhodes@FIRSTENE
RGYCORP.COM> To
Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU
Dist Stor cc
Manager"
<[email protected] Subject
.EDU> [ADSM-L] TDPO problem - can't
delete old tdpo backups
11/02/2009 07:17
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
We've been using rman/tdpo backups for over a year
now, and are still trying to get our heads fully
around it. I've been working with TSM support
on a problem and not getting very far, so I thought
I'd ask the list.
We have several TDPO nodes in a TSM server that have
old backups we cannot get rid of. In all other ways
TDP/TSM is working great. When we run TDPOSYNC it
says the RMAN catalog and TDPO is INSYNC - nothing to
cleanup. But, a list of objects form the backups table
in TSM for the node shows old backups. we keep backups
for 50 days - these old files are well back into last year.
What we think happened:
Back in Oct/Nov/Dec time frame, we did RESTORES on
several databases. According to the DBA's, part
of these restore was Oracle creating a new DBID (Database ID).
In essence, after the restore we had a completely NEW DATABASE.
>From RMAN's perspective, these were NEW DATABASES.
The old objects in TSM that we can't get rid of appear
to be from PRIOR TO THE RESTORE. It's as if both RMAN
and TDPO have no knowledge of these objects. The DBA
who handles rman/tdpo (who is very good!) says that
these old objects are NOT in RMAN. RMAN/TDPO/TSM is
CORRECTLY backing up and deleting backups SINCE the
restore. Also, we setup rman/tdpo so that every
Oracle db has it's own TSM node.
IBM suggested
1) delete them with the BA client. It doesn't work. It seems the files in
TSM have no owner, and the ba client won't/can't see them.
2) rename the node and start over. Yes, I can do this, but it seems to be
running around the problem.
or 3) User error (the dba and myself) - we don't understand something
about RMAN/TDPO/TSM.
It seems to me that I have either a RMAN bug, or a TDPOSYNC bug.
what I wish is that tdposync would list out the full set
of files that it is comparing from rman and tsm.
Yes, I'm aware of the "delete object" command . . . I really don't want to
go there!
=================
Here is an example of a the files in one of the problem nodes:
==> tsmsap2 TDPO-ONSITE SAPEQ1D1_DB
==> q node: SAPEQ1D1_DB AIX TDPO-ONSITE 1 1 No
<these lines are the old backups that tdposync/rman doesn't see>
i0jo7odu_1_1 ACTIVE_VERSION 2008-08-17
i8jo7tuc_1_1 ACTIVE_VERSION 2008-08-17
<deleted lines>
u7jrej66_1_1 ACTIVE_VERSION 2008-09-25
u8jrejb3_1_1 ACTIVE_VERSION 2008-09-25
<deleted lines>
ucjrejk0_1_1 ACTIVE_VERSION 2008-09-25
udjrejlo_1_1 ACTIVE_VERSION 2008-09-25
<GAP - no files - the lines below are GOOD backups that are created/deleted
correctly>
4mk2gkvp_1_1 ACTIVE_VERSION 2008-12-17
4tk2gv5l_1_1 ACTIVE_VERSION 2008-12-17
<deleted lines>
o0k3bpge_1_1 ACTIVE_VERSION 2008-12-28
o5k3bvvt_1_1 ACTIVE_VERSION 2008-12-28
<delted lines>
6pk410jh_1_1 ACTIVE_VERSION 2009-01-05
6uk4173b_1_1 ACTIVE_VERSION 2009-01-05
<deleted lines>
btk4iavp_1_1 ACTIVE_VERSION 2009-01-11
buk4ib01_1_1 ACTIVE_VERSION 2009-01-11
Thanks
Rick
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
|
