Re: Getting a consistent copy

From: John Hurley <johnbhurley_at_sbcglobal.net>
Date: Mon, 20 Jul 2009 17:00:22 -0700 (PDT)
Message-ID: <051d6d00-5652-4fcf-b69c-31af59482f67_at_o15g2000yqm.googlegroups.com>



On Jul 20, 1:09 pm, Pat <pat.ca..._at_service-now.com> wrote:

snip

> One thing we're considering trying here to achieve the same thing
> though is to use SAN snapshotting, something like this:
>
> 1) Leave the source running
> 2) SNAP /u01 on the san
> 3) Mount the SNAP on a different database server in read/write mode
> 4) Restart Oracle over there
> 5) Let it go through a recovery (since we did just crash it)
> 6) Run a data pump export out of there.
>
> Is anybody doing something like this? Does anybody know of any
> subtleties that I should be aware of? In theory the above should work
> fine, but as one of my colleagues is fond of pointing out, in theory
> you shouldn't need practise.

Yup doing this all the time ... we are using EMC on Clariions ... and using a clone ( full copy ) not a snap ... but same basic thing.

Yes there was at least poster noting that this technique failed for them on extremely high volume transactions rate systems. I haven't seen it fail on any of the systems I have worked on.

We use this technique to refresh a test and/or dev database with fresh data. Usually we also get a local clone of the refreshed database so that it can be restored multiple times to the same starting point ( groundhog day ) in a testing loop. Received on Mon Jul 20 2009 - 19:00:22 CDT

Original text of this message