Good idea to read the doc, but shortly:
RMAN does not backup online redo logs, only archived redo logs.
RMAN never backs up software, administrative scripts, init files, or
password files.
With the mountpoints, and directories setup, as well as restorations of
those items mentioned above, RMAN should have no problem restoring and
recovering a database provided proper incremental backups and archived logs
are available.
KRoshto
Steve and Hilda Harris <sjharris AT OZEMAIL.COM DOT AU>@VM.MARIST.EDU> on
11/01/2000 07:51:21 AM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Oracle Database Query
Hi All
I've just taken over a somewhat badly organized site and have a query about
Oracle databases on normal file systems.
At my previous position the Oracle databases resided on AIX raw logical
volumes, so I didn't have to exclude them from filesystem backups and on a
restore (say to a replaced disk) I had to arrange for the logical volumes
to
be created prior to the restore process running.
At the new site the databases reside on normal filesystems. Currently the
database files aren't excluded and so they are backed up by the BA client.
Worse, the application is up so if a checkpoint is taken Oracle touches
every file and TSM has to resend the file currently being backed up.
Assuming that we have appropriate RMAN backups and an RMAN catalog
database,
what happens when we try to restore an instance to a clean filesystem
(again
assume that the disk has been replaced). Will RMAN handle the creation of
all the underlying files - pfiles, control files, log files, and
tablespaces - or do I need to have some basic set of files already present
on disk for RMAN to work?
i.e. if I have only RMAN backups and exclude all tablespace, control and
log files from the BA client backup can I restore the instance?
Thanks for listening
Steve Harris
AIX, ADSM Contractor
Queensland Health, Brisbane Australia
|
