Re: DG for nologging

The way I understand this is that a "failover" will basically consist of Oracle doing a crash recovery on the standby site - similar to if you had done a shutdown abort. It will use the redo logs to bring the database up consistently.

On Wed, Mar 7, 2018 at 10:20 AM, Mladen Gogala <gogala.mladen_at_gmail.com> wrote:

> Replies in line:
>
> On 03/06/2018 07:56 PM, Jeff Chirco wrote:
>
> When you say " Continuous Disk Replication" you must not be talking about
> storage based snapshots right?
>
>
> Yes, I'm not talking about snapshots. Snapshots are discrete, not
> continuous.
>
> It replicates the disk on the fly?
>
>
> It replicates disk synchronously. Every write request to the local disk is
> also sent to remote disk. It is like DG, only for physical devices.
>
> And is this a database consistent replication?
>
>
> It guarantees disk consistency, if your network is wide enough.
>
> I question if the database will actually startup in a fail over situation.
>
>
> It will. I was present during DR test for one of my clients which
> performed fail-over with Hitachi HDS replication. It went flawlessly.
>
>
> Maybe I am miss understanding.
>
>
> As long as you don't misunderstimate things, you're OK.
>
> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217
>
>

-- 
//
zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
Visit us at zztat.net | Support our Indiegogo campaign at igg.me/at/zztat |
_at_zztat_oracle

--
http://www.freelists.org/webpage/oracle-l