Restoring the database thru RMAN using a remote tape device can be a little
tricky. Restoring an entire database from scratch is actually pretty easy
if you are on the same box restoring the same database but when you start
remoting everything and changing things, it gets weird real quick. A whole
lot of what you can restore with RMAN depends on how you backed it up. I
know that sounds like an obvious statement but when you start talking about
RMAN database backups, there are so many options for backing up control
files, archive logs, etc that it's real easy to make a mistake. Basically,
you don't need anything except the configuration file and the catalog
database on the remote system to do a restore if you took the right kind of
backup.
Here's an idea. If you have the disk space, change the backup type from
tape to disk. Don't change anything else, just take a disk backup using
RMAN. Then you can move the backup files around wherever you like and test
the restore, a lot easier than connecting to a remote tape device. This
won't test the physical tape media but it will test to make sure you can
bring the database up at a remote location as the backup is correctly
configured.
Another extremely important part of RMAN backups is the catalog database.
You need it to do the restore except under certain circumstances.
There are lots of examples on metalink.oracle.com but you have to have
Oracle support to get in (I think).
Hope this helps.
Jim Edwards
-----Original Message-----
From: Chad Smykay [mailto:csmykay AT rackspace DOT com]
Sent: Monday, September 29, 2003 10:20 AM
To: 'James Edwards'; 'Legato NetWorker discussion'
Subject: RE: [Networker] Help with Oracle NMO and Directed Restore
Thanks Jim.
I got a pretty good doc from Pieter on it. I understand how RMAN works in
regards with Legato. However I am NOT by no means an Oracle DBA (but
somehow have to be for my job). Basically I have a customer that wants to
"test" the actual backup we have from RMAN on our Legato system. However he
can not bring down the main database because of it being a production
system. He does have another server that has some test instances of Oracle
databases which we can restore to. This is on a separate server. Both the
production and the test server are Win2k. I have an RMAN script to restore
table spaces but this is just way over my head as I am not (nor would I like
to be) an Oracle DBA. So my question is how do we create a test instance on
the test server for a proper restore? And also how does it affect an
instance if it were re-named on the test server. For example the production
servers instance is "prod1", but the test server has an instance of
"seconddb" will this effect the restore if they are not the same instance
name? Then is it possible to just re-create everything through RMAN from
the backups? If not how does one get a good solid instance up. Do you need
to get all of the archive logs, redo logs and control files in place before
that backup. Let me know what you think.
Thanks,
Chad Smykay, RHCE
-----Original Message-----
From: James Edwards [mailto:jedwards AT sos.state.tx DOT us]
Sent: Monday, September 29, 2003 9:55 AM
To: 'Legato NetWorker discussion'; 'Chad Smykay'
Subject: RE: [Networker] Help with Oracle NMO and Directed Restore
You seem to be confusing a few things. First off a few words of
explanation.
If you are using RMAN, Legato is nothing more than a media manager, a way
for RMAN to write to your jukebox. So, that being said, everything you do
you do thru RMAN and just configure things so it can see the tapes. You
don't use Legato directed recover, you use RMAN. RMAN is a very powerful
tool but it is also very confusing at times and using it with Legato
confuses things even more.
That being said, depending on what you want to do, there might be a better
way to skin this cat. Naturally, if you are testing disaster recovery using
these tapes, you don't have much choice but if you just want to get the
database on the other machine, there are lots better ways to do it. Give us
a little more info on what you want to do and why and I'll see if I can
help.
Jim Edwards
-----Original Message-----
From: Chad Smykay [mailto:csmykay AT RACKSPACE DOT COM]
Sent: Monday, September 29, 2003 9:17 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Help with Oracle NMO and Directed Restore
Anyone? Anyone?
Regards,
Chad Smykay
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On
Behalf Of Chad Smykay
Sent: Wednesday, September 24, 2003 1:20 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Help with Oracle NMO and Directed Restore
Does anyone have a good step by step document on restoring an oracle
database to an alternate server? I know that you need to create a new
"test" instance on the server you want to restore to. I also know that the
hostname of the needs to be in the "remote access" list on the legato
networker server. I have read the legato document on performing a restore
but it does not document what needs to be done on the Oracle side of things
very well.
So what I am asking is how does one restore an Oracle database from a full
that is being preformed with RMAN. I have verified that the backups are
good however I don't know where to start when you a directed restore. After
I create a "test" instance on the server I am directing the restore to do I
then restore all of the files that are in the "oradata" folder for that
instance? And if that is correct do I then stop that instance copy the
files over start it and then connect in with RMAN and then perform the
normal RMAN table space recovery?
Any help on this issue would be awesome. I am not an Oracle DBA and have
little experience with it. Just a good idea of where to start would help.
Thanks,
Chad Smykay, RHCE
Storage Administrator
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.516 / Virus Database: 313 - Release Date: 9/1/2003
--
Note: To sign off this list, send a "signoff networker" command via email to
listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also view
and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.516 / Virus Database: 313 - Release Date: 9/1/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.516 / Virus Database: 313 - Release Date: 9/1/2003
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.516 / Virus Database: 313 - Release Date: 9/1/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.516 / Virus Database: 313 - Release Date: 9/1/2003
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
