The worst kind of recovery to experience is a time-base recovery. Although not necessary, we
have been in a position, several times, where we had to create a completely new database
instance for the purpose of recovery. Under this situation you will need the following:
-Backup of Control files (Can use current version from production)
-Datafile backups (most importantly System tablespace datafiles, more frequently if possible)
-Archive Log file backups.
If you have a device failure, you fix the device, restore the datafiles and apply archive log
files. If someone drops a table, consider shooting them (joke) and then create a recovery
instance that consists of the system datafile(s) and the datafiles comprising the tablespace
where the dropped table once existed. Apply archive log files until you're happy and if
necessary, OPEN RESETLOGS, export, import, and you're back on the map again. Not much detail, I
know, but characterizes which backups are necessary.
I cannot find the justification for backing up rollback segment datafiles or Redo log files.
If anyone else can find reason for backing up more than the three file types above I would like
to have those reasons explained without having the text transposed.
Thanks.
-D