Re: Replicated File System Consistency
Date: Mon, 29 Dec 2008 11:03:57 -0800 (PST)
Message-ID: <140d6aa8-a1c6-4a7f-a9e4-a3b111625191@r15g2000prd.googlegroups.com>
On Dec 29, 10:53 am, Pat <pat.ca..._at_service-now.com> wrote:
> So we've got a half dozen or so Oracle 10G (10.2.0.3) servers with
> production data on them.
>
> Historically, we ran them with direct attached RAID arrays, but
> recently we moved them to a new data center with a netapp 3040 SAN.
> Performance on the new hardware seems about the same; SAN is
> theoretically faster but I think there's more latency so from what I
> can see its a wash.
>
> Question I have though is about dr and consistency.
>
> We have a second san offsite.
>
> I can configure san mirroring to mirror our primary san off to another
> data center (more accurately I can ask the san guys to do so).
>
> In the event of a catastrophy at my primary center, can I mount the
> mirror copy of the database in dr, go through a recovery, and be
> relatively comfortable I've got a conistent data set?
>
> I know that if I pull the plug on the machine, Oracle commits that,
> post recovery, I won't lose any commits and it'll be consistent
> (although the recovery may take a while).
>
> Does the same commitment hold if I'm using a lower level (block level)
> replication technology and the replication fails in some unexpected
> place?
>
> Sorry if this is an obscure question, but I don't understand the
> interaction of Oracle's file system with the SAN well enough to make
> intelligent recommendations to the DR guys.
You might want to read this thread before you go any further:
David Fitzjarrell Received on Mon Dec 29 2008 - 13:03:57 CST