Skip to Main Content
  • Questions
  • Periodically Test Recovery Procedures

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Eliomar.

Asked: November 18, 2020 - 5:10 pm UTC

Last updated: November 23, 2020 - 6:29 am UTC

Version: 19c

Viewed 1000+ times

You Asked

Hello Team,

I need to document our RMAN backup and restore best practices, and I'm struggling to answer the question:

How often (months, years, etc.) should we test our restore procedures? (max time between restores, at least "RESTORE... VALIDATE")

Thanks.



Here an old document:

https://docs.oracle.com/cd/B12037_01/server.101/b10726/configbp.htm#1007459

and Connor said...

I'll propose a slightly different metric.

"Test" (and improve) your RMAN restore/recovery processes so that you can get a non-technical person to do it via running a single command at a terminal (because one day, that might be one you need to do).

If you can get your process so that it resembles:

myhost:$  restore_production_to_backup_node.sh
Enter the last moment in time everything was fine (YYYY/MM/DD HH24:MI:SS)
(Default will be to try recover as up to date as possible)


Then now you have something you can test at *any* frequency you want, and in particular get anyone to test it for you, or even make it an automated test. Its a fantastic level to strive for.

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

... and you then fork these tests out to Finance/Controlling/Auditors Depts

Christian Klammer, November 27, 2020 - 7:32 am UTC

... and then you are able to fork out these tests out to Finance/Controlling/Auditor Depts.

Auditors love this stuff: they live for it ;-) ... and they will document everything they do very carefully, too.

Means you will have an other department doing your work off your budget ... :-)

More to Explore

Backup/Recovery

Check out the complete guide to all of the Backup & Recovery techniques in the Oracle Database.