SEO

#1 (**permalink**) 02-28-2008, 04:59 PM

One possible approach is to use replication to keep the two databases in
sync. This has the advantage that if the Radius devices update something in
one DB (last login time for example), this change will automatically go to
other DB, so the data remains consistent.

There is plenty of information in BOL on replication, but it can be a
complex area, depending on your implementation needs. Perhaps you might want
to ask this question in microsoft.public.sqlserver.replication for more
specific feedback.

Simon

"Saeed" <tryagain@clickasun.net> wrote in message
news:25567287.0306270433.465d5be@posting.google.co m...
> Hello every body,
> I am going to define a plan for a online mirror and failover recovery
> in the db system we have. Let me describe more :
> Cosider some radius complaint devices which are sending their
> accounting packets to a Radius server which is running MS-SQL server
> 2000. If IP connectivity of this server and the device is lost, the
> devices try to send their packets to their secondary radius server.
> These 2 different primary and secondary IP addresses defined for
> devices are using different internet back bones and very far from each
> other (for example one is in US & next is in CA). In this way I can
> not use any windows clustering services.
> The question is that how can I have a online mirror of db located on
> IP address t.x.y.z on the computer with IP address of a.b.c.d ?
>
> Thank you all body in adnvance,

#2 (**permalink**) 02-28-2008, 04:59 PM

Thanks Simon for your guidance to
microsoft.public.sqlserver.replication. I will copy my question to
that also.
I am a beginner in DB fields, just as my final question in this group,
what would happen if the first server fails, some record updates are
done on the second server, and then the first server comes into live ?
Are the updated records replicated to the first server also ? I mean
is this replication one-way or two-way ?

Thanks

Saeed

"Simon Hayes" <sql@hayes.ch> wrote in message news:<3efda807$1_4@news.bluewin.ch>...
> One possible approach is to use replication to keep the two databases in
> sync. This has the advantage that if the Radius devices update something in
> one DB (last login time for example), this change will automatically go to
> other DB, so the data remains consistent.
>
> There is plenty of information in BOL on replication, but it can be a
> complex area, depending on your implementation needs. Perhaps you might want
> to ask this question in microsoft.public.sqlserver.replication for more
> specific feedback.
>
> Simon
>
> "Saeed" <tryagain@clickasun.net> wrote in message
> news:25567287.0306270433.465d5be@posting.google.co m...
> > Hello every body,
> > I am going to define a plan for a online mirror and failover recovery
> > in the db system we have. Let me describe more :
> > Cosider some radius complaint devices which are sending their
> > accounting packets to a Radius server which is running MS-SQL server
> > 2000. If IP connectivity of this server and the device is lost, the
> > devices try to send their packets to their secondary radius server.
> > These 2 different primary and secondary IP addresses defined for
> > devices are using different internet back bones and very far from each
> > other (for example one is in US & next is in CA). In this way I can
> > not use any windows clustering services.
> > The question is that how can I have a online mirror of db located on
> > IP address t.x.y.z on the computer with IP address of a.b.c.d ?
> >
> > Thank you all body in adnvance,

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: Having a online mirror on a different IP adress