This is a multipart message in MIME format.
--=_alternative 0063D2D888256C48_=
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit
I use both the "hot" backup of Oracle using scripts and RMAN.
(1) Using the Veritas Database Edition we use RMAN to work its magic to
perform online/hot backup. It did take some time to setup but it was
certainly less time than setting up the hot backup using scripts (and
without Database Edition/Agent). I've done two successful restores using
RMAN and both went very well. I'm using a recovery catalog and it does
add more responsibility. However, I use a script to perform a cold backup
of the recovery catalog during the day when there's no RMAN backups going
on. Another DBA I know do not use a catalog with RMAN but I'm not
familiar anymore with the recovery process in that scenario.
(2) I haven't used the snapshot or storage checkpoint feature but I
haven't a experience and comfort feeling doing this including myself. My
recollection is that you still have to shutdown the database for a brief
moment while it creates the snapshot. In my opinion, I'm going with RMAN
for now since it is what Oracle is pushing.
(3) I also have a couple of databases that uses scripts to perform hot
backup. It dumps the datafiles, archivelogs, controlfile to a separate
filesystem. These scripts are invoked by NetBackup's
bpstart_notify/bpend_notify scripts (the bpend_notify erases the archive
logs from the source directories). I created a separate class/policy for
the hot backups with several clients backing up only that filesystem which
I named the same for all clients. I've had success restoring from this
scenario which is quite a bit more involved than RMAN but it does the job.
This filesystem and the Oracle oradata directories are excluded from the
another policy that performs ALL_LOCAL_DRIVES backup.
There are probably better ways but I had to make do with what I got stuck
with.
With regards to Tony Johnson's question:
(1) If you run the "recover database until time" command the it will
rollback the whole database back to that time. It's an incomplete
recovery and may not be acceptable. What I've seen done is the creation
of another database (recovered until time) where the data still exist.
Then the DBA exports the table and imports it back to the production
database.
Rene
"Johnson, Tony -Research" <gjohnson AT ADMWORLD DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
10/04/2002 06:43 AM
To: "'Mark Parsisson'" <Mark.Parsisson AT ncfe DOT com>, "'Peter
DrakeUnderkoffler'"
<pcd AT xinupro DOT com>, "Rien, Julie L. [C]" <RienJL AT nima DOT mil>
cc: "'veritas-bu AT mailman.eng.auburn DOT edu'" <veritas-bu AT
mailman.eng.auburn DOT edu>
Subject: RE: [Veritas-bu] VERITAS Database Edition for Oracle on
Solaris
Speaking of Oracle Restores, I had one detail that I'd like to ask. From
my
understanding to restore an oracle database from BEFORE the time the
disaster (accidental table drop) happened , I believe you have to use the
RMAN "until time" option so archive logs dont write the disaster back to
the
restore.
I was wondering if that works by specifying that in the rcv file Veritas
supplies.
-----Original Message-----
From: Mark Parsisson [mailto:Mark.Parsisson AT ncfe DOT com]
Sent: Friday, October 04, 2002 8:24 AM
To: 'Peter DrakeUnderkoffler'; Rien, Julie L. [C]
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] VERITAS Database Edition for Oracle on Solaris
We have had spotty success with RMAN. The setup in the beginning does take
some extra effort. However, once that is done, backups hum along well. The
problems we have had are the times when we need to restore an Oracle DB
via
RMAN. One outage took us around 36 hours to get RMAN to actually do the
*first* step of the restore. Each time we started a restore request it
would
work for several hours then promptly die spitting out a few errors. Our
DBA's worked with Veritas support during the entire restore. Eventually
the
restore worked but not due to any particular config or process change.
Just
happened that one time it actually worked. The total restoration time
start
to finish was around 72 hours. Lucky for us it was over a weekend so only
one day of production was lost really.
My point is, RMAN is a good way to do hot backups of DB's. Just be aware
that it may take a long time to recover a DB is the planets aren't aligned
just right. Others may have better mileage, I'm only speaking from our
experiences here.
Mark
-----Original Message-----
From: Peter DrakeUnderkoffler [mailto:pcd AT xinupro DOT com]
Sent: Friday, October 04, 2002 7:32 AM
To: Rien, Julie L. [C]
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: Re: [Veritas-bu] VERITAS Database Edition for Oracle on Solaris
"Rien, Julie L. [C]" wrote:
>
> To all:
>
> System details:
> SUN Enterprise 5500
> 2 A1000 Arrays
> 1 L1000 Tape Library
>
> Software:
> Solaris 8
> Oracle 8i
> VERITAS Volume Manager
> VERITAS NetBackUP
>
> We currently allow 4.5 hours of down time a night to do daily exports
and
> backups through oracle export and netbackup respectively. Our window of
> down time is shrinking beyond a point that utilizing incremental backup
will
> not shorten our backup time enough.
>
> I have been researching solutions to this and have come up with two
options
> to allow for 24hr by 7day uptime but allow for solid backups.
> 1. SNAPSHOT -- will not work because of the oracle db (this is a db
> server...its only purpose)
> 2. VERITAS Database Edition for Oracle on Solaris
>
> I was hoping that this group may have some success stories with VERITAS
> Database Edition for Oracle on Solaris OR suggestions on other solutions
you
> have used.
>
> I am interested in hearing your restoring experiences with either of
these
> options also.
>
> Thank you in advance for your help.
>
> Julie
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Hot backups with NetBackup via RMAN have always worded well. It is
a little extra work to setup in the beginning, but it is well worth it.
I've set it up several times on various sized databases. Of course
I needed a DBA to deal with the RCAT database and all the other Oracle
specific things.
Thanks
Peter
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This message contains information intended only for the use of the
addressee(s) named above, and may contain information that is privileged
and
confidential. If you are not the intended recipient of this message, or
the
employee or agent responsible for delivering it to the intended recipient,
you are hereby notified that any dissemination or copying of this message
is
strictly prohibited. If you have received this message in error, please
immediately notify us by replying by e-mail and destroy the original
message. Thank you.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 0063D2D888256C48_=
Content-Type: text/html;
charset=us-ascii
Content-Transfer-Encoding: 7bit
<br><font size=2 face="sans-serif">I use both the "hot" backup of
Oracle using scripts and RMAN.</font>
<br>
<br><font size=2 face="sans-serif">(1) Using the Veritas Database Edition we
use RMAN to work its magic to perform online/hot backup. It did take some
time to setup but it was certainly less time than setting up the hot backup
using scripts (and without Database Edition/Agent). I've done two
successful restores using RMAN and both went very well. I'm using a
recovery catalog and it does add more responsibility. However, I use a
script to perform a cold backup of the recovery catalog during the day when
there's no RMAN backups going on. Another DBA I know do not use a catalog
with RMAN but I'm not familiar anymore with the recovery process in that
scenario.</font>
<br>
<br><font size=2 face="sans-serif">(2) I haven't used the snapshot or storage
checkpoint feature but I haven't a experience and comfort feeling doing this
including myself. My recollection is that you still have to shutdown the
database for a brief moment while it creates the snapshot. In my opinion,
I'm going with RMAN for now since it is what Oracle is pushing.</font>
<br>
<br><font size=2 face="sans-serif">(3) I also have a couple of databases that
uses scripts to perform hot backup. It dumps the datafiles, archivelogs,
controlfile to a separate filesystem. These scripts are invoked by
NetBackup's bpstart_notify/bpend_notify scripts (the bpend_notify erases the
archive logs from the source directories). I created a separate
class/policy for the hot backups with several clients backing up only that
filesystem which I named the same for all clients. I've had success
restoring from this scenario which is quite a bit more involved than RMAN but
it does the job. This filesystem and the Oracle oradata directories are
excluded from the another policy that performs ALL_LOCAL_DRIVES backup.</font>
<br>
<br><font size=2 face="sans-serif">There are probably better ways but I had to
make do with what I got stuck with.</font>
<br>
<br><font size=2 face="sans-serif">With regards to Tony Johnson's
question:</font>
<br><font size=2 face="sans-serif">(1) If you run the "recover database
until time" command the it will rollback the whole database back to that
time. It's an incomplete recovery and may not be acceptable. What
I've seen done is the creation of another database (recovered until time) where
the data still exist. Then the DBA exports the table and imports it back
to the production database.</font>
<br>
<br><font size=2 face="sans-serif">Rene</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Johnson, Tony -Research"
<gjohnson AT ADMWORLD DOT com></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">10/04/2002 06:43 AM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"'Mark Parsisson'" <Mark.Parsisson AT ncfe DOT
com>, "'Peter DrakeUnderkoffler'" <pcd AT xinupro DOT com>,
"Rien, Julie L. [C]" <RienJL AT nima DOT mil></font>
<br><font size=1 face="sans-serif"> cc:
"'veritas-bu AT mailman.eng.auburn DOT edu'"
<veritas-bu AT mailman.eng.auburn DOT edu></font>
<br><font size=1 face="sans-serif"> Subject:
RE: [Veritas-bu] VERITAS Database Edition for Oracle on
Solaris</font></table>
<br>
<br>
<br><font size=2 face="Courier New">Speaking of Oracle Restores, I had one
detail that I'd like to ask. From my<br>
understanding to restore an oracle database from BEFORE the time the<br>
disaster (accidental table drop) happened , I believe you have to use the<br>
RMAN "until time" option so archive logs dont write the disaster back
to the<br>
restore.<br>
<br>
I was wondering if that works by specifying that in the rcv file Veritas<br>
supplies.<br>
<br>
-----Original Message-----<br>
From: Mark Parsisson [mailto:Mark.Parsisson AT ncfe DOT com]<br>
Sent: Friday, October 04, 2002 8:24 AM<br>
To: 'Peter DrakeUnderkoffler'; Rien, Julie L. [C]<br>
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'<br>
Subject: RE: [Veritas-bu] VERITAS Database Edition for Oracle on Solaris<br>
<br>
<br>
We have had spotty success with RMAN. The setup in the beginning does take<br>
some extra effort. However, once that is done, backups hum along well. The<br>
problems we have had are the times when we need to restore an Oracle DB via<br>
RMAN. One outage took us around 36 hours to get RMAN to actually do the<br>
*first* step of the restore. Each time we started a restore request it would<br>
work for several hours then promptly die spitting out a few errors. Our<br>
DBA's worked with Veritas support during the entire restore. Eventually the<br>
restore worked but not due to any particular config or process change. Just<br>
happened that one time it actually worked. The total restoration time start<br>
to finish was around 72 hours. Lucky for us it was over a weekend so only<br>
one day of production was lost really.<br>
<br>
My point is, RMAN is a good way to do hot backups of DB's. Just be aware<br>
that it may take a long time to recover a DB is the planets aren't aligned<br>
just right. Others may have better mileage, I'm only speaking from our<br>
experiences here.<br>
<br>
Mark<br>
<br>
-----Original Message-----<br>
From: Peter DrakeUnderkoffler [mailto:pcd AT xinupro DOT com]<br>
Sent: Friday, October 04, 2002 7:32 AM<br>
To: Rien, Julie L. [C]<br>
Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'<br>
Subject: Re: [Veritas-bu] VERITAS Database Edition for Oracle on Solaris<br>
<br>
<br>
"Rien, Julie L. [C]" wrote:<br>
> <br>
> To all:<br>
> <br>
> System details:<br>
> SUN Enterprise 5500<br>
> 2 A1000 Arrays<br>
> 1 L1000 Tape Library<br>
> <br>
> Software:<br>
> Solaris 8<br>
> Oracle 8i<br>
> VERITAS Volume Manager<br>
> VERITAS NetBackUP<br>
> <br>
> We currently allow 4.5 hours of down time a night to do daily exports
and<br>
> backups through oracle export and netbackup respectively. Our window
of<br>
> down time is shrinking beyond a point that utilizing incremental backup<br>
will<br>
> not shorten our backup time enough.<br>
> <br>
> I have been researching solutions to this and have come up with two<br>
options<br>
> to allow for 24hr by 7day uptime but allow for solid backups.<br>
> 1. SNAPSHOT -- will not work because of the oracle db (this is a db<br>
> server...its only purpose)<br>
> 2. VERITAS Database Edition for Oracle on Solaris<br>
> <br>
> I was hoping that this group may have some success stories with VERITAS<br>
> Database Edition for Oracle on Solaris OR suggestions on other
solutions<br>
you<br>
> have used.<br>
> <br>
> I am interested in hearing your restoring experiences with either of
these<br>
> options also.<br>
> <br>
> Thank you in advance for your help.<br>
> <br>
> Julie<br>
> <br>
> _______________________________________________<br>
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<br>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
<br>
Hot backups with NetBackup via RMAN have always worded well. It is<br>
a little extra work to setup in the beginning, but it is well worth it.<br>
I've set it up several times on various sized databases. Of course<br>
I needed a DBA to deal with the RCAT database and all the other Oracle<br>
specific things.<br>
<br>
<br>
Thanks<br>
Peter<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
This message contains information intended only for the use of the<br>
addressee(s) named above, and may contain information that is privileged and<br>
confidential. If you are not the intended recipient of this message, or
the<br>
employee or agent responsible for delivering it to the intended recipient,<br>
you are hereby notified that any dissemination or copying of this message is<br>
strictly prohibited. If you have received this message in error,
please<br>
immediately notify us by replying by e-mail and destroy the original<br>
message. Thank you.<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
<br>
--=_alternative 0063D2D888256C48_=--
|