Re: DR Options.

> On Mar 9, 2:54 pm, "Preston" <dontwant..._at_nowhere.invalid> wrote:
> > We're looking into providing an off-site disaster recovery server
> > for some of our clients, & I'd appreciate some input on the best
> > way to do this.
> >
>
> Assuming each database generates 1GB of redo per day (AWR can generate
> a good bit), you should be able to copy the archived redo logs to the
> remote data centre and script an apply process for them. That assumes
> you can sustain 512K per second of throughput for about 40GB per day
> if you absolutely saturate the link, which would allow you to do this
> for 40 databases.
>
> Set archive_lag_target on the primary databases and let'er fly.
>
> Conversely, you could use materialized views on the primary database
> and run a fast refresh of these in a group every 60 minutes at the
> standby.
>
> HTH,
It does indeed - thanks Steve.

-- 
Preston