----- Original Message -----
Sent: Thursday, January 09, 2003 1:18
PM
Subject: RE: RE : RMAN Repository
Yeah but do you have to pay for another Veritas NetBackup
license and server to backup the catalog? If just have one database server and
one database license why should I have to buy another license and install
another 1-2GB of Oracle software on another server? The only answer I can
think of is so Larry can spend more money on yachts, planes, and cars.
Contrary to Oracle Corporate aspirations, not all data in the
universe really needs to be stored in Oracle databases, especially backup
information about Oracle databases I want to backup. If I need a database to
backup a database then do I need another database to backup the database that
backed up the original database? ;-) Seems the simple solution to this
silliness is just to remove the requirement of having a database to backup a
database.
Steve Orr
-----Original Message-----
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 09, 2003 10:50 AM
To: [EMAIL PROTECTED]
Cc: Orr, Steve
Subject: RE: RE : RMAN Repository
Importance: High
> The overhead of the repository database is more. With the
initial
releases of RMAN (EBU) Oracle was rightly
> criticized for the fact that you had to backup
the database that holds
information about the database
you want to backup.
> Getting rid of this silliness
seems reasonable to me.
Why silly?
It isn't any more silly than making a separate backup of the
Veritas
Netbackup catalog.
It's just a different level of abstraction.
Jared
"Orr, Steve" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
01/09/2003
08:45 AM
Please respond to ORACLE-L
To:
Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: RE: RE : RMAN
Repository
If you aren't using a repository all you have to do is make
sure control
file backups are part of the routine.
There are 2 ways to backup the
backup metadata: 1) the
RMAN repository database; 2) backup controlfiles.
Functionally and operationally they're pretty much the same. The only
things you can't do with controlfile RMAN/database
metadata is: 1) use
previous "incarnations" of the
database for recovery; 2) use database
stored scripts.
No big deal as far as I'm concerned.
When RMAN first
came out a separate repository database was a requirement.
Subsequent releases added some functionality for using controlfiles.
The
vulnerability of losing the repository or losing
the backup controlfile is
about equivalent. The
overhead of the repository database is more. With
the
initial releases of RMAN (EBU) Oracle was rightly criticized for the
fact that you had to backup the database that holds
information about the
database you want to backup.
Getting rid of this silliness seems
reasonable to
me.
Steve Orr-man for RMAN,
Bozeman,
Montana
-----Original Message-----
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 2:14 PM
To: Multiple recipients of list ORACLE-L
Subject: RE : RMAN Repository
Importance: High
And how does one go about restoring a database when all
control files
are lost, and the only recovery data is
stored in the control file?
This doesn't sound very
reasonable.
Jared
"Deshpande, Kirti" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
01/08/2003 11:44 AM
Please respond
to ORACLE-L
To:
Multiple recipients of list ORACLE-L
<[EMAIL PROTECTED]>
cc:
Subject: RE : RMAN Repository
Joe,
That's what I have
heard (from 2 Oracle University
Professors/Lecturers/Demonstrators). But no one would tell me when it
may
happen. We do not use RMAN (yet) so I did not
pursue it further.
- Kirti
-----Original Message-----
Sent: Wednesday,
January 08, 2003 1:08 PM
To: Multiple recipients of
list ORACLE-L
<snip>
Obilgatory oracle statement/question: rumor has it by some
instructors
that RMAN repository is going away and
only control file recoveries
will be possible, truth
or fiction?
joe
