Replicated File System Consistency

From: Pat <>
Date: Mon, 29 Dec 2008 08:53:42 -0800 (PST)
Message-ID: <>

So we've got a half dozen or so Oracle 10G ( 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. Received on Mon Dec 29 2008 - 10:53:42 CST

Original text of this message