hi Oliver,
I don't have any comment regarding bare metal restore. Please see my
comments below for oracle connect agent.
management class
management class for oracle agent must have verdelete=0 and retonly=0 to
be able to delete the backups. I would recommend using different domain
for oracle agent backups. For oracle agent backups, we also recommend to
use different nodename from b/a client backups.
version of agent and API
I don't know what version of agent you have now. If you have agent level
2.1.7, there is a fix test 2.1.7d. Agent 2.1.7 requires version 3.1API.
There is a new PTF, 2.1.9b available which requires API 3.7.1. So it
depends on which b/a client level you are using now.
I can only perform full (offline or online) backups at the weekend. Is it
better to backup the archived redo logs during the week or to use the
"incremental" function of
RMAN?
I would recommend backing up archive logs everyday rather than incremental
backups. There are two reasons to it:
1. incremental backup will take almost as long as a full database backup.
2. recovery time will be longer than applying archive logs.
regards,
Thiha
>I have to implement an ADSM installation, where a Sun Solaris 2.6 Client
with a
>500 GB
>Oracle 8.1.5 DB has to be backed up using Oracle´s Recovery Manager
(RMAN).
>Does anyone has some advices to:
>- SUN Solaris bare metal restore
>- concept for RMAN with ADSM (f.e. which data to divide into which
different
>management classes)
>- which version of the connect agent & API go with Oracle 8.1.5 on Solaris
2.6
>(RMAN Catalog is Oracle 8.0.3)
>- I can only perform full (offline or online) backups at the weekend. Is
it
>better to backup
> the archived redo logs during the week or to use the "incremental"
function of
>RMAN?
>Thank you for any suggestions!
>Kindly regards, Oliver Janzen.
>ojanzen AT de.ibm DOT com
>Date: Wed, 9 Feb 2000 14:29:35 +0200
>From: Clarence Beukes <clarence AT ZA.IBM DOT COM>
>Subject: Re: Management Class DEFAULT
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
|
