From oracle-l-bounce@freelists.org Thu Sep 29 11:05:04 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j8TG54Jf007822 for ; Thu, 29 Sep 2005 11:05:04 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j8TG4u6H007779 for ; Thu, 29 Sep 2005 11:04:57 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id E44791EFEBC; Thu, 29 Sep 2005 11:04:49 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08883-05; Thu, 29 Sep 2005 11:04:49 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 60E171EFF55; Thu, 29 Sep 2005 11:04:49 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5C50F.38CC3F84" Subject: FW: Oracle RAC backup hardware/software recommendation? Date: Thu, 29 Sep 2005 12:02:28 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Oracle RAC backup hardware/software recommendation? Thread-Index: AcXE9SR5qQql80MoRQ6yYRzKTV/zRAAAGVfgAAGw9fAAATMIxgADhcWb From: "Marquez, Chris" To: X-archive-position: 26107 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: cmarquez@collegeboard.org Precedence: normal Reply-To: cmarquez@collegeboard.org X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-mailscan-MailScanner-Information: Please contact the ISP for more information X-mailscan-MailScanner: Found to be clean X-MailScanner-From: oracle-l-bounce@freelists.org X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on air891.startdedicated.com X-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE autolearn=ham version=2.63 ------_=_NextPart_001_01C5C50F.38CC3F84 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >> We do not have to mess around with the MML config >> we just ensure that the NSR_CLIENT is set correctly >> and privileges are correct within Networker=20 Well, I would call that the "config". ;o) But yes this is exactly what I mean. Its hit the DBA smack in the face when one tries to=20 RMAN>restore archive log all; in a RAC environment where the "local" arch logs are backed up = independently on each server (instance) in the RMAN backup = session/script. The logs belong to one database, but two MML clients. The RMAN-MML restore session will blow up because it is restoring the = logs for one client only at a time, but the RMAN command was for ALL = logs (from any instance...incompatible). I would set up each TDPO client database server to be able to "spoof" = the other RAC server at anytime. That meant duplicate config files on each client RAC server. So at = anytime I could restore (RMAN) backup from node A to node A, and backup = from node B to node A...thus getting all of my arch logs file in a = failure. You don't want to *learn* this in the heat of battle, but not is not = intuitive during the set up. Again, #1 Test, Test, Test complete and total loss database restores. = Then and only them "missed" issue become obvious. Thus a strong argument can be made for cluster filesystem for arch logs = (Which ocfs does not support/recommend). PS >>We don't use RAC (well I don't!!) We might stop using RAC...but that is a whole other thread, for another = day. :o| Chris Marquez Oracle DBA -----Original Message----- From: Hallas, John, Tech Dev [mailto:John.Hallas@gb.vodafone.co.uk] Sent: Thu 9/29/2005 9:53 AM To: Marquez, Chris; mueller_m@fiz-chemie.de; oracle-l@freelists.org Subject: RE: Oracle RAC backup hardware/software recommendation? =20 Well thought out and interesting response Chris.=20 I am interested in your point 3.=20 We don't use RAC (well I don't!!) but do have occasions when we restore archived log files from the MML/Tape Robot when they were backed up on Client A and the database is now on Client B. (cluster and the databse has failed over to the alternate node). We do not have to mess around with the MML config, we just ensure that the NSR_CLIENT is set correctly and privileges are correct within Networker (or whichever MML you will be using) Have I misunderstood your point or is it RAC specific? John -----Original Message----- From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of Marquez, Chris Sent: 29 September 2005 14:09 To: mueller_m@fiz-chemie.de; oracle-l@freelists.org Subject: RE: Oracle RAC backup hardware/software recommendation? ... 3.) On the same note as #2 above learn now that Oracle-RMAN sees a "backup" as a whole...a single logical unit, while *ANY* MML sees individual pieces of data from a client (machine). This becomes critical when you are trying to restore *ALL* (local) arch log files at one time from two DIFFERENT clients...or you are trying to restore all the datafiles backed up from RAC-node A to RAC-node B. These are the same database and RMAN backup, but different clients as far as the MML is concerned. Server "spoofing" with MML config files is a must "know" with RAC and MML. hth Chris Marquez Oracle DBA ------_=_NextPart_001_01C5C50F.38CC3F84 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable FW: Oracle RAC backup hardware/software recommendation?

>> We do not have to mess around with the MML = config
>> we just ensure that the NSR_CLIENT is set correctly
>> and privileges are correct within Networker

Well, I would call that the "config". ;o)

But yes this is exactly what I mean.
Its hit the DBA smack in the face when one tries to
        RMAN>restore archive log = all;
in a RAC environment where the "local" arch logs are backed up = independently on each server (instance) in the RMAN backup = session/script.  The logs belong to one database, but two MML = clients.
The RMAN-MML restore session will blow up because it is restoring the = logs for one client only at a time, but the RMAN command was for ALL = logs (from any instance...incompatible).
I would set up each TDPO client database server to be able to = "spoof" the other RAC server at anytime.
That meant duplicate config files on each client RAC server.  So at = anytime I could restore (RMAN) backup from node A to node A, and backup = from node B to node A...thus getting all of my arch logs file in a = failure.

You don't want to  *learn* this in the heat of battle, but not is = not intuitive during the set up.
Again, #1 Test, Test, Test complete and total loss database = restores.  Then and only them "missed" issue become = obvious.

Thus a strong argument can be made for cluster filesystem for arch logs = (Which ocfs does not support/recommend).


PS
>>We don't use RAC (well I don't!!)
We might stop using RAC...but that is a whole other thread, for another = day. :o|


Chris Marquez
Oracle DBA






-----Original Message-----
From: Hallas, John, Tech Dev [mailto:John.Hallas@gb.vodaf= one.co.uk]
Sent: Thu 9/29/2005 9:53 AM
To: Marquez, Chris; mueller_m@fiz-chemie.de; oracle-l@freelists.org
Subject: RE: Oracle RAC backup hardware/software recommendation?

Well thought out and interesting response Chris.

I am interested in your point 3.

We don't use RAC (well I don't!!) but do have occasions when we = restore
archived log files from the MML/Tape Robot when they were backed up = on
Client A and the database is now on Client B. (cluster and the = databse
has failed over to the alternate node). We do not have to mess = around
with the MML config, we just ensure that the NSR_CLIENT is set = correctly
and privileges are correct within Networker (or whichever MML you = will
be using)

Have I misunderstood your point or is it RAC specific?

John

-----Original Message-----
From: oracle-l-bounce@freelists.org
[mailto:oracle-l-bounce@free= lists.org] On Behalf Of Marquez, Chris
Sent: 29 September 2005 14:09
To: mueller_m@fiz-chemie.de; oracle-l@freelists.org
Subject: RE: Oracle RAC backup hardware/software recommendation?

...

3.) On the same note as #2 above learn now that Oracle-RMAN sees a
"backup" as a whole...a single logical unit, while *ANY* MML = sees
individual pieces of data from a client (machine).  This = becomes
critical when you are trying to restore *ALL* (local) arch log files = at
one time from two DIFFERENT clients...or you are trying to restore = all
the datafiles backed up from RAC-node A to RAC-node B.  These are = the
same database and RMAN backup, but different clients as far as the = MML
is concerned.  Server "spoofing" with MML config files is = a must "know"
with RAC and MML.

hth

Chris Marquez
Oracle DBA





------_=_NextPart_001_01C5C50F.38CC3F84-- -- http://www.freelists.org/webpage/oracle-l