I have had such case with 2 servers using Oracle Advanced Replication (this is, master-to-master). The backup scenario I implemented had such thing:
1. run backups so they finish "about" the same time
2. when both backups are finished, break replication push jobs (this is equal to STOP SYNCHRONIZATION)
3. get SCN from one database; get SCN from other database; white both SCNs to flat file
4. un-break push jobs (this is equal to RESTORE SYNCHRONIZATION)
Steps 2-4 can be done with a script in less than a minute. In this scenario nothing have to be done in extremely same moment on both databases (which would be quite difficult).
--
Regards,
Yavor Ivanov
Senior Database Expert
Stemo Ltd
On Thu, 12 Apr 2007 10:56:20 +0300, Johan Eriksson <valpis_at_gmail.com> wrote:
> Hi
>
> We have 2 different systems that exchanges quite alot of information, both ways.
> but his creates some problems when it comes to backup, if one system
> crashes and needs to recover it will be in a state which is not
> syncronized to the other system. Even if we restores both databases it
> is hard to make sure they were in perfect sync.
> Both the system is 24/7 so take them offline for backup is not my
> first choice...
>
> Anyone has any experiance with a situation like this?
>
> /johan
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Apr 12 2007 - 08:59:24 CDT
