Re: HELP RMAN Best Practices

It does not really matter what machine you run RMAN from because RMAN is just an utility dealing with connection strings to the target database and catalog's database (if used) through net8. You actually need to take care of recovery catalog reliability (backup) if you use it. Moreover you can run RMAN from a PC to make a database backup which resides mainframe using recovery catalog on UNIX's database.

Eugene.

Van Messner <vmessner_at_bestweb.net> wrote in message news:x8Ut4.4374$Zh4.673301_at_newshog.newsread.com...
> If I have the recovery catalog database on separate server from the target
> database, then I have two copies of RMAN since RMAN installs as part of
> Oracle. What's the best practice in terms of running RMAN -
> 1) Run the Rman.exe that's on the catalog server
> 2) Run the Rman.exe that's on the target server.
>
> Option 1 can be awkward since you have to keep a copy of the target
database
> pfile on the catalog server in order to startup the target database. This
> is even more awkward if you have ten different targets on ten different
> servers.
>
> Option 2 means you have to go to each target server to run RMAN. And what
> happens if you lose a target server. Do you lose all your RMAN scripts
for
> that target? If not do you secure them by copying them to some other
> machine?
>
> My first thought was to go with option 1. I asked Oracle support and they
> said they though most people used option 2, although 1 would work. What
do
> you all do/think?
>
> Thanks,
>
> Van
>
>
Received on Sun Feb 27 2000 - 13:12:10 CST