>Our Environment has the following setup.
>1. Oracle 10.2 running on Linux.
>2. NMO 4.2 library has been installed in $ORACLE_HOME/lib.
>3. Oracle Database TEST has been created and RMAN activated.
>
>In order to backup my RMAN backup files to my Backup server, what are
>the steps I have to take?
>
>1. What could be server side settings?
>2. What could be client side settings?
>3. How to activate the backup?
>4. Is it from the Backup server end or from the Client?
>5. Can we use cron jobs instead?
>Please if anybody works in this environment, please clarify.
>Thanks
>Bhaskar
Each Oracle Instance will require a separate client configured for a Full
and also one for the Incremental (level 1). Then you can setup a 3rd
instance to backup the rest of the system using a directive to skip oracle
databasse files, redologs etc, and a saveset of ALL...
Create a Group for your RMAN backups
Create a group for the systembackup (or add it to a global group etc)
This is because the System backup if it uses a saveset of "all" cannot be
in the same group as the rman clients...
On the client side, create your RMAN script....
i.e. /ora/oracle/admin/blah/blah/Oracle_SID_Full_RMAN.rcv
update the client entry on the networker server using this script in the
saveset section
i.e. saveset: RMAN:/ora/oracle/admin/blah/blah/Oracle_SID_Full_RMAN.rcv
or for the Incr
RMAN:/ora/oracle/admin/blah/blah/Oracle_SID_Level_1_RMAN.rcv
modify the nsrnmo file on the client side to reflect the Oracle config
info.. i.e. Oracle_Home, Oracle_SID, paths, logs etc, update it to
reflect cataloging or if not using a catalog server nocatalog etc...
"you will need a seperate nsrnmo for each instance"
then update the client on the nsr server with this nsrnmo file name in the
Backup command Param
i.e. backup command: nsrnmo_SID
basically for 1 system with 1 oracle instance, i would have 3 clients
configured..
RMAN full
RMAN Incr
System Backup with oracle exclusion directive.
if there are more instances, you can still use the same RMAN group as
above, so still only 2 groups.....or if you dont think the system mount
points will ever change, hardcode them into the System backup client entry
asnd use the same 1 group for them all.
start the Networker group and see how you go.
cron can be used to initiate the rman backups, but why bother, let
Networker control the rman backups, and allow it to use it's scheduling,
and logging, retry ability, and also allow Management console to report on
the group etc if your using NMC or v7.3.#
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
wit 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
|
