Brandon Bryant wrote:
>
> OK.. Then here is another question for you. How difficult is it to set
up
> replication for two SQL servers? I am reluctant to point both radius
Its not for the weak of heart or under powered machines. You should
have
atleast a 256mb, SCSI based, PII box for the replication source.
Well, that's what we have, but I want to make sure that it's going to do
what we want it to do. Does it work like mirrored drives, in that when you
change one, the other is updated in real time, and then if one goes down,
the other takes over?
> servers to the same SQL server. Right now, the primary radius and the
> primary SQL are the same machine, and the secondary radius and the
> secondary SQL are the same machine. If the Primary radius server goes
> down, chances are the db is down too. I guess we could have one db
server
> and point two other servers running radius to that one, and then have
even
> another machine running a backup DB, and then use the multiple DSN
feature
> on Radius to switch to the backup DB when there is a problem with the
If you have the hardware (RadiusNT takes very little CPU usage) then I
recommend NOT running RadiusNT on your SQL Servers. I don't recommend
running ANYTHING on your SQL Servers. Build them so that they wont
go down and you'll be in good shape.
You can't build a machine not to go down. Hardware fails. I don't care
how much you spent on it. Especially with a flaky OS like NT running on
it. (Die hard Solaris fan) And as complicated as multiple DSNs apparently
are, I am very interested in this feature.
> first. Does (will) RadiusNT have the multi-DSN feature? I know it has
> been discussed on the list before but I never really saw whether or not
> this feature will do what I want it to here.
This is quite a but more complicated than just connecting to a bunch of
listed DSNs. You should see this in the next major release, as we
are working on it actively.
> I'm trying to keep my point of failure as far back as possible. If the
> server goes down at 2AM, I don't want to have change anything to get
> service back up.
Some of the new RadiusNT 2.5.200 features will greatly help here, as
they
actively cache and can keep on going if SQL Server goes down.
--Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.comFor more information about this list, including removal,please see http://www.iea-software.com/maillist.html
For more information about this list, including removal,please see http://www.iea-software.com/maillist.html