Hi Baris,
I've done an install in an environment like the one you describe, however, our
customer only wanted to backup their archive logs once a day (at backup time),
and only used "save" to backup their bcvs.
We worked with EMC to script the backup process so that the following (basic)
processes would occur:
1 - unmount the bcvs and sync them with the standard/target disks.
2 - switch oracle redo log file.
3 - put db into hot backup mode.
4 - split the bcvs for the disks that contain the database.
5 - take db out of hot backup mode.
6 - switch oracle redo log file.
7 - split the bcvs for the disks that contain the archive logs.
8 - mount the bcvs on the backup node.
9 - do a full backup of the bcv filesystems.
These processes could be adapted to backup your archive logs through bcvs.
HTH,
John
_______________________________________
John Herlihy - System Engineer
e-DataServices
A Division of XSI Data Solutions Pty Ltd
Direct: +61-2-9496-1153
Fax: +61-2-9417-4932
Email: johnh AT e-dataservices.com DOT au
www: http://www.e-datagroup.com.au
> -----Original Message-----
> From: Baris Yeter [mailto:barye AT KOCBANK.COM DOT TR]
> Sent: Thursday, 27 March 2003 02:47
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] EMC-ORACLE-LEGATO
>
>
> Hi,
>
>
> Does anyone have experience with using EMC's Timefinder and
> BCVs for Oracle backups?
>
> Assume that BCVs mounted from backup server. After BCV is
> established, I opened database in mount mode at backup
> server. via RMAN script(I am using Recovery catalog), I
> backup up mounted database, as a result, there is no load on
> production server.
>
> But to backup generated archive logs on production server,
> what strategy will be applied to get best results?
>
>
> Thanks.
>
>
> Bu mesaj ve onunla iletilen tüm ekler gönderildigi kisi ya da
> kuruma özel ve Bankalar Kanunu geregince, gizlilik
> yükümlülügü tasiyor olabilir. Bu mesaj, hiçbir sekilde,
> herhangi bir amaç için çogaltilamaz, yayinlanamaz ve para
> karsiligi satilamaz; mesajin yetkili alicisi veya alicisina
> iletmekten sorumlu kisi degilseniz, mesaj içerigini ya da
> eklerini kopyalamayiniz, yayinlamayiniz, baska kisilere
> yönlendirmeyiniz ve mesaji gönderen kisiyi derhal uyararak bu
> mesaji siliniz. Bu mesajin içeriginde ya da eklerinde yer
> alan bilgilerin dogrulugu, bütünlügü ve güncelligi Bankamiz
> tarafindan garanti edilmemektedir ve bilinen virüslere karsi
> kontrolleri yapilmis olarak yollanan mesajin sisteminizde
> yaratabilecegi zararlardan Bankamiz sorumlu tutulamaz.
>
> This message and the files attached to it are under the
> privacy liability in accordance with the Banking Law and
> confidential to the use of the individual or entity to whom
> they are addressed. This message cannot be copied, disclosed
> or sold monetary consideration for any purpose. If you are
> not the intended recipient of this message, you should not
> copy, distribute, disclose or forward the information that
> exists in the content and in the attachments of this message;
> please notify the sender immediately and delete all copies of
> this message. Our Bank does not warrant the accuracy,
> integrity and currency of the information transmitted with
> this message. This message has been detected for all known
> computer viruses thence our Bank is not liable for the
> occurrence of any system corruption caused by this message.
>
> --
> Note: To sign off this list, send a "signoff networker"
> command via email to listserv AT listmail.temple DOT edu or visit
> the list's Web site at
> http://listmail.temple.edu/archives/networker.> html where you
> can also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
