RE: Build RMAN catalog
- From: William Wagman <wjwagman@xxxxxxxxxxx>
- To: "Thomas.Mercadante@xxxxxxxxxxxxxxxxx" <Thomas.Mercadante@xxxxxxxxxxxxxxxxx>, "ravi.madabhushanam@xxxxxxxxx" <ravi.madabhushanam@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <Oracle-L@xxxxxxxxxxxxx>
- Date: Tue, 9 Jun 2009 09:26:50 -0700
Greetings,
It is my understanding that information does not gracefully age out of the
Tivoli catalog. For one user I setup RMAN backups directing output to tape
using Tivoli. The backup information Tivoli maintains did not age
automatically. The method the Tivoli admins provided was to do the following -
run {
ALLOCATE CHANNEL D1 TYPE 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=C:\Program Files\Tivoli\TSM\AgentOBA64\tdpo.opt)';
delete obsolete recovery window of 15 days device type 'sbt_tape';
}
Also, for Tivoli use the TDPOSYNC utility to reconcile differences between the
control file and TDP. For the most part, RMAN control file/catalog can be used
interchangeably with Tivoli Data Protection. TDPOSYNC is documented to have
some limitations with the control file, but we haven't encountered them yet.
Thanks.
Bill Wagman
Univ. of California at Davis
IET Campus Data Center
wjwagman@xxxxxxxxxxx
(530) 754-6208
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Mercadante, Thomas F (LABOR)
Sent: Tuesday, June 09, 2009 7:32 AM
To: ravi.madabhushanam@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Build RMAN catalog
Ravi,
To me, you seem to be making this much more complicated than it possibly
could be.
How about this approach:
Create the Rman catalog and register your database. This informs the
catalog of everything that the control file knows about. Start running
backups using the catalog today.
Now to me, I would not worry about the backups on tape. They will age
out automatically. They are only an issue if you need them to perform a
recovery. How far back have you guaranteed to be able to recover to?
This is a management decision. Lets say your management agreed that you
need to be able to roll back 30 days. Keep your tape backups for 30
days. Then start to resuse them. The Rman catalog knows nothing about
them - you probably have a manual process in place, right? Just keep
that process running for 30 days and you are done.
Optionally, look at cataloging files within the Rman catalog. This
might be your best bet.
I don't think I would restore a control file and resync that up. That
seems risky to me.
Hope this helps.
Tom
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Ravi Madabhushanam
Sent: Tuesday, June 09, 2009 8:16 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Build RMAN catalog
Hi All,
We have implemented RMAN backups for our database around 5 months
back. Initially to make the environment simple we didnt opted for a
recovery catalog database. Now we would like to implement the Recovery
catalog for our database and have few things to get clarified before
going forward.
1. Our present control_file_record_keep_time is set to 7 days. If i
create a catalog now at max i'll be having only 7 days of information
. What about the earlier information. Is there any way i can get that?
2. All our backups are taken to Tape (Tivoli). Presently we have many
backups on tape and we haven't deleted them yet. If we want to delete
those old copies we are unable to do so as the information about those
backup sets is not available in RMAN ( control file). how can i delete
those old stuff without affecting the consistency of the tape/recovery
catalog in control file.
3. We are planning to use the below approach to build the new recovery
catalog from scratch and resync it to have complete tape backup
information. below is the strategy i would like to follow..
(a) create a rcat database & register it with database
(b) resync the catalog to have the present control file information
dumped to catalog
(c) restore the oldest possible controlfile from tape ( which will
be around 20days old) and try to resync catalog from controlfile copy
. ===> i'm not sure about the effects of this command. Will this just
updates the old information to catalog and leave the new information
as it is? this is what i'm expecting ? but not sure how exactly it
behaves. Any inputs from anyone already tried would be really helpful.
(d) repeat the above process maximum possible times to make sure
that we have maximum possible information.
(e) clean up all obsolete backupsets from tape , which would ideally
delete old information as this should be present in catalog by now.
Please review my above plan and let me know if it is the right way or
not.
Any comments would be realy helpful.
Thanks & Regards,
Ravi.M
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
