Hi,
To be able to fallback to Site A, Site B needs to have a replication server
running that replicates to Site A. When preparing for fallback one should
check where Site A is at in the replication and ensure that it gets
the replication records for the missing info.
Check the manual for more details on how to get hold of this info. Also
you need to write scripts handling the failover and fallback. Manual has
some examples on those.
Rgrds Mikael
Lionel Horn Wrote:
-------------------------------------------------------
> Is it possible to get data back from a redundant
> site to the primary site after a failover?
>
> Here is our proposed usage scenario:
>
> Site A – California
> Primary site. Contains cluster with two SQL nodes
> and two data nodes
>
> Site B – North Carolina
> Redundant site. Contains cluster with two SQL
> nodes and two data nodes
>
> We use a dynamic DNS company to automatically
> route traffic to redundant Site B if the primary
> Site A is not accessible.
>
> What typically happens is that our the T1 into
> Site A goes down and the DNS company routes
> traffic to Site B. Within 10 minutes (generally)
> the T1 is back up and DNS points back to Site A.
> During the failover, Site A is constant
> communication with Site B.
>
> My question is how do we get data from Site B into
> Site A after the failback? I could see how to do
> this via replication but I don’t know how this
> would (or could) be done in the cluster
> environment.
>
> Thanks
Mikael Ronstrom
Senior Software Architect, MySQL AB
My blog:
http://mikaelronstrom.blogspot.com