Re: Size of an archive log file for dataguard

In case we need to invoke DR we may be able to live with the last known backup (ie the last night)..sorry if my understandings of the concepts are way off but how about using incremental backups of my prod and using scripts to copy to DR site and restore there .. all SIDs, files etc would be replicated

If, for example, I have 1GB of archive per day, a lot of that is full table updates (poor app design, cant do anything about it) where before and after images are being stored, if incremental backups are only backing up changes then (Im thinking based on limited knowledge) that theres not 1GB of backup, theres a lot less as "before images" wouldnt be backed up.

would that minimise the amount of data I need to send over the line?

Steve Howard wrote:
> clint_silver wrote:
> > ok, I'll investigate. I still need to find out the size in MBs of the
> > usage of the line( currently upgrading) and all I have to go on is the
> > current rate and sizes of my archive logs.
> >
>
> If you are using standby redo logs on the standby and LGWR (versus
> ARCH) as the method in your dest_2 parameter on the primary, you aren't
> shipping the entire log (at one time), but instructing LGWR to
> propagate its redo I/O over the network as it is generated. I'm not
> sure that helps you, but if you are concerned about network bursts at
> log switches ("rather then ship the physical 50mb log"), that should
> help.
>
> HTH,
>
> Steve
Received on Mon Nov 13 2006 - 11:42:19 CST