RE: 8i and Veritas NetBackup
Hi Rick, Sorry, replying very late. I was facing some problem in setting up RMAN with netbackup 3.4 and Oracle has sent me one document. Its very easy to setup. I'll cut n paste it here. Hope this helps. Regards, Sandeep. Problem == How to configure RMAN to work with Netbackup for Oracle ? Solution: Steps for configuring Netbackup for Oracle : 1. First of all we need to decide whether we want to use Recovery catalog or not . Recovery catalog stores critical backup information that is required for doing a database restore . It stores information about a. Datafiles and archived redo log backup set and backup piece information b. Datafile copy information c. Archived redo logs and their copy information d. Tablespaces and datafiles on the target database information e. Stored scripts We can also use RMAN without a recovery catalog wherein all these information are stored in the control files of the database . More details about this , is given in the ORACLE 8i BACKUP AND RECOVERY GUIDE . Oracle recommends that use Recovery catalog if you have more than 20 datafiles in an instance . Since you find critical information in this , we need to keep this catalog away from the target database , because if it's on the same database and in the same disk where we have the datafiles , if the database crashes or the disk gets corrupted , it's very difficult to restore the database . So Oracle recommends that in case we need to backup 2 databases on 2 servers , say DB1 and DB2 , create 2 recovery catalogs , one on each say RCAT1 and RCAT2 , so that RCAT1 on DB1 stores the backup information for DB2 and vice versa .. 2. Create a database for housing the recovery catalog . Lets' call this instance as RCAT1 . The typical disk space requirements depends on the number of databases this catalog monitors , the number and size of the stored scripts and it grows as the number of archived logs and backups grow . The typical requirement for 1 year is : SYSTEM TABLESPACE :50 MB TEMP TABLESPACE : 5 MB ROLLBACK SEGMENT :5 MB ONLINE REDO LOG : 1 MB for each RECOVERY CATALOG :10 MB You can create this database using the dbassist command in Oracle . 3. Create a tablespace called "cattbs" for holding the recovery catalog . $ sqlplus sys/change_on_install@RCAT1 SQL> create tablespace cattbs DATAFILE '' SIZE 10M; SQL> exit 4. Create a user for using the recovery catalog . $ sqlplus sys/change_on_install@RCAT1 SQL > create user rman identified by rman temporary tablespace temp default tablespace cattbs quota unlimited on cattbs ; where cattbs -> is the name of the recovery catalog's tablespace . SQL > grant RECOVERY_CATALOG_OWNER to rman ; SQL > grant connect , resource to rman ; 5. Now the user has been created try testing the connection as the user RMAN . $ sqlplus rman/rman@RCAT1 This should work fine . 6. Now create the RMAN catalog tables in the tablespace CATTBS . $ rman catalog rman/rman@RCAT1 rman > create catalog tablespace cattbs ; This command takes some time when the tables are created . Query this , to see if the tables have been created or not . $ sqlplus rman/rman@rcat1 SQL > select table_name from user_tables ; This should list all the table names from the catalog . 7. Now you need to register the target database with the recovery catalog . Before this , if the database is running in MTS mode , make sure that RMAN gets a dedicated server connection when connecting . For this create an entry in $ORACLE_HOME/network/admin/tnsnames.ora file Inst1_ded ( description ( address = ( protocol = TCP ) ( host = db1 ) ( port1521 )) ( connect_data = (service_name = inst1 ) (server = dedicated )) ) You can test this connection to see if it's a dedicated server connection or not .. $ sqlplus sys/@inst1_ded SQL > select server from v$session where sid ( select distinct sid from v$mystat ) ; Here you should get DEDICATED . 8. Register the target database . $ rman target sys/@inst1_ded catalog rman/rman@RCAT1 rman > register database ; Please note that RMAN connects to the target database using a user who has a SYSDBA privilege defined in the target . So grant SYSDBA privilege to user RMAN . 9. Now you are all set to use the catalog for storing the backup information . A recovery catalog can store information for multiple target databases . So it needs to be backed up frequently . In case this catalog is lost , we can reconstruct the catalog partially from the current control file or it's copies . The recovery catalog should be run in ARCHIVE LOG mode . 10. The recovery catalog can be backed up using either export command , or use a cold backup strategy . $ exp rman/rman@rcat1 file = RCAT1_backup.dmp owner=rman 11. Now the Netbackup server must have already been configured and the Oracle server must have been configured as
RE: 8i and Veritas NetBackup
Rick, This is what our corporation uses as a standard. We are not having any of the problems you describe, however, we are on HP, AIX, Tru64, and NT, not Solaris. Jim [EMAIL PROTECTED] wrote: >Is anyone using this combination? We're having problems getting backups to work with >8i. It works fine with our 8 dbs, but when we try to backup the 8i ones, the control >panel says the backup has started, but it doesn't finish and usually has a dead rman >process on the db. > >We've working with Veritas support, but it's been 2 weeks and no answer. > >The dbs are 8.1.7.3 on Solaris 7 and we did patch the oracle executables. > >Thank you for any help. > > >-- >Please see the official ORACLE-L FAQ: http://www.orafaq.com >-- >Author: > INET: [EMAIL PROTECTED] > >Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 >San Diego, California-- Public Internet access / Mailing Lists > >To REMOVE yourself from this mailing list, send an E-Mail message >to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in >the message BODY, include a line containing: UNSUB ORACLE-L >(or the name of mailing list you want to be removed from). You may >also send the HELP command for other information (like subscribing). > -- _ Jim Hawkins Oracle Database Administrator [EMAIL PROTECTED] St. Louis, MO USA __ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jim Hawkins INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: 8i and Veritas NetBackup
Title: RE: 8i and Veritas NetBackup
The folloiwng is a good post from Samir which I kept. It seems to cover your environment well. Hope it helps John
Hi,
In order for RMAN to work with a third party backup product the third party
vendor writes an interface to an Oracle supplied API and supplies this in
the form of a library.
Oracle supplies a default copy of the library as $ORACLE_HOME/lib/libobk.so
which has the RMAN default functionality of writing to disk only.
Installation of an RMAN media management product logically replaces this
library. How this logical replacement is done depends on several Oracle
documents and one netbackup document, most of which contradict each other.
As long as it is clear how the library is logically presented to Oracle it
doesn't matter how it is done.
The library that Oracle currently uses can be established by executing:
ldd $ORACLE_HOME/bin/oracle
This will list the libraries linked to the Oracle executable, specifically
libobk.so.
The Veritas supplied file is called libobk.so.1. Oracle thinks it is called
libobk.so, which it looks for in LD_LIBRARY_PATH. Therefore a soft link is
needed from libobk.so somewhere in LD_LIBRARY_PATH to the Netbackup supplied
libobk.so.1. This can be done with:
LD_LIBRARY_PATH=$ORACLE_HOME/lib:
and then either:
ln -s /opt/openv/netbackup/bin/libobk.so.1 $ORACLE_HOME/lib/libobk.so
or:
cp /opt/openv/netbackup/bin/libobk.so.1 $ORACLE_HOME/lib/libobk.so.1
ln -s $ORACLE_HOME/lib/libobk.so.1 $ORACLE_HOME/lib/libobk.so
Other combinations of these links are obviously possible, but the important
thing is to be consistent. With several ORACLE_HOME's the former is
preferable, the latter becomes more relevant if a version dependency had
been discovered between RMAN and Netbackup such that each ORACLE_HOME needed
a different copy of the library.
Additionally, Oracle 8.0.5 statically links the library into the Oracle
executable, so once the executable is relinked it doesn't matter what
happens to the original library file. At 8.1.6 however the library is
THEORETICALLY dynamically linked and so always depends on finding a copy on
LD_LIBRARY_PATH. A bug in 8.1.6 (1252142) means this dynamic linking does
not work and the library still has to be statically linked to the Oracle
executable. The bug is fixed at 8.1.7.
Hope this helps.
Hi Listers,
I have a question regarding using 8i RMAN with Netbackup 3.4.
I remember on 8i one no longer needs to relink the oracle executable
when intergrate with a 3rd party backup software. All I have to
do it change the symbolic link $ORACLE_HOME/lib/libobk.so to point
to the media management library.
Now from the Netbackup 3.4 for Oracle manual, it says on Solaris
for 8.1.6, you need to relink the oracle executable by doing:
make -f ins_rdbms.mk ioracle LLIBOBK=-lobk
So the question is should I relink or not?
Thanks for your feedback.
Rich
Nice answer Samir. As an additional note... after linking I've used the
sbttest utility from Oracle to verify a working installation. (We're using
Netbackup with Linux and have encountered problems which Veritas is
working on.)
The sbttest program is nice but for complete backup installation testing I
believe in performing test recoveries. I've created small test databases
on production servers and have scripted several recovery scenarios. For our
current situation it turns out that we can get a successful backup but
restores are a problem. Since backups aren't any good if you can't restore
the backup is suspect. We can restore files from tape to disk but finishing
the recovery requires getting out of RMAN and recovering from the SQL
prompt. We can also restore from RMAN as long as we don't have more than 2
commands in the run { commands... } syntax. Of course this could get quite
tedious in a multiple datafile restore scenario so we're insisting that
Veritas fix the communication problems between RMAN, Netbackup and our tape
robot.
So I guess the object lesson from all this is that, regardless of "apparent"
linking success, it pays to be anal and thorough when it comes to validating
your backup implementation and the best way to do this is to perform some
actual recoveries.
Hi Listers,
I have a question regarding using 8i RMAN with Netbackup 3.4.
I remember on 8i one no longer needs to relink the oracle executable
when intergrate with a 3rd party backup software. All I have to
do it change the symbolic link $ORACLE_HOME/lib/libobk.so to point
to the media management library.
Now from the Netbackup 3.4 for Oracle manual, it says on Solaris
for 8.1.6, you need to relink the oracle executable by doing:
make -f ins_rdbms.mk ioracle LLIBOBK=-lobk
So the question is should I relink or not?
Thanks for your feedback.
Rich
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 22 February 2002 14:38
To: Multiple recipients of list ORACLE
