[Ocfs2-users] Lost write in archive logs: has it ever happened?

[Silviu Marin-Caea]

On Thursday 04 December 2008 10:17:17 Silviu Marin-Caea wrote:
> On Wednesday 03 December 2008 18:05:49 Luis Freitas wrote:
> >    Depending on your configuration, dataguard will transfer the
> > modifications on the online log directly to the standby, so that the
> > archived logs are recreated there. It doesnt transfer the archivedlogs
> > from disk, instead it transfers the redo log entries directly to the
> > other host, as they are generated, and the archivelogs are recreated
> > there.
>
> We had the transport method of dataguard set to log writer.  So what you're
> saying was expected.  Then we have changed the transport to ARCH.  We
> thought that this would copy archives from production to standby after
> they're closed on production.  They it would apply them on standby.
>
> >    So the remote copy is created independently from the local copy.
>
> Even if the transport is set to ARCH?
>
> >    The problem could be on the process writing the archivelog to disk or
> > on the operating system/hardware.
>
> Well, on the production system we're multiplexing the archives on two
> completely separate physical devices: a shared storage with OCFS2 and local
> storage with reiserfs.  Both archives are identical (same MD5sum) and both
> not good.

I mean both on production are identical.  But the error is given by standby 
when trying to apply its own archive that is not the same as in production.  
And that is assuming the train of thought that archives are transported then 
applied.  Which is not something we're sure of anymore.  This is very 
confusing! I have to read documentation...

This is no longer ontopic for OCFS2.. we should switch to private.