| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle Backup with Veritas
Sybrand Bakker <gooiditweg_at_sybrandb.demon.nl> wrote in message news:<9rh7lvk37d9ptrvft292bfeghf5v8jfj8k_at_4ax.com>...
> On Mon, 01 Sep 2003 20:06:31 +0500, Eddy Vagapov <eddyv_at_udm.net>
> wrote:
>
> >Hello, Sybrand Bakker!
> >
> > Thank you for answer...
> > But, I must replace 'SBT_TAPE' and
> > wrote '/dev/rmt/0un' or name my tape drive?
> >
> >Best Regards,
> >Eddy
>
> Likely not. Usually you have an additional parms section.
> The vendor documentation (you know: that is the thing no one reads)
> should be able to tell you how to set it all up, as it is vendor
> specific and not managed by Oracle
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
A couple items here first, I see that you're running 8.1.7 but on Sun 2.????, AIX?? what??? Also, what's the version of Veritas, or did I miss it? Next, here's a sample of one of my RMAN scripts. I'm on Veritas 4.5, with an oracle instance 9.0.1 backed up via RMAN and a recovery catalog database. Regarding SBT_TAPE, you do need additional parameters specifed, basically class/client information so that when the RMAN backup starts writing, it knows which tape to write to. Below is an excerpt of one of my RMAN script output:
Thu Aug 21 03:05:48 CDT 2003 - Setting the Oracle Home.
RMAN: rman
SVRMGR: sqlplus /nolog
ORACLE_SID: PODW1 ORACLE_USER: ora901 ORACLE_HOME: /oracle/901/home NB_ORA_SCRIPTS:
NB_ORA_FULL: 0 NB_ORA_INCR: 0 NB_ORA_CINC: 1 NB_ORA_SERV: dba3 NB_ORA_CLASS: emsdb1_PODW1 NB_ORA_PC_SCHED: daily_incremental_hot NB_ORA_SCHEDULED: 1 NB_ORA_USER_INITIATED:
-----Starting RMAN Backup------
This is the Oracle owner whose
ORACLE_HOME is /oracle/901/home
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19>
20> 21> 22
> 23> RMAN return status = 0
Recovery Manager: Release 9.0.1.3.0 - 64bit Production
(c) Copyright 2001 Oracle Corporation. All rights reserved.
RMAN> connect target sys/change_on_install_at_DB1
2> connect catalog rman901/rmanpasswd_at_RMAN1
3> sql 'alter system archive log current';
4> run {
5> # Hot database level 1 cumulative incremental backup
6> allocate channel t1 type 'SBT_TAPE'
7> parms="ENV=(NB_ORA_CLASS=server1_DB1,
NB_ORA_SCHED=dailyincremental)";
10> backup current controlfile for standby; 11> backup 12> incremental level 1 13> cumulative 14> skip offline 15> skip readonly 16> skip inaccessible 17> tag hot_DB1_bk_level1_cm 18> filesperset 20 19> format 'bk_DB1_hot_cm_lv1_%U_%t_%s' 20> (database); 21> } 22> resync catalog;
My NB_ORA_SCHED=dailyincremental is a schedule classsified as an 'Application backup', note, I specified this schedule in my script. However, the schedule that kicks this backup off is classified as an Automatic Incremental backup with a different schedule name, daily_incremental_hot. I don't recall the exact reason for this, but, if I specifed the daily_incremental_hot again, then Veritas would kick off another job. And also with the RMAN implementation on Veritas, you needed a 'Application Backup' specified with each RMAN backup class. In Netbackup 3.4, this used to be called 'Backup Policy'. So what I have done is for each schedule, I've created a 'Application Backup' schedule to match that of the schedule that runs. On the Application Backups, I've left the window open 24hrs so that it may write to the tapes anytime the schedule is kicked off. This may seem like a klugged together backup, but, I started this on NB 3.4 and was the only way I could get it to work with the proper retention levels.
Here's what've got for libobk files in my Veritas Install directory, this is on AIX 4.3.3 ML09:
-r-xr-xr-x 1 root bin 708908 Mar 21 2002 libobk.a -r-xr-xr-x 1 root bin 784101 Mar 21 2002 libobk.a64 lrwxrwxrwx 1 root system 8 Jan 02 2003 libobk.so -> libobk.a lrwxrwxrwx 1 root system 10 Jan 02 2003 libobk.so64 ->libobk.a64
The last two files denote symbolic links back to the .a & .a64(32bit & 64bit libs respectively). Next, in my $ORACLE_HOME/lib directory(which is 9.0.1.2 64bit), here's what I've got for libobk:
May 22 2002 libobk.a -> /usr/openv/netbackup/bin/libobk.a64 May 22 2002 libobk.a64 -> /usr/openv/netbackup/bin/libobk.a64 May 22 2002 libobk.so -> /usr/openv/netbackup/bin/libobk.a64 May 22 2002 libobk.so64 -> /usr/openv/netbackup/bin/libobk.so64
I pointed the .a, .a64, .so, .so64 essentially back to the .a64 in the Veritas Install Directory. This may seem odd, but, since the Oracle install is 64bit, I made sure that the 64 bit libobk was going to be used. Also in the $ORACLE_HOME/lib32, I have the same setup for symbolic links.
HTH,
Pete's
Note-The views I may have expressed here are solely my own and not that of my employer. Use any scripts or advice from this post is at your own risk. All other exclusions apply. Received on Tue Sep 02 2003 - 08:50:58 CDT
 |
 |