Matthew Huff schrieb:
Yes it is possible. In fact, it is required even with RMAN catalogs. In order
to backup the RMAN catalog, you can't use the RMAN catalog. The info about the
backup is saved in the control files. The biggest difference is that you can't
store scripts in the RMAN database. Then again, with Legato, you usually don't
anyway. You lose some reporting and flexibility, but with a single database, it
shouldn't be an issue. Just follow the instructions here:
Hi list,
i would like to add a few bits here.
First of all RMAN is an oracle product. It takes the blocks from
the database and puts these block either on disk (built-in support)
or transfers them to a media management library (libnwora.so - the
library which costs the money).
RMAN itself must store what was backed up (which datafile, which
scn and so on). This information is neccessary for restore/recovery
and can be stored in the control files or in an rman catalog.
Storing the information in the control files is problematic in
cases where all your data (including the controlfiles) is gone:
How do you tell the rman what to restore if the information about
the backups are in the control files which are not available?
The answer: There are ways to restore the control files from networker,
but it might be time consuming. The most dangerous part here is that
you need to restore the most recent backup of the control files. Any
other version leads to data loss because an older version of the control
files does not know about backups which were performed after the control
file was backed up.
The rman catalog is a auxilliary database which is installed on a
separate system (*not* the same system as where the database to be
backed up is located on). The rman catalog database is very small
(approx. 2 GB in total size; 512 MB memory usage) and you do not need an
oracle licence for it as long you only use it as rman catalog!
You need to backup this database as well: I prefer rman backups to disk
plus exports which are saved with networker. In case of emergency it is
unlikely the server with the rman catalog and the database server
are affected at the same time. For instance i have installed the rman
catalog on the networker server (no networker server - no database
restore!). The database itself is self managing. Nearly no data
growth and no problem as far as i have seen. And you can use one
database as rman catalog for all your databases. With three years of
backup information for > 20 database our catalog is 500 MB in total
size.
Storing the rman information in an auxilliary rman catalog
gives you some report functionality - thats nice to have but
not the cause for using the rman catalog.
The main reason is: If all your data is gone and you have an rman
catalog, simply recover your database server with oracle binary
installation, start rman, connect to the rman catalog database and
start you recovery! Thats it.
Because you do not need to cope with restores of control files
you will save a lot of time and it will always restore the most recent
backups!
Hope that helps.
(If anything is unclear - drop me a mail... i had to hurry.)
--
Mit freundlichen Grüßen
Ronny Egner
Diplom-Ingenieur (BA)
Systeme & Service
Oracle Certified Professional (OCP)
Telefon: +49 381 2524-422
Telefax: +49 381 2524-399
SIV.AG - Service für Informationsverarbeitung AG
Hauptsitz: Konrad-Zuse-Str. 1, 18184 Roggentin
Handelsregister: Amtsgericht Rostock, HRB 8677, Ust.-IdNr.: DE 137477226
Vorstand: Jörg Sinnig (Vorsitzender), Andreas Lehmann, Arno Weichbrodt
Aufsichtsratsvorsitzender: Thomas Huth
*************************************************************************
Aus Rechtsgründen ist die in dieser E-Mail gegebene Information nicht
rechtsverbindlich. Eine rechtsverbindliche Bestätigung reichen wir
Ihnen auf Anforderung in schriftlicher Form nach. Diese Nachricht ist
ausschließlich für den Adressaten oder dessen Vertreter bestimmt.
The information contained in this email is not legally binding.
At your request, we will provide you with a legally binding confirmation
in written form. This message is intended solely for the addressee,
entity to which the email is addressed or the authorised agent.
*************************************************************************
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
