First, we use SQL to backup to a file on a different drive...
Second, we have Seagate Backup Exec scheduled to backup the SQL server...
Backup Exec has a SQL module that will backup an active database.. no
sweat...
The problem is that during the time that either backup is running some files
and tables will be locked via the backup... otherwise you can't get a true
backup. Most of the locks only take a few seconds. During the time that
the files/tables are locked we still authenticate, but the callsonline is
not updated and probably not all the stop records make it to the database.
The SQL server this is running on is only using about 3% of the processors,
and memory usage is normal... The backup is actually running on another
machine through the network, so all the SQL server is doing is feeding it
out the ethernet port..
Radius is setup to fall back to text file in the event it doesn't see the
SQL server.. and this is only good procedure.
With the new, yet unreleased Radius 3.0 I understand that it will allow a
fallback to a secondary SQL server... at that point in time I will setup an
identical SQL server and have radius authenticat to it when it can't find
the primary....
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart