RE: RMAN Testing Suggestions

Dennis,

That's a good start.

Here's something else to consider.

In the past, I've had recoveries fail that depended on the size of the database file. It recovered fine for a file up to a certain size. Anything larger and it failed. If I remember correctly, it was more of a hardware problem than software.

But I would only consider a recovery successful if you performed a full recovery of your production database. Otherwise, you are just whistling in the dark - you never really know if it's going to work until it *has* to.

Just my little 2 cents.

Hope it helps.

Tom

-----Original Message-----

From: DENNIS WILLIAMS [mailto:DWILLIAMS_at_LIFETOUCH.COM] Sent: Monday, November 22, 2004 10:23 AM To: ORACLE-L
Subject: RMAN Testing Suggestions

List - Recently in response to an RMAN question, several listers mentioned how critical it is to perform a test recovery after configuring RMAN. I agree whole-heartedly. I was wondering if some people could share some details of what tests seem appropriate. A simple test I can think of is to backup the database, then shut it down, rename the system datafile, then attempt to bring the database back up, then recover the datafile using an RMAN command and open the database. Is this test sufficient? On one hand I want to ensure RMAN is correctly configured for backup and recovery, but on the other hand these tests are best performed on a new database before handing it over to the users. And the users are usually clamoring to use the database, so I don't want to conduct extensive tests that are just testing RMAN itself. Any thoughts?  

Dennis Williams

DBA Lifetouch, Inc.

--

http://www.freelists.org/webpage/oracle-l
--

http://www.freelists.org/webpage/oracle-l Received on Mon Nov 22 2004 - 10:09:16 CST